New: CentriCall AI voice agents that answer, qualify, and book around the clock
Centricone Technologies
Staff augmentation

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.

Tell us the gapHow our staffing works

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

01

Building and maintaining automated suites in CI

02

Exploratory testing on new features before release

03

Regression coverage on the paths that carry revenue

04

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.

Mid-level

Writes and maintains automated tests within an established framework and executes structured exploratory testing.

Senior

Owns test strategy for a product, decides the automation boundary, and keeps the suite trustworthy.

Lead / QA lead

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.

Both, and anyone who says otherwise is selling something. Automation covers regression on known paths; exploratory testing finds what nobody thought to specify. The engineers we place do both and can explain where each earns its keep.
Playwright and Cypress most often for end-to-end, with the unit and integration layers in whatever the codebase already uses. We assess against your stack rather than the one they prefer.
That is one of the most common reasons teams hire here, and it is a real skill — usually a mix of timing assumptions, shared state, and test isolation. We screen for it specifically because a suite nobody trusts is worse than no suite.
Both, and the stronger engineers push coverage down toward the API deliberately, because those tests are faster and far less brittle than driving a browser. If your current suite is entirely UI-level, that rebalancing is often the highest-value thing a QA hire does in the first months.
Some do, and it is a separate skill worth requesting explicitly. The valuable part is not running the tool but designing a scenario that resembles real traffic and interpreting the result against a target you agreed beforehand — a load test without a stated threshold produces numbers, not answers.
Several can, and it matters where you have a legal obligation, a public-sector buyer, or an enterprise procurement process that asks. Automated checks catch a useful minority of issues; the rest needs someone who will navigate the product by keyboard and screen reader, which is what we screen for.

Keep reading

Talent management

Engagement models side by side, the screening gates every candidate clears, and what happens after a placement starts.

Read more

IT staff augmentation

The capability page: how augmentation works, what we screen for, and the shapes an engagement takes.

Read more

Other roles we staff