About the role
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.
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.
What good looks like
In your first 90 days, release a useful example, resolve a recurring integration problem and establish a sustainable contributor workflow.
Evidence we look for
Bring credible engineering work and clear communication. Evidence may include maintained projects, thoughtful reviews, teaching or documentation that helped others succeed.
What we need to see
- Credible engineering work of your own that people can look at
- Clear communication in writing, which is most of open source
- Evidence you helped others succeed: maintained projects, thoughtful reviews, teaching, or documentation
- You engage respectfully with contributors, including ones who are wrong
Nice to have
- You have maintained a project with outside contributors
- Experience with open governance
- Conference or workshop organising
The exercise
Teach an unfamiliar engineer how to debug an extension failure, then identify what the platform should improve.
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.