JMeter Performance Test Engineer

[mike]

Title: JMeter Performance Test Engineer

Remote

1^st round:  Coding Interview(Video will be recorded and shared with the client)

2^nd round:  1 hour of Coding Interview with the Client

 





Skills	No. of Years of Experience	Detailed Write up
Total No. of Years of Experience
No. of Years as a Handson JMeter Performance Engineer (Min 7-10 years)  Not looking for Managers or Architects
Which year did you last work in JMeter and how many years of continuous experience do you have in JMeter.
Must have Groovy/Bean Shell Scripting
Must have test Plans, Correlation, Parameterization, Assertions, Distributed Load Execution
No. of years in Load Modeling.  Experience designing and executing load, stress, soak, spike, and scalability tests.  Must have handson experience.
Must have experience with the ability to define and track performance metrics such as latency, throughput, error rates, and concurrency.
Must have experience integrating CI/CD Pipelines
Must have experience with Azure DevOps (ADO) pipelines, automated performance runs, dashboards, reporting, and work‑item tracking.
Must have good working knowledge of Git for branching, merging, pull requests, and repository management
Strong experience with Application Insights, including metrics, logs, dependency tracking, failures, and KQL queries.
Familiarity with APM tools such as Dynatrace, New Relic, AppDynamics, or Azure Monitor.
Understanding of REST APIs, JSON payload structures, authentication, and use of tools such as Postman.
Working knowledge of Azure components like App Service, APIM, Azure SQL/Cosmos DB, autoscaling, and networking fundamentals.
Ability to prepare and manage test data, identify environment gaps, and work through technical dependencies.
Understanding of root‑cause analysis, telemetry review, debugging issues, and identifying bottlenecks across app, service, and DB layers.
Organized and detail‑oriented with strong analytical and problem‑solving abilities.
Ability to produce clear performance reports with insights, charts, trends, and recommended optimizations.
Strong collaboration skills to work effectively with developers, architects, DevOps, QA, and product teams.
Good communication skills to articulate findings, risks, and recommendations to both technical and non‑technical partners.
Self‑starter with the ability to take ownership of tasks, work independently, and proactively identify performance risks or improvements.