Join our Newsletter — 33% off our NHI Course
Home› Guides› IAM Analyst vs IAM Engineer vs IAM Architect:…
Guide Security Careers

IAM Analyst vs IAM Engineer vs IAM Architect: Roles, Skills and Progression Compared

PDF for newsletter subscribers · free to read online

← All guides
By NHI Mgmt Group, edited by Lalit Choda Updated 14 November 2026 15 min read
On this page

Job adverts use "IAM analyst", "IAM engineer" and "IAM architect" loosely, so candidates apply for the wrong level and hiring managers write job descriptions that mix three different jobs into one. The three roles sit on the same identity stack but answer different questions: the analyst asks whether access is right, the engineer makes the systems that grant it work, and the architect decides how identity should work across the organisation for the next five years. This guide compares them on responsibilities, skills, certifications, pay, progression and the growing non-human identity (NHI) and AI agent specialism. It is for people choosing or changing identity roles and for managers designing identity teams. The engineer role is covered in depth in the IAM Engineer Career Guide; this page focuses on how the three roles differ and how to move between them.

Key takeaways

  • The short answer: analysts run and assure access, engineers build and operate identity systems, architects design the target state and the standards everyone else builds to.
  • The dividing line is the artefact: analysts produce review results and tickets, engineers produce working integrations and automation, architects produce reference architectures, standards and roadmaps.
  • Protocol depth is the gate between analyst and engineer: reading a SAML assertion or an OAuth token and fixing what is wrong is the skill most analysts must add to move up.
  • Breadth and influence are the gate to architect: architects need cloud, application and business fluency, and must win arguments without line authority.
  • NHI and agent identity cuts across all three: service accounts, workload identities and AI agents need analysts to inventory them, engineers to federate them and architects to design the model.

The three roles at a glance

DimensionIAM analystIAM engineerIAM architect
Core questionIs this access correct and evidenced?How do we make this access work reliably and securely?How should identity work across the organisation?
Typical outputsAccess review results, provisioning tickets, role definitions, audit evidence, exception reportsSSO integrations, provisioning connectors, policies, scripts, pipelines, runbooksReference architecture, identity standards, target state, roadmap, design approvals
Time horizonDays to a quarter (review cycles, audits)Weeks to months (projects, sprints)One to five years
Main stakeholdersApplication owners, managers, auditors, service deskPlatform teams, developers, infrastructure, vendorsCISO, enterprise architecture, CIO, business unit heads
Hands on keyboardAdmin consoles, IGA tools, spreadsheets, reportsMost of the day: consoles, APIs, code, config as codeOccasional proofs of concept; mostly design and review
Typical entryService desk, IT administration, audit, graduate schemesAnalyst, system administrator, developer, cloud engineerSenior engineer, security architect, solution architect
Failure looks likeRubber-stamped reviews, orphaned accounts, audit findingsBrittle integrations, manual workarounds, outages at loginFragmented platforms, standards nobody follows, roadmap ignored

Titles vary. "Identity analyst", "access management analyst" and "IGA analyst" are usually the analyst role; "identity engineer" and "IAM developer" the engineer role; "identity architect" and "principal identity engineer" overlap with architect. Judge a job by its outputs, not its title.

IAM analyst: responsibilities, threat model and failure modes

What the job is: the analyst owns the correctness of access. Day to day that means processing access requests that automation cannot, running access certification campaigns, chasing managers who have not reviewed, analysing role membership for toxic combinations, investigating orphaned and dormant accounts, and producing evidence for auditors. In many organisations the analyst also handles joiner, mover and leaver exceptions: the contractor whose end date slipped, the transfer who kept old access.

The risk the analyst manages: access accumulation and drift. Movers who keep previous access, leavers whose accounts survive in applications not connected to provisioning, and privileged group membership granted "temporarily" years ago. These are the conditions attackers exploit with valid accounts, and the evidence gaps auditors flag.

Where analysts go wrong: treating reviews as a completion metric rather than a revocation metric, approving bulk certifications without context, and accepting "the application is not connected" as a reason to skip it. A strong analyst measures revocation rate, not just completion rate, and escalates the disconnected applications as an engineering backlog.

Skills that matter: joiner, mover, leaver process design; role-based access control (RBAC) and segregation of duties; IGA tooling; SQL or spreadsheet analysis on large entitlement exports; clear writing for audit evidence; and enough protocol awareness to know when a problem needs an engineer. See IAM and IGA Basics for the concepts analysts work with every day.

IAM engineer: responsibilities, threat model and failure modes

