Product Manager

About Us

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.

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.

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.

Position Overview

We're looking for a Product Manager to help drive the vision of the Scotch back office - the web application where our merchants run their business. The register is where a sale happens; the back office is where the business gets managed, and it's where Scotch can help our merchants make better revenue-driving decisions.

This is a hands-on role with real autonomy. You'll work with other product managers to build and execute the back office vision end-to-end. In particular, you'll focus on the product catalog, ordering and receiving, and other inventory management features.

We're also building AI into the core of the product to help merchants get through the tedious, error-prone parts of running inventory and books faster, without giving up control or trust. You'll help decide where AI genuinely earns its place in a SaaS workflow, and where it doesn't.

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. You won't be setting strategy alone but you'll have a real hand in shaping it, and have one of the closest views of the customer in the room.

Key Responsibilities

- The merchant operations roadmap for the back office web app: turning direction into a sequence of releases, and owning what goes into each one

- Core inventory and back-office workflows: creating/editing products, receiving, ordering, transfers, pricing, and shelf labels

- Requirements gathering from merchants and their staff: what they need, what they actually do, and the frequent gap between the two

- Executing on our AI feature strategy within the back office: which problems it should solve, how it earns merchant trust, and how we measure whether it's working

- Serving as the product point of contact for support, onboarding, and go-to-market on anything happening in the back office feature areas you own

- Shape the direction for the back office with us, then own the decisions inside it and defend those tradeoffs to people who'd rather ship something else

- Translate messy, conflicting merchant input into a clear direction, and hold that direction when the inputs keep changing

- Write requirements that describe the problem and the outcome, not the implementation

- Design for scale of organization, not just scale of data: the same workflow has to work for a solo owner and for a multi-location tenant with layered roles, delegated access, and different people responsible for different things

- Decide where AI belongs in a workflow — what it drafts, what it automates, what it must show its work on, and where a human stays in the loop — and define how we evaluate quality before we ship

- Prioritize across merchant escalations, platform work, and the long-horizon bets that never feel urgent

- Partner closely with engineering on scoping and sequencing, including the parts where the right answer is "not yet"

- Coordinate releases end to end: what goes in, how it rolls out, who needs to know before it lands, and what happens when it doesn't go to plan

- Define what success looks like before we build, then go look; instrument the work, watch adoption, and say plainly when something didn't land

- Spend real time with merchants and their back-office staff, and bring back things nobody would have found in a ticket

- Raise the bar around you — on how we write, how we decide, and how we talk to merchants

Qualifications & Skills

- Web application product experience, heavily preferred. You've owned a complex, data-heavy web app as a product surface — the kind with lots of screens, lots of settings, and users who live in it all day. You've shipped changes to a product with real customers already depending on it, and you know how to evolve a workflow without breaking the people who rely on it.

- AI feature development inside a traditional SaaS product. You've taken an AI-powered capability from idea to production inside an established product, not a standalone AI tool. You have a point of view on where it helps, where it fails, how to evaluate it, and how to earn user trust when the output isn't always right.

- Administrative workflow and multi-tenant instincts. You've designed for the person who administers the product, not just the person who uses it day to day. You understand roles, permissions, approvals, and audit needs, and you've taken a product from a single solo user to complex accounts with multiple locations, teams, and levels of access — and know what breaks along the way.

- Evidence of operating without a backstop. Somewhere in your history, you were the only person accountable for a decision, with nobody reviewing your work before it shipped. We care about this more than company size or the word "startup" on your resume.

- A real habit of customer contact. Not "I read the research deck." You've sat with users, watched them work, and changed your mind about something as a result. For this role that means the people who run the business behind the register — owners, managers, buyers, and bookkeepers. Going onsite to do research in a store with our users should excite and not scare you.

- Judgment you can articulate. We'll ask you about a call you got wrong. The best answers involve noticing it yourself before someone told you.

- Breadth under pressure. You've held multiple workstreams at once and made tradeoffs between them, not just executed one thing deeply while someone else set the priorities.

- Range in how you communicate. You can write a spec an engineer can build from, and explain the same decision to a merchant, a support lead, and an executive without losing any of them.

- 5+ years of product experience.

Nice to Haves

- Prior product experience in accounting, finance, or inventory management products — anything where accuracy, reconciliation, and an audit trail matter to the user. Bonus points if you're fond of FIFO

- Experience with purchasing, receiving, invoicing, or accounts-payable workflows

- Retail, distribution, or point-of-sale background, particularly with independent or small-format merchants

- Comfort working with data directly — writing or reading SQL to answer your own product questions

- Fluency with AI tools in your daily workflow

Compensation & Benefits

- Compensation: The anticipated base salary range for this position is $150,000 – $170,000. Individual offers are based on a variety of factors, including experience, skills, qualifications, and internal equity.

- Competitive equity package

- Comprehensive medical, dental, and vision coverage

- Unlimited flexible PTO

Why Scotch?

- Build from the ground floor: Create systems, processes, and operational standards that will scale with the business

- Lead a growing organization: Inherit an existing team while building new functions and capabilities

- Drive meaningful impact: Shape the customer experience and directly influence product quality

- Grow with the company: Join a rapidly scaling business with significant long-term opportunity

*]:pointer-events-auto R6Vx5W_threadScrollVars scroll-mb-[calc(var(--scroll-root-safe-area-inset-bottom,0px)+var(--thread-response-height))] scroll-mt-[calc(var(--header-height)+min(200px,max(70px,20svh)))]" data-turn-id="request-WEB:2270b521-3510-4afb-ae3e-980ebb0154bb-0" data-turn-id-container="request-WEB:2270b521-3510-4afb-ae3e-980ebb0154bb-0" data-testid="conversation-turn-2" data-scroll-anchor="false" data-turn="assistant">