About the role
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.
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.
What good looks like
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.
Evidence we look for
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.
What we need to see
- Exceptional technical depth with broad impact behind it, through shipped systems or research
- You can give a specific account of what you changed and how you know
- You work across team boundaries where you have no authority
- Evidence of engineers who grew because of you
Nice to have
- You have owned an architecture across multiple product generations
- Public technical writing or talks
- Both research and production engineering experience
The exercise
Present an architectural disagreement you resolved and explain the evidence, decision and long-term consequences.
Where and how we work
In the office together five days a week, in any of these cities. Remote-friendly around your family, arranged one person at a time.