The opportunity
We're hiring a QA Engineer to help us test and strengthen the quality of our product.
What you'll do
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.
What they're looking for
- 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.
