Performance / Load: market

A Performance Test Engineer checks how a system behaves under load: designs scenarios, generates traffic, finds bottlenecks in code, database and infrastructure and helps remove them. We currently track 60 open positions for this role, 59 of them fresh. Most often required are JMeter, LoadRunner, Gatling or k6, scripting in Java, Scala, Python or JavaScript, monitoring and APM (Grafana, Prometheus, Dynatrace), and an understanding of networks, databases and profiling. By co-occurrence in requirements, Jmeter, Grafana, Salesforce and Jenkins appear most often. 45% of the postings allow fully remote work. Below is a live slice of the Performance Test Engineer market: geography, seniority, adjacent stack and sources.

open jobs

45%

remote

The Performance / Load market currently has 60 open roles, 59 of them freshly observed.

45% of Performance Test Engineer postings allow fully remote work; the share counts only postings that state the format.

⚠ salary known for 1 of 60 jobs; remote share from 47 with a stated format; 59 counted as fresh observations; trend and hiring difficulty are not shown

Timeline: postings and sources

How many Performance / Load postings appeared each week since 4 May, and from how many sources. The second line separates market growth from coverage growth: a jump in the week new sources were connected means we started seeing more, not that the market grew.

New postings and active sources per week

Sources over the period: 47

New sources connected: 11 May +2 · 18 May +2 · 25 May +1 · 1 Jun +1 · 8 Jun +1 · 15 Jun +1 · 22 Jun +5 · 29 Jun +6 · 6 Jul +1 · 13 Jul +4 · 20 Jul +5 · 3 Aug +2 · 10 Aug +2 · 24 Aug +2 · 31 Aug +1 · 7 Sept +2 · 28 Sept +3 · 5 Oct +3 · 12 Oct +3

Week = posting first-seen date, all statuses; postings are selected by the same rule as this page's counter. Sources are distinct collection channels; their names are not published.

Remote work over time

Share of Performance / Load postings offering fully remote work, per week.

Remote postings, %

The share is among postings that state a format (remote, hybrid, office). Weeks with fewer than 10 such postings are left blank.

Demand and observed supply: Performance / Load

Open demand	60
Observed supply	— not published

⚠ candidates matching a vacancy are not counted yet: demand and the observed pool are shown

Salary distribution: Performance / Load

The range histogram for Performance Test Engineer uses only postings with an explicit compensation range; the median is computed over the same sample.

The chart will appear once enough observations accumulate for this breakdown.

Demand geography: Performance / Load

country	jobs
US	8
PL	8
IN	8
GB	4
CY	3
RU	2
ES	2
PE	2
IE	2
UA	2

The top country for Performance Test Engineer demand is the US (8 positions).

⚠ job counts only: salary by country is not published

Used together with

cloud 25 jmeter 24 grafana 12 salesforce 12 jenkins 10 java 10 k6 10 azure 8 javascript 8 prometheus 8 aws 7 docker 6

In Performance Test Engineer requirements the most frequently named skills and technologies are Jmeter, Grafana, Salesforce and Jenkins.

Demand by grade: Performance / Load

grade	jobs
senior	18
lead	6
junior	2
principal	2

Senior-and-above is about 93% of 28 Performance Test Engineer postings with an explicit grade.

⚠ demand side only: the grade of the observed pool is unknown for most of it

Employers: Performance / Load

Demand is spread across 41 employers. The largest accounts for 15.5%, the top ten for 46.6%; the remaining 53.4% is long tail.

share	value
top-1	15.5%
top-3	27.6%
top-10	46.6%
long tail	53.4%

Performance Test Engineer openings come from 41 distinct employers.

⚠ names are not shown: staffing agencies and end employers are not yet told apart by the classifier

Where Zorky sees this market

Observed across 16 sources; the largest accounts for 21.7% — this market does not rest on a single channel.

Performance Test Engineer postings arrive mostly from ATS & career sites and job boards & aggregators.

Recent openings: Performance / Load

All jobs →

Adjacent markets

Manual QA QA Automation SDET Mobile QA Security QA API QA

⚠ adjacent markets for comparison are not defined yet

How this is measured

Vacancy: an open job that cleared the quality gate and lists at least two technologies
Observed candidate: a candidate whose stack contains this technology; an aggregate — not a single record leaves the perimeter
Matchable candidate: not counted yet
Window: jobs open at the moment the snapshot was built

About the data

Some breakdowns are hidden: their data coverage is not yet sufficient.
Statistics are shown only where the sample clears a quality gate.
A missing block does not mean a value of zero.

Breakdowns currently hidden: 9.

Data as of 2026-10-23

Frequently asked questions

Common questions about the Performance Test Engineer role — short answers from the same data slice.

What does a Performance Test Engineer do?

A Performance Test Engineer checks how a system behaves under load: designs scenarios, generates traffic, finds bottlenecks in code, database and infrastructure and helps remove them.

Which skills do Performance Test Engineer postings require?

Most often required are JMeter, LoadRunner, Gatling or k6, scripting in Java, Scala, Python or JavaScript, monitoring and APM (Grafana, Prometheus, Dynatrace), and an understanding of networks, databases and profiling. In the current slice, Jmeter, Grafana, Salesforce and Jenkins appear in requirements most often.

How does performance testing differ from functional testing?

Functional testing answers 'does it work'; performance testing answers 'will it hold': how many users and requests the system can serve, where it slows down and how it behaves at peaks.

How remote-friendly are Performance Test Engineer jobs?

45% of postings with an explicit format allow fully remote work; the slice tracks 60 open positions.

Get the full Performance / Load market details

Full role analytics — salary bands, employers, trends and available candidates. Leave a contact and we'll send the details.