Hire manual QA engineers vetted on bug reports developers can act on

Hire manual QA engineers who test what your developers didn't plan for. Manual QA ran on our eHealth, patient portal and fair lending projects.

Abstract 3D illustration of a white magnifying lens over a row of blocks, with one block highlighted in orangeAbstract 3D illustration of a white magnifying lens over a row of blocks, with one block highlighted in orange

WHICH ROLE FIRST

Manual tester, automation engineer or both?

The gap in your team decides which one to hire first

Your developers test their own work

A developer tests the path they built and expect to work. A manual tester goes looking for the other paths: the double-click on Pay, the form sent after the session expired, the phone turned sideways. Exploratory testing, usability and accessibility checks on real devices, and user acceptance testing with your business users are a tester's job. If features still change every sprint, hire the tester before anyone writes a regression suite, because a script written against an unstable feature gets rewritten along with it.

The same checks run every release

Once the same checks run release after release, scripts start to pay for themselves. Keep a manual tester on new features and edge cases, and bring in automation engineers for repeated regression checks. We staff both. Most mature products end up running the two side by side.

The flow works, but users get lost

A tester can tell you a checkout is confusing and point to the step where it loses people. Deciding how it should work instead is a design job, and for that we staff UI/UX designers for design review and usability checks.

Someone has to plan the testing

Which risks a release covers, and what has to pass before a build ships, is a plan somebody owns. A senior manual QA engineer can own it, and on a larger product you can ask for a lead-level tester to run it. Fitting that plan into the release schedule is a project manager's work, and we can place project managers on your team as well.

Abstract 3D illustration of two white block stacks side by side, one beside an orange checklist, the other beside a gearAbstract 3D illustration of two white block stacks side by side, one beside an orange checklist, the other beside a gear

THE WORK

What does a manual QA engineer own on your team?

Your tester writes test cases from your requirements, runs exploratory and regression checks on the browsers and devices your users have, and files bug reports a developer can reproduce. They take direction from your lead, work in your tracker and report what still fails before release.

Under staff augmentation, manual testers who join your team work to your priorities and in your tools. If you would rather hand the whole job over, we run manual testing as a project, and you accept each milestone.

Functional and exploratory

Each requirement turns into test cases, steps with an expected result, run on web and mobile across real devices and browsers in BrowserStack.

Exploratory sessions then chase the odd inputs and broken flows nobody wrote a case for. Each bug report gives steps, expected and actual result, build, device, severity and a recording or logs.

Regression and smoke checks

Which old features does this change put at risk? Regression testing starts from that question, every fix is re-tested before its bug is closed, and each new build gets a smoke test first.

APIs are checked by hand against the spec in Postman, so a wrong status code or payload shows up before the screen that calls it does.

User acceptance testing

The tester writes the acceptance scenarios and runs them with your business users, the people who asked for each feature in the first place.

Before release you get a list of what passed and what is still open. The sign-off decision stays with you.

Usability and accessibility

A heuristic usability review walks each flow as a user would and flags the steps where people are likely to get lost.

Manual accessibility checks against WCAG cover keyboard-only use, a screen reader pass, focus order and text contrast.

Tell us what your testers will test

Send us the apps you ship, the seniority you need and the tool your test cases live in, and we start the search from there.

TECHNOLOGIES

Tools our manual QA engineers work with

Jira

TestRail

Zephyr

Xray

Postman

BrowserStack

HOW WE VET

How do we check a tester before you meet one?

Judged on the test cases and bug reports they write for us

Three checks for every candidate

Every tester we present has passed three checks. First comes the technical skills assessment, which for manual QA is a practical task: the candidate writes test cases from a requirements document, runs an exploratory session on a sample app and files bug reports. We judge the result on clarity and on whether each bug can be reproduced from its report. A soft-skills evaluation follows (English, taking feedback, working in a team), and last an analysis of their job history, which is our check of the CV.

Why the task outweighs a certificate

Some of our testers are ISTQB-certified, and we are glad when a candidate is. A certificate shows what someone studied. The task shows how they test, so that is what we judge on, certificate or not.

Live sessions and background checks

Where a live step applies to a tester, it is a live testing session, not live coding. A background check, which verifies the CV is genuine, runs only when a client asks for one.

What you see before you interview

