01Careers
We hire the engineers who can sit in front of a Head of Risk on Tuesday and ship the change on Thursday.
A forward deployed engineer sits in front of a Head of Risk on Tuesday and ships the change on Thursday. That requires two things most engineering roles separate: the technical depth to build the system, and the composure to be questioned about it by someone who is accountable for the outcome. We hire for both. The failure mode we screen hardest against is the engineer who is brilliant in a repository and silent in a room.
02The archetype
Four things we screen for, in this order.
You ship inside constraints you did not choose
The change board meets fortnightly. The core is frozen. The data you need is in a system that predates you. This is the job, not an obstacle to the job.
You can be wrong in front of a client
Being corrected by a domain expert and adjusting in the same meeting is a skill. Defending a bad design because you proposed it is disqualifying.
You treat evaluation as engineering
You write the harness before you tune the prompt. You know the difference between a benchmark result and evidence that a system works on this institution's cases.
You read the regulation
Not to become a lawyer. To know which control the design has to satisfy before you pick an architecture that cannot satisfy it.
03Open roles
Every role below writes code.
Including the lead ones. An engineer who has stopped shipping cannot hold technical authority in a client’s room, and we do not pretend otherwise.
Lead Forward Deployed Engineer
- Delivery
- Full-time
New York · London
Own a pod inside a client institution. You are the technical authority in the room and the person accountable for what ships.
What you do
- Run a three to five person pod embedded in a client's engineering estate
- Set the control boundary with the client's risk and security functions before build starts
- Write code every week; this is not an oversight role
- Carry the weekly ship commitment and the incident pager that comes with it
What we look for
- Eight or more years building production systems, some of it in or against regulated infrastructure
- Direct experience deploying software inside an organisation that was not your employer
- Fluency in a conversation with a Head of Risk without an account manager translating
Agent Platform Engineer
- Platform
- Full-time
Bengaluru · London · Remote (UTC-1 to UTC+6)
Build the orchestration, isolation and audit layer that every engagement deploys onto.
What you do
- Own the execution substrate: task graphs, tool typing, isolation cells, replay
- Make the audit record complete enough that an auditor never has to ask us for context
- Keep the provider interface genuinely model agnostic as the frontier moves
- Drive the latency and cost budget down without loosening a single control
What we look for
- Distributed systems depth: queues, idempotency, failure semantics under partial outage
- Scepticism toward agent frameworks and a clear view of when explicit state machines win
- Security instincts on credential scoping, egress control and untrusted input
Evaluation Engineer
- Platform
- Full-time
London · Bengaluru
Decide whether a system is allowed to reach production, and build the machinery that decides it.
What you do
- Turn a client's adjudicated case history into an evaluation suite that means something
- Build adversarial and prompt-injection corpora per engagement
- Own the release gate: a regression blocks the deploy, including when it is inconvenient
- Monitor drift against the week-one baseline and raise it early
What we look for
- Experimental rigour: you know why a held-out set matters and how leakage happens
- Comfort disagreeing with delivery pressure while holding a working relationship
- Statistics that are actually applied, not recited
Domain Engineer, Financial Crime
- Delivery
- Full-time
London · Singapore
The person on the pod who knows what a SAR narrative has to contain and why the typology matters.
What you do
- Translate AML and fraud operating reality into system design an engineer can build
- Sit with the alert queue before proposing anything that changes it
- Own the relationship with the MLRO through design, build and review
What we look for
- Operational financial crime experience, ideally on the receiving end of the queue
- Enough technical fluency to read the code and argue with the design
General application
- Any
- Full-time
Any delivery hub
If the archetype describes you and no listed role fits, write to us anyway. Tell us about a system you shipped inside someone else's constraints.
How we interview
Three conversations, one of them with a client-facing scenario, and no take-home longer than two hours.
The scenario is real: a constraint you cannot change, a stakeholder who is accountable, and a design decision to defend. We are not testing whether you get it right. We are watching how you handle being told you are wrong.