Hire QA engineers who reduce risk, not just ticket counts
Centricone places quality engineers screened on judgement as much as tooling: what is worth automating, what is better tested by hand, and how to write a suite that does not become the reason nobody trusts CI.
Screening
What we check that a keyword match does not
Every candidate sits a live assessment with an engineer who does this work. For this role, that conversation covers:
- Test strategy — what belongs at unit, integration, and end-to-end level
- Flakiness reasoning: how they find and fix an intermittently failing test
- Exploratory testing skill, which automation does not replace
- Bug reporting quality, including reproduction steps someone else can follow
What they do once they are in your team
Building and maintaining automated suites in CI
Exploratory testing on new features before release
Regression coverage on the paths that carry revenue
Working with engineers on testability rather than testing around them
Which level you actually need
Most briefs ask for senior by default. Sometimes that is right; often the work is better served by a mid-level engineer and a clearer specification.
Writes and maintains automated tests within an established framework and executes structured exploratory testing.
Owns test strategy for a product, decides the automation boundary, and keeps the suite trustworthy.
Sets quality standards across teams and owns release-readiness criteria.
Questions about hiring QA engineers
Not sure what you need? Describe the work and we’ll tell you which role fills it.