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 →

Security QA: market

Data as of November 19, 2026: 20 open Security QA jobs, 33% remote among jobs that state a work format. Source: Zorky, updated daily.

Security QA — security testing engineer: embeds vulnerability checks into the quality control process and SDLC (software development lifecycle). This is a bridge between QA and information security (AppSec). Security QA answers the question "are there vulnerabilities in the application that an attacker can exploit" — in addition to functional "does the feature work correctly". Important to distinguish roles: Security QA embeds regular security testing into the development and release process; Penetration Tester conducts deep attack simulations (see /research/security/pentest); AppSec Engineer is responsible for application security overall — processes, architecture, threat modeling (see /research/security/appsec). Security QA — the most accessible entry point from testing into the highly-paid security area. Role family: Security QA Engineer (general — security testing in QA process), Application Security Tester, QA with DevSecOps lean (embedding security checks in CI/CD). Foundation of knowledge — OWASP Top 10 (typical web app vulnerabilities: injections, broken access control, XSS, insecure authentication etc.), OWASP API Security Top 10, OWASP ASVS (verification standard). Stack 2026: DAST (dynamic analysis — testing a running application): OWASP ZAP, Burp Suite (main tool of the security tester). SAST (static code analysis): Semgrep, SonarQube, Checkmarx, CodeQL. SCA (dependency analysis for known vulnerabilities): Snyk, Dependabot, OWASP Dependency-Check, Trivy. Other: Nuclei (template scanner), Nmap, sqlmap, Postman (API security testing), DevSecOps integration (security checks in CI/CD — shift-left). Top stack: ci/cd, devops, python, azure, agile. Among jobs with a stated work format, 33% are remote. Security QA — narrow but strategically advantageous specialization: paid above regular QA and opens the road to security.

Data as of:

Key numbers for the Security QA market: open jobs, median salary, observed talent pool and remote share.

20
open jobs — by job title, reposts merged
33%
remote

The Security QA market currently has 20 open roles, 18 of them freshly observed.

Among jobs with a stated work format, 33% are remote. Security testing well done remotely (stand access by VPN); part of financial and government sector prefers office / hybrid.

⚠ salary known for 4 of 20 jobs; remote share from 15 with a stated format; 18 counted as fresh observations; trend and hiring difficulty are not shown

Timeline: postings and sources

How many Security QA 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-017
2026-06-086
2026-06-153
2026-06-223
2026-06-292
2026-07-062
2026-07-1312
2026-07-204
2026-07-270
2026-08-033
2026-08-100
2026-08-170
2026-08-240
2026-08-311
2026-09-070
2026-09-140
2026-09-212
2026-09-284
2026-10-053
2026-10-1215
2026-10-193
2026-10-265
2026-11-023
2026-11-097

Active sources per week

Sources over the period: 28. ▲ — 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-012
2026-06-082
2026-06-152
2026-06-222
2026-06-292
2026-07-062
2026-07-132
2026-07-204
2026-07-270
2026-08-032
2026-08-100
2026-08-170
2026-08-240
2026-08-311
2026-09-070
2026-09-140
2026-09-212
2026-09-282
2026-10-053
2026-10-128
2026-10-193
2026-10-265
2026-11-023
2026-11-096
New sources connected: Jul 20 +4 · Oct 12 +5 · all weeks (14) in the table
WeekNew sourcesNew postings
Jun 22+23
Jun 29+12
Jul 6+22
Jul 13+212
Jul 20+44
Aug 3+13
Aug 31+11
Sep 21+12
Sep 28+14
Oct 5+13
Oct 12+515
Oct 19+23
Oct 26+15
Nov 2+23

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 — Security QA. 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-0172
2026-06-0862
2026-06-1532
2026-06-2232
2026-06-2922
2026-07-0622
2026-07-13122
2026-07-2044
2026-07-2700
2026-08-0332
2026-08-1000
2026-08-1700
2026-08-2400
2026-08-3111
2026-09-0700
2026-09-1400
2026-09-2122
2026-09-2842
2026-10-0533
2026-10-12158
2026-10-1933
2026-10-2655
2026-11-0233
2026-11-0976

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 Security QA.

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 — Security QA. 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 Security QA 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 demand20
Open demand20
Observed supply— not published