What the job is: the engineer builds and runs the identity systems. That includes onboarding applications to single sign-on with SAML 2.0 or OpenID Connect, building SCIM 2.0 provisioning, writing conditional access and authentication policies, deploying phishing-resistant MFA, automating lifecycle flows from the HR source, running directories, and increasingly managing identity configuration as code with review and rollback.

The risk the engineer manages: broken or bypassable authentication and authorisation. Applications that keep a local password path beside SSO, overly long token lifetimes, misconfigured redirect URIs, service accounts excluded from MFA policies, and provisioning that creates accounts but never disables them. Token theft and abuse of valid cloud accounts (ATT&CK T1528 and T1078.004) are the attacker techniques engineers most directly prevent and detect.

Where engineers go wrong: building one-off integrations without templates, leaving break-glass accounts untested, excluding "difficult" applications from policy, and fixing incidents by hand without automating the fix.

Skills that matter: federation protocols, a scripting language (PowerShell or Python) against identity provider APIs, cloud IAM policy in at least one major cloud, directory administration, and log analysis. The IAM Engineer Career Guide covers the engineer's skill set, tools and a worked application onboarding in detail, and the IAM Engineer Interview Questions page shows what hiring panels test.

IAM architect: responsibilities, threat model and failure modes

What the job is: the architect defines how identity should work across the whole estate and makes everyone else's work fit. Typical outputs are an identity reference architecture (authoritative sources, directories, identity providers, IGA, privileged access, secrets and workload identity, and how they connect), identity standards (which protocols for new applications, minimum authentication assurance, token lifetimes, naming), a multi-year roadmap, and design approvals for projects that touch identity. Architects also lead platform consolidation and vendor selection, and translate regulation and audit requirements into design rules.

The risk the architect manages: structural weakness. Multiple unmanaged identity stores, trust relationships nobody can draw, privileged paths that bypass the privileged access platform, and machine identities with no model at all. These are the conditions that turn a single compromised account into an estate-wide incident.

Where architects go wrong: producing target-state diagrams with no migration path, writing standards that engineering cannot meet, designing only for human identity, and losing touch with how the platforms behave in practice.

Skills that matter: breadth across access management, IGA, privileged access, CIAM and workload identity; cloud and application architecture; authorisation models (RBAC, ABAC, relationship-based); assurance frameworks such as NIST SP 800-63; cost and licensing; and the ability to persuade senior stakeholders. The wider architect path is in the Security Architect Career Guide.

Skills compared

Skill areaAnalystEngineerArchitect
Federation (SAML, OIDC, OAuth 2.0)Awareness: knows which protocol an app usesDeep: configures, decodes and debugs tokens and assertionsDeep: chooses patterns and trust models
Provisioning (SCIM 2.0, connectors)Operates and reconcilesBuilds and maintainsSets the integration standard
Access governance and rolesDeep: runs reviews, designs roles, finds toxic combinationsImplements role and policy logicDefines the governance model
Privileged accessReviews privileged membershipDeploys vaulting, just-in-time elevation and session controlsDesigns tiering and break-glass
Cloud IAMReviews entitlements in reportsWrites least-privilege policiesDesigns account and tenant structure
Scripting and automationUseful: queries and reportsEssential: APIs, config as code, pipelinesUseful: proofs of concept
Audit and regulationDeep: evidence and control testingBuilds controls that produce evidenceMaps obligations to design rules
Stakeholder influenceManagers and application ownersTechnical teamsExecutives and business units

Certifications by role

Certifications help most at the analyst-to-engineer transition, where they signal protocol and platform knowledge. Vendor certifications are listed alphabetically by vendor; facts come from each body's own pages, checked on 14 November 2026.

CertificationBodyBest fitFacts from the issuer
CIDPRO (Certified Identity Professional)IDProAnalyst, early engineerVendor-neutral foundational IAM; about 150 multiple-choice questions in three hours, online proctored; exam fee $750 with member discounts; no continuing education required at present; study material is the IDPro Body of Knowledge
Microsoft Certified: Identity and Access Administrator Associate (SC-300)MicrosoftAnalyst moving to engineer, engineerIntermediate level; skills measured cover user identities, authentication and access management, workload identities and identity governance; renewed every 12 months free via an online assessment
Okta certifications (Professional, Administrator, Consultant, Technical Architect, Developer)OktaAnalyst (Professional) through architect (Technical Architect)Okta lists these levels in order, plus Auth0 Certified Developer and specialty certifications for Workflows and Access Gateway
CISSPISC2Senior engineer, architectBroad security certification; prerequisite for ISSAP
ISSAP (Information Systems Security Architecture Professional)ISC2ArchitectRequires CISSP; ISC2 states the requirement as CISSP plus 2 years, or 7 years cumulative experience

