Senior Product Manager

B-Stock•San Mateo, CA

25d•$160,000 - $170,000•Hybrid

About The Position

B-Stock is a managed B2B recommerce marketplace, and its two sides couldn't be more different: enterprise sellers moving returned and excess inventory at scale, and thousands of buyers hunting for value in it. You'll own one part of that machine end to end, whether that's seller operations, buyer experience, logistics, or core platform. When the business's biggest problem moves, you may move with it. The domain changes; the bar doesn't. We're hiring for how fast you build real fluency in something you've never seen and start making sound calls before the picture is complete. Somewhere in your 4+ years of product experience is clear evidence you've done exactly that. We work AI-natively. Engineering ships fast with agentic tooling (Claude Code and similar), and the Product team operates at the same speed: AI is already part of how you research, prototype, and write, with the judgment to know what to delegate and where your own thinking stays in the loop.

Requirements

A track record of stepping into unfamiliar domains and getting effective quickly.
Decisiveness under uncertainty. You chase down the signal that exists (research, tickets, behavior, conversations), then commit without the signal that doesn't, and stay honest about what would change your mind.
Data fluency. You define KPIs, run the analysis yourself, and are comfortable in analytics and experimentation tooling.
Technical fluency. You read API docs, reason about architecture tradeoffs, and hold your own with engineers.
AI-native habits. AI tooling is already part of how you research, prototype, and ship.
4+ years of product experience.

Nice To Haves

B2B marketplace, auction, or two-sided platform experience
Shipping AI/ML into customer-facing products
Operations or logistics product work
Time in scrappy 0-to-1 environments

Responsibilities

Own a domain of the marketplace end to end, from framing ambiguous, high-stakes problems to shipped, measured outcomes.
Frame problems sharply: separate what you know from what you're assuming, commit to the highest-leverage path, and be explicit about what would prove you wrong.
Write PRDs and acceptance criteria engineering can execute in one read.
Own the metric, not just the launch: define the KPI, ship, and stay on it until it moves.
Collaborate across the org: engineering, design, data, operations, account management, and whatever other teams the problem touches. This role cuts across departments, and you'll pull in the right people wherever the work leads.
Communicate outcome first, with tradeoffs and rationale legible without a second meeting.