Product Manager

About this role

<p><strong>About Us</strong></p> <p>Scotch is building the next-generation operating system for beverage alcohol retailers — combining POS, payments, back office, and e-commerce into a platform purpose-built for liquor stores.</p> <p>We’re modernizing one of the oldest industries in the world: the $1.6T beverage alcohol market. Our platform helps retailers run more efficiently through streamlined payments, inventory management, reporting, and day-to-day operations.</p> <p>Our founders came from Skupos (acquired 2023) and Drizly (acquired by Uber). We've raised $28M from VMG Partners, First Round, Lerer Hippeau, Watchfire, and Toba Capital, with angels including the founder of Drizly and early Toast executives. Forbes has recognized Scotch as a leader in liquor retail tech. We closed a $20M Series A in 2026 off 500%+ YoY growth and $1B+ in processed payment volume.</p> <p><strong>Position Overview</strong></p> <p>We're looking for a Product Manager to own a meaningful surface of our retail and payments platform. You'll start with our integration work — the connections between our back office and the third-party systems our merchants depend on to run their businesses — and we expect your scope to move as the business does.</p> <p>This is a hands-on role with real autonomy. You'll own a surface end-to-end: talking directly to merchants, defining what we build, and working with engineering to ship it. You'll be the person who understands how a surface actually behaves in the wild, and the person our customer-facing teams come to when something doesn't add up.</p> <p>We're a small product org. That means you'll make calls without a committee, and you'll be accountable for the ones that turn out wrong. It also means the shape of your role in a year is genuinely open — we're looking for someone who finds that appealing rather than unsettling.</p> <p><strong>What You'll Own:&nbsp;</strong></p> <ul> <li>The integrations roadmap — existing partner integrations and the ones we haven't built yet, from partner evaluation through launch and ongoing health</li> <li>Requirements gathering directly from merchants: what they need, what they actually do, and the frequent gap between the two</li> <li>Working across engineering teams to coordinate work that spans multiple surfaces</li> <li>Serving as the product point of contact for support, onboarding, and go-to-market when integration questions escalate</li> <li>Payments workstreams as they intersect with the integrations surface — tender handling, reconciliation, and processor behavior</li> </ul> <p><strong>Key Responsibilities&nbsp;</strong></p> <ul class="[li_&amp;]:mb-0 [li_&amp;]:mt-1 [li_&amp;]:gap-1 [&amp;:not(:last-child)_ul]:pb-1 [&amp;:not(:last-child)_ol]:pb-1 list-disc flex flex-col gap-1 pl-8 mb-3"> <li>Translate messy, conflicting merchant input into a clear direction, and hold that direction when the inputs keep changing</li> <li>Write requirements that describe the problem and the outcome, not the implementation</li> <li>Prioritize across competing partner commitments, merchant escalations, and platform work — and explain the tradeoffs to people who won't all agree with you</li> <li>Partner closely with engineering on scoping and sequencing, including the parts where the right answer is "not yet"</li> <li>Monitor how shipped integrations actually perform, and act on what you find rather than waiting to be asked</li> <li>Keep engineering teams pointed in a coherent direction when the work spans more than one of them</li> </ul> <p><strong>Qualifications &amp; Skills</strong></p> <ul> <li>3–6 years of experience in product, with demonstrated ownership weighted more heavily than years</li> <li>Having been the sole person accountable for a decision at some point, with nobody reviewing your work before it shipped</li> <li>Maintaining a real habit of customer contact, having sat with users, watched them work, and changed your mind about something as a result</li> <li>Showing judgment you can articulate, including a call you got wrong that you noticed yourself before anyone told you</li> <li>Holding multiple workstreams at once and making tradeoffs between them, not just executing one thing deeply while someone else set priorities</li> <li>Communicating with real range, from writing a spec an engineer can build from to explaining that same decision to a merchant, a support lead, and an executive</li> <li>Bringing, ideally, some depth in integrations, having owned third-party integrations as a product surface, including the partner relationship, failure modes, support burden, and customer-facing consequences when something breaks upstream</li> </ul> <p><strong>Nice to Haves</strong></p> <ul> <li>Payments experience — processors, tender types, reconciliation, or dual pricing</li> <li>Retail or point-of-sale background, particularly with independent or small-format merchants</li> <li>Working familiarity with mobile app development (you don't need to be a mobile PM)</li> <li>Comfort with SQL or a BI tool — enough to answer your own questions without waiting on someone else</li> <li>Fluency with AI tools in your daily workflow</li> </ul> <p><strong>Why Scotch?</strong></p> <ul class="[li_&amp;]:mb-0 [li_&amp;]:mt-1 [li_&amp;]:gap-1 [&amp;:not(:last-child)_ul]:pb-1 [&amp;:not(:last-child)_ol]:pb-1 list-disc flex flex-col gap-1 pl-8 mb-3"> <li>Real ownership, fast: as an early product hire, you'll see your decisions become shipped features in weeks, not quarters, with a direct line of sight to customer impact</li> <li>You'll be tackling an underserved problem: modernizing retail and payments software for industries — like alcohol and wholesale distribution — that legacy platforms have largely ignored</li> <li>A small, high-caliber team means your voice shapes the roadmap directly, without layers of process between you and the decision</li> <li>Broad exposure across the stack: retail operations, payments, and developer-facing APIs, giving you range most PM

View the original posting ↗