IAM: market
Data as of November 19, 2026: 178 open IAM jobs, 31% remote among jobs that state a work format; median advertised salary $9,760/mo (from 24 postings that state a salary). Source: Zorky, updated daily.
IAM Engineer (Identity & Access Management) — a security specialty focused on managing identities and access: SSO (Single Sign-On), MFA, provisioning / deprovisioning, privileged access, identity governance, authorization. «Identity is the new perimeter» — central principle of the Zero Trust era 2026. Role family: IAM Engineer (general — workforce identity + SSO + MFA operations), Senior IAM Engineer (multi-system identity architecture + automation + lifecycle management), Identity Architect (org-wide IAM strategy + Zero Trust identity design + protocol expertise), PAM Engineer (Privileged Access Management specialty — CyberArk / Delinea / HashiCorp Boundary deep), IGA Engineer (Identity Governance & Administration — SailPoint / Saviynt — access certification + compliance), CIAM Engineer (Customer IAM — consumer-facing auth — Auth0 / Cognito / modern developer-first platforms), Authorization Engineer (rising 2024+ — fine-grained authorization specialty — OPA / OpenFGA / Cedar / SpiceDB). Stack 2026: Workforce IdP (Identity Providers — employee SSO): Okta (industry leader — Workforce Identity Cloud), Microsoft Entra ID (former Azure AD — dominates Microsoft-shop), Ping Identity (enterprise), OneLogin, JumpCloud (SMB-focused), Keycloak (open-source — Red Hat — popular in RF), Authentik (open-source modern — rising 2024+), Zitadel (open-source modern). Russian workforce IdP: Avanpost (IDM + FAM — leader RF), Solar inRights (IGA), Indeed Identity, RT-IAM (Rostelecom), CryptoPro (certificate-based auth). PAM (Privileged Access Management): CyberArk (industry leader — Privileged Access Manager + Conjur secrets), BeyondTrust (Password Safe + Privileged Remote Access), Delinea (former Thycotic + Centrify merger — Secret Server), HashiCorp Vault + Boundary (modern infrastructure access), Teleport (modern — SSH / Kubernetes / database access — rising 2024+), StrongDM. Russian PAM: Solar SafeInspect, Indeed PAM, Avanpost PAM, SKDPU NT (IT Bastion). IGA (Identity Governance & Administration): SailPoint (industry leader — IdentityIQ + IdentityNow), Saviynt, Microsoft Entra ID Governance, Omada, One Identity. Russian: Solar inRights, Avanpost IDM. Protocols / standards mastery: SAML 2.0 (enterprise SSO standard), OAuth 2.0 / 2.1 (authorization framework), OIDC (OpenID Connect) (authentication layer on OAuth), SCIM (System for Cross-domain Identity Management — provisioning standard), FIDO2 / WebAuthn (passwordless standard), LDAP + Kerberos (legacy directory + auth). MFA / Passwordless: FIDO2 / WebAuthn / Passkeys, YubiKey (hardware tokens — phishing-resistant), Duo Security (Cisco), Okta Verify / Microsoft Authenticator, magic links + OTP (legacy). Secrets management (overlap): HashiCorp Vault + cloud-native (AWS Secrets Manager / GCP Secret Manager / Azure Key Vault). Zero Trust identity: Conditional Access (risk-based authentication), continuous verification, device trust, identity threat detection (ITDR — Identity Threat Detection & Response — rising 2024+). Certifications: Okta Certified (Professional / Administrator / Consultant / Developer), Microsoft Identity (SC-300 Identity and Access Administrator), SailPoint certifications, CyberArk certifications (Defender / Sentry / Guardian), CIDPRO (Certified Identity Professional — IDPro). Languages: Python primary (IAM automation + SCIM connectors + custom integrations), JavaScript / TypeScript (CIAM frontend integration), bash + PowerShell (AD administration). Top stack: cloud, active directory, aws, python, azure. Among jobs with a stated work format, 31% are remote.
Data as of:
Key numbers for the IAM market: open jobs, median salary, observed talent pool and remote share.
The IAM market currently has 178 open roles, 151 of them freshly observed. Median salary $9,760/mo.
Among jobs with a stated work format, 31% are remote. IAM work primarily cloud-based (IdP consoles + SaaS + API integrations). Outsourcers — almost always remote. Russian banks + state companies — hybrid/office due to regulatory + identity-data sensitivity + security clearances (especially PAM — high-trust). International tech companies — full-remote standard. CIAM Engineers (Backend-leaning) — full-remote-friendly.
⚠ salary known for 24 of 178 jobs; remote share from 152 with a stated format; 151 counted as fresh observations; trend and hiring difficulty are not shown
Timeline: postings and sources
How many IAM 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
| Period | New postings per week |
|---|---|
| 2026-06-01 | 3 |
| 2026-06-08 | 6 |
| 2026-06-15 | 7 |
| 2026-06-22 | 9 |
| 2026-06-29 | 16 |
| 2026-07-06 | 33 |
| 2026-07-13 | 30 |
| 2026-07-20 | 21 |
| 2026-07-27 | 7 |
| 2026-08-03 | 17 |
| 2026-08-10 | 13 |
| 2026-08-17 | 15 |
| 2026-08-24 | 9 |
| 2026-08-31 | 14 |
| 2026-09-07 | 14 |
| 2026-09-14 | 18 |
| 2026-09-21 | 44 |
| 2026-09-28 | 28 |
| 2026-10-05 | 26 |
| 2026-10-12 | 82 |
| 2026-10-19 | 43 |
| 2026-10-26 | 50 |
| 2026-11-02 | 46 |
| 2026-11-09 | 39 |
Active sources per week
Sources over the period: 67. ▲ — a week with a large batch of new sources.
Chart data
| Period | Active sources |
|---|---|
| 2026-06-01 | 3 |
| 2026-06-08 | 3 |
| 2026-06-15 | 3 |
| 2026-06-22 | 4 |
| 2026-06-29 | 8 |
| 2026-07-06 | 15 |
| 2026-07-13 | 11 |
| 2026-07-20 | 12 |
| 2026-07-27 | 5 |
| 2026-08-03 | 8 |
| 2026-08-10 | 8 |
| 2026-08-17 | 8 |
| 2026-08-24 | 7 |
| 2026-08-31 | 8 |
| 2026-09-07 | 9 |
| 2026-09-14 | 9 |
| 2026-09-21 | 21 |
| 2026-09-28 | 16 |
| 2026-10-05 | 13 |
| 2026-10-12 | 20 |
| 2026-10-19 | 19 |
| 2026-10-26 | 23 |
| 2026-11-02 | 19 |
| 2026-11-09 | 25 |
New sources connected: Jun 29 +5 · Jul 6 +10 · Sep 21 +6 · Oct 12 +5 · Oct 19 +5 · all weeks (22) in the table
| Week | New sources | New postings |
|---|---|---|
| Jun 8 | +1 | 6 |
| Jun 15 | +1 | 7 |
| Jun 22 | +3 | 9 |
| Jun 29 | +5 | 16 |
| Jul 6 | +10 | 33 |
| Jul 13 | +4 | 30 |
| Jul 20 | +3 | 21 |
| Jul 27 | +3 | 7 |
| Aug 3 | +1 | 17 |
| Aug 10 | +2 | 13 |
| Aug 17 | +1 | 15 |
| Aug 24 | +1 | 9 |
| Aug 31 | +1 | 14 |
| Sep 7 | +2 | 14 |
| Sep 14 | +1 | 18 |
| Sep 21 | +6 | 44 |
| Sep 28 | +1 | 28 |
| Oct 12 | +5 | 82 |
| Oct 19 | +5 | 43 |
| Oct 26 | +3 | 50 |
| Nov 2 | +1 | 46 |
| Nov 9 | +4 | 39 |
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
| Week | New postings per week | Active sources |
|---|---|---|
| 2026-06-01 | 3 | 3 |
| 2026-06-08 | 6 | 3 |
| 2026-06-15 | 7 | 3 |
| 2026-06-22 | 9 | 4 |
| 2026-06-29 | 16 | 8 |
| 2026-07-06 | 33 | 15 |
| 2026-07-13 | 30 | 11 |
| 2026-07-20 | 21 | 12 |
| 2026-07-27 | 7 | 5 |
| 2026-08-03 | 17 | 8 |
| 2026-08-10 | 13 | 8 |
| 2026-08-17 | 15 | 8 |
| 2026-08-24 | 9 | 7 |
| 2026-08-31 | 14 | 8 |
| 2026-09-07 | 14 | 9 |
| 2026-09-14 | 18 | 9 |
| 2026-09-21 | 44 | 21 |
| 2026-09-28 | 28 | 16 |
| 2026-10-05 | 26 | 13 |
| 2026-10-12 | 82 | 20 |
| 2026-10-19 | 43 | 19 |
| 2026-10-26 | 50 | 23 |
| 2026-11-02 | 46 | 19 |
| 2026-11-09 | 39 | 25 |
Remote work over time
Share of IAM postings offering fully remote work, per week.
Remote postings, %
Chart data
| Period | Remote |
|---|---|
| 2026-06-29 | 71.4 |
| 2026-07-06 | 50 |
| 2026-07-13 | 50 |
| 2026-07-20 | 35.7 |
| 2026-07-27 | — |
| 2026-08-03 | 7.7 |
| 2026-08-10 | — |
| 2026-08-17 | 20 |
| 2026-08-24 | — |
| 2026-08-31 | 9.1 |
| 2026-09-07 | 36.4 |
| 2026-09-14 | 0 |
| 2026-09-21 | 27.8 |
| 2026-09-28 | 44 |
| 2026-10-05 | 39.1 |
| 2026-10-12 | 63 |
| 2026-10-19 | 31.4 |
| 2026-10-26 | 39 |
| 2026-11-02 | 37.8 |
| 2026-11-09 | 25.8 |
The series starts on Jun 29: 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
| Week | Remote |
|---|---|
| 2026-06-01 | — |
| 2026-06-08 | — |
| 2026-06-15 | — |
| 2026-06-22 | — |
| 2026-06-29 | 71.4 |
| 2026-07-06 | 50 |
| 2026-07-13 | 50 |
| 2026-07-20 | 35.7 |
| 2026-07-27 | — |
| 2026-08-03 | 7.7 |
| 2026-08-10 | — |
| 2026-08-17 | 20 |
| 2026-08-24 | — |
| 2026-08-31 | 9.1 |
| 2026-09-07 | 36.4 |
| 2026-09-14 | 0 |
| 2026-09-21 | 27.8 |
| 2026-09-28 | 44 |
| 2026-10-05 | 39.1 |
| 2026-10-12 | 63 |
| 2026-10-19 | 31.4 |
| 2026-10-26 | 39 |
| 2026-11-02 | 37.8 |
| 2026-11-09 | 25.8 |
Technologies over time
How the share of IAM postings mentioning each of the top technologies changed.
Postings mentioning the technology, %
Chart data
| Period | cloud | active directory | Python |
|---|---|---|---|
| 2026-09-21 | 73.1 | 11.5 | 34.6 |
| 2026-09-28 | — | — | — |
| 2026-10-05 | 42.9 | 23.8 | 38.1 |
| 2026-10-12 | 64.4 | 30.5 | 27.1 |
| 2026-10-19 | 62.5 | 46.9 | 18.8 |
| 2026-10-26 | 69.2 | 33.3 | 23.1 |
| 2026-11-02 | 63.2 | 39.5 | 28.9 |
| 2026-11-09 | 66.7 | 47.6 | 66.7 |
The series starts on Sep 21: there is no data before that.
Share among postings with a tagged stack; the series starts on Aug 10: earlier stack tags were assigned differently. Weeks with fewer than 20 tagged postings are left blank.
Chart data
| Week | cloud | active directory | AWS | Azure | Python |
|---|---|---|---|---|---|
| 2026-08-10 | — | — | — | — | — |
| 2026-08-17 | — | — | — | — | — |
| 2026-08-24 | — | — | — | — | — |
| 2026-08-31 | — | — | — | — | — |
| 2026-09-07 | — | — | — | — | — |
| 2026-09-14 | — | — | — | — | — |
| 2026-09-21 | 73.1 | 11.5 | 26.9 | 34.6 | 34.6 |
| 2026-09-28 | — | — | — | — | — |
| 2026-10-05 | 42.9 | 23.8 | 19 | 4.8 | 38.1 |
| 2026-10-12 | 64.4 | 30.5 | 50.8 | 47.5 | 27.1 |
| 2026-10-19 | 62.5 | 46.9 | 28.1 | 28.1 | 18.8 |
| 2026-10-26 | 69.2 | 33.3 | 30.8 | 33.3 | 23.1 |
| 2026-11-02 | 63.2 | 39.5 | 15.8 | 15.8 | 28.9 |
| 2026-11-09 | 66.7 | 47.6 | 33.3 | 52.4 | 66.7 |
Countries over time
How the share of IAM postings in each of the top countries changed, per week.
Postings in the country, %
Chart data
| Period | USA | UK | Poland |
|---|---|---|---|
| 2026-07-06 | 35.7 | 3.6 | 21.4 |
| 2026-07-13 | 19 | 9.5 | 33.3 |
| 2026-07-20 | — | — | — |
| 2026-07-27 | — | — | — |
| 2026-08-03 | — | — | — |
| 2026-08-10 | — | — | — |
| 2026-08-17 | — | — | — |
| 2026-08-24 | — | — | — |
| 2026-08-31 | — | — | — |
| 2026-09-07 | — | — | — |
| 2026-09-14 | — | — | — |
| 2026-09-21 | 28.2 | 15.4 | 0 |
| 2026-09-28 | 16 | 24 | 12 |
| 2026-10-05 | 38.5 | 11.5 | 0 |
| 2026-10-12 | 16.9 | 7 | 33.8 |
| 2026-10-19 | 28.9 | 5.3 | 2.6 |
| 2026-10-26 | 41.3 | 4.3 | 2.2 |
| 2026-11-02 | 31.6 | 13.2 | 5.3 |
| 2026-11-09 | 21.2 | 21.2 | 3 |
The series starts on Jul 6: there is no data before that.
Share among postings with a known country; the chart shows the five countries with the most postings over six months. Weeks with fewer than 20 postings with a known country are left blank. A rising share can mean a newly connected source in that country rather than market growth.
Chart data
| Week | USA | UK | Poland | Australia | India |
|---|---|---|---|---|---|
| 2026-06-01 | — | — | — | — | — |
| 2026-06-08 | — | — | — | — | — |
| 2026-06-15 | — | — | — | — | — |
| 2026-06-22 | — | — | — | — | — |
| 2026-06-29 | — | — | — | — | — |
| 2026-07-06 | 35.7 | 3.6 | 21.4 | 7.1 | 10.7 |
| 2026-07-13 | 19 | 9.5 | 33.3 | 23.8 | 4.8 |
| 2026-07-20 | — | — | — | — | — |
| 2026-07-27 | — | — | — | — | — |
| 2026-08-03 | — | — | — | — | — |
| 2026-08-10 | — | — | — | — | — |
| 2026-08-17 | — | — | — | — | — |
| 2026-08-24 | — | — | — | — | — |
| 2026-08-31 | — | — | — | — | — |
| 2026-09-07 | — | — | — | — | — |
| 2026-09-14 | — | — | — | — | — |
| 2026-09-21 | 28.2 | 15.4 | 0 | 15.4 | 5.1 |
| 2026-09-28 | 16 | 24 | 12 | 8 | 20 |
| 2026-10-05 | 38.5 | 11.5 | 0 | 3.8 | 19.2 |
| 2026-10-12 | 16.9 | 7 | 33.8 | 4.2 | 7 |
| 2026-10-19 | 28.9 | 5.3 | 2.6 | 2.6 | 15.8 |
| 2026-10-26 | 41.3 | 4.3 | 2.2 | 10.9 | 10.9 |
| 2026-11-02 | 31.6 | 13.2 | 5.3 | 7.9 | 5.3 |
| 2026-11-09 | 21.2 | 21.2 | 3 | 6.1 | 9.1 |
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 IAM.
Hiring index, Oct 16 = 100
Chart data
| Period | Hiring index |
|---|---|
| 2026-10-16 | 100 |
| 2026-10-17 | 100.03 |
| 2026-10-18 | 99.76 |
| 2026-10-19 | 99.68 |
| 2026-10-20 | 99.27 |
| 2026-10-21 | 98.6 |
| 2026-10-22 | 99.07 |
| 2026-10-23 | 97.4 |
| 2026-10-24 | 97.41 |
| 2026-10-26 | 97.33 |
| 2026-10-27 | 96.76 |
| 2026-10-28 | 96.21 |
| 2026-10-29 | 95.17 |
| 2026-10-30 | 95.13 |
| 2026-10-31 | 93.65 |
| 2026-11-01 | 93.33 |
| 2026-11-02 | 92.67 |
| 2026-11-03 | 92.65 |
| 2026-11-04 | 92.41 |
| 2026-11-05 | 92.13 |
| 2026-11-06 | 90.44 |
| 2026-11-07 | 90.48 |
| 2026-11-08 | 90.45 |
| 2026-11-10 | 90.29 |
| 2026-11-11 | 90.22 |
| 2026-11-13 | 90.12 |
| 2026-11-14 | 89.7 |
| 2026-11-15 | 89.68 |
| 2026-11-16 | 89.62 |
| 2026-11-18 | 88.91 |
| 2026-11-19 | 88.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
| Day | Hiring index |
|---|---|
| 2026-10-16 | 100 |
| 2026-10-17 | 100.03 |
| 2026-10-18 | 99.76 |
| 2026-10-19 | 99.68 |
| 2026-10-20 | 99.27 |
| 2026-10-21 | 98.6 |
| 2026-10-22 | 99.07 |
| 2026-10-23 | 97.4 |
| 2026-10-24 | 97.41 |
| 2026-10-26 | 97.33 |
| 2026-10-27 | 96.76 |
| 2026-10-28 | 96.21 |
| 2026-10-29 | 95.17 |
| 2026-10-30 | 95.13 |
| 2026-10-31 | 93.65 |
| 2026-11-01 | 93.33 |
| 2026-11-02 | 92.67 |
| 2026-11-03 | 92.65 |
| 2026-11-04 | 92.41 |
| 2026-11-05 | 92.13 |
| 2026-11-06 | 90.44 |
| 2026-11-07 | 90.48 |
| 2026-11-08 | 90.45 |
| 2026-11-10 | 90.29 |
| 2026-11-11 | 90.22 |
| 2026-11-13 | 90.12 |
| 2026-11-14 | 89.7 |
| 2026-11-15 | 89.68 |
| 2026-11-16 | 89.62 |
| 2026-11-18 | 88.91 |
| 2026-11-19 | 88.02 |
How many open IAM jobs there are and how many matching specialists Zorky observes.
Demand and observed supply
Chart data
| Metric | Value |
|---|---|
| Open demand | 178 |
| Open demand | 178 |
| Observed supply | — not published |
IAM — a stable premium segment with growing demand 2026. Drivers: «identity is the new perimeter» Zero Trust shift, passwordless migration, regulatory pressure (access certification audits — SOC 2 / ISO 27001 / SOX), import substitution in RF (shift to Russian IAM — Avanpost / Solar / Indeed Identity), authorization renaissance (OPA / OpenFGA / Cedar — fine-grained authz rising 2024+), CIAM growth (consumer auth as competitive differentiator — WorkOS / Clerk explosion). Russian banks dominate + Russian IAM vendors. International remote via Okta / Microsoft Entra / SailPoint / CyberArk / WorkOS.
⚠ candidates matching a vacancy are not counted yet: demand and the observed pool are shown
How salaries in IAM jobs are distributed, in US dollars per month.
Salary distribution
Chart data
| Metric | Value |
|---|---|
| <$1k | 0 |
| $1–2k | 0 |
| $2–3k | 0 |
| $3–4k | 1 |
| $4–5k | 0 |
| $5–6k | 0 |
| $6–7k | 3 |
| $7–8k | 1 |
| $8–9k | 4 |
| $9–10k | 3 |
| $10–12k | 5 |
| $12–15k | 3 |
| $15–20k | 3 |
| $20k+ | 1 |
- usable for the calculation: 24 (13.5%)
- stated but not converted to USD/month: 29 (16.3%)
- not stated: 125 (70.2%)
One in ten postings offers under $6,775, one in ten over $16,083. Half of the postings offer between $8,016 and $12,275. Sample: 24.
⚠ percentiles from 24 salaries out of 178 jobs — a guide on a small sample
Chart data
| Metric | Lower bound | Upper bound | Count |
|---|---|---|---|
| <$1k | 0 | 1,000 | 0 |
| $1–2k | 1,000 | 2,000 | 0 |
| $2–3k | 2,000 | 3,000 | 0 |
| $3–4k | 3,000 | 4,000 | 1 |
| $4–5k | 4,000 | 5,000 | 0 |
| $5–6k | 5,000 | 6,000 | 0 |
| $6–7k | 6,000 | 7,000 | 3 |
| $7–8k | 7,000 | 8,000 | 1 |
| $8–9k | 8,000 | 9,000 | 4 |
| $9–10k | 9,000 | 10,000 | 3 |
| $10–12k | 10,000 | 12,000 | 5 |
| $12–15k | 12,000 | 15,000 | 3 |
| $15–20k | 15,000 | 20,000 | 3 |
| $20k+ | 20,000 | — | 1 |
Which countries have the most open IAM jobs.
Demand geography
| country | jobs | share |
|---|---|---|
| United States | 62 | 40.8% |
| India | 16 | 10.5% |
| United Kingdom | 11 | 7.2% |
| Poland | 10 | 6.6% |
| Canada | 9 | 5.9% |
| Germany | 5 | 3.3% |
| Brazil | 5 | 3.3% |
| Philippines | 3 | 2% |
| Australia | 3 | 2% |
| Netherlands | 2 | 1.3% |
| Other countries | 26 | 17.1% |
Leader by IAM job count — the US (62 positions). Russia — banks + Russian IAM vendors (Avanpost / Solar / Indeed Identity / RT-IAM / CryptoPro / IT Bastion) + EPAM Security Practice dominate. Poland — IAM-friendly EU hub. Germany — Berlin + Munich enterprise. Large international remote via Okta / Microsoft Entra / Ping Identity / SailPoint / CyberArk / BeyondTrust / WorkOS / Auth0 / Clerk / Stytch.
⚠ job counts only: salary by country is not published
Chart data
| Country | Jobs |
|---|---|
| US | 62 |
| IN | 16 |
| GB | 11 |
| PL | 10 |
| CA | 9 |
| DE | 5 |
| BR | 5 |
| PH | 3 |
| AU | 3 |
| NL | 2 |
Which technologies are most often required in the same job as IAM.
Used together with
Share — how many of the 178 jobs in the IAM market mention this technology. Ordered by job count, not by “strength of association”. Umbrella terms like cloud are not a specific cloud (AWS, Azure).
Learning roadmap: identity fundamentals (AAA + RBAC/ABAC/ReBAC) → protocols deep (SAML + OAuth + OIDC + SCIM) → Active Directory fundamentals → workforce IdP hands-on (Okta / Entra ID / Keycloak) → MFA/Passwordless → CIAM or PAM or IGA specialization → authorization (OPA / OpenFGA) → IAM automation (Python) → certifications (Okta Certified / Microsoft SC-300 / SailPoint / CyberArk / CIDPRO).
Chart data
| Name | Count |
|---|---|
| cloud | 93 |
| active directory | 54 |
| aws | 45 |
| azure | 45 |
| python | 41 |
| terraform | 19 |
| gcp | 18 |
| java | 17 |
| kubernetes | 15 |
| javascript | 12 |
| servicenow | 11 |
| google cloud | 10 |
How many IAM jobs there are at each level, from junior to principal.
Demand by grade
| grade | jobs |
|---|---|
| senior | 68 |
| lead | 18 |
| principal | 17 |
| middle | 4 |
Junior — typical entry Sysadmin (AD admin) / Security Middle / Backend Middle + IAM focus. Career flow: Sysadmin / Security / Backend Middle (2-3 years) + IAM focus → IAM Junior (1-2 years) → Middle (2-3 years) → Senior → either Identity Architect, or PAM specialist, or IGA specialist, or CIAM Engineer (Backend-leaning), or Authorization Engineer (OPA / OpenFGA — rising).
⚠ demand side only: the grade of the observed pool is unknown for most of it
Chart data
| Level | Count |
|---|---|
| senior | 68 |
| lead | 18 |
| principal | 17 |
| middle | 4 |
Who hires the most for IAM and how concentrated demand is among the largest companies.
Employers
Demand is spread across 147 employers. The largest accounts for 4.7%, the top ten for 15.4%; the remaining 84.6% is long tail.
| share | value |
|---|---|
| top-1 | 4.7% |
| top-3 | 7.1% |
| top-10 | 15.4% |
| long tail | 84.6% |
⚠ 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 IAM jobs from.
Where Zorky sees this market
Observed across 38 sources; the largest accounts for 16.9% — this market does not rest on a single channel.
Chart data
| Class | Name | English name | Count | Share |
|---|---|---|---|---|
| ats | ATS и карьерные сайты | ATS & career sites | 127 | 0.7135 |
| board | джоб-борды и агрегаторы | job boards & aggregators | 47 | 0.264 |
| telegram | Telegram | Telegram | 4 | 0.0225 |
The newest IAM jobs from company career sites.
Recent openings
- Okta | Identity and access management software
- IAM Engineer · US
- IAM Engineer · GB
- Lead Identity Engineer - Saviynt Zuma, ISPM and Intelligence Module · IN
- Lead Identity Engineer - HashiCorp · IN
- Senior IT IAM Engineer · $12,275
- Security Engineer II - Identity and Access Management · CA
- Identity Engineer · US
Latest open IAM Engineer jobs — most recent positions in the sample (narrow pool of explicit IAM roles — real market wider due to overlap with Security / Backend / DevOps). Full list — in our CRM or via the «see all» link below. For a broader view check the security-engineer + backend pages.
Adjacent markets
IAM Engineer overlaps with Security Engineer general (IAM is one security domain — 40% overlap), Backend Engineer (CIAM auth implementation — 50% overlap in consumer context), DevOps (machine identity + secrets + service-to-service auth — 30%), Cloud Security (cloud IAM — IAM Access Analyzer / privilege management), Identity Architect (career evolution). Comparison with security-engineer/appsec/cloud-security/pentest/soc/network-security — in the SiblingSubnichesChart above.
⚠ 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: 8.
Direction: Security
Related specializations
Inside IAM Engineer: IAM Engineer (general — workforce identity + SSO + MFA operations), Senior IAM Engineer (multi-system identity architecture + automation + lifecycle management), Identity Architect (org-wide strategy + Zero Trust identity design), PAM Engineer (Privileged Access Management — CyberArk / Delinea / HashiCorp Boundary deep), IGA Engineer (Identity Governance & Administration — SailPoint / Saviynt — access certification), CIAM Engineer (Customer IAM — consumer-facing auth — Auth0 / Cognito / Clerk), Authorization Engineer (rising 2024+ — fine-grained authz — OPA / OpenFGA / Cedar / SpiceDB). Comparison with security-engineer/appsec/cloud-security/pentest/soc/network-security — in the bar below.
Frequently asked questions
The most common questions about IAM Engineer: pay (stable premium — «identity is the new perimeter»), IAM Engineer vs Identity Architect vs Security Engineer vs Backend Engineer (4-way + workforce vs CIAM split), IAM platforms 2026 decision tree (Okta vs Entra ID vs Ping vs Keycloak vs Auth0 vs WorkOS — 14 options), PAM Engineer / IGA Engineer / CIAM / Authorization Engineer specializations, remote, how to become one (4-8 months from Sysadmin AD admin / Security / Backend Middle), Senior skills (protocols mastery + workforce IdP + PAM/IGA + authorization OPA/OpenFGA + IAM automation). Answers recompute automatically.
What stack is most often required from IAM Engineer?
Top 5: cloud, active directory, aws, python, azure. Workforce IdP mastery: one of Okta (industry leader — Workforce Identity Cloud — premium knowledge) / Microsoft Entra ID (former Azure AD — dominates Microsoft-shop) / Ping Identity (enterprise) / OneLogin / JumpCloud / Keycloak (open-source Red Hat — popular RF) / Authentik (open-source modern rising) / Zitadel. Russian: Avanpost (leader RF) / Solar inRights / Indeed Identity / RT-IAM / CryptoPro. PAM (Privileged Access Management): CyberArk (leader — PAM + Conjur secrets) / BeyondTrust / Delinea (Thycotic + Centrify merger) / HashiCorp Vault + Boundary / Teleport (modern infrastructure access — rising 2024+) / StrongDM. Russian: Solar SafeInspect / Indeed PAM / Avanpost PAM / SKDPU NT (IT Bastion). IGA (Identity Governance & Administration): SailPoint (leader — IdentityIQ + IdentityNow) / Saviynt / Microsoft Entra ID Governance / Omada / One Identity. Russian: Solar inRights / Avanpost IDM. Protocols / standards mastery — must: SAML 2.0 (enterprise SSO), OAuth 2.0 / 2.1 (authorization framework — grant types, PKCE, token rotation), OIDC (OpenID Connect — authentication layer), SCIM (provisioning standard — joiner-mover-leaver automation), FIDO2 / WebAuthn (passwordless), LDAP + Kerberos (legacy directory + auth). MFA / Passwordless: FIDO2 / WebAuthn / Passkeys, YubiKey (hardware tokens), Duo Security (Cisco), Okta Verify / Microsoft Authenticator, magic links + OTP (legacy). Zero Trust identity: Conditional Access policies (risk-based authentication), continuous verification, device trust, ITDR (Identity Threat Detection & Response — rising 2024+). Secrets management (overlap): HashiCorp Vault + cloud-native. Languages: Python primary (IAM automation + SCIM connectors + custom integrations) + JavaScript / TypeScript (CIAM frontend integration) + bash + PowerShell (AD administration).
IAM Engineer vs Identity Architect vs Security Engineer vs Backend Engineer — what's the difference?
IAM Engineer (this page) — focus on identity & access management implementation: SSO + MFA + provisioning + privileged access + governance. Specialty within security. Identity Architect — Senior IAM with org-wide strategy focus: Zero Trust identity architecture design + protocol expertise + technology selection + compliance leadership. Less programming, more strategy. Career evolution from Senior IAM Engineer. Security Engineer (general) — broad coverage of all security domains (SIEM + EDR + network + IAM — but IAM is just one part). See Security Engineer (general). Backend Engineer (auth-focused) — implements authentication / authorization in product code (OAuth flows + session management + JWT handling + RBAC implementation). Not an IAM specialist, but overlap in CIAM context. Pay varies — backend tier. Workforce IAM vs CIAM split: Workforce IAM — employee identity (Okta / Entra ID — SSO for internal apps + lifecycle management) — closer to traditional IT / security. CIAM (Customer IAM) — consumer-facing auth (Auth0 / Cognito / Clerk — millions of users + scalability + UX) — closer to Backend engineering + product. These two IAM directions require different skill sets. Career pivots: Sysadmin (AD admin) → Workforce IAM Engineer — 4-8 months. Backend Engineer → CIAM Engineer — 3-6 months (auth knowledge translates). Security Engineer → IAM Engineer — 3-6 months. IAM Senior → Identity Architect — 2-4 years.
IAM platforms 2026 decision tree — Okta vs Entra ID vs Ping vs Keycloak vs Auth0 vs WorkOS?
Strengths: deep Microsoft ecosystem, Conditional Access, free tier with M365. Weaknesses: complex licensing tiers, weaker non-Microsoft app integration historically. 2) Okta (Workforce Identity Cloud) — best for multi-vendor environments + best-of-breed approach. Strengths: 7000+ pre-built app integrations (largest catalog), vendor-neutral, polished UX, strong lifecycle management. Weaknesses: premium pricing, 2022 breach reputational hit (recovered). Use case: non-Microsoft-centric orgs + want best integration coverage. 3) Ping Identity — enterprise-heavy, complex hybrid environments. Use case: large enterprises with on-prem + cloud hybrid + complex federation needs. 4) Keycloak (open-source — Red Hat) — best for self-hosted + zero-budget + technical teams. Strengths: free, full-featured (SAML + OIDC + identity brokering), customizable. Weaknesses: operational burden (you run it), steeper learning curve. Use case: budget-constrained + technical team + popular in RF context (self-hosted preference). 5) Authentik / Zitadel — open-source modern alternatives to Keycloak (better UX). Rising 2024+. 6) Russian workforce IdP (after import substitution): Avanpost (leader RF) / Solar inRights / Indeed Identity / RT-IAM — for RF-only organizations + state companies. CIAM (consumer-facing auth): 7) Auth0 (Okta-owned) — developer favorite, best DX (developer experience), extensive SDK / docs. Use case: startups → mid-market, fast time-to-market. Pricing scales aggressively at high MAU (Monthly Active Users). 8) Amazon Cognito — best for AWS-native applications. Cheap at scale. Weaknesses: clunky DX, limited customization. 9) WorkOS — B2B SSO-as-a-service — «enterprise readiness in one API» (SAML + SCIM + directory sync for B2B SaaS selling to enterprises). Rising fast 2024+ — best for B2B SaaS that needs to support enterprise customers' SSO. 10) Clerk — modern developer-friendly, React-first, beautiful pre-built UI components. Use case: modern web apps (Next.js / React), fast iteration. 11) Stytch — passwordless-first, modern API. 12) Firebase Authentication — best for mobile apps + Firebase ecosystem. 13) Ory (open-source — Kratos + Hydra + Keto) — best for self-hosted CIAM + full control. 14) SuperTokens — open-source CIAM alternative. Default 2026 recommendations: Microsoft-shop workforce → Entra ID. Multi-vendor workforce → Okta. Zero-budget self-hosted workforce → Keycloak (or Authentik / Zitadel for better UX). RF-only org → Avanpost / Solar. Consumer app CIAM → Auth0 (fast) or Clerk (modern React) or Cognito (AWS-native). B2B SaaS needing enterprise SSO → WorkOS. Self-hosted CIAM → Ory or SuperTokens. Authorization layer (separate from authentication): OPA (general policy) / OpenFGA or SpiceDB (relationship-based, Zanzibar-style) / Cedar (AWS) / Oso or Permit.io (embedded).
What share of jobs are remote?
Among jobs with a stated work format, 31% are remote. Jobs without a stated format are excluded from the denominator; hybrid work is not counted as remote.
How is PAM Engineer different from a regular IAM Engineer?
IAM Engineer (general) — focus on workforce identity broadly: SSO + MFA + provisioning + access management for all users. PAM Engineer (Privileged Access Management specialty) — focus specifically on privileged accounts (administrator / root / service accounts — highest-risk identities). Day-to-day: 1) PAM platform deployment (CyberArk / BeyondTrust / Delinea / HashiCorp Boundary / Teleport), 2) Privileged credential vaulting (secrets rotation + checkout / checkin workflows), 3) Session recording + monitoring (record admin sessions for audit + forensics), 4) Just-In-Time (JIT) privileged access (grant admin rights temporarily, auto-revoke), 5) Privilege escalation control + least-privilege enforcement, 6) Service account / machine identity management (non-human identities — often 10× more than human accounts), 7) Break-glass access procedures (emergency access). Why a specialty: privileged accounts — primary target of ransomware + APT attacks (compromise admin → game over). Regulatory mandate (PCI-DSS / SOX / 187-FZ require PAM controls). IGA Engineer (Identity Governance & Administration specialty) — another specialty: focus on access governance — access certification campaigns (periodic review «does this person still need this access?»), Segregation of Duties (SoD) policy enforcement, access request workflows, compliance reporting (SOC 2 / ISO 27001 / SOX access audits). Tools: SailPoint / Saviynt. CIAM Engineer — consumer-facing auth (millions of users — scalability + UX + Backend-engineering-leaning). See decision tree above. Authorization Engineer (rising 2024+) — fine-grained authorization specialty (OPA / OpenFGA / Cedar / SpiceDB) — «who can do what on which resource» at scale. Career choice: general IAM if breadth + workforce identity, PAM if high-trust + privileged-account-deep + security-critical, IGA if governance + compliance + audit-focused, CIAM if consumer-scale + product engineering, Authorization Engineer if fine-grained authz + modern policy engines.
How to start in IAM in 2026?
Roadmap: 1) Identity fundamentals — authentication vs authorization vs accounting (AAA), identity lifecycle (joiner-mover-leaver), least-privilege principle, RBAC vs ABAC vs ReBAC (Role / Attribute / Relationship-Based Access Control). 2) Protocols deep — must: SAML 2.0 (assertions + bindings + SP-initiated vs IdP-initiated flows), OAuth 2.0 / 2.1 (grant types — authorization code + PKCE + client credentials; token types; common pitfalls), OIDC (OpenID Connect) (ID tokens + UserInfo + discovery), SCIM (provisioning standard). Book: «Solving Identity Management in Modern Applications» Yvonne Wilson / Abhishek Hingnikar (canonical — OAuth/OIDC for developers). 3) Active Directory fundamentals — AD structure (forests / domains / OUs), Group Policy, Kerberos authentication, LDAP. Book: «Active Directory» Brian Desmond (O'Reilly). 4) Workforce IdP hands-on — pick one: Okta (Okta Developer free tier — best for learning + Okta Certified Professional cert) or Microsoft Entra ID (Azure free tier + SC-300 cert) or Keycloak (self-host free — learn protocols deeply). Set up SSO for test apps. 5) MFA / Passwordless — understand FIDO2 / WebAuthn / Passkeys (passwordless future), set up YubiKey, configure Conditional Access policies. 6) CIAM hands-on (if consumer-facing track) — Auth0 free tier or Clerk or Keycloak. Implement login flows in test app (React / Next.js). 7) PAM hands-on (if privileged-access track) — HashiCorp Vault (free self-host) + Boundary, or Teleport (free tier). Understand secrets vaulting + session recording + JIT access. 8) IGA basics (if governance track) — SailPoint training (SailPoint University) — access certification + SoD concepts. 9) Authorization (rising 2024+) — OPA (Open Policy Agent — Rego language) + OpenFGA (relationship-based — read Google Zanzibar paper) + Cedar (AWS). Build fine-grained authz demo. 10) IAM automation — Python for SCIM connectors + custom integrations + IdP API automation (Okta API / Microsoft Graph API). 11) Certifications path: Okta Certified (Professional → Administrator → Consultant / Developer) or Microsoft SC-300 (Identity and Access Administrator) — foundational. Advanced: SailPoint certifications / CyberArk certifications (Defender → Sentry → Guardian) / CIDPRO (Certified Identity Professional — IDPro — vendor-neutral). 12) Pet project portfolio: a) full SSO setup (Keycloak / Okta) with multiple apps + SAML + OIDC + SCIM provisioning; b) CIAM demo app with passwordless (WebAuthn / Passkeys); c) fine-grained authorization demo (OpenFGA / OPA). Document on GitHub. RF courses: BI.ZONE Cybersecurity Academy, Otus «IAM» / Security courses, Avanpost training (Russian IAM), Solar training (inRights IGA / SafeInspect PAM). International (eng): Okta Learning (free — best for Okta track), Microsoft Learn SC-300 (free), IDPro Body of Knowledge (vendor-neutral — best foundational resource, free), Auth0 docs + blog (excellent CIAM learning), «OAuth 2 in Action» Justin Richer / Antonio Sanso (Manning — protocols deep). Books-must: «Solving Identity Management in Modern Applications» Wilson / Hingnikar, «OAuth 2 in Action» Richer / Sanso, IDPro Body of Knowledge (online). Conferences: Identiverse (largest identity conference), Gartner IAM Summit, European Identity & Cloud Conference (EIC). Sysadmin (AD admin) / Security Middle / Backend Middle + IAM focus → IAM Junior — 4-8 months.
How many open jobs are in this sample?
The published sample contains 178 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 IAM Engineer need?
Senior IAM Engineer owns the full identity & access management lifecycle + technical leadership. Protocols mastery deep: SAML 2.0 (assertions + bindings + SP/IdP-initiated flows + signing / encryption), OAuth 2.0 / 2.1 (all grant types + PKCE + token rotation + DPoP + common vulnerabilities — token leakage / CSRF / redirect manipulation), OIDC (ID tokens + claims + discovery + session management + back-channel logout), SCIM (provisioning automation — joiner-mover-leaver), FIDO2 / WebAuthn (passwordless implementation), Kerberos + LDAP (legacy directory). Workforce IdP mastery: one of Okta / Microsoft Entra ID / Ping deeply — SSO architecture, lifecycle management automation, Conditional Access / risk-based policies, app integration (7000+ catalog for Okta), custom SAML / OIDC app onboarding, IdP federation (multi-IdP scenarios). Directory services mastery: Active Directory deep (forest / domain / OU architecture + Group Policy + replication + AD security — Kerberoasting / DCSync awareness), Entra ID hybrid (AD Connect / Cloud Sync). PAM mastery (if PAM track): CyberArk / BeyondTrust / Delinea / HashiCorp Boundary / Teleport — privileged credential vaulting, session recording, JIT access, service account management, break-glass procedures. IGA mastery (if governance track): SailPoint / Saviynt — access certification campaigns, Segregation of Duties (SoD) policy, access request workflows, role mining, compliance reporting. CIAM mastery (if consumer track): Auth0 / Cognito / Clerk — scalable consumer auth (millions of MAU), passwordless UX, social login, progressive profiling, account security (credential stuffing protection + bot detection). Authorization mastery (rising 2024+): OPA (Rego policy language), OpenFGA / SpiceDB (relationship-based — Google Zanzibar model), Cedar (AWS), fine-grained authz design at scale. Zero Trust identity: Conditional Access architecture, continuous verification, device trust, ITDR (Identity Threat Detection & Response) integration. IAM automation: Python deep (SCIM connectors + IdP API automation — Okta API / Microsoft Graph API + custom integrations), Terraform for IaC IAM (Okta Terraform provider / Entra Terraform). Identity security: identity attack awareness (phishing / MFA bombing / token theft / OAuth consent phishing / Golden SAML), passwordless migration strategy, MFA hardening. System design for IAM: design enterprise SSO architecture on a whiteboard, design CIAM for millions of users, design Zero Trust identity architecture, design privileged access workflows. Compliance frameworks: SOC 2 + ISO 27001 + SOX (access controls) + PCI-DSS + 152-FZ + 187-FZ — access certification + audit support. Soft: ADRs writing for IAM decisions, technical writing (IAM architecture docs), cross-team collaboration (Security / IT / Backend / DevOps / HR teams — IAM touches everyone), executive communication (identity strategy to CISO / CIO), mentoring Middle IAM Engineers. English for Senior+ MUST — protocols specs (SAML / OAuth / OIDC RFCs) + vendor docs (Okta / Microsoft / SailPoint / CyberArk) + community (IDPro / Identiverse) are English-language. Certifications: Okta Certified Consultant / Developer, Microsoft SC-300, SailPoint / CyberArk certifications, CIDPRO (vendor-neutral). Optional bonus: open-source contributions to IAM tools (Keycloak / Ory / OpenFGA / Authentik), conference talks (Identiverse / EIC), authorization specialty depth (OpenFGA / SpiceDB — rising rare skill) — sharply increase market value for frontier-IAM companies (Okta / WorkOS / Authzed) hiring.
Leave a request
Describe the task and leave a contact — the request goes to our CRM and we reply at the contact you provide.