QA Performance Engineer at NationsBenefits, LLC
—
Jul 12, 2026
—
Jul 21, 2026
What this job asks for AI summary
A performance testing engineering role focused on designing and running load, stress, endurance, and spike tests primarily with Apache JMeter against web applications, REST APIs, and microservices. The position involves analyzing bottlenecks across application, database, and infrastructure layers, integrating tests into CI/CD pipelines, and collaborating with development and infrastructure teams to resolve performance issues. Suits someone with solid hands-on performance engineering experience and familiarity with APM tooling.
Mid level · 4+ years · National
“or” means any one of them counts — you don't need all of them.
We read this from the posting text with AI. Skim the description below before ruling yourself out.
How this req sits in the market our data
Rare in this occupation — lead with these, and say what you built with them.
Most people in this occupation already list these. Still required — just not what gets you shortlisted.
What the occupation pays Median $106,594 (middle half $82,076–$136,109).
Estimated from BLS employment for this occupation and area, per-skill prevalence across our listing corpus, and published wage benchmarks — as of Jul 28, 2026. It is a model, not a headcount.
Why we read it this way (5)
The posting lists multiple office locations across Florida, California, Pennsylvania, Tennessee, Texas, Utah, and India, but does not specify a primary work location or remote eligibility — CBSA and state are left blank accordingly.
The 4–6 year experience range maps to a Mid-level band; the role has no title-level modifier and the scope (executing tests, integrating into CI/CD, collaborating with other teams) is consistent with an independent mid-career contributor rather than a senior engineer owning a domain.
APM tools (Dynatrace, AppDynamics, New Relic, Grafana, Prometheus) are listed with 'such as' / 'familiarity with' language in the Required Skills section; the qualifier signals the specific tool is interchangeable, so the requirement is treated as a hard gate on APM capability but the individual tools are marked preferred with alternatives.
CI/CD pipeline integration is a hard gate; the specific platforms (Jenkins, Azure DevOps, GitHub Actions, GitLab CI) are listed as interchangeable options and are marked preferred with alternatives capturing all named peers.
Groovy and BeanShell are listed as interchangeable scripting options within JMeter — emitted as one skill with BeanShell as the alternative.
Read the full posting
The employer publishes the full description on their own site — read it there ↗. Or sign in to read it here — it's free, and it also lets you track this application.