Product Manager
Tipstat®
Job Description
This is not a traditional PM role. We don‘t need more user stories, PRDs, or Jira tickets. We need someone who opens draft PRs with working prototypes, files issues with failing eval cases, and settles design debates by shipping a branch — and who can turn that craft into a business.
You will be the third voice in the room alongside engineering and design, and the person who owns whether the product actually feels good to use. If the agent gives a bad answer on a Tuesday, you‘ll find the upstream cause — in the prompt, the tool schema, the retrieval layer, or the UX — and open a PR by Wednesday.
You will also own the unglamorous half of product: instrumenting what matters, watching the funnel, noticing which accounts are about to churn, and figuring out why the self-serve signup from Tuesday converted and the one from Wednesday didn‘t,
What you‘ll actually do
Build the product
- Ship v0 of new agent capabilities behind feature flags so engineers can harden them into production.
- Write evals before we build the capability, and keep the eval set honest as the product evolves.
- Debug customer-reported agent failures directly in the repo — traces, prompts, tool calls, the whole stack.
- Own the changelog, the public roadmap, and the quality bar.
Scale it
- Design the product for the tenth customer, the hundredth, and the thousandth — not just the one on the call today.
- Instrument the funnel end to end: signup → activation → habit → expansion → referral. Know the numbers cold.
- Run experiments weekly on onboarding, activation, and time-to-first-value. Kill what doesn‘t work.
- Build the feedback loops (in-product, support, sales) that let product quality compound instead of decay.
Drive growth and GTM
- Co-own the go-to-market motion with the founders: positioning, pricing, packaging, ICP, and where to play.
- Run 5+ customer calls a week — across prospects, new users, and power users — and close the loop by the end of the same week, often with a prototype in the reply.
- Prototype pricing pages, onboarding flows, and admin consoles on weekends when you care enough.
- Partner with sales and marketing on the story, the demo, the collateral, and the objections — and make sure the product backs up every claim.
- Decide the PLG vs. sales-led balance for each product and each segment, and revisit it as we learn.
- Turn the changelog into a growth channel. Turn every customer win into a case study. Turn every loss into a lesson.
What we‘re looking for
- A builder‘s portfolio. GitHub, Replit, Vercel, a domain you bought at 2am — show us the last three things you shipped solo. For this role, we care more about what you‘ve built than where you‘ve worked.
- Fluency with the AI stack. You‘ve wired up function calling, fought with retrieval, written evals, and have opinions about when to use an agent vs. a well-placed regex. You use Claude Code / Cursor daily and it shows.
- Real product taste. You can look at a flow and tell us what‘s wrong with it in 30 seconds, and you‘re right more often than not. You can critique a product you love and a product you hate with equal precision.
- A growth brain. You think in funnels, cohorts, and retention curves, not in feature lists. You‘ve instrumented a product, run experiments, and made activation or retention numbers move. You can tell the difference between a vanity metric and a real one.
- Commercial instinct. You understand pricing, packaging, and positioning as product decisions, not marketing afterthoughts. You‘ve sat on enough sales calls to know what loses deals and what closes them.
- B2B instinct. You understand why enterprise procurement is different from PLG, how to design for admin/user/auditor personas, and why ‘just add a setting‘ is usually the wrong answer.
- Range. You can run a customer call, a design review, a pricing debate, and pair with an engineer on a retry loop in the same afternoon without losing momentum.
- Strong writing. Not PM-speak — the kind of writing that makes complicated things feel obvious. The kind customers forward internally.