QA Engineer

QA Engineer

Location Remote - US

Employment Type

Full time

Location Type Remote

Department Engineering QA

• US $90K - $115K Offers Equity
• CA $85K - $105K Offers Equity

The posted range represents the typical compensation range for this role. To determine actual compensation we review the market rate of each candidate which can include a variety of factors including qualifications, experience, and location. Additional benefits are shared as part of the job posting.

Hi! I'm Shriya, and I lead QA at Ashby.

We're hiring a QA Engineer to help us test and strengthen the quality of our product.

I think of QA as something you build into the system, not as something you layer on top for added confidence. I'm not interested in gatekeeping quality or creating a process for its own sake. I care about feedback that's fast and useful, the kind engineers trust, and catching the problems users would actually notice.

That's what brought me to Ashby. Engineers take on a lot of ownership, including the quality of their work, which often means they test it themselves. QA here isn't about convincing people to care or taking quality off their plate. It's about being another set of eyes on a fast-evolving product. Sometimes that means seeing the edge case. Sometimes that means spotting the product's blind spot before it hits production.

In this role, you'll decide what to test, when to test, and which product areas are worth automating. We're a small team, so the work is mixed. We all roll up our sleeves when needed.

Most of your time, roughly 70%, is hands-on manual testing. 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.

The other 30% is automation. You'll write Playwright end-to-end tests and help expand test coverage. You do not need to be an SDET, and you do not need to have built a framework from scratch. You do need to be comfortable writing code, reading someone else's code, and getting better  you've written some E2E tests and want to write more, that's the right starting point.

We have an existing Playwright suite and page object structure you'll build on, and SDETs who will pair with you and help you grow.

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 are 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,…