Choose platform certifications for the platforms your target employer runs, and a vendor-neutral credential for the discipline. See the Identity Certifications Guide, the Microsoft Security Certifications Guide, Okta Certifications and the ISC2 CISSP Concentrations Guide.

Pay and progression

Official statistics do not track IAM titles separately, so pay must be read from the nearest official categories and adjusted for seniority. The US Bureau of Labor Statistics Occupational Outlook Handbook gives a median annual wage of $129,180 for information security analysts as of May 2025, with employment projected to grow 21 percent from 2025 to 2035, which it describes as much faster than average. For related occupations it lists computer network architects at a $134,050 median and computer and information systems managers at $175,140. Most IAM analyst and engineer jobs sit within or near the first category; architect roles usually pay above it, and identity leadership roles approach the management category. Outside the US, use your national statistics body and treat recruiter salary surveys as indicative only.

The relative order is consistent: analyst pay is lowest of the three, engineer pay rises quickly with protocol and automation depth, and architect pay is highest, reflecting breadth and accountability. The biggest single step is usually analyst to engineer.

MoveWhat usually unlocks itEvidence to show
Service desk or admin to IAM analystProcess discipline, attention to detail, IGA tool exposureReduced provisioning errors, a review campaign you ran
Analyst to engineerProtocol depth, scripting, one platform certificationAn application you onboarded to SSO and SCIM end to end; an automation that replaced a manual task
Engineer to senior engineerOwning a platform, templates others reuse, incident leadershipA reusable integration pattern; an identity incident you led to root cause
Senior engineer to architectBreadth across IGA, PAM, CIAM and workload identity; writing; influenceA standard adopted across teams; a design decision record; a migration you planned
Architect to identity leadershipBudget, team building, executive reportingA funded multi-year roadmap and its delivered milestones

Not everyone should become an architect. Many organisations now offer a principal engineer track that keeps senior people hands-on with comparable seniority. Analysts with strong audit skills often move sideways into governance, risk and compliance instead; see the GRC Analyst Career Guide.

The NHI and AI agent identity specialism

Service accounts, API keys, OAuth clients, workload identities and AI agents now make up a large and fast-growing share of identities in most estates, and they break assumptions built for people: no manager to certify them, no HR record to drive the leaver process, and credentials that live in code and pipelines. Each role has a distinct part in fixing that.

RoleNHI and agent identity workSkills to add
AnalystInventory machine identities, assign a human owner to each, run ownership attestation, flag unused and over-privileged accountsOwnership models, attestation campaigns, reading cloud entitlement reports
EngineerReplace static secrets with workload identity federation and short-lived credentials, vault and rotate what remains, scope OAuth clients and agent permissionsWorkload identity federation, SPIFFE concepts, secrets managers, OAuth delegation and token exchange
ArchitectDesign the machine and agent identity model: issuance, trust domains, delegation from humans to agents, lifecycle and auditAgent identity standards, cross-cloud trust, authorisation for delegated actions

This is where demand is moving fastest and where few candidates have experience, so a demonstrable NHI project is a strong differentiator at every level. Start with the Service Account Security Guide, the NHI Ownership Guide, the Workload Identity Federation Guide and the Agentic AI Identity Guide.

Which role fits you: decision guidance

  • Choose analyst if: you like process, evidence and finding what is wrong in large data sets, and prefer working with people across the business over writing code. It is the most accessible entry point.
  • Choose engineer if: you enjoy making systems work, debugging, scripting and seeing an integration go live. Expect on-call duty, because login outages are visible to everyone.
  • Choose architect if: you already have engineering depth, enjoy writing and debate, and are comfortable being accountable for decisions whose results appear years later.

Small versus large organisations: in a small organisation one person often does all three jobs, which is excellent experience but makes titles meaningless; expect "IAM engineer" to include reviews and architecture. In a large organisation the roles are split, sometimes further into access management, IGA, PAM, CIAM and workload identity teams, and the architect may cover only one of those domains.

Worked scenarios

Scenario 1, analyst to engineer: an analyst running quarterly reviews notices the same twenty applications appear as "not connected" every cycle. Instead of logging exceptions, they learn SCIM, pair with an engineer to connect two of the applications, and script a report that ranks the rest by user count. Six months later they hold SC-300 or an Okta administrator certification, depending on the employer's platform, and move into an engineer role with a concrete integration story to tell.

