Skip to main content

Next Insurance

AI Engineer- Agentic Customer Flow

Boston, MAFrom $220kmidAdded 1 month ago

About this role

ERGO NEXT is looking for an AI Engineer in Boston, MA, to enhance their small business insurance technology. The role primarily involves designing and scaling AI-driven backend systems while integrating ML and LLM models for high performance and reliability.

What you'll do

  • Design and optimize backend services for AI workflows
  • Integrate ML and LLM models into production systems
  • Build and manage AI features end to end
  • Monitor AI systems in production environments
  • Collaborate with cross-functional teams for technical planning
  • Contribute to system architecture and code quality

What they're looking for

  • 4+ years in backend engineering (Python, Go, Java)
  • Experience with ML and LLM model integration
  • Strong understanding of cloud infrastructure
  • Ability to diagnose complex data pipeline issues
  • Familiarity with performance metrics evaluation
  • Strong communication and collaboration skills
  • Experience with microservices
  • Ability to work in dynamic environments

Benefits

  • Hybrid work model (3 days in-office)
  • [Unknown]
  • [Unknown]
  • [Unknown]
  • [Unknown]
  • [Unknown]
Apply with Autofill

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.

View all jobs at Next Insurance

Likely interview questions

  • Walk us through a time you integrated an ML or LLM model into a production system. What challenges did you face with performance, reliability, or scalability, and how did you solve them?
  • Describe your experience building and maintaining backend microservices. What observability and monitoring practices did you implement?