Hire engineers

Hire manual testers who test your releases by hand, inside your team

Hire manual testers through Zapple.Tech when you set your own testing priorities and need more hands to test releases by hand. You describe the role, we propose testers, you meet them, and they join your stand-ups, sprints and tracker for exploratory, regression and end-to-end checks. An engagement can start within two weeks of your go-ahead.

4.9 out of 5 on Clutch, from 7 client reviews

hire-manual-testers / manual-tester-role-brief.md

Before you meet anyone

Manual tester role brief
Release in scopeThe release the tester starts on, with the stories it contains Named
Release rhythmHow often you ship, so regression passes fit the calendar Written
Defect write-upWhat a report must hold before your developers accept it Open
Access to buildsTest accounts and an installable build, still to be sent Missing

Zapple.Tech in figures

  • CodeceptJSFounded by the founders of CodeceptJS and Codeception, open-source testing frameworks
  • 2015On the market since 2015
  • 50+More than 50 testimonials

Who we are. Zapple.Tech is a QA and test automation company founded by the founders of CodeceptJS and Codeception, open-source testing frameworks. Clients rate us 4.9 out of 5 on Clutch, from 7 client reviews.

Page updated . Written by the Zapple.Tech QA team.

What you can order

What can you order here? Three ways in, depending on where you are today.

Manual testers for exploratory testing of new features

A tester takes each new feature as it lands, tries the paths a user would and the ones nobody planned for, and reports what broke.

  • Test cases from your stories, plus time to explore around them
  • Bug reports your developers can reproduce from the steps alone

Manual testers for regression passes and release checks

A tester runs the regression pass before each release, on the journeys you name in the role brief as the ones that must not break.

  • A regression pass on every release, in your sprint calendar
  • Defects logged in your tracker with steps and evidence

Manual testers for end-to-end checks of key journeys

A tester walks whole journeys from the user's side, such as sign-up to first purchase, on web and on mobile.

  • Journeys named in the role brief, checked from the user's side
  • Manual end-to-end checks are a current service

How it works

How hiring a manual tester works

How hiring a manual tester worksFour steps. Role brief: you send the role through the form and approve a written brief with what to test by hand, the release rhythm, the tools, the term and the first release. Meet the testers: Zapple.Tech proposes testers, you talk to each of them and choose. Terms agreed: the quote names how many testers, for how long, the notice period and how a tester is replaced. Joins your team: the tester works inside your sprint and in your tracker. A review after the first month checks the role against the work.YouRole briefWhat to test by hand,release rhythm, tools,term, first releaseYouMeet the testersYou talk to each testerwe propose, and youchooseZapple.TechTerms agreedHow many testers, forhow long, notice, andhow a tester isreplacedTesterJoins your teamWorks in your sprintand your tracker,reading stories as theyare writtenFirst-month review: the role brief is checked against the workHow hiring a manual tester worksFour steps. Role brief: you send the role through the form and approve a written brief with what to test by hand, the release rhythm, the tools, the term and the first release. Meet the testers: Zapple.Tech proposes testers, you talk to each of them and choose. Terms agreed: the quote names how many testers, for how long, the notice period and how a tester is replaced. Joins your team: the tester works inside your sprint and in your tracker. A review after the first month checks the role against the work.YouRole briefWhat to test by hand, release rhythm,tools, term, first releaseYouMeet the testersYou talk to each tester we propose, and youchooseZapple.TechTerms agreedHow many testers, for how long, notice, andhow a tester is replacedTesterJoins your teamWorks in your sprint and your tracker,reading stories as they are writtenFirst-month review: the role brief is checkedagainst the work
How hiring manual testers works, from a written role brief you approve and a conversation with each tester to the tester working in your sprint.

What does a manual tester do in your team?

A manual tester checks your product the way a user meets it. In your team, a manual tester can take on five things in each two-week sprint:

  • Exploratory sessions on new features, before any script exists for them.
  • A manual regression pass before a release, on the journeys that must not break.
  • Manual end-to-end checks of the journeys that earn money, from the first screen to the last.
  • Acceptance checks against the story, so “done” means what the story said.
  • Bug reports with steps and evidence in your tracker, written so a developer can reproduce the defect.

QA is involved at every stage of delivery, so the tester also reads stories while they are written. A question asked before code is written is cheaper than a defect found after.

When should you hire manual testers instead of automating?

Hire testers for the work that changes, and automate the work that repeats. This is practitioner judgement, not a measured rule.

  • The interface is still changing. A script written today breaks next sprint.
  • The flow is rare or runs once, such as a migration or a launch. Writing automation costs more than running it.
  • The question is about wording or usability. A script confirms a label exists. A person notices it is confusing.
  • The flow is slow to automate, for example one that depends on a person or a device.

The checks that run on every release are the ones to automate. For those, see hire test automation engineers or automate regression tests.

Hire manual testers or outsource manual testing: which fits?

Decide who directs the work. If you have someone to set priorities and need more hands, hire testers into your team. If you want the result and not the people, have Zapple.Tech run it: see the manual and exploratory testing services. If the role is wider than manual testing, see hire QA engineers. The table on this page sets the three side by side.

How does hiring a manual tester work?

  1. Send the role. Use the form on this page. One call follows, and the answers go into a role brief you approve: what to test by hand, how often you release, the tools, the term and the first release.
  2. Talk to the testers. We put testers forward against that brief. You ask each one how they would test your product, and you decide who joins.
  3. Agree the terms. The quote says how many testers, for how long, the notice period and how a tester is replaced.
  4. Start in your sprint. The tester joins your stand-ups and works from your tracker.
  5. Look back after a month. The brief is compared with the work done so far and changed where it was wrong.

Not sure you need a person in your team? Start with a one-week exploratory test of one release, described on the manual and exploratory testing services page. Pricing is by quote.

How do manual testers use AI, and what does AI not do?

AI tools can draft test ideas from a story, prepare test data and write the first version of a bug report. The team uses Testeiya and Explorbot, agents from Testomat.ai: Testeiya is a QA agent that works with Testomat.io, MCP, GitHub, GitLab and Jira, and Explorbot is an AI agent that scans a live UI, runs exploratory tests and generates Playwright code. It also uses Playwright MCP, and Testomat.io for test management. Zapple.Tech was founded by the founders of Testomat.io and Testomat.ai.

What AI cannot do is use your product the way a customer does. It does not notice that a flow is confusing, and it does not decide which defect matters for the release. The tester does both, and fixes every AI draft before it reaches your tracker. Which tools may touch your product is your decision; personal data stays out of them by default, and where your rules allow none, the tester works without any.

What if a manual tester is not what you need?

If this is closer to your situation Look at
You need people who write and maintain test code Hire test automation engineers
You need developers who write and fix Playwright tests Hire Playwright developers
The work is your iOS and Android app builds Hire mobile app testers
You want a whole team with a lead of its own, working to your priorities A dedicated QA team
You want an outside company to take over the testing of the product QA outsourcing
You want a written plan before you hire anyone A one-week QA audit

Who you are hiring from

The company behind your tester has been on the market since 2015. Its founders created CodeceptJS and Codeception, two open-source testing frameworks, and also built Testomat.io and Testomat.ai. Clients have left more than 50 testimonials. Your tester follows that company’s test process and its rules for AI drafts. Whether a tester is right for your product is for you to judge in the conversation before they start.

Honest limits

What hiring manual testers does not solve. A hired tester works under your direction, so the decisions around testing stay with you.

  • 01

    A tester tests what your team puts in scope. What gets priority, and whether a release ships, are still your calls.

  • 02

    Manual regression grows with every release. At some point the passes that repeat have to be automated.

  • 03

    A tester needs access, test data, a test environment and one person who answers product questions, all arranged by your team before the start.

  • 04

    One tester is not a QA function. If nobody owns the test strategy, look at a dedicated QA team.

  • 05

    AI can draft a bug report, but it cannot tell whether the defect is real. The tester confirms each draft against the product first.

Compare the options

Three ways to get manual testing done, by who directs the work.

Three ways to get manual testing done, by who directs the work.
OptionWho directs the workWhat you getChoose it when
Hire manual testersYou, task by taskPeople in your team who test by handYou have someone to set priorities and need more hands
Manual testing servicesZapple.Tech, against an agreed scopeTested releases and a written view of what to keep manual and what to automateYou want the result, not the people
Hire QA engineersYouEngineers who test and also automate or shape the test processThe role is wider than manual testing

How the work runs

How does the work start? With the role brief: your form, then one call. You decide after each step whether to continue.

  1. Your form, then one call

    Role brief

    You send the role through the form on this page. On one call we then write down what the tester will test by hand, how often you release, which tracker and tools they will use, how long the term is and which release they test first.

    • A role brief in writing, approved by you
    • A named first release for the tester
  2. Agreed with you

    Meet the testers

    We put testers forward against the brief. Ask each of them how they would test a feature like yours and how they write up a defect, then choose who joins. The start date is fixed once you have chosen.

    • Testers put forward for your brief
    • Time to talk with each tester before you decide
    • How many testers, the term, notice and how a replacement works, written into the quote
  3. For the agreed term

    Ongoing

    An engagement can start within two weeks of your go-ahead. The tester works in your sprint and reads stories while they are written. Once a month has passed, we sit down with you, compare the brief with the work the tester actually did, and adjust it.

    • Features and releases tested by hand, defects logged in your tracker
    • The role brief revised after month one

Each step has a defined scope, duration and deliverables. You decide after each one whether to continue.

Tell us what to test by hand, how often you release and for how long you need the tester. We reply within one business day with scope, timeline and a quote. The role brief is then settled with you on one call.

An engagement can start within two weeks of your go-ahead.

Hire manual testers: your questions answered

What does a manual tester do?

A manual tester tests the product by using it. They explore new features, run the regression pass before a release, walk key journeys end to end, check a feature against its story and file bug reports with steps and evidence in your tracker. They can also read stories before code is written, because QA is involved at every stage of delivery.

Should we hire manual testers or automate our tests?

Hire manual testers for what changes or is hard to script, and automate what repeats. A changing UI, a rare flow, wording and usability are better tested by a person. The checks that run on every release are the ones to automate, so hire test automation engineers or automate regression tests for those.

What is the difference between hiring manual testers and outsourcing manual testing?

Hiring means the testers join your team and you direct them task by task. Outsourcing means Zapple.Tech runs the testing against an agreed scope and you receive tested releases and a report. If you want the result rather than the people, see the manual and exploratory testing services or QA outsourcing.

How quickly can a manual tester start?

An engagement can start within two weeks of your go-ahead. What moves the date most is how soon the tester can get into your tracker, builds and test environment.

Can we meet the testers before they join our team?

Yes. We propose testers for your role brief, you talk to each one, and you choose. The start date is fixed after that and goes into the quote.

Can a manual tester run end-to-end tests across our whole product?

A manual tester can run end-to-end checks of the journeys you name in the role brief, such as sign-up to first purchase, and manual end-to-end testing is a current service. Covering the whole product is a question of scope and time, so the brief names the journeys and the first release.

Do your manual testers use AI tools on our product?

Only the AI tools your team approves, and none if your rules forbid them. Where they are allowed, they prepare test ideas, test data and first drafts of bug reports. The tester corrects every draft before it reaches you, and personal data is kept out of AI tools by default.

What do you need from us before a tester starts?

Access to your tracker and builds, a test environment with test accounts, and one person who can answer product questions. The role brief also needs your release rhythm and the first release to test.

How much does it cost to hire a manual tester?

We do not publish prices. What you pay depends on how many testers you need and for how long, both set in the role brief. Send the role through the form and a scoped quote comes back within one business day.

Start with a written role brief

Tell us what to test by hand, how often you release and for how long you need the tester. We reply within one business day with scope, timeline and a quote. The role brief is then settled with you on one call.

What happens after you send this

  1. You send the form: your situation and what you need tested, then your name and work email.
  2. Within one business day, we reply with a suggested first step, its scope, timeline and a quote.
  • You meet each tester before they join
  • Team size, term and notice in the quote
  • You decide after each step
  • An NDA signed before access

“They helped us to close the positions and consult our team how to proceed further. High-quality quick feedbacks with the deep checking of the required tasks, professional approach, great understanding of the company's technologies and product, detailed reports.”

Kristina Lavrentieva, Manager at keepgo.com, Israel
  • Rated 4.9 out of 5 on Clutch, from 7 client reviews
  • On the market since 2015
  • Founded by the founders of CodeceptJS and Codeception, open-source testing frameworks

Request a team proposal

    What is closest to your situation?
    Optional. The product, the platforms, how often you release, what broke last.

    You decide after our reply whether to go ahead.

    Prefer to talk first? Book a call

    Role brief · you meet the testers

    Describe the role