Performance Testing Engineer
Performance Testing Engineers need precise English to document test strategies, report bottlenecks to stakeholders, and define SLA thresholds in CI/CD pipelines. This path covers load test terminology, latency percentile notation, and the language of capacity planning discussions. You will practise writing test plans, interpreting results, and communicating performance regressions clearly.
Topics covered
- Load Test Types
- Latency Percentiles
- Bottleneck Analysis
- CI/CD Performance Gates
- Scripting & Tooling Vocabulary
- SLA & SLO Language
Vocabulary spotlight
4 terms every Performance Testing Engineer should know in English:
The number of requests a system processes per unit of time, typically expressed in requests per second (RPS)
"After tuning the connection pool, throughput increased from 800 to 1,400 RPS under the same load profile."
The 99th percentile response time, meaning 99% of requests complete within this duration
"Our SLA requires p99 latency to remain below 200 ms during peak traffic, but the soak test revealed it spiked to 480 ms after two hours."
The load level at which a system's throughput stops increasing and response times begin to degrade
"The stress test identified the saturation point at roughly 2,000 concurrent users, beyond which error rates climbed sharply."
To deliberately limit the rate of requests or resource consumption to prevent overload
"The API gateway was configured to throttle inbound traffic to 500 RPS per client to protect downstream services during the spike test."
📚 Vocabulary Reference
Key terms organised by category for Performance Testing Engineers:
Load Test Types
Latency & Throughput
Bottleneck & Capacity
Tooling
Recommended exercises
Real-world scenarios you'll practise
- Presenting a load test summary to a product manager who needs to understand why the release is being blocked by a p99 regression.
- Writing a Confluence page that documents the soak test methodology, acceptance criteria, and remediation plan for the infrastructure team.
- Participating in a post-incident review and articulating how a missed performance gate caused the production degradation.
- Negotiating SLA thresholds with a client's technical architect during a pre-sales proof-of-concept engagement.