Performance Test Engineer

Roles & Responsibilities 1. Test Strategy & Scripting Analyze non-functional requirements (NFRs) and collaborate with product owners, architects, and developers to define performance benchmarks (response time, throughput, resource utilization). Design and develop robust performance test scripts using tools like JMeter, k6, or Locust that accurately simulate real-world user behavior and complex business workflows. Maintain and modularize test scripts to ensure scalability and reusability as application features evolve. Manage test data preparation , utilizing SQL to query databases, create data sets, and ensure data integrity across different test scenarios. 2. Test Execution & Environment Management Execute various types of performance tests , including baseline, load, stress, spike, endurance/soak, and scalability tests based on project needs. Configure and manage cloud-based test environments (AWS or Azure), provisioning necessary infrastructure and ensuring they mirror production-like configurations. Set up distributed load generation infrastructure , coordinating multiple load injectors to simulate high-concurrency traffic. Monitor system health during test execution using APM tools and cloud-native monitoring services (CloudWatch/Azure Monitor) to detect infrastructure limitations. 3. Analysis, Reporting & Bottleneck Identification Analyze test results and identify performance bottlenecks across the full technology stack (frontend, backend services, database, and infrastructure). Correlate application metrics (response times, error rates) with infrastructure metrics (CPU, Memory, Disk I/O, Network) to pinpoint root causes. Author detailed performance test reports , summarizing findings, highlighting risks, and providing actionable recommendations for tuning and optimization to development teams. Present analysis and technical findings to stakeholders and engineering leadership. 4. CI/CD Integration & Automation Integrate automated performance test suites into CI/CD pipelines (Jenkins, GitLab CI, or equivalent) to enable "shift-left" testing and continuous performance feedback. Develop automated pass/fail criteria within the CI/CD pipeline to prevent performance degradation in new builds. Maintain version control for all performance test scripts and configurations (e.g., using Git). 5. Collaboration & Tuning Work closely with developers and database administrators to reproduce performance issues and verify the effectiveness of tuning efforts (e.g., query optimization, code changes, infrastructure scaling). Stay current on industry best practices in performance engineering and cloud technologies to continuously improve testing methodologies.