Best Egg
Software Engineer II
About this role
Best Egg, a fintech platform specializing in installment lending and financial wellness tools, is hiring a Software Engineer II to help build scalable solutions that empower customers to make confident financial decisions. You'll work in a collaborative, values-driven culture while the company prepares for its acquisition by Barclays in Q2 2026.
What you'll do
- Design and develop robust backend and/or frontend services for lending and financial products
- Collaborate with cross-functional teams to translate customer needs into technical solutions
- Participate in code reviews and maintain high code quality standards
- Troubleshoot, debug, and optimize existing systems for performance and reliability
- Contribute to architecture decisions and technical documentation
- Support deployment and monitoring of production systems
What they're looking for
- Backend software development (Java, Python, Node.js, or similar)
- RESTful API design and development
- Database design and SQL
- Problem-solving and debugging
- Version control (Git)
- Agile development practices
- System design and scalability concepts
- Communication and teamwork
Benefits
- Competitive salary and equity opportunities
- Comprehensive health, dental, and vision coverage
- Flexible work environment and work-life balance
- Professional development and career growth
- Inclusive, diverse workplace culture
- Access to Barclays resources and global opportunities post-acquisition
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.
Best Egg
Best Egg is a Barclays fintech company that builds financial products with a focus on secure cloud infrastructure and application delivery. The company is hiring senior security and DevSecOps engineers to lead security initiatives, drive risk reduction, and shape technical direction across its platforms.
- Website
- bestegg.com
Likely interview questions
- Walk us through a recent project where you designed a system to handle high transaction volume—what trade-offs did you make?
- How do you approach debugging a complex production issue affecting customer transactions?