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
Key Responsibilities
- Own the QA strategy for the POS app, back office, and payments, deciding what gets automated, what gets tested by hand, and what blocks a release.
- Build and maintain automated test suites across layers: unit and integration coverage alongside engineers, E2E tests for the back office (Playwright or similar), and API and contract tests between the POS and back office.
- Wire tests into CI (GitHub Actions) so every pull request and release candidate gets fast, reliable feedback, and keep flaky tests at near zero.
- Turn our release process into evidence-based gates: regression results per build, upgrade testing from older app versions, staged rollouts by ring, and clear go/no-go criteria for hotfixes.
- Test on real hardware in real conditions: Elo terminals across Android and firmware versions, card readers, scanners, printers, offline mode, flaky networks, and long-running overnight soak tests.
- Drive payments quality, including processor certification test runs, refund and split-tender edge cases, and failure modes like reader disconnects and processor outages.
- Build test data and environments: seeded merchant data, isolated per-branch environments, and emulators so anyone can reproduce a merchant's setup in minutes.
- Use AI tools to move faster, from generating test cases and test code to triaging crash logs and support tickets.
- Partner with support to shorten the path from a merchant report to a reproducible bug, with the register, app version, and transaction details attached.
- Track quality with a few clear metrics, such as escaped defects, crash-free sessions, release-health by version, and time from merge to store, and report on them plainly.
