Earn a community by helping people build useful things. You will connect technical contribution, documentation and respectful collaboration.
Not open yet: Pilot expansion
This work starts when that stage arrives, so there is no application to submit today and we will not pretend otherwise. What is written below is what the role is for and what would make somebody right for it, published early on purpose so you can decide whether it is worth watching.
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.
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.