The brief
The client needed QA engineers who would work as part of their own team for the long term: testing new code as it landed, keeping regression testing on schedule before releases, and keeping the project's documents in order.
What we did
- Tested the latest code changes as the developers delivered them.
- Ran regression testing before releases, including over weekends when a release needed it.
- Tracked project documents alongside the testing.
- Reported results to the client's team throughout.
How it went
Both engineers stayed on the project for more than five years, more than 21,000 hours between them, and both contracts closed with 5.0 ratings.
The client's reviews single out three things: flexibility around release weekends, attention to the project's needs, and the effort that went into testing and reporting. Those are the habits that make a QA engineer part of the team rather than a supplier.
In the Client's Words
"He was also flexible in working weekends to get regression testing done."
"Many kudos to him for his efforts and drive for quality."
What This Means for You
This is our dedicated QA model in practice: engineers who learn your product, work to your release rhythm, and stay.
See Dedicated QA Options