Technical Product Owner, Partner Platform & Delivery Readiness

Fair

Fair

Product, IT
United States
USD 100k-160k / year + Equity
Posted on Mar 31, 2026

👉 Contract (1099) to hire

👉 Compensation: $100K to $160K base salary + 0.05% – 0.5% equity (No Visa Sponsorship)

👉 Location: Onsite strongly preferred in Phoenix, Arizona

Great products don't ship themselves.

Auto warranties have been a racket for decades. Fine print designed to deny. Coverage that disappears when you need it most. Customers left holding a $4,000 repair bill they thought was covered. We built Fair Warranty because that's wrong, and because we know exactly how to do it better.

We're a Series A company with a working platform, a set roadmap, and real customers who trust us. What we need now is someone who can take all of that and turn it into a steady, predictable flow of build-ready work that engineering can actually execute on. We're growing fast and expanding to Enterprise partners. The quality of what flows into engineering needs to match that ambition.

What you'll own

You sit between product direction and engineering execution. You work directly with the CEO on priorities, and day to day with the Platform Lead, Senior Backend, SDET, and Product Tech Lead to make sure work is sized, scoped, and ready to build before it hits the sprint.

Concretely, that means:

  • Owning backlog health. A prioritized, groomed backlog with a real Definition of Ready. Epics broken into 1 to 3 day slices. No mystery tickets, no half-baked requirements
  • Writing specs engineers trust. PRD-lite docs and tickets with testable acceptance criteria, explicit edge cases, named non-goals, and documented tradeoffs. If an engineer has to guess, the ticket isn't done
  • Driving partner platform requirements. You'll work with engineering to harden our partner-facing features. Idempotency, API versioning, webhook signing and replay, sandbox vs production separation, rate limiting. You don't need to build it. You need to understand it well enough to spec it
  • Writing AC that QA can automate. Scenario-based, measurable outcomes. Test plan notes and validation steps baked in before the ticket hits the board
  • Ruthlessly cutting scope. Outcomes over nice-to-haves. Front-load decisions so mid-sprint changes stop happening
  • Keeping delivery moving without running a meeting factory. Lead grooming, maintain sequencing, keep stakeholders aligned on status and risk

Our stack

Node.js + TypeScript (NestJS), REST (OpenAPI + codegen), GraphQL (code-first + codegen), MySQL, AWS (ECS, EventBridge, Lambda, S3, SQS/SNS, SES), Git, CI/CD.

What you bring (Must haves)

  • 3+ years as a Product Owner, Technical PM, or Technical BA supporting teams shipping real production systems
  • A proven ability to take ambiguous requests and produce clear goals, prioritized tickets, testable acceptance criteria, and named failure modes
  • Strong technical fluency with modern web platforms. APIs (REST/GraphQL), auth concepts, data modeling, integration patterns like webhooks and async events. You don't code it, but you speak it
  • Written communication that engineers respect. Tickets, specs, release notes, decision logs that actually get used
  • Comfortable working fast, working directly with a CEO, and making tradeoffs out loud

What stands out

  • Experience supporting a public B2B API or integrations-heavy product with Stripe-level expectations
  • Fintech, insurtech, or payments-adjacent background. Billing, refunds, chargebacks, reconciliation
  • Familiarity with OpenAPI/codegen and GraphQL schema workflows
  • SOC 2 experience. Controls, audit trails, change management
  • Partner-facing documentation, onboarding guides, support runbooks

What the first 90 days look like

The team has a steady flow of ready work with minimal churn and fewer blocked tickets. Epics are consistently broken into small, shippable slices with clear sequencing and ownership. Acceptance criteria is tight enough that QA automation gets planned early and regressions drop. Partner-facing features ship with better docs, cleaner release notes, and zero surprise breaking changes.

That's the job. If you're the person who makes engineering faster by doing the hard thinking upstream, we want to talk.