About the role
What a person saves in an app stays on their phone; we never see it, by design. What our server does hold is everything around the apps: who signed in, which assistants are connected, every version of every app with the checks it passed, and a log of each tool call an assistant made (with the app's code replaced by its length).
From that, the product needs a few honest numbers: how many apps a person makes, how often an assistant's first try passes the checks, how often an update is rolled back, and whether people come back after two weeks.
What you'd do
- Define the product's core measures with the product team, and build them from our own tables
- Keep reporting inside what the privacy page promises: what's kept, for how long, and who can see it
- Make the numbers reproducible: one query per measure, checked into the repo, with a test
- Spot what the numbers can't tell us, and say so
What we need
- Three or more years building data pipelines or analytics on production data
- Strong SQL on Postgres
- You've worked under privacy limits and can describe a measure you chose not to build
Nice to have, not required
- Privacy-preserving analytics: aggregation, retention limits, data minimisation
- TypeScript, to work in the same codebase as the server
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.
