ROLE — ENGINEERING · REF ENG-114
Senior Engineer,
Agent Runtime
The runtime is where proof meets reality: it schedules agent runs, holds their state for hours, checks every tool call twice, and writes the record everything else depends on. You will own pieces of it end to end — design, code, the run-book, and the 3 a.m. page when it comes.
Responsibilities
- Build and run the scheduler that keeps long agent runs alive, resumable and exactly replayable.
- Own the tool-call gate: the checks before a call runs and after it returns, with failure modes a reviewer can read.
- Keep the audit writer honest — append-only, hashed, and fast enough to never be the bottleneck anyone routes around.
- Review more than you write. The runtime is small because its reviewers are stubborn.
What we ask
- Five or more years building systems that other people's work depends on — queues, schedulers, storage, or runtimes.
- Fluency in Go or Rust, and the judgement to know when the boring tool is the right one.
- A written sample we can argue with: a design doc, a post-mortem, a proof — yours, in your words.
- Comfort with being checked. Everything here is reviewed; the runtime most of all.
We do not ask for a degree, a pedigree, or experience with this exact stack. We ask for evidence of care, and we read it.
PROCESS — FOUR STEPS, ALL HUMAN
STEP 01
Apply in writing
The form below. We reply within five working days, either way.
STEP 02
A working conversation
Ninety minutes with two engineers on a real runtime problem — ours, not a puzzle.
STEP 03
A paid bench day
One day at the lab, paid at the band rate, working the way the team works.
STEP 04
Offer, in writing
Band, terms and start date on one page. No surprises after it.
APPLY — REF ENG-114