Product Manager

About the role

You'll own a significant area of the product — discovery, roadmap, and outcomes. That means talking to warehouse operators and distributors constantly (10+ calls a month, run by you, not delegated), understanding how their workflows actually run, and translating that into a prioritized plan the engineering team can build from. We're small enough that you'll write specs engineers can implement without a follow-up meeting, be in sprint reviews saying "this isn't ready," and own the public roadmap promise on the website. No ivory-tower product work here: you're close to the code, close to the customer, and responsible for whether what you ship actually changes anything.

What you'll do

• Own your product area: set the strategy, write the roadmap with 'why now' justification for each item, and measure whether what shipped actually landed
• Run 10+ customer and prospect calls per month yourself — not for show, but to gut-check prioritization decisions with real data from real users
• Write specs engineers can implement without guessing: acceptance criteria, edge cases, wireframes, and an explicit out-of-scope section
• Define success metrics for every major feature before it ships; report back to the team on whether it moved the needle and what you'd do differently
• Manage competing priority requests from sales, CS, and leadership — say no clearly and explain why, without being apologetic about prioritization tradeoffs
• Keep the public roadmap honest: make promises you intend to keep, explain delays when they happen, and never let it go more than a month stale
• Partner with engineering to ship features and then go validate they work the way you intended — close the loop yourself, don't hand it off to CS

What we're looking for

• 3+ years in product management for a software product with real, paying customers — not internal tools or pre-revenue projects
• A bias for talking to users and making decisions with direct evidence — you run your own discovery calls, not just surveys
• Clear, concise writer: you can write a spec that an engineer can implement without a follow-up meeting, including edge cases and out-of-scope clarifications
• Can hold the business goal and the technical detail in your head at once — enough depth to reason about data model tradeoffs without needing it explained

Nice to have

• Experience with B2B, SMB, or operations / ERP / inventory software
• Technical background or depth to read a schema and reason about migration or performance tradeoffs
• Experience running a public, customer-facing roadmap and managing the expectations that creates