QA Engineer

Summary

Ashby is a growth-stage software company building a product used by more than 100,000 weekly active users. The QA Engineer will strengthen product quality through hands-on manual testing, bug reproduction, launch coordination, and Playwright end-to-end test automation while collaborating closely with engineers and stakeholders.

Responsibilities

• You'll decide what to test, when to test, and which product areas are worth automating
• You'll work with engineers and other stakeholders on features as they ship, reproduce bugs reported by customers, and, for larger launches, coordinate testing across an entire feature area
• You'll write Playwright end-to-end tests and help expand test coverage
• Your first few weeks are about learning the product deeply, because good testing starts with understanding how customers actually use what we've built
• You'll get hands-on fast, testing real PRs early and increasing in scope as you build context
• On the automation side, you'll start by getting familiar with our existing Playwright suite and writing your first e2e tests with support from the team

Skills

• You have strong product instincts. You test like a user and know the difference between "it works" and "it works the way someone would actually use it."
• You're good at reproducing bugs. When something is broken, you narrow it down. You don't file vague bugs and move on
• You are self-sufficient and can scope your own work. Given a feature and a spec, you decide what's worth testing and what's not, and you know when to ask for help when something is taking too long
• You want to grow on the automation side. You don't need to be an expert to be interested
• You want to write more tests, get faster at it, and learn from the engineers around you
• You write clearly. Your writing should be concise, clear, and easy to follow
• You think of QA as gatekeeping. We don't have sign-off gates, and we're not adding them. Your influence comes from the quality of your judgment, not from a checkbox
• You're happiest when someone hands you a test plan and a set of instructions. This role operates on ownership, with you often deciding what to test and why
• You want to stay at the surface. Testing Ashby well means understanding it well. The interesting problems are several layers in
• You're used to working on large QA teams with lots of ceremony and fixed roles
• You want a pure automation or SDET role. The majority of this job is hands-on testing. If you want to spend your days building frameworks and tooling, apply for our SDET role instead; it's a better fit, and you'll be happier
• You don't want to write code at all. A meaningful part of this role is automation, and we expect that to grow with you
• You do need to be comfortable writing code , reading someone else's code, and getting better at both
• If you've written some E2E tests and want to write more, that's the right starting point

Qualifications

Must Haves

• You have strong product instincts. You test like a user and know the difference between "it works" and "it works the way someone would actually use it."
• You're good at reproducing bugs. When something is broken, you narrow it down. You don't file vague bugs and move on
• You are self-sufficient and can scope your own work. Given a feature and a spec, you decide what's worth testing and what's not, and you know when to ask for help when something is taking too long
• You want to grow on the automation side. You don't need to be an expert to be interested
• You want to write more tests, get faster at it, and learn from the engineers around you
• You write clearly. Your writing should be concise, clear, and easy to follow
• You think of QA as gatekeeping. We don't have sign-off gates, and we're not adding them. Your influence comes from the quality of your judgment, not from a checkbox
• You're happiest when someone hands you a test plan and a set of instructions. This role operates on ownership, with you often deciding what to test and why
• You want to stay at the surface. Testing Ashby well means understanding it well. The interesting problems are several layers in
• You're used to working on large QA teams with lots of ceremony and fixed roles
• You want a pure automation or SDET role. The majority of this job is hands-on testing. If you want to spend your days building frameworks and tooling, apply for our SDET role instead; it's a better fit, and you'll be happier
• You don't want to write code at all. A meaningful part of this role is automation, and we expect that to grow with you
• You do need to be comfortable writing code , reading someone else's code, and getting better at both
• If you've written some E2E tests and want to write more, that's the right starting point

Benefits

• Equity.
• 10-year exercise window for stock options.
• Unlimited PTO, and we will encourage you to take it.
• A minimum of 12 weeks of fully paid parental leave, covered by Ashby. The actual number may increase to satisfy local requirements.
• Generous equipment, software, and office furniture budget. Get what you need to be happy and productive!
• $100/month education budget with more expensive items (like conferences) covered with manager approval.
• $250/month tool budget plus access to Claude, Cursor, and Codex with generous token budgets.
• If you’re in the US, we offer top-tier health insurance for you and your dependents, with 100% of premiums covered by Ashby.
• In other countries, we provide high-quality supplemental health insurance for you and your dependents, also fully covered by us.