We use technical cookies and Zorky's de-identified visit log. Yandex Metrica (data is stored on servers in Russia) runs only with your consent. We never sell data. More about cookies and statistics.
Zorky is in test mode — everything is free. Jobs and company pages are open to everyone; links to postings and your personal feed open after you sign up. Sign up →

Performance / Load: market

Data as of November 19, 2026: 76 open Performance / Load jobs, 33% remote among jobs that state a work format; median advertised salary $9,583/mo (from 5 postings that state a salary). Source: Zorky, updated daily.

Performance / Load Testing — load and performance testing engineer: checks how the system behaves under load — throughput, latency, scalability, stability under prolonged and peak load. Unlike functional testing (does the feature work correctly) performance engineer answers the question "does the system work fast and reliably enough at N concurrent users". Role family: Performance / Load Testing Engineer (general — load scenarios and analysis), Performance QA (load testing as part of QA process), Performance Engineer (deeper — optimization, capacity planning, at the intersection with development and SRE — see /research/devops/sre). Types of load testing: load test (normal load), stress test (beyond capacity — where it breaks), soak / endurance test (prolonged load — memory leaks), spike test (sharp surge), scalability test (how it grows with resources). Stack 2026: k6 (modern tool from Grafana Labs, scenarios in JavaScript — dominant 2024–2026), JMeter (classic, Apache — still massively used), Gatling (on Scala — high performance), Locust (on Python), Yandex.Tank (relevant in CIS), Artillery, BlazeMeter / LoadRunner / NeoLoad (enterprise). Observability / APM (results analysis — half the work): Grafana + Prometheus, Datadog, New Relic, Dynatrace, Elastic / OpenTelemetry. CI/CD integration (performance tests in pipeline), profiling, finding bottlenecks (DB, CPU, memory, network, blocking). Metrics: RPS / TPS, latency percentiles (p50 / p95 / p99), error rate, throughput, resource utilization. Top stack: ci/cd, cloud, jmeter, grafana, java. Among jobs with a stated work format, 33% are remote. Performance — narrow but well-paid specialization: one of the most expensive QA branches, borders backend development and SRE.

Data as of:

Key numbers for the Performance / Load market: open jobs, median salary, observed talent pool and remote share.

76
open jobs — by job title, reposts merged
$9,583
median $/mo
33%
remote

The Performance / Load market currently has 76 open roles, 65 of them freshly observed. Median salary $9,583/mo.

Among jobs with a stated work format, 33% are remote. Load testing well suits remote (load from cloud, analysis on APM dashboards).

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

Timeline: postings and sources

How many Performance / Load postings appeared each week since Jun 1, and from how many sources. The lower chart 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 per week

Chart data
New postings per week. Block data table. A missing value is not zero; units and sample are stated in the metric description.
PeriodNew postings per week
2026-06-011
2026-06-081
2026-06-151
2026-06-2210
2026-06-297
2026-07-065
2026-07-139
2026-07-2017
2026-07-276
2026-08-037
2026-08-109
2026-08-173
2026-08-246
2026-08-316
2026-09-074
2026-09-1410
2026-09-219
2026-09-286
2026-10-055
2026-10-1258
2026-10-1915
2026-10-2619
2026-11-0212
2026-11-0924

Active sources per week

Sources over the period: 62. ▲ — a week with a large batch of new sources.

Chart data
Active sources per week. Block data table. A missing value is not zero; units and sample are stated in the metric description.
PeriodActive sources
2026-06-011
2026-06-081
2026-06-151
2026-06-224
2026-06-296
2026-07-064
2026-07-136
2026-07-2010
2026-07-274
2026-08-034
2026-08-107
2026-08-173
2026-08-246
2026-08-314
2026-09-073
2026-09-143
2026-09-215
2026-09-286
2026-10-055
2026-10-1211
2026-10-1910
2026-10-2613
2026-11-029
2026-11-0916
New sources connected: Jul 20 +7 · Nov 9 +8 · all weeks (19) in the table
WeekNew sourcesNew postings
Jun 8+11
Jun 15+11
Jun 22+410
Jun 29+57
Jul 6+25
Jul 13+59
Jul 20+717
Aug 3+27
Aug 10+29
Aug 24+36
Aug 31+16
Sep 7+24
Sep 28+36
Oct 5+35
Oct 12+358
Oct 19+315
Oct 26+519
Nov 2+112
Nov 9+824

