You earn a community by helping people build useful things, connecting technical contribution, documentation, and collaboration that treats contributors well. We support open models and open source as a matter of principle, so this role is about being a good participant, not about extraction.
Open for applications. Starts at: Pilot expansion.
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
Maintain examples, answer technical questions and contribute fixes upstream. Turn real developer friction into product changes. Work with engineering and research on publishable benchmarks, issue triage and extension quality, with clear boundaries around private user data.
The milestone
In your first 90 days, release a useful example, resolve a recurring integration problem and establish a sustainable contributor workflow.
Required
Nice to have
Evidence
Bring credible engineering work and clear communication. Evidence may include maintained projects, thoughtful reviews, teaching or documentation that helped others succeed.
Evidence, not credentials. We are describing work you can point at, in whatever form it exists.
The exercise
Teach an unfamiliar engineer how to debug an extension failure, then identify what the platform should improve.
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.
