Senior QA Engineer

Zip•San Francisco, CA

About The Position

Zip is the AI platform for enterprise procurement — built for humans and agents working together. By orchestrating procurement across teams, tools, and suppliers with the help of AI agents, companies can secure the resources they need to innovate faster than ever before. The world’s most influential enterprises trust Zip, including T-Mobile, OpenAI, AMD, Mars, Dollar Tree, and more. Together they’ve saved over $8 billion and processed over $500 billion in spend. Zip’s team includes product leaders from Apple, Airbnb, and Meta, as well as former procurement leaders from United Health, Sanofi, MGM Resorts, Discover, and NASA. Backed by Adams Street, Alkeon, BOND, CRV, DST, Tiger Global, and Y Combinator, Zip has raised $371 million, most recently at a $2.2 billion valuation and has been recognized by Forbes Fintech 50, Fast Company's Most Innovative Companies, Inc. Best in Business, and LinkedIn Top Startups. Your Role You're a quality engineer who thinks like a customer and works like an owner. You don't wait to be handed a test plan — you read the PRD, join the bug bash, and come back with edge cases no one else found. You have a strong automation-first instinct and the technical depth to build it: you write Playwright tests in TypeScript the way an engineer writes production code — with care, structure, and an eye toward maintainability. You thrive in fast-moving environments. Zip ships four days a week, and you're the person who makes that pace feel safe rather than reckless. You're comfortable with ambiguity, skilled at managing a large manual workload when it matters, and motivated by the idea that great quality is a product discipline, not a catch-net. You care about the product, not just the test suite. You put on the customer hat, dig into real failure patterns, and use what you find to improve coverage, process, and product — not just to close tickets.

Requirements

Proven track record owning QA end-to-end in a fast-moving SaaS environment — independently developing test plans, triaging failures, and driving resolution without needing direction on what to cover
Strong Playwright and TypeScript skills — you write automation tests with the same care and structure you'd apply to production code; experience with pytest or Python is a plus
Automation-first mindset with a working knowledge of the testing pyramid — you can speak credibly to when and why to use unit, contract, integration, and UI tests, and you prioritize accordingly
Demonstrated ability to collaborate across EPD functions — you communicate test plans clearly, align with stakeholders on coverage decisions, and reduce friction for product teams rather than adding to it
Sharp attention to detail and a customer-first orientation — you debug, refactor, and review test cases with edge cases and real user behavior in mind, not just the happy path

Nice To Haves

Experience with financial or transactional workflows (invoices, bills, payments, or payouts) is a strong plus
Experience with SaaS release workflows, performance testing, or accessibility testing
Domain knowledge in procurement, spend management, or contract management
Familiarity with Python, Selenium WebDriver, or Cypress

Responsibilities

Own product quality OKRs in partnership with the EPD team — staying ahead of customer-reported issues by analyzing failure patterns, improving test coverage, and surfacing regressions before they reach production
Build and maintain Playwright automation (TypeScript) as the primary testing approach, aligned with the testing pyramid across UI, integration, and unit layers — and partner with engineering to expand that coverage over time
Own the quality gate for every release cycle: review PRs lacking test coverage, collaborate with an offshore QA team on regression execution, and partner with engineering to resolve release-blocking issues fast
Embed deeply with the product team to develop domain expertise, own end-to-end test plans, and drive quality outcomes for new features and releases
Serve as Zip's quality advocate in the deploy process — not just flagging issues, but actively raising the bar across the team for how testing gets done
Continuously improve QA processes, tooling, and documentation based on what's working and what isn't — you treat the test suite as a living system, not a static artifact