The current week is not over yet and is not shown: an incomplete week would look like a drop.

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.

Chart data
Timeline: postings and sources — Performance / Load. Block data table. A missing value is not zero; units and sample are stated in the metric description.
WeekNew postings per weekActive sources
2026-06-0111
2026-06-0811
2026-06-1511
2026-06-22104
2026-06-2976
2026-07-0654
2026-07-1396
2026-07-201710
2026-07-2764
2026-08-0374
2026-08-1097
2026-08-1733
2026-08-2466
2026-08-3164
2026-09-0743
2026-09-14103
2026-09-2195
2026-09-2866
2026-10-0555
2026-10-125811
2026-10-191510
2026-10-261913
2026-11-02129
2026-11-092416

Remote work over time

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

Remote postings, %

Chart data
Remote postings, %. Block data table. A missing value is not zero; units and sample are stated in the metric description.
PeriodRemote
2026-07-2036.4
2026-07-27—
2026-08-03—
2026-08-10—
2026-08-17—
2026-08-24—
2026-08-31—
2026-09-07—
2026-09-140
2026-09-21—
2026-09-28—
2026-10-05—
2026-10-1265
2026-10-1920
2026-10-2640
2026-11-0227.3
2026-11-0923.5

The series starts on Jul 20: there is no data before that.

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

Chart data
Remote work over time — Performance / Load. Block data table. A missing value is not zero; units and sample are stated in the metric description.
WeekRemote
2026-06-01—
2026-06-08—
2026-06-15—
2026-06-22—
2026-06-29—
2026-07-06—
2026-07-13—
2026-07-2036.4
2026-07-27—
2026-08-03—
2026-08-10—
2026-08-17—
2026-08-24—
2026-08-31—
2026-09-07—
2026-09-140
2026-09-21—
2026-09-28—
2026-10-05—
2026-10-1265
2026-10-1920
2026-10-2640
2026-11-0227.3
2026-11-0923.5

Clean market: hiring index

The same 7,505 employer job boards; the posting count comes from the board itself. Connecting new sources does not move this index — it shows the market, not our coverage. This is the whole panel market, not just Performance / Load.

Hiring index, Oct 16 = 100

Chart data
Hiring index, Oct 16 = 100. Block data table. A missing value is not zero; units and sample are stated in the metric description.
PeriodHiring index
2026-10-16100
2026-10-17100.03
2026-10-1899.76
2026-10-1999.68
2026-10-2099.27
2026-10-2198.6
2026-10-2299.07
2026-10-2397.4
2026-10-2497.41
2026-10-2697.33
2026-10-2796.76
2026-10-2896.21
2026-10-2995.17
2026-10-3095.13
2026-10-3193.65
2026-11-0193.33
2026-11-0292.67
2026-11-0392.65
2026-11-0492.41
2026-11-0592.13
2026-11-0690.44
2026-11-0790.48
2026-11-0890.45
2026-11-1090.29
2026-11-1190.22
2026-11-1390.12
2026-11-1489.7
2026-11-1589.68
2026-11-1689.62
2026-11-1888.91
2026-11-1988.02

Chain index: each day compares only boards polled on both that day and the previous one; outliers and platform-wide polling outages are excluded. Days with no comparable pairs are left blank.

Chart data
Clean market: hiring index — Performance / Load. Block data table. A missing value is not zero; units and sample are stated in the metric description.
DayHiring index
2026-10-16100
2026-10-17100.03
2026-10-1899.76
2026-10-1999.68
2026-10-2099.27
2026-10-2198.6
2026-10-2299.07
2026-10-2397.4
2026-10-2497.41
2026-10-2697.33
2026-10-2796.76
2026-10-2896.21
2026-10-2995.17
2026-10-3095.13
2026-10-3193.65
2026-11-0193.33
2026-11-0292.67
2026-11-0392.65
2026-11-0492.41
2026-11-0592.13
2026-11-0690.44
2026-11-0790.48
2026-11-0890.45
2026-11-1090.29
2026-11-1190.22
2026-11-1390.12
2026-11-1489.7
2026-11-1589.68
2026-11-1689.62
2026-11-1888.91
2026-11-1988.02

How many open Performance / Load jobs there are and how many matching specialists Zorky observes.

