Plaid
Software Engineer, Backend
About this role
Join Plaid as a Backend Software Engineer to build scalable, reliable systems powering financial connectivity for millions of users. You'll design and maintain APIs that enable developers and consumers to securely access and move financial data across a network of 12,000+ institutions.
What you'll do
- Design and build scalable backend systems and APIs that power Plaid's financial products
- Collaborate with product managers, designers, and engineers to define and ship customer-focused features
- Write clean, well-tested code and participate in code reviews to maintain engineering standards
- Build automated tests, monitor system performance, and troubleshoot production issues
- Contribute to technical design discussions and share best practices across the team
- Take ownership of projects from definition through delivery and iteration
What they're looking for
- Backend system design and architecture
- API development and RESTful design principles
- Software testing and test automation
- Production debugging and performance monitoring
- Problem-solving and critical thinking
- Code quality and maintainability practices
- Cross-functional collaboration
- Scalable system development
Benefits
- Medical, dental, and vision coverage
- 401(k) retirement plan
- Equity and/or commission opportunities
- Work with products impacting millions of users
- Fast-paced, collaborative environment
- Opportunities for rapid career growth
Opens the application — the Jobs AI extension fills it for you. Set up autofill
Opens the official application on the employer’s site. No login required.
Plaid
Plaid builds infrastructure that connects users to their financial data and enables secure financial transactions through APIs and integrated experiences. The company is hiring Full Stack Software Engineers, Backend Engineers, Security Engineers, and Sales Engineers to develop and support its platform for millions of users.
- Website
- plaid.com
Likely interview questions
- Tell us about a scalable system or API you've built—what were the key design decisions and challenges?
- How do you approach debugging and troubleshooting issues in production environments?