Security QA — narrow but stably growing specialization. Drivers 2026: growth of cyberattacks and incidents, tightening of regulator requirements (especially in RF), DevSecOps mainstream and shift-left security, shortage of security specialists. Demand concentrates in fintech, cybersecurity and government sector.

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

Which countries have the most open Security QA jobs.

Demand geography

countryjobsshare
India425%
Singapore318.8%
United States212.5%
Poland212.5%
Switzerland16.3%
Norway16.3%
France16.3%
Brazil16.3%
Philippines16.3%

Leader by Security QA job count — India (4 positions). Demand concentrates in fintech / banks, cybersecurity vendors, government sector and large products. International companies hire Russian-speaking Senior Security QA / AppSec on full-remote.

⚠ job counts only: salary by country is not published

Chart data
Demand geography — Security QA. Block data table. A missing value is not zero; units and sample are stated in the metric description.
CountryJobs
IN4
SG3
US2
PL2
CH1
NO1
FR1
BR1
PH1

Which technologies are most often required in the same job as Security QA.

Used together with

python
945%
cloud
735%
java
420%
aws
420%
azure
315%
active directory
315%
gcp
210%
burp suite
210%

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

Top stack Security QA 2026: DAST — OWASP ZAP, Burp Suite (main tool); SAST — Semgrep, SonarQube, Checkmarx, CodeQL; SCA — Snyk, Dependabot, Trivy, OWASP Dependency-Check; scanners — Nuclei, Nmap, sqlmap; DevSecOps integration in CI/CD. Foundation of knowledge more important than tools: OWASP Top 10 and API Security Top 10, OWASP ASVS / WSTG, HTTP and web technologies, authentication and cryptography, Python for automation.

Common pairs: Burp Suite + OWASP Top 10, ZAP + CI/CD (DAST in pipeline), Semgrep + Snyk (SAST + SCA), SAST + DAST + SCA in one pipeline (DevSecOps). Learning roadmap: QA base → web and HTTP → OWASP Top 10 → practice on grounds (Juice Shop, PortSwigger Academy) → Burp Suite / ZAP → SAST / DAST / SCA → DevSecOps → authentication and cryptography → Python.

Chart data
Used together with — Security QA. Block data table. A missing value is not zero; units and sample are stated in the metric description.
NameCount
python9
cloud7
java4
aws4
kubernetes4
azure3
active directory3
gcp2
devsecops2
burp suite2
nessus2
sql2

How many Security QA jobs there are at each level, from junior to principal.

Demand by grade

gradejobs
senior4
principal2
junior1
middle1
lead1

Pure Junior vacancies few — come from functional / automated QA. Career flow: QA → Security QA → AppSec Engineer / Penetration Tester / DevSecOps — each step raises salary. Security QA — the most accessible entry from testing to expensive security area.

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

Chart data
Demand by grade — Security QA. Block data table. A missing value is not zero; units and sample are stated in the metric description.
LevelCount
senior4
principal2
junior1
middle1
lead1

Who hires the most for Security QA and how concentrated demand is among the largest companies.

Employers

Demand is spread across 18 employers. The largest accounts for 5.6%, the top ten for 55.6%; the remaining 44.4% is long tail.

largest 5.6%2nd–3rd 11.1%4th–10th 38.9%the rest 44.4%
sharevalue
top-15.6%
top-316.7%
top-1055.6%
long tail44.4%

⚠ 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 Security QA jobs from.

Where Zorky sees this market

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

Security QA vacancies: hh.ru («security QA» / «security testing specialist» / «application security engineer»), Habr Career, getmatch, LinkedIn (international segment), Telegram (security and AppSec communities). Real market is wider than exact search — security responsibilities are often embedded in vacancies «QA Engineer» and «AppSec Engineer».

