About the role
You choose which problems are worth solving first, and turn a broad mission into a product people can understand, use and afford. Affordability is part of the product brief rather than a pricing decision made later, because the commitment is that this is free to the person.
The work
Spend time with users in real workflows and define outcomes before features. Coordinate software, device, service and partner decisions. Measure successful task completion, repeat use, user control and support burden, and keep the roadmap grounded in evidence.
What good looks like
In your first 90 days, deliver a prioritized pilot problem, acceptance criteria and a tested account of why users would pay for the solution.
Evidence we look for
Bring product judgment and evidence of taking a complex idea into daily use. Deep technical fluency and careful listening matter more than presentation polish.
What we need to see
- Product judgement with evidence: you took a complex idea into daily use by real people
- Deep technical fluency, enough to be useful in an architecture discussion
- You listen carefully, and can show a decision that changed because of what you heard
- You can decide what not to build and hold that line
Nice to have
- Hardware and software together
- You have worked on something with a strong ethical constraint
- Experience taking a product from nothing to its first real users
The exercise
Choose between two attractive use cases with different security, integration and customer-support costs.
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.