QA Engineer

About the role

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.

Responsibilities

• Decide what to test, when to test, and which product areas are worth automating.
• Perform hands‑on manual testing (~70% of time).
• Work with engineers and other stakeholders on features as they ship.
• Reproduce bugs reported by customers.
• For larger launches, coordinate testing across an entire feature area.
• Write Playwright end‑to‑end tests and help expand test coverage (~30% of time).
• Build on the existing Playwright suite and page‑object structure.
• Pair with SDETs to grow automation skills.

Requirements

• Strong product instincts; test like a user and distinguish between “it works” and “it works the way someone would actually use it.”
• Good at reproducing bugs; narrow down issues rather than filing vague reports.
• Self‑sufficient; able to scope your own work, decide what’s worth testing, and know when to ask for help.
• Comfortable writing code, reading others’ code, and improving both skills.
• Interest in growing the automation side; want to write more tests, get faster, and learn from engineers.
• Clear, concise writing ability.
• No need to be an SDET or to have built a test framework from scratch.
• Some experience writing E2E tests (Playwright) and a desire to write more.

Skills

• TypeScript (frontend & backend), React, GraphQL API, Node.js, Postgres, Redis.
• QA tools: Playwright (TypeScript) for e2e tests, TestRail for test management, BrowserStack for cross‑browser testing, Postman for manual API testing.
• Prior experience with the stack is not required; a love of typed languages is helpful.

Benefits

• Competitive salary and equity.
• 10‑year exercise window for