Chart data
Where Zorky sees this market — Security QA. Block data table. A missing value is not zero; units and sample are stated in the metric description.
ClassNameEnglish nameCountShare
atsATS и карьерные сайтыATS & career sites110.55
boardджоб-борды и агрегаторыjob boards & aggregators70.35
telegramTelegramTelegram20.1

The newest Security QA jobs from company career sites.

Recent openings

All jobs →

Latest open Security QA 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: 9.

Direction: QA / Testing

Related specializations

Inside Security QA: Security QA Engineer (general — security testing in QA process), Application Security Tester, QA with DevSecOps lean (embedding security checks in CI/CD). Adjacent roles — Penetration Tester and AppSec Engineer (cross-link to /research/security/pentest and /research/security/appsec). Comparison of QA specializations — in the bar below.

API QAQA AutomationManual QAMobile QAPerformance / LoadSDET

Frequently asked questions

The most common questions about Security QA: pay, grades, tools (ZAP / Burp / SAST / DAST / SCA), Security QA vs Penetration Tester vs AppSec Engineer, OWASP Top 10 and shift-left security, SAST vs DAST vs SCA, remote, companies, how to start, Senior skills. Answers recompute automatically.

What tools are most often required from Security QA?

Top-5: ci/cd, devops, python, azure, agile. DAST (dynamic analysis — attack on running application): OWASP ZAP (free, open-source), Burp Suite (main working tool of security tester — proxy, scanner, manual attacks). SAST (static code analysis for vulnerable patterns): Semgrep (popular, simple rules), SonarQube, Checkmarx, CodeQL (GitHub). SCA (third-party library analysis for known vulnerabilities — CVE): Snyk, Dependabot, OWASP Dependency-Check, Trivy (also containers). Scanners and utilities: Nuclei (template checks), Nmap (network scanning), sqlmap (SQL injections), Postman / Burp for API security testing. DevSecOps: embedding SAST / DAST / SCA in CI/CD pipeline (shift-left). Knowledge more important than tools: OWASP Top 10 and API Security Top 10, OWASP ASVS / WSTG (testing methodology), understanding of web technologies and HTTP, basics of cryptography and authentication (OAuth / JWT / sessions), threat model. Useful scripting (Python) for check automation.

Security QA vs Penetration Tester vs AppSec Engineer — what's the difference?

Three adjacent roles at the intersection of QA and security. Security QA — embeds regular security testing into development and release process: runs SAST / DAST / SCA, checks features for typical vulnerabilities (OWASP Top 10), logs security defects on par with functional. Works inside QA / SDLC, focus — not to miss known vulnerability classes in each release. Penetration Tester — conducts deep attack simulations: looks for ways to break in, exploitation chains, non-standard vectors; works in campaigns (per project / period), writes report with confirmed findings. Deeper, more creative, more expensive (see /research/security/pentest). AppSec Engineer (Application Security) — responsible for application security systematically: processes, policies, threat modeling, security architecture, developer training, tool selection and implementation, secure SDLC (see /research/security/appsec). Boundary: Security QA — "security as part of QA process"; Pentester — "deep break-in check"; AppSec — "building security of development overall". Career flow usually: QA → Security QA → AppSec Engineer or Penetration Tester. Security QA — the most accessible entry to this chain from testing.

What are OWASP Top 10 and shift-left security?

OWASP (Open Worldwide Application Security Project) — non-profit community creating open materials on application security. OWASP Top 10 — regularly updated list of ten most critical categories of web application vulnerabilities: for example, broken access control, injections (including SQL injections and XSS), insecure configuration, vulnerable components, authentication errors, cryptographic failures and others. This is the basic "dictionary" of Security QA — what must be known and checked. There's also OWASP API Security Top 10 (for API), OWASP ASVS (security verification levels standard), OWASP WSTG (testing methodology). Shift-left security — the "shift to the left" principle: check security not at the end (before release or after), but as early as possible in the lifecycle — at the code and build stage. In practice this is DevSecOps: SAST / SCA scanning runs automatically in CI/CD on every commit, DAST — on test stand, vulnerabilities are caught before prod, when they're cheap to fix. Security QA precisely embeds these automatic checks into the pipeline — this is the core of modern approach to secure development 2026.

