Senior Engineer, Agent Runtime

The runtime is the part of rovecode that runs tool calls: the four policy layers, the process supervision, the session log with its hash chain, and the seam between the agent loop and the terminal. You would own it.

What you would do

• Design and ship the next policy layer — likely a capability model for MCP servers — with its limit written down beside it.
• Make the runtime's behaviour on Windows, macOS and Linux identical, and prove it in CI on all three.
• Keep the session log append-only and cheap: rewinds, checkpoints and exports are the shapes you would design.
• Review the work of the two other runtime engineers and be reviewed by them.

What we are looking for

• Years of TypeScript in anger, ideally on Bun or Node, and comfort reading the runtime's source when the docs run out.
• A record of shipping software that other engineers run on their machines — a CLI, a build tool, an agent.
• Care about the boundary between "what the model asked for" and "what the machine did", and opinions about it.
• Written English good enough that your design notes need no meeting.

What this is not

Not a research role: we do not train models. Not a platform role: the hosted service is a different team. It is the agent, on the machine, doing what it was told and nothing else.

Process

A short note and links, a conversation with the team, a take-home that takes an afternoon and is paid, a final conversation. Two weeks end to end, and a reply at every step.