Demand and observed supply

Chart data
Block data table. A missing value is not zero; units and sample are stated in the metric description.
MetricValue
Open demand76
Open demand76
Observed supply— not published

Performance / Load — narrow but stably in-demand QA branch. Drivers 2026: growth of high-load systems (fintech, marketplaces, government services), shift of performance tests to CI/CD (k6), SLO / error budget culture. Demand targeted — concentrates in industries with real load; few vacancies but well paid.

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

How salaries in Performance / Load jobs are distributed, in US dollars per month.

Salary distribution

P25 $9,541 · P50 $9,583 · P75 $9,958
Chart data
Block data table. A missing value is not zero; units and sample are stated in the metric description.
MetricValue
<$1k0
$1–2k0
$2–3k0
$3–4k0
$4–5k0
$5–6k0
$6–7k0
$7–8k1
$8–9k0
$9–10k3
$10–12k1
$12–15k0
$15–20k0
$20k+0
Salary in postings: base 76
  • usable for the calculation: 5 (6.6%)
  • stated but not converted to USD/month: 6 (7.9%)
  • not stated: 65 (85.5%)

One in ten postings offers under $7,507, one in ten over $11,666. Half of the postings offer between $9,541 and $9,958. Sample: 5.

⚠ percentiles from 5 salaries out of 76 jobs — a guide on a small sample

Chart data
Salary distribution — Performance / Load. Block data table. A missing value is not zero; units and sample are stated in the metric description.
MetricLower boundUpper boundCount
<$1k01,0000
$1–2k1,0002,0000
$2–3k2,0003,0000
$3–4k3,0004,0000
$4–5k4,0005,0000
$5–6k5,0006,0000
$6–7k6,0007,0000
$7–8k7,0008,0001
$8–9k8,0009,0000
$9–10k9,00010,0003
$10–12k10,00012,0001
$12–15k12,00015,0000
$15–20k15,00020,0000
$20k+20,000—0

Which countries have the most open Performance / Load jobs.

Demand geography

countryjobsshare
India1726.2%
United States1523.1%
Poland913.8%
United Kingdom46.2%
Romania23.1%
Mexico23.1%
Philippines23.1%
Russia11.5%
United Arab Emirates11.5%
New Zealand11.5%
Other countries1116.9%

Leader by Performance job count — India (17 positions). Demand concentrates in high-load industries: fintech / banks, telecom, e-commerce / marketplaces, gaming, government sector. International companies hire Russian-speaking Senior Performance on full-remote.

⚠ job counts only: salary by country is not published

Chart data
Demand geography — Performance / Load. Block data table. A missing value is not zero; units and sample are stated in the metric description.
CountryJobs
IN17
US15
PL9
GB4
RO2
MX2
PH2
RU1
AE1
NZ1

Which technologies are most often required in the same job as Performance / Load.

Used together with

cloud
3039.5%
java
2228.9%
jmeter
2228.9%
grafana
1621.1%
aws
1418.4%
k6
1215.8%
azure
1114.5%
gcp
1114.5%
docker
1013.2%

Share — how many of the 76 jobs in the Performance / Load market mention this technology. Ordered by job count, not by “strength of association”. Umbrella terms like cloud are not a specific cloud (AWS, Azure).

Common pairs: k6 + Grafana, JMeter + Grafana / InfluxDB, Gatling + CI/CD, load tool + Prometheus + APM. Learning roadmap: base (HTTP / DB / latency / percentiles) → load tool (k6 or JMeter) → load modeling → observability (Grafana + Prometheus) → bottleneck analysis → SQL → CI/CD integration → pet project with found bottleneck.

Chart data
Used together with — Performance / Load. Block data table. A missing value is not zero; units and sample are stated in the metric description.
NameCount
cloud30
java22
jmeter22
grafana16
aws14
k612
azure11
gcp11
docker10
javascript9
jenkins8
python7

How many Performance / Load jobs there are at each level, from junior to principal.

Demand by grade

gradejobs
senior31
lead9
junior1
principal1
middle1

Pure Junior vacancies few — come from functional / automated QA, backend or DevOps. Career flow: QA Automation / backend → Performance Middle → Senior → Performance Lead / Performance Engineer / SRE. One of the highest-paid QA branches.

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

