--- title: "Manual QA Tester | Outsourced QA Team | Azendo" description: "Assign a Manual QA Tester to your roadmap under one monthly agreement, working from Thailand with an Azendo service delivery manager accountable for delivery." url: "https://azendo.co/services/qa-engineering-and-test-automation/manual-qa-tester/" --- [← QA and test automation](https://azendo.co/services/qa-engineering-and-test-automation/) # Manual QA Tester assigned to your roadmap. A Manual QA Tester finds what automation cannot. Visual defects, confusing flows, and the specific sequence of actions no test author thought to write. Assigned under one service agreement with a minimum monthly capacity in hours, run by a service delivery manager in Chiang Mai, Thailand — five hours ahead of Northern Europe. [Contact us](https://azendo.co/get-in-touch/) [See pricing](https://azendo.co/pricing/) Part of our service line [QA and test automation](https://azendo.co/services/qa-engineering-and-test-automation/) This role is delivered as part of our QA and test automation services. Take the role on its own, or the whole discipline as one delivery team. ## What a Manual QA Tester does on an outsourced QA team. Skills and scope are agreed before delivery starts, so the first sprint is productive rather than a ramp-up month. The work runs to the same backlog, the same repositories and the same definition of done as your own team's. ### Manual QA Tester skills and technology we assign for * [Exploratory and session-based testing](https://azendo.co/skills/exploratory-testing/) * [acceptance criteria validation](https://azendo.co/skills/acceptance-criteria-validation/) * [Jira](https://azendo.co/skills/jira/) * [TestRail](https://azendo.co/skills/testrail/) * [BrowserStack](https://azendo.co/skills/browserstack/) * [cross-device testing](https://azendo.co/skills/cross-device-testing/) * [bug reporting with reproduction steps](https://azendo.co/skills/bug-reporting-with-reproduction-steps/) * Exploratory testing against new features, following the product rather than a script. * Acceptance testing against requirements, with clear evidence attached to each ticket. * Cross-browser and cross-device checks where real hardware behaviour differs from emulation. * Accessibility checks with a screen reader, which automation catches only partially. * Verifying fixes and closing the loop, so a ticket marked done has actually been confirmed. ## Seniority levels we assign. Junior through mid. This role rewards curiosity and product knowledge more than seniority. Seniority is one of the inputs behind the [committed monthly capacity](https://azendo.co/pricing/) written into your agreement. ## When a Manual QA Tester is the right assignment. Often assigned alongside automation, covering the areas automation deliberately does not. On an ongoing roadmap this role is most often assigned alongside a QA Engineer or a Test Automation Engineer. All 4 roles in this service line can sit on the same agreement, and capacity moves between them at the monthly cycle rather than requiring a new contract. This capacity is assigned under [QA outsourcing](https://azendo.co/services/qa-engineering-and-test-automation/) rather than sold as a separate engagement. 160 h Typical monthly capacity for this role Fixed Monthly price, unaffected by leave or holidays 4–6 weeks From signed scope to delivery starting Monthly Cycle to raise or lower committed hours ## Other roles in QA and test automation. [QA Engineer QA and test automation role](https://azendo.co/services/qa-engineering-and-test-automation/qa-engineer/)[Test Automation Engineer QA and test automation role](https://azendo.co/services/qa-engineering-and-test-automation/test-automation-engineer/)[Performance Test Engineer QA and test automation role](https://azendo.co/services/qa-engineering-and-test-automation/performance-test-engineer/) The same delivery team, on your product, month after month. Chiang Mai and Bangkok, Thailand — five hours ahead of Northern Europe ## Questions about assigning a Manual QA Tester. Is manual testing not obsolete? No. Automation confirms what you already thought to check. Manual exploratory testing finds what nobody thought of. How do you report defects? With reproduction steps, environment, expected and actual behaviour, and evidence attached. A developer should not have to ask a follow-up question. ## Add manual QA tester capacity to your roadmap. Tell us the scope and the stack. We come back with the profile, the capacity and what the first month looks like, or you can [talk to a service delivery manager](https://azendo.co/get-in-touch/) first. [Contact us](https://azendo.co/get-in-touch/) [How it works](https://azendo.co/how-it-works/) ## Assign a Manual QA Tester to your roadmap.