Product Owner

iSpeedToLead

11h•Remote

About The Position

Turning marketing into a market-domination weapon, we created a new category - the marketplace for future customers. Businesses shop for leads as they shop for products in e-commerce: you see everything about a lead before you buy - full transparency, control, and predictable outcomes. We're the #1 lead marketplace in the USA, and we're accelerating. We are looking for a Product Owner to ensure that the most valuable product decisions are executed efficiently, shipped quickly, and delivered in the right order. You will own the "how and when" of the product, turning direction into reality while maintaining speed, clarity, and high delivery quality. You will work in close partnership with a Product Manager, who owns direction ("what and why"), while you own delivery flow, backlog quality, and release readiness.

Requirements

2+ years as a Product Owner making real scope decisions, on a team of 8+ engineers.
You optimize for value shipped, not tickets closed, and can explain calls where you shipped less to deliver more.
You can reason about cost of delay and effort vs value out loud, not just in story points.
You read API contracts and talk about service boundaries without a translator; Node.js / microservices is a plus.
Your specs are praised by engineers; we will ask to see real tickets you wrote.
English B1/B2+.
AI-first by default — if you are not already using AI to 3x your output, you will be behind our engineers.

Responsibilities

Take product briefs and decompose them into shippable increments. A 3-week ticket is a planning failure, and it is yours.
Own the backlog end-to-end: acceptance criteria, edge cases, definition of done, all in place before an engineer touches anything.
Weigh every increment against its cost: engineering effort vs expected value and cost of delay. Cheap and high-value ships first; expensive and speculative waits.
Prioritize with a visible score, not a feeling. Anyone can challenge it; you defend it with numbers.
Own communication outward: founders, sales, support, and the PM always know what's shipping, what's next, and what changed, without anyone interrupting the team to ask.
Keep the team unblocked and own the delivery numbers (cycle time, predictability, carryover, QA flow) as tools to spot problems early. Hygiene, not the mission.
Push back on the PM when a brief is not buildable. That friction is the system working.