Senior/Staff Software Engineer

What you’ll build
We’re serving an orchestrated system of agents answering millions of contacts daily and now also expanding into other modalities like chat. Pulling that off requires elite engineering paired with incredible DevOps — voice is unforgiving: it’s real-time, there are no retries or page refreshes, and the customer is literally on the line.

The work breaks into three lanes:

Vertical engineering — building the agents themselves: complex multi-step customer workflows and deep integrations into the contact center and the industries we serve — order systems, healthcare workflows, logistics. This is where “mostly works” isn’t shippable.
Platform engineering — the orchestration layer every agent runs on: routing, state, tool use, and the primitives that let vertical teams ship fast without reinventing the engine.
Inference & DevOps — we host our own models; low-latency serving at production scale is a core competency here, not a vendor line item. Plus the telephony, observability, and deployment infrastructure that keeps millions of live calls healthy.

What we look for
We intentionally wrote this as one role for senior and staff engineers, because we believe builders love to build — and how they build varies. Some want the flexibility of working alone and joining forces when it counts; some do their best work in a small pod. We don’t prescribe it. What we do hold as a core principle: we are always raising the bar on each other. As we grow, our best builders often end up with two or three engineers building behind them — if that’s a direction you want, it’s here. And if you’d rather stay a pure builder, that raises the bar too.

- Real production experience. You’ve built and owned systems where failure had consequences. We don’t count years — we look at what you’ve shipped and what you learned shipping it.
Judgment that survives contact with production. Agentic development is how we work — but what we’re actually hiring is your experience: knowing what to ship, what to slow down on, and what never to ship at all.
Low ego, high execution. You own outcomes, not tickets. You’d rather ship the thing than present the plan for the thing.
Customer obsession. You want to be close to the problem — sometimes literally in the room — and you measure yourself by what the customer got.