Careers

Build the tool you wish you had had.

A small team building the thing we wanted and could not find. If that sounds like a line, read the principles on the about page and decide for yourself.

How we work

The parts worth knowing up front.

Nothing exotic. It is written down so you can tell whether it suits you before you apply, rather than three weeks in.

Remote, written-first

Remote, with deliberate overlap hours rather than a fixed timezone. We write things down because the alternative is meetings.

Small surface, wide scope

Everyone ships. Designers work in the codebase, engineers argue about copy, and the person closest to the problem makes the call.

We are our own members

We use for our own goals. It is the fastest way to find out which parts are genuinely good and which parts we have been forgiving about.

Honest about the stage

Early access means some of it is rough. Comfort with shipping something imperfect, then fixing it in public, matters more here than polish in a portfolio.

Open roles

What we are hiring for.

Apply by email with something you have built and a paragraph on why this problem. A CV is welcome but it is not the part we read first.

Senior Product Engineer

Own features end to end across the web app, the Convex backend, and the iOS client.

Product · Remote

iOS Engineer

SwiftUI, offline check-ins, and making the daily loop feel native rather than wrapped.

Mobile · Remote

Product Designer

Interaction and visual design for the goal-update flow — the screen people will use most.

Design · Remote

Community Lead

Mentor onboarding, guideline enforcement, and keeping the public directory worth browsing.

Community · Remote

Nothing quite right?

Open applications.

If you can point at a part of and explain precisely what is wrong with it and how you would fix it, that is a better application than most of the ones we get against a job title. Send it.