Chart data
Demand by grade — Performance / Load. Block data table. A missing value is not zero; units and sample are stated in the metric description.
LevelCount
senior31
lead9
junior1
principal1
middle1

Who hires the most for Performance / Load and how concentrated demand is among the largest companies.

Employers

Demand is spread across 58 employers. The largest accounts for 4.3%, the top ten for 30.0%; the remaining 70.0% is long tail.

largest 4.3%2nd–3rd 5.7%4th–10th 20%the rest 70%
sharevalue
top-14.3%
top-310.0%
top-1030.0%
long tail70.0%

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

Which company sites and job boards Zorky collects Performance / Load jobs from.

Where Zorky sees this market

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

Performance vacancies: hh.ru («load testing engineer» / «performance QA» / «load testing engineer»), Habr Career, getmatch, Djinni, LinkedIn (international segment), Telegram (QA and performance channels). Demand concentrates in high-load industries.

Chart data
Where Zorky sees this market — Performance / Load. Block data table. A missing value is not zero; units and sample are stated in the metric description.
ClassNameEnglish nameCountShare
atsATS и карьерные сайтыATS & career sites540.7105
boardджоб-борды и агрегаторыjob boards & aggregators180.2368
telegramTelegramTelegram40.0526

The newest Performance / Load jobs from company career sites.

Recent openings

All jobs →

Latest open Performance / Load jobs — most recent 10 positions with adequate description quality. Full list — in our CRM or via the «see all» link below.

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: 8.

Direction: QA / Testing

Related specializations

Inside Performance / Load: Performance / Load Testing Engineer (general — load scenarios and analysis), Performance QA (load testing as part of QA process), Performance Engineer (optimization + capacity planning, closer to development), adjacent role — SRE (reliability and performance in production, cross-link to /research/devops/sre). Comparison with other QA specializations — in the bar below.

API QAQA AutomationManual QAMobile QASDETSecurity QA

Frequently asked questions

The most common questions about Performance / Load: pay, grades, tools (k6 vs JMeter vs Gatling vs Locust), types of load testing (load / stress / soak / spike), Performance QA vs SRE / Performance Engineer, remote, companies, how to start, Senior skills. Answers recompute automatically.

What tools are most often required from Performance engineer?

Top-5: ci/cd, cloud, jmeter, grafana, java. Load generation tools: k6 (from Grafana Labs, scenarios in JavaScript — modern dominant 2024–2026, fits great in CI/CD), JMeter (Apache — classic, GUI + large plugin set, still massively used), Gatling (on Scala / Java — high performance, code-as-test), Locust (on Python — convenient for Python teams), Yandex.Tank (relevant in CIS), Artillery (Node.js), enterprise — BlazeMeter / LoadRunner / NeoLoad. Observability / APM (analysis — half the work of performance engineer): Grafana + Prometheus, Datadog, New Relic, Dynatrace, Elastic / OpenTelemetry. Adjacent: HTTP and protocol understanding, basic SQL and slow query analysis, profilers (for JVM / Go / Python), Docker + Kubernetes, CI/CD (running load tests in pipeline), Git. Key skill — not "press a button" but design a realistic load scenario and correctly interpret metrics (latency percentiles, error rate, resource utilization).

JMeter vs k6 vs Gatling vs Locust — what to choose in 2026?

k6 — modern default choice 2024–2026: scenarios written in code on JavaScript, integrates well into CI/CD, native Grafana integration, lightweight and fast. Minus — for very complex protocols plugin ecosystem smaller than JMeter. JMeter — veteran (Apache): GUI for scenario assembly (low entry threshold), huge plugin set, support for many protocols; still massively used and often mentioned in vacancies. Minuses — heavyweight, GUI scenarios version worse in Git. Gatling — high performance of one machine, scenarios in code (Scala / Java / Kotlin DSL), beautiful reports; slightly higher entry threshold. Locust — scenarios in pure Python, convenient if team is already Python-oriented, easily extended. Strategy 2026: learn k6 as main (trend + CI/CD-friendliness), know JMeter (still a lot of it in vacancies and legacy projects). Gatling / Locust — by team context. Main thing — tool is secondary; primary is ability to model load and analyze bottlenecks.

What types of load testing exist?

