Build software that runs other people's production
It is a demanding constraint and the reason the work is interesting. Every design decision has to hold up when it is executing against twenty thousand instances at two in the morning.
What to expect
Small teams, wide ownership
Teams of four to seven own a capability end to end, including its reliability, its documentation and its on-call rotation.
Remote by construction
Written-first communication, recorded decisions, and meeting-light weeks. Four hub offices exist for people who prefer them, not as a requirement.
Real production stakes
Every engineer spends time with customer platform teams. It is difficult to design a safe abstraction for work you have never watched someone do.
Where we are hiring
- Apply
Staff Engineer, Workflow Execution
- Apply
Senior Engineer, Database Automation
- Apply
Applied AI Engineer, Root Cause
- Apply
Security Engineer, Product Security
- Apply
Solutions Architect, Financial Services
- Apply
Senior Technical Writer
- Apply
Site Reliability Engineer
- Apply
Product Designer, Console
- Apply
Engineering Manager, Compliance
Four conversations, two weeks
An introductory call, a technical conversation about work you have actually done, a practical exercise scoped to three hours, and a session with the team you would join. We pay for the exercise.
Tell us what you would want to work on
We open roles when we meet people worth opening them for. If none of the listings fit but the problem interests you, write to us.