You take responsibility for a hard technical boundary that spans teams, and you earn influence through judgement, evidence and the people you help grow rather than through position. A senior title elsewhere is useful context; what matters is a clear account of what you actually changed.
Open for applications. Starts at: Research program.
We are taking applications for this role now and building the pipeline for it. The stage above is when the work itself is expected to begin, which is something you deserve to know before you apply rather than after. It is context, not a gate.
Where
In the office together five days a week, in one of our garages, and remote-friendly around your family, arranged one person at a time. We hire across the United States 🇺🇸, India 🇮🇳 and the UAE 🇦🇪.
The work
Choose a consequential systems problem with the founder and CTO, build a reference solution and lead rigorous design reviews. Mentor senior engineers and improve architecture across the product. Keep the mandate narrow enough to produce visible progress.
The milestone
In your first 90 days, resolve one cross-stack problem and leave behind a working artifact, measurements and a team able to continue the work.
Required
Nice to have
Evidence
Bring exceptional technical depth and evidence of broad impact through shipped systems or research. A senior title elsewhere is useful context, not a substitute for a clear account of your contribution.
Evidence, not credentials. We are describing work you can point at, in whatever form it exists.
The exercise
Present an architectural disagreement you resolved and explain the evidence, decision and long-term consequences.
The package
Indicative pay ranges by market and level are on the compensation page. Plan numbers are confirmed in your offer letter.
Apply
One short form. A person reads every application and you hear back either way. You will get your own link to check where things stand, and you can withdraw or delete your application from it at any time, without an account.
