Dedicated QA engineers for your offshore team.
Offshore QA engineers in Chiang Mai and Bangkok, working full time on your product and managed by us. A QA engineer owns whether a release is safe to ship: test strategy and judgement as well as running the tests.
One fixed monthly fee, with the hiring, managing and training of the testers handled by us in Thailand.
This role is part of a dedicated QA and test automation team. It's staff augmentation, fully managed: take one role on its own, or the whole area as one delivery team.
One QA Engineer, assigned to your product and fully managed.
We assign a QA Engineer to your team full time and run everything around them: a service delivery manager who oversees delivery, training and coaching, the office and equipment, and HR and payroll. The price below is for a junior QA Engineer; other levels are priced in your proposal, and how the monthly fee is built explains the arithmetic.
From price
One junior QA Engineer, full time, everything below included. All 27 things included ››
- QA engineer From USD 2,100 per month
-
Service
We manage and develop the team
- A service delivery manager who oversees operations and delivery
- A 1:1 with our Head of Delivery every two weeks
- Weekly delivery scoring and monthly capacity reports
- A Talent Success Manager for every team member
-
HR
We are the employer
- Recruitment and technical assessment
- Employment contracts
- Salary and payroll
- Tax and social security
-
Facilitation
We provide the workplace
- A desk in our office in Chiang Mai or Bangkok
- A Workplace Experience Manager on site
- Team events through the year
- IT support
-
Equipment
We supply the tools
- Laptop and hardware
- Software licences
- LinkedIn Learning access
- Device security and management
What a QA Engineer does on a dedicated QA and testing team.
They join your sprint from planning onwards, test each story as it lands and give your team a clear yes or no before anything ships.
QA Engineer skills and technologies
-
Building a test strategy around your real release risk.
-
Exploratory and regression testing across each sprint, with defect reports a developer can act on.
-
Release sign-off, including saying no when the evidence says the release is not ready.
-
Maintaining the regression suite scope as features are added and others are retired.
-
Working with support to turn recurring customer issues into permanent test coverage.
QA Engineer seniority levels.
Junior to lead. A mid-level engineer covers most regression and release work well. If that is enough for you, it shows in how the monthly fee is built.
When your team needs a QA Engineer.
Usually the first QA role, before automation is added. Often joined later by a test automation engineer or a manual tester, and the three together make a dedicated QA and testing team. It is the role companies add when they hire dedicated developers and want release decisions backed by someone whose job is quality.
What we look for in a dedicated QA Engineer.
We look for QA engineers who are curious enough to find the defect no test script covers. They also need to be firm enough to advise against a release when the evidence calls for it. Clear bug reports matter. A developer should be able to reproduce the issue from the ticket alone.
A remote QA Engineer's first three months on your team.
- Weeks 1 to 2Learning your product, release process and known risk areas, and testing the current sprint.
- Weeks 3 to 6Writing a test strategy for your release risk and running regression each sprint.
- Months 2 to 3Owning release sign-off and turning recurring customer issues into permanent test coverage.
Questions about adding a QA Engineer to your team.
Does a QA engineer write automated tests too?
Some. A QA engineer owns test strategy, exploratory testing and release decisions, and writes automated tests where they add the most value. When building and maintaining a large automated suite is the main need, a test automation engineer is the better fit. The two roles are often combined on one team.
Can the QA engineer stop a release?
They can recommend against a release, with evidence: the defects found, their severity and the risk of shipping now. The decision stays yours, with the information you need to make it quickly. A good QA engineer also suggests what would make the release safe, so the conversation moves forward instead of stopping.
Add remote QA engineers to your team.
Tell us how you release today, where defects slip through and which devices or browsers matter. We'll come back with the QA profile we'd hire, the level we suggest and the monthly fee. We hire the QA engineer in four weeks from signing.
Tell us what your QA engineer would work on.
Loading the form…
We reply within one business day.
