You design how a person sets an intention, grants permission, and sees what happened. Making powerful computing feel calm rather than impressive is the whole brief, and permission interfaces are where most products quietly give up and produce a dialog nobody reads.
Open for applications. Starts at: First team.
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
Create onboarding, task review, consent, status, correction and recovery experiences. Work directly with engineers and users on realistic prototypes. Design for accessibility and make uncertainty, background activity and sharing boundaries visible without overwhelming the user.
The milestone
In your first 90 days, deliver and test a complete interaction from device setup through task completion and permission withdrawal.
Required
Nice to have
Evidence
Bring a portfolio showing interaction judgment and careful execution. Explain the user evidence, constraints and tradeoffs behind the work, including how the design changed.
Evidence, not credentials. We are describing work you can point at, in whatever form it exists.
The exercise
Redesign an approval flow where people cannot tell which files will be shared or what the agent is about to do.
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.