If you hire under staff augmentation, you can ask to see a candidate's test cases and bug reports from the task before the interview, and you can turn anyone down on the CV or the interview. Read the bug reports first, because they show how this person will talk to your developers. With a managed manual QA team we select and vet the testers ourselves, and you can interview the key roles.

Abstract 3D illustration of a white clipboard with a report sheet, one line marked in orange, beside a small block stackAbstract 3D illustration of a white clipboard with a report sheet, one line marked in orange, beside a small block stack

BY THE NUMBERS

7 years

Average experience, company-wide

80%+

Senior-level or above, testers included

50+

Projects delivered by our team

PROCESS

What happens after you contact us

These are usual times. What we commit to is presenting candidates within 7 days of your request. Hiring developers or designers for the same release as well? Browse all the engineering and testing roles we staff.

  1. STEP 1

    Define the testing role

    We agree the seniority, what you test (web, mobile or APIs), which test-case tool you use and how releases run today.

    1 day

  2. STEP 2

    Match vetted testers

    We shortlist testers who passed the practical testing task and fit your products and the seniority you asked for.

    1–2 days

  3. STEP 3

    Interview your shortlist

    You interview the testers you pick and decide who joins.

    1 day

  4. STEP 4

    Onboard the tester

    We handle contracts, the NDA and security setup, and you give the tester access to your tracker, test-case tool and test environments.

    1–2 days

HOW WE WORK

Engagement models and terms

Staff augmentation

Our engineers join your team and work in your process and tools. You manage them; we source, vet and contract them.

Hourly rate per engineer by role and seniority, invoiced monthly.

  • If an engineer isn't the right fit, we replace them within 14 days at no extra cost.
  • Knowledge transfer to the replacement engineer isn't billed.
  • There is no free trial period.
  • 30 days' notice to take an engineer off or end the engagement, with no minimum term beyond it.
  • Out-of-hours on-call only if agreed with you; we set its hours and billing together.
  • After two years, moving an engineer onto your own staff is something we can discuss.

Managed team

An agreed team capacity that we manage. We coordinate delivery and handle the team's make-up. You set the priorities and own the backlog.

Per-engineer rates, or a fixed monthly fee for the agreed capacity.

  • We handle replacements ourselves, and the team keeps its agreed capacity and pace.
  • Engineers work full-time for your team only.

Project delivery

We deliver an agreed scope end to end: plan, team, milestones, QA and release. You make the product decisions and accept each milestone.

Fixed price per milestone after discovery, or time and materials against an estimate.

  • Scope changes go through change requests.
  • On fixed-price projects, a warranty period agreed in the contract, usually 30–60 days.

Whichever model you choose

  • We reply to an inquiry from the contact form within 24 hours.
  • We sign an NDA before work starts, and IP passes to you on payment.

Put a tester on your next release

"What a tester really ships is the bug report. One a developer can work from without a single follow-up question is worth ten vague ones."

Dzmitry Kuchynski, Chief Operating Officer at Octalance

Dzmitry Kuchynski, Chief Operating Officer, Octalance

FAQ

Questions to settle before a tester joins

What does a manual QA engineer cost?

Rates are agreed with each client, so we don't publish one. The price moves with how many testers you use, for how long, and how senior they are. A tester placed through staff augmentation is billed at an hourly rate by role and seniority, invoiced monthly. The other price types are in the Engagement models and terms section of this page.

Can I hire one manual tester, or only a team?

One is fine. A single tester can join your team under staff augmentation and works full-time for you only. If you need several testers and would rather we coordinate them, a managed team covers that. And if what you need is a round of testing before a launch, a testing project fits better than a hire.

How do I tell a good manual tester from a weak one in an interview?

Give them a short feature description and ask which cases they would run first. A strong tester asks who uses the feature and what breaks if it fails before listing anything, and goes past the happy path without being prompted. Then ask how they would report a bug that only shows up on one device. Listen for the build, the device, the exact steps and what they expected to happen.

Where should a new manual tester start on our product?

With the bugs your users reported after the last release. Each one becomes a regression case, and the regression set checks for it every release. Exploratory sessions on the newest features come once the tester knows the product. Keep the test plan with a senior tester or your lead from day one.

What hours do your testers work with a US team?

Our default working day is CET/CEST business hours. We match yours by choosing where the tester is based and shifting the schedule, which for a US team means 4+ hours of daily overlap with the West Coast and more with the East Coast. We don't run shifts, so there is no round-the-clock cover.