Skip to main content

Hatch

Integration Engineer

United StatesfulltimemidAdded today

About this role

Join Hatch as a Forward Deployed Integration Engineer, embedding with strategic clients to build production-grade code that connects Hatch's Voice AI platform to customer systems. You'll own complex integrations end-to-end, translate client needs into core product improvements, and ship code with genuine autonomy and impact.

What you'll do

  • Partner with sales to scope and deliver complex integration projects for strategic clients
  • Build and ship production-quality code for integrations, connectors, and automation tooling
  • Own technically complex onboardings end-to-end, including CRM integrations and multi-system orchestrations
  • Conduct QA, testing, and post-launch monitoring to ensure successful implementations
  • Serve as technical consultant for clients, including onsite visits and architectural guidance
  • Identify patterns from implementations and collaborate with Product to influence core product development

What they're looking for

  • Python and/or Elixir programming
  • Voice AI systems architecture and development
  • API integration and webhook design
  • CRM and business systems integration
  • Developer documentation navigation and technical problem-solving
  • Client communication and stakeholder management
  • Go programming (in scope)
  • Automation tooling experience (n8n or similar)
Apply on the employer's site

Opens the official application on the employer’s site. No login required.

Hatch

Hatch builds integration and workflow automation solutions that help enterprise clients connect their systems through custom API implementations and middleware. The company is hiring forward-deployed engineers who implement complex integrations, own technical onboardings, and serve as the technical bridge between customers and the product team.

View all jobs at Hatch

Likely interview questions

  • Walk us through a complex integration you've built—what made it challenging and how did you approach it?
  • How do you decide when an implementation problem should be solved in middleware versus core product code?