Forward-deployed engineer

The work

• Sit with deal teams at client firms and map the workflow you're about to remove the legwork from. You'll present the map before you build anything.
• Build agents from the platform's parts: Memory, Context, Universes, Workflows, Review. When a part is missing, you write the spec for it.
• Ship working output inside the first week of a build and put it in front of the people who'll judge it.
• Own the quality gates: what carries sources, what gets held back, who signs off. Low confidence is a feature, and you'll defend it in the room.
• Bring what each client teaches you back into the firm: playbooks, evals, sharper defaults.

You, probably

• Several years shipping production systems, the recent ones with LLMs in the loop and users who didn't forgive.
• Fluent in Python or TypeScript, and comfortable owning both ends of an integration you didn't choose.
• Able to hold a room of investors: explain a trade-off plainly, take a hard question without flinching, change your mind in public when you're wrong.
• You've worked near finance, or you're the kind of person who reads the footnotes anyway.
• You'd rather ship the unglamorous correct thing than the impressive demo. This is most of the job.

Pay and terms

• £95,000 to £130,000 depending on what you've shipped, plus meaningful equity.
• London. Hybrid, honestly weighted; you're with clients when the work needs it and with us the rest of the week.

One limit, volunteered

Forward-deployed means client offices, client calendars and occasionally client moods. It's the best way we know to build things that get used; it is not always tidy. Ask about the untidy parts on the call and you'll get examples, not a brochure.