Load test — system under expected normal and peak load: checking if SLA holds for latency and errors. Stress test — load beyond rated: looking for the point where system breaks, and if it breaks "gracefully" (graceful degradation) or catastrophically. Soak / endurance test — moderate load for many hours or days: catching memory leaks, log growth, connection pool exhaustion, degradation over time. Spike test — sharp load surge (sale, mailing, viral traffic): how system reacts to sudden surge and recovers. Scalability test — how performance changes when adding resources (horizontal / vertical scaling), linearly or not. Volume test — behavior with large data volumes in DB. Capacity planning — based on results, determining how many resources are needed for planned growth. Senior performance engineer picks test types by risks of specific system, not "runs everything in a row".

Performance QA vs SRE / Performance Engineer — what's the difference?

Roles are adjacent and overlap. Performance QA / Load Testing Engineer — focus on testing: designs load scenarios, runs tests before release, records if system holds SLA, logs performance defects. Works in QA process. Performance Engineer — broader: not only finds problem, but optimizes — gets into code, DB, configuration, profiles, does capacity planning; closer to development. SRE (Site Reliability Engineer) — responsible for reliability and performance of system in production: monitoring, SLO / error budget, incident management, load as part of operations (see /research/devops/sre). Boundary: Performance QA checks performance before release in test environment; SRE follows it in production; Performance Engineer connects testing with optimization. Career flow often goes Performance QA → Performance Engineer → SRE (with growth of salary and responsibility). Many vacancies mix these roles — look at responsibilities, not title.

What share of jobs are remote?

Among jobs with a stated work format, 33% are remote. Jobs without a stated format are excluded from the denominator; hybrid work is not counted as remote.

How to start a Performance engineer career in 2026?

Performance — rarely first role; more often come from functional / automated QA, backend or DevOps. Roadmap: 1) Base — how web application is structured: HTTP, client-server, DB, queues, cache, load balancers; what is latency, throughput, percentiles. 2) Load tool — start with k6 (great documentation, JavaScript) or JMeter (GUI, low threshold); learn to write realistic scenarios (not just "hit one endpoint"). 3) Load modeling — load profiles, ramp-up, think time, data correlation, parameterization. 4) Observability — Grafana + Prometheus: learn to read dashboards, understand what application and infrastructure metrics show. 5) Bottleneck analysis — where the "chokes" are: DB (slow queries, blocks, connection pool), CPU, memory and GC, network, external integrations. 6) SQL and basic DB understanding — mandatory (DB — most common bottleneck). 7) CI/CD — running load tests in pipeline. 8) Pet project: take an open application, write a load scenario on k6, raise Grafana + Prometheus, find a bottleneck, describe conclusions. Resources: k6 and JMeter documentation, book «The Art of Application Performance Testing» (Ian Molyneaux), Brendan Gregg materials on performance, load testing courses (Otus, Stratoplan, testing schools). Main thing in Performance engineer's resume — cases of found and explained bottlenecks, not list of tools.

How many open jobs are in this sample?

The published sample contains 76 open jobs after merging reposts. This is the same count shown in the main indicator. The geography section describes the sample coverage; this is not an estimate of the entire market.

What skills does a Senior Performance engineer need?

Senior Performance engineer — engineer understanding the system as a whole, not "operator of load tool". Load tools: expert command of k6 / JMeter / Gatling, design of complex realistic scenarios (correlation, parameterization, load profiles). Architecture: understanding of distributed systems structure — DB, caches, queues, balancers, microservices, external integrations; ability to build hypotheses where bottleneck will be. Bottleneck analysis — main skill: problem diagnosis in DB (slow queries, blocks, connection pools, indexes), CPU, memory and GC (for JVM / Go / .NET), network, concurrency. Observability: free work with APM (Grafana / Prometheus / Datadog / Dynatrace), building dashboards, correlating load test metrics with system metrics. SQL and DB: advanced level — DB most often is the bottleneck. Profiling: profilers for project stack, flame graphs. Capacity planning: based on results, forecasting resource needs for growth. CI/CD: automation of load tests in pipeline, performance gates. Coding: confident scripting (JavaScript / Python / Java — depends on tool). Communication: ability to explain to development and management the essence of the problem and justify recommendations with numbers. English — for international market and documentation. The main value of Senior — not a report «system held N RPS», but a specific bottleneck diagnosis and justified recommendation.

Leave a request

Describe the task and leave a contact — the request goes to our CRM and we reply at the contact you provide.

By submitting, you agree to the privacy policy.