Step 01
Send us the work
No CV-first applications. Send a system you have shipped and a paragraph on what broke. We read every one.
Careers · The bench
We don’t hire CVs. We hire operators.
Two hundred of us, across three studios, hold one bar. If you’ve shipped systems that earned the right to keep running — read on.
ScrollHow we hire, in six acts
Act I · The bar
We look for operators who have already done the work —
who can read a system, find the joint that breaks under load,
and ship the fix on the architects’ line.
Who disagree well. Who write code that other people can read on a Tuesday.
Who stay until the in-house team ships faster than us.
That is the bar. We hold it without exception.
Act II · How we work
Four commitments, held without exception.
- 01
You ship into the operator’s desk.
Engagements begin with a week of sitting next to the people who will use the thing. The first artefact is not a deck — it is a list of workarounds.
- 02
You answer the phone in eighteen months.
We measure ourselves on adoption six quarters past handover. If the in-house team has reverted to the old way, we did not ship — we delivered.
- 03
You write code other operators can read.
Tactics change every quarter; clarity does not. We optimise for the engineer who inherits the system, not the one who wrote it.
- 04
You disagree well, and on the record.
Strong opinions, weakly held, in writing. The architects’ line is a meritocracy of arguments — not seniority, not volume.
Act III · The path in
Three steps, no theatre.
Step 02
A working session
A two-hour conversation with two operators on the line. We bring an open problem from a live programme. You bring how you would think about it.
Step 03
A two-week embed
Paid. Inside a real engagement. You meet the team, the cadence, and the bar. If it is mutual, you are on the bench.
Act IV · Open seats
Six seats open, across four studios.
We hire only when there is a programme to hold. Don’t see your shape on the bench? Send us the work anyway — we keep an unsolicited list and call back when the brief lands.
- Engineering
Senior Platform Engineer
Backend & platform. You have shipped multi-tenant systems at scale and care more about the on-call rotation than the framework war.
Noida · Hybrid - Engineering
Senior Frontend Engineer
React, TypeScript, design systems. You can hold the line on accessibility and performance when product is pushing for one more surface.
Noida / Remote · India - Engineering
Solutions Architect
You have been the named throat to choke on a live programme. Comfortable in the executive room and the deploy log on the same Tuesday.
Noida · Hybrid - AI
Applied AI Engineer
You have shipped one model into production that was still being used six months later. You can talk drift, evals, and adoption — not benchmarks.
Noida · Hybrid - Design
Senior Product Designer
Systems-minded. You have led the surface design on enterprise products where the operator is the user — not the buyer.
Noida / Remote - Adoption
Adoption Lead
Programme operator. You enable in-house teams until they ship without us, then write the playbook so the next team does the same.
Delaware · United States
Sign-off
Send us the work, not a CV.
A system you’ve shipped. A paragraph on what broke. A sentence on what you would do differently. That is the shape of every application we read carefully.