The Kind of QA Engineer This Role Needs
We’re not looking for someone who just runs a checklist and closes tickets.
We’re looking for someone who:
• Asks “what could go wrong here?” before a feature ships
• Is comfortable when specs are incomplete or evolving
• Can think from the user’s perspective, not just the test plan
• Takes ownership of quality
• Communicates clearly with engineers, not just in Jira
• Wants a career in quality engineering, not just a job
If you’ve worked somewhere perfectly structured with locked-down processes: this will feel different. If you’ve ever found a bug no one else caught and felt genuinely good about it: you’ll fit right in.
We don’t expect you to know everything on day one. You should have a solid foundation in:
• Understanding of the software developer lifecycle (SDLC) and QA methodologies
• Experience writing test cases, test plans, and bug reports
• Familiarity with functional, regression, integration, and exploratory testing
• Comfort working in Agile/Scrum environments
• Bug tracking tools: Jira, Azure DevOps, or similar
• Basic understanding of browser developer tools for frontend debugging
• Familiarity with API testing concepts (Postman or similar is a plus)
Automation (Preferred, Not Required)
• Exposure to test automation frameworks: Playwright, Cypress, Selenium, or similar
• Basic scripting ability in JavaScript, TypeScript, or Python
• Understanding of CI/CD pipelines and how automated tests fit in
We need QA engineers who care about UX, not just pass/fail.
• You notice when something works technically but feels broken to a user
• You think about edge cases that live in the gap between spec and reality
• You can communicate UX observations clearly to engineers and PMs