SAST vs DAST vs SCA — how do they differ and why all three?

Three complementary types of automated security analysis. SAST (Static Application Security Testing) — static analysis of source code for vulnerable patterns, without running the application. Pros — catches problems early (at code stage), points to specific line. Cons — many false positives, doesn't see runtime and configuration problems. Tools: Semgrep, SonarQube, Checkmarx, CodeQL. DAST (Dynamic Application Security Testing) — dynamic analysis of running application from outside, as an attacker would do (sends malicious requests, watches reaction). Pros — finds real exploitable problems, sees runtime and configuration. Cons — needs deployed application, doesn't point to code line, covers only what it reached. Tools: OWASP ZAP, Burp Suite. SCA (Software Composition Analysis) — analysis of third-party dependencies (libraries, packages) for known published vulnerabilities (CVE). Critical because most of modern application code is other people's libraries. Tools: Snyk, Dependabot, Trivy, OWASP Dependency-Check. Why all three: they cover different layers — own code (SAST), application behavior (DAST), third-party code (SCA) — and none replaces the others. Mature Security QA / DevSecOps process integrates all three in CI/CD; manual check and pentest complement automation where it's blind (logical vulnerabilities, complex chains).

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 Security QA career in 2026?

The best path to Security QA is through regular testing plus accumulating security knowledge (this is a convenient bridge from QA to the expensive security area). Roadmap: 1) QA base — test design, types of testing, bug reports (if not already working as tester). 2) Web technologies and HTTP — how requests / responses, headers, cookies, sessions, REST / API work; without this it's impossible to test security. 3) OWASP Top 10 — learn each category: what it is, how to find, how to defend; then OWASP API Security Top 10. 4) Practice on training grounds — OWASP Juice Shop, DVWA, PortSwigger Web Security Academy (free and excellent — teaches right on Burp Suite), TryHackMe, Hack The Box. 5) Burp Suite and OWASP ZAP — master as main tool (PortSwigger Academy is ideal for this). 6) SAST / DAST / SCA — understand the difference and try Semgrep, ZAP, Snyk. 7) DevSecOps — how security checks are embedded in CI/CD. 8) Basics of authentication and cryptography — OAuth, JWT, sessions, hashing. 9) Scripting — Python for automation. Resources: PortSwigger Web Security Academy (must, free), OWASP materials (Top 10, WSTG, Cheat Sheets), courses (Otus «Application Security», HackerU, profile programs), certifications (as orientation — eJPT for entry, further Burp Suite Certified Practitioner, OSCP — for moving into pentest). In Security QA resume practical findings and solved labs are valued, not only tool list.

How many open jobs are in this sample?

The published sample contains 20 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 Security QA need?

Senior Security QA combines engineering discipline of testing with expertise in security. Vulnerabilities: deep knowledge of OWASP Top 10 and API Security Top 10 — not at the list level but understanding the mechanics of each (how it's exploited, how to find, how to defend), classes of logical vulnerabilities and access control problems. Tools: expert command of Burp Suite (including manual attacks, not only scanner) and OWASP ZAP; SAST / DAST / SCA (Semgrep, SonarQube, Snyk, Trivy) and, most importantly, ability to filter out false positives. Web and protocols: confident understanding of HTTP, REST / GraphQL, authentication and sessions (OAuth, JWT, SSO), basics of cryptography. DevSecOps: design and embedding of security checks in CI/CD (shift-left), security gates, work with vulnerabilities as managed flow. Threat modeling: basic threat modeling — understanding where the system's attack surface is and what to check first. Process: building security testing in SDLC, methodology (OWASP WSTG / ASVS), triage and prioritization of findings by real risk. Programming: code reading (for SAST results and vulnerability understanding), Python scripting for automation. Infrastructure: basics of networks, containers (Docker / Kubernetes) and clouds — attack surface is wider than application. Communication: ability to explain to developers the essence of vulnerability and risk, teach team secure coding, without alarmism prioritize. English — mandatory (OWASP, CVE, reports, international market). Senior Security QA effectively works at the intersection with AppSec — this is the natural next step of career.

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.