Dedicated performance test engineers for your offshore team.
Offshore performance test engineers in Chiang Mai and Bangkok, working full time on your roadmap and managed by us. A performance test engineer finds the point where your system slows down or fails, well before your users reach it on a launch day.
One agreement and one fixed monthly fee, with a service delivery manager in Thailand who runs your team day to day.
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 discipline as one delivery team.
One Performance Test Engineer, assigned to your product and fully managed.
We assign a Performance Test Engineer to your team full time and run everything around them: a service delivery manager who answers for the work, training and coaching, the office and equipment, and HR and payroll. The price below is for a mid-level Performance Test Engineer; junior and senior levels are priced in your proposal, and how the monthly fee is built explains the arithmetic.
From price
One mid-level Performance Test Engineer, full time, everything below included. All 27 things included ››
- Performance test engineer From USD 3,300 per month
-
Service
We manage and develop the team
- A service delivery manager who runs the team and answers for 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 specialist
-
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 own 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 Performance Test Engineer does on a dedicated QA and testing team.
They work with your own developers and infrastructure team, using your analytics to model traffic and your monitoring to show where time goes under load.
Performance Test Engineer skills and technologies
-
Load, stress, spike and endurance testing modelled on realistic traffic rather than round numbers.
-
Profiling and bottleneck analysis across application, database and infrastructure layers.
-
Establishing performance baselines so CI catches a regression before production does.
-
Capacity modelling ahead of a known traffic event, so infrastructure is sized before the day arrives.
-
Setting performance budgets in CI so a slow regression fails a build.
Performance Test Engineer seniority levels.
Mid-level to senior. Performance work often takes part of a specialist's week within your QA team, stepping up around launches and migrations. Seniority is one of the inputs into how the monthly fee is built.
When your team needs a Performance Test Engineer.
Usually brought in ahead of a major launch or migration, then kept on in your QA team to run performance baselines. Performance test engineers join as part of a dedicated QA and testing team at Azendo. It is usually a targeted addition for companies that hire a dedicated development team ahead of a launch, a migration or a seasonal peak.
What we look for in a dedicated Performance Test Engineer.
We look for engineers who can build a load model from your analytics and read a flame graph as well as a load test report. They should explain a bottleneck to your own developers with the evidence that proves it.
A remote Performance Test Engineer's first three months on your team.
- Weeks 1 to 2Studying your traffic patterns and architecture, and running a baseline load test.
- Weeks 3 to 6Finding the first bottlenecks across application, database and infrastructure.
- Months 2 to 3Adding performance budgets to CI and preparing for your next launch or migration.
Questions about adding a Performance Test Engineer to your team.
When should we run performance testing?
Before a launch, before a migration and before any expected traffic peak, and then as a baseline in your pipeline, so slowdowns show up in the build that caused them. Running tests early is far cheaper than finding the limit on launch day, when every minute of slowness costs customers.
What if we don't know our expected traffic?
We model it from your analytics, your growth plans and comparable launches, and agree a target together. The tests then measure something that matters, such as response time at twice your current peak. As real traffic arrives, the model is updated and the tests follow it.
Add remote performance test engineers to your team.
Tell us your roadmap and your stack, and we'll come back with the right profile, the capacity and a start date. You can also talk to a service delivery manager first.
Tell us what your performance test engineer would work on.
Loading the form…
We reply within one business day.
