Next Insurance
Backend Engineer - DevEx Team
Boston, MAFrom $220kmidAdded 1 month ago
About this role
ERGO NEXT is seeking a Backend Engineer for its DevEx team in Waltham, MA. The role involves leading Platform Engineering efforts by enhancing developer experiences and implementing an AI-driven Software Development Life Cycle.
What you'll do
- Lead the development of an AI-based Software Development Life Cycle.
- Serve as a technical liaison between global and US teams.
- Architect and manage cloud infrastructure as a product.
- Address complex challenges using diverse technologies and cloud services.
- Enhance developer workflows by identifying and resolving friction points.
- Collaborate with business units to ensure engineering excellence.
What they're looking for
- 6+ years as a Software Developer
- Experience with Java, Kotlin, JS, TS, bash, or Python
- Knowledge of CI/CD methodologies
- Familiarity with Kubernetes & Containers
- Understanding of Cloud/Infrastructure-As-Code
- Strong problem-solving and communication skills
- Self-driven with a curiosity for AI technologies
- Experience with observability tools
Benefits
- Hybrid work environment
- Opportunity to shape the future of software development
- Collaborative team culture
- Access to cutting-edge technologies
- Professional growth opportunities
- [Unknown]
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.
Next Insurance
Next Insurance builds technology-driven insurance solutions for small businesses, combining web applications with AI-powered backend systems. The company is hiring Front End Engineers, Backend Engineers, DevEx/Platform Engineers, and AI Engineers to develop and scale their product.
- Website
- nextinsurance.com
Likely interview questions
- Tell us about a time you led a meaningful infrastructure or platform project from conception to implementation. What was your role and what impact did it have on developer productivity?
- How have you approached improving developer experience in previous roles? Can you give a specific example of friction you identified and how you resolved it?