About the role
People ask their assistants for small, personal apps: habit trackers, budgets, checklists, timers. The platform's job is to make those apps safe to install, easy to change by asking, and dependable on a phone.
What comes next is yours to shape and to order: backup with a key we never hold, sync between a person's devices, sharing an app with family, reminders (all planned), and what the assistant is told about writing an app that works here.
What you'd do
- Talk to people using it, and find the apps they want that don't work well yet
- Decide what to build next, and in what order, and say why
- Write what a feature must do in a form engineering can test
- Keep the website, the listings and the roadmap honest about what's built
What we need
- Four or more years in product, on something with real users
- You've shipped a consumer product or a developer platform
- You can read a spec and a test and tell whether they say the same thing
Nice to have, not required
- You've worked on a product built on top of AI assistants
- Privacy-first products, where what you don't collect is a feature
How we work
- Small team, thin slices, shipped weekly. Nothing sits on a branch for a month.
- Reviews are real. Every feature ships with its tests, and a bug found in review is cheaper than one found by someone using it.
- Private by default. A person's app data stays on their phone, and nothing we build may need to read it.
- We only claim what ships. That applies to the product, the roadmap and the offer letter.
How hiring works
- 1A 30-minute call about something you've built and what was hard about it.
- 2A working session on a real problem from this codebase. You can drive, or we can pair.
- 3A conversation about how you make decisions when the evidence is thin.
- 4References, then an offer. We aim to answer within a week at every stage.
