Hi all,
Welcome to the second Job Intelligence report.
You do not need this to stay up to date with job offers and understand which profiles are most in demand.
You just need to read this. In 10 minutes, you will be up to date and ready to spot trends and better opportunities.
So, let’s go
Summary
Emerging signals
Senior and lead roles dominate identity hiring across regions.
IGA remains the strongest hiring cluster in every market.
Okta, Entra, SailPoint, and CyberArk anchor demand.
Likely next moves
More hiring around identity architecture, governance, and platform modernization.
CIAM demand grows where customer journeys drive transformation.
Automation and integration skills become stronger screening criteria.
Potential risks
Senior talent shortages could slow delivery and transformation programs.
Platform concentration may increase vendor dependency and retraining costs.
Compliance-heavy hiring may underweight innovation and customer experience.
Strategic focus areas
Build depth in IGA, PAM, authentication, and CIAM.
Prioritize platform integration, automation, and architecture capabilities.
Strengthen leadership pipeline for roadmap and governance ownership.
Time horizon
0-6 months: sustained demand for senior delivery roles.
6-12 months: more architecture and modernization mandates emerge.
12-24 months: identity leadership becomes more product-oriented.
Job market Analysis
IAM
IAM — quick read
IAM hiring in these source workbooks is mainly platform-and-governance delivery, not only policy writing.
The strongest demand sits at Mid, Senior, and Lead/Manager levels, with juniors present but clearly smaller.
IAM — general patterns
Employers repeatedly ask for people who can run identity lifecycle, provisioning, access governance, and application onboarding.
The section is strongly tied to enterprise platforms rather than generic cyber roles.
IAM jobs often sit between operations, engineering, and stakeholder-facing delivery.
IAM — skill patterns
SailPoint is the clearest US platform signal.
Entra ID / Active Directory is a recurring signal in Central Europe and UK/IE.
RBAC / roles / entitlements / access governance appears as a core design skill across markets.
Lifecycle management / JML / provisioning is a repeated requirement in the US and UK/IE material.
Automation and integrations show up most clearly in UK/IE through PowerShell/Python and connector-style work.
IAM — responsibility patterns
Operate and improve IAM stacks across Entra, AD, MFA, CyberArk, and governance tooling.
Own user lifecycle processes, including onboarding, movers/leavers, and entitlement changes.
Connect applications, systems, and directories into the IAM estate.
Translate business or regulatory requirements into IAM solutions and controls.
Deliver IAM workstreams for large clients, often with consulting, programme, or enterprise delivery expectations.
IAM — differences by level
Junior: supports provisioning, access reviews, and ticket-driven lifecycle work under established controls.
Mid: owns day-to-day IAM delivery, onboarding flows, and defined integrations with more independence.
Senior: drives design improvements, complex integrations, governance tuning, and mentoring.
Lead/Manager: owns roadmap, operating model, governance, prioritisation, and stakeholder or team leadership.
IAM — main differences by market