Scenario 2, engineer to architect: a senior engineer is asked to move two hundred service accounts off static passwords. Rather than fixing them one by one, they write a short standard (workload identity federation first, vaulted rotating secrets second, exceptions approved and time-boxed), get it adopted by three platform teams, and present the risk reduction to the security leadership. That standard is the first architecture artefact in their portfolio.

Scenario 3, building a team: a manager with budget for three hires in a 5,000-person organisation hires one analyst for governance and audit, one engineer for access management and automation, and gives an existing senior engineer architecture responsibility for half their time. A single "IAM specialist" advert asking for all three skill sets would have attracted few qualified candidates.

How to move up: a step-by-step plan

  1. Map your current outputs: list what you produced in the last quarter and compare it with the outputs column for the next role.
  2. Close the core skill gap first: protocols and scripting for analysts; breadth, writing and cost awareness for engineers.
  3. Pick one platform and one discipline credential: a vendor certification for your platform plus a vendor-neutral one.
  4. Deliver one visible project: an end-to-end integration, an automation, or an adopted standard; machine identity projects stand out.
  5. Write it up: a design note or post-incident review shows the thinking hiring panels look for.
  6. Test the move internally first: shadow the next role or take a stretch assignment; if it does not suit you, returning is easy.

Measuring progress

For individuals and managers, track evidence rather than tenure:

  • Analyst: revocation rate in reviews, orphaned accounts closed, audit findings closed.
  • Engineer: applications onboarded to SSO and provisioning, manual tasks automated, secrets replaced by federation.
  • Architect: standards adopted, design reviews completed, identity platforms consolidated, roadmap milestones delivered.
  • Team: share of human and machine identities with an owner and automated lifecycle.

Common failure patterns

  • One advert for three jobs: asking a single hire to run reviews, build integrations and set strategy produces burnout or a mismatch.
  • Analysts stuck as ticket processors: no route to engineering skills means the best analysts leave.
  • Engineers promoted to architect for tenure: deep platform skill without breadth or writing produces designs nobody adopts.
  • Architects detached from operations: target states that ignore how the platforms behave in practice.
  • Machine identity left to nobody: service accounts fall between the IAM team, platform teams and developers, with no role accountable.

Decision checklist

  • Do the job's main outputs match analyst, engineer or architect, whatever the title says?
  • Can you decode a SAML assertion and an OAuth token today? If not, that is your next skill for engineering.
  • Have you delivered one identity project end to end that you can explain in an interview?
  • Do you hold one platform certification relevant to your target employer and one vendor-neutral credential?
  • Can you point to a standard or design others adopted? That is the architect test.
  • Have you done any service account, workload identity or agent identity work?

Practitioner checklist

  • Write job descriptions by outputs: reviews and evidence, integrations and automation, or standards and roadmap.
  • Give analysts a funded route into engineering, including protocol training and paired work.
  • Require engineers to template and automate repeated integrations.
  • Assess architect candidates on adopted standards and migration plans, not diagrams alone.
  • Assign explicit ownership of non-human and agent identity across all three roles.
  • Use official statistics for pay benchmarks and treat surveys as indicative.
  • Offer a principal engineer track alongside the architect track.

Standards and references

Related NHI Mgmt Group resources: Cybersecurity Careers Guide, Identity Security Programme Guide, Privileged Access Management Guide, OAuth 2.0 and OpenID Connect Guide.

PDF for subscribers

Take this guide with you

Every section, table and checklist in one PDF, with links to the sources and related guides. Subscribe to our weekly NHI & AI Identity Journal and we’ll email you a download link.

Free weekly newsletter

Subscribe to the NHI & AI Identity Journal

The latest on NHI and Agentic AI security – articles, research, breaches, news and events every week.

Bonus 33% off our NHI Course when you subscribe.

NHIMG Editorial Note
Researched and written by the NHI Mgmt Group editorial team using AI tools, under the editorial direction of Lalit Choda. Facts are drawn from the sources listed on this page and checked by our automated quality process. Last updated 14 November 2026. Spotted an error? Use our contact page.
NHI Mgmt Group, the independent authority on Non-Human Identity, IAM and Agentic AI security. nhimg.org

PDF Downloads for Newsletter Subscribers

Get the guide

Enter your details and we’ll email you a download link.

The full guide is free to read online. The PDF is a thank you for subscribing.

Fill in all fields marked * and tick the PDF box to continue.