About the role
You help other builders extend personal computing without having to understand every internal subsystem, which means making the safe path the easy one. If the secure way to do something is harder than the insecure way, developers will pick the second and be right to.
The work
Build SDKs, permission schemas, local development tools, examples and compatibility tests. Make capability boundaries explicit and error messages actionable. Support extension versioning, revocation and migration without exposing personal secrets to development tooling.
What good looks like
In your first 90 days, enable an outside developer to build and test one useful extension from documentation and examples.
Evidence we look for
Bring API design and software development experience with a strong interest in developer usability. Show how you reduced confusion, integration time or misuse.
What we need to see
- API design and software development with a real interest in developer usability
- You can show how you reduced confusion, integration time, or misuse
- You design so the safe path is the path of least resistance
- You write documentation as part of the work rather than after it
Nice to have
- You have maintained a public SDK
- Developer research or usability testing on an API
- Multi-language client libraries
The exercise
Design an extension API that asks for the minimum necessary data and remains compatible when permissions become more precise.
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.