Product Engineer

A Product Engineer at Tipstat owns a product surface end-to-end figuring out what to build, shipping it, watching how it performs in the real world, and iterating until it's actually loved.

There is no PM translating tickets for you. There is no senior engineer assigning you JIRA stories. You decide what's worth building, you build it, and you're accountable for whether users actually use it.

The leverage that makes this role possible is AI. We expect you to operate as a one-person product team by orchestrating coding agents Claude Code, Codex, OpenCode, and whatever comes next to compress what used to take a team of five into something one engineer can ship in a week. If you've been doing this on side projects already, you know exactly what we mean.

What you'll actually do

• Own a product area end-to-end discovery, design, implementation, deployment, and iteration
• Run multiple coding agents in parallel as part of your normal workflow, not as an experiment
• Talk to users directly on calls, in support threads, over WhatsApp and let those conversations shape what you build
• Make calls about what not to build, and defend them
• Ship to production frequently. Weekly at minimum, often daily.
• Build the patterns, evals, and abstractions that let agents do more of your work and the team's work over time
  

What we're looking for

We don't care about years of experience or where you went to school. We care about what you've shipped and how you think.

You're probably a fit if:

• You've built and shipped real products mostly solo, ideally with AI agents doing a meaningful share of the implementation. We want to see them live URLs, GitHub, screenshots, whatever you've got.
• You can describe your agent workflow in detail. How do you decompose problems? When do you let an agent run vs. intervene? How do you run 3+ agents in parallel without the output turning to mush? How do you verify what they produce? If this question is hard to answer, the role isn't for you yet.
• You'd rather talk to a user than read a spec. You have opinions about products. You notice when interfaces are bad. You can articulate why.
• You move fast and ship. A working prototype on Friday beats a perfect plan on Monday.
• You have strong taste about code, about UX, about what's worth doing. Taste is the thing agents can't replace, and it's what we're really hiring for.

You're probably not a fit if you want clear specs, predictable scope, a manager assigning you work, or a clean separation between "engineering" and "product."