Manual testing
Test cases run by hand on real devices and browsers.
Home / Technology / Hire developers / QA testers
QA testers · Manual and automated testing · USA and Canada
PromotEdge International lets businesses in the USA, Canada and other markets hire QA testers from our team. They test web and mobile apps by hand and with automated tests, and report bugs your developers can act on. By the hour, part-time or full-time, in your tools and release process, under your lead. Our delivery team is in India.
Bugs found before your customers find them.
In short
Hire a QA tester before a big release, for regular regression testing, or to start automating the tests your team runs by hand. Take one by the hour in blocks of 40 hours, part-time at 80 hours a month, or full-time at about 160.
On an existing product or a new release.
Test cases run by hand on real devices and browsers.
The same checks run before every release, so old features do not break.
Automated tests for the flows that matter most.
Clear steps, screenshots and severity, written for your developers.
iOS and Android apps checked across screen sizes and OS versions.
Keyboard use, screen readers and contrast tested against WCAG.
Tools we work with: the testing and automation tools your team uses. We match the tester to them, and the technical test checks it before you meet anyone.
Brands we have worked with
Work delivered from India. Results are shared one to one, under NDA.
We use these details only to reply to you.
Rather talk now?
A rough note through the form on what you sell and what needs to change.
How people find you today, where inquiries get lost, then a call in your working day.
The work, who does it and how it is measured. Nothing starts until you approve it.
Our team in India does the work, with calls set in your working hours.
Every number we report shows its source and date range, and we travel to our clients every 3 to 4 months.
Stand-up in your overlap hours; the week's release scope and test plan agreed.
New features tested and bugs logged on your board.
Regression run on the release candidate.
Sign-off report for the release, and automation added for repeated checks.
Every tester passes four checks before you meet them: a technical test, a code review, a spoken interview in English and a reference check. Then you interview them yourself.
Test cases and bug reports they have written, read for clarity and coverage.
A small feature tested and reported, reviewed by a senior colleague.
A spoken interview in English, and a reference check with people they have worked for.
You interview the tester about your stack and your work, and approve them before they start.
Pick by how much QA work you have.
| Question | Hourly | Part-time | Full-time |
|---|---|---|---|
| Fits when | Testing before a few big releases a year | Regular releases with a light test load | A product that ships every week |
| Same tester | We aim for it | We aim for it | We aim for it |
| What you pay for | The hours worked, in blocks of 40 | 80 hours a month | About 160 hours a month |
| How long you commit | No lock-in | Month to month | Month to month |
QA testers check that software does what it should before users see it, by hand and with automated tests. ISTQB is a widely used certification scheme for software testers. We say which testers hold which skills when we propose someone, and you interview them.
By the hour or part-time: fit the hours to how much QA work you have. See hourly developers for how hours are agreed and logged. Hourly work is bought in blocks of 40 hours, and part-time is a steady 80 hours a month.
Want the work built for you instead? See our software testing services page, outsourced web development or all our software development services.
We do not publish rates. We quote after we understand the role.
You see the rate and the terms in writing before anything starts. Every engagement is covered by an NDA, and the contract assigns the code and every deliverable to you once paid for; we keep no rights in it.
Yes. You buy hours in blocks of 40 and use them on the tasks you approve. See hourly developers for how it works.
Yes, by the hour or for a short block of time before a release.
The tools your team already uses. We match the tester to them, and the technical test checks that skill before you meet anyone.
Yes. You talk to the tester about your work before anything is signed. You approve every tester before they start.
Hourly work is bought in blocks of 40 hours. Part-time is 80 hours a month, and full-time about 160 hours a month. Every engagement runs month to month, with no long lock-in.
Yes. The first week is a paid trial on a real task from your backlog, so you can judge the tester before you go on.
Tell us, and we replace them within 10 business days at no extra cost.
Hourly work is bought in blocks of 40 hours; part-time is 80 hours a month and full-time about 160 hours a month, all month to month with no long lock-in. Every engagement is covered by an NDA, and the contract assigns the code and every deliverable to you once paid for; we keep no rights in it. You interview and approve every person before they start, and the first week is a paid trial on a real task. The people you hire are online at least 4 hours a day inside US Eastern time. If someone is not the right fit, we replace them within 10 business days at no extra cost. Every developer passes four checks: a technical test, a code review, a spoken interview in English and a reference check (for designers, a practical design test and a review of past work take the place of the first two). You get an estimate before work starts, hours go into a shared weekly timesheet that you approve before we bill, and the block you buy is your monthly cap unless you add hours in writing. Staff augmentation ends on 30 days' notice, with a handover.
Our testers work from India and are online at least 4 hours a day inside US Eastern time, with the rest of the overlap agreed to suit your day. We are available round the clock, 24x7, as per your location.
A real person reads every message and replies.
Four kinds of work. One plan.