What success looks like
- A runner pairs with one click and survives sleep, network loss and a killed process.
- Approvals and budgets are enforced in code, never by a prompt.
- A new agent CLI joins the fleet in days, not months.
What you will do
- Build and harden the local runner and its contract with the platform.
- Model process lifecycles: start, stream, pause, stop, resume and clean up.
- Write fake CLIs and fixtures so tests never touch a real vendor.
- Find the failure before a customer does, then add the guard.
About you
- You have built tooling that runs other people’s code safely.
- You are patient with edge cases: signals, files, ports, clocks.
- You write short, boring code that is easy to trust.
Nice to have
- macOS or Linux process internals
- Container and VM isolation
- Terminal and PTY work
A short note, please
With your resume, write a page or less on the work you are proudest of. Tell us what you chose to cut, and which of our values you would hold us to.