Skip to content
MVPeopleGroup
Back to insightsIAM

IAM consultant, engineer or architect: who do you need?

Mathijs VisserNovember 14, 20266 min read
IAM consultant, engineer or architect: who do you need?

An IAM consultant decides who should have access and why. An IAM engineer builds and runs the technology. An IAM architect makes sure the pieces fit together. Which one you need depends on the problem in front of you, so define that first and pick the job title second.

Plenty of requests simply ask for an "IAM specialist". That label covers people who design role models and people who write connectors, and those are very different jobs. Bring in the wrong one and it can take months, and a fair chunk of budget, before anyone notices.

The four IAM profiles

IAM consultant

The consultant owns the process and governance side. That means the role model and authorisation matrix, the joiner, mover and leaver process agreed with HR, and a named owner for every system who signs off on access. When an auditor raises a finding or a regulation lands, the consultant turns it into policy and working agreements. Expect to find them in meetings with the business rather than in an admin console. A background in GRC or IT audit, followed by a few substantial IAM programmes, is a strong foundation.

IAM engineer

The engineer builds. Typical work includes Microsoft Entra ID (known as Azure AD until 2023), conditional access, MFA, provisioning from the HR system, SaaS integrations and scripting to automate administration. They know the products inside out and fix what breaks. Negotiating a role model with the board is a different skill set altogether.

IAM architect

The architect designs the landscape. Which system is the source of truth for identities? How do on-premises Active Directory, Entra ID, the IGA platform, PAM and the SaaS estate connect? Which standards do you use for federation and provisioning? The architect owns a multi-year roadmap and checks that individual projects fit it. It does not matter much if they no longer build things themselves, as long as they understand what the engineers can deliver.

IGA specialist

IGA stands for identity governance and administration. An IGA specialist sets up access reviews (recertification), manages roles and segregation-of-duties rules, and produces reports an auditor can actually use. Many specialise in one platform, such as SailPoint, Saviynt or Omada. Some are functional and shape the processes; others are technical and build the connectors. Ask which kind you are talking to in the first conversation.

Matching the role to the job

For an Entra ID migration, or a clean-up of an Active Directory that has grown wild over the years, start with an engineer. If the estate is complex, with several forests, a hybrid set-up and hundreds of SaaS integrations, get an architect to draw the target state first. You only need a consultant here once it turns out nobody knows who should have which rights.

An IGA implementation works the other way round. The tool automates a process, and if the process is a mess you end up automating the mess. Have a consultant or functional IGA specialist pin down the role model and approval steps, then let the engineer build.

Audit findings about excessive rights, missing recertification or accounts belonging to people who left long ago are rarely a technical problem. What is missing is ownership, which calls for a consultant or an IGA specialist with governance experience.

If you work at a bank, insurer or other financial entity, DORA (the EU Digital Operational Resilience Act) spells much of this out. The regulatory technical standard on ICT risk management, Delegated Regulation 2024/1774, requires a unique identity for every member of staff, access granted on need-to-know and least-privilege principles, segregation of duties, and withdrawal of access rights without undue delay when someone's employment ends. Access rights have to be reviewed at least once a year, and at least every six months for systems that support critical or important functions. Meeting that takes a consultant to translate the requirements for your organisation, an IGA specialist to make the reviews workable, and proper attention to administrator accounts. I covered that last point in a piece on privileged access management under DORA.

Outside financial services, Article 21 of the NIS2 Directive lists access control policies and multi-factor authentication among the mandatory security measures. It is less prescriptive than DORA, but the upshot is the same: someone has to be demonstrably accountable for who can reach what.

The common mistake: an engineer for a governance problem

My view is that if you hire an engineer to solve a governance problem, you get technology with no owner. The engineer will set up a tidy review campaign in the tool. But who decides which manager approves which rights? And what happens when that manager ticks every box without looking? No amount of configuration fixes that.

It goes wrong the other way too. Put a consultant on a migration and you may get a polished design document while the integrations never get built and the deadline does not move.

So my advice is to write down the problem and the outcome before you write the job title. Something like: "within six months the half-yearly review of our critical systems is running and we can show it to the regulator." The right role follows from that, and candidates can tell straight away whether they fit.

One person or a small team?

Hybrids exist. In a smaller organisation on a single platform, one experienced person can often both configure and build. On a contained migration, an architect who is still hands-on can design the target state and take the first steps. On a large IGA programme that falls apart: you want the functional and technical sides covered by different people, with an architect above them.

Contractor or permanent hire? An implementation, migration or audit finding is time-bound work with a clear end, which suits an interim specialist. Day-to-day management of Entra ID or the IGA platform carries on indefinitely, so a permanent hire or a secondment makes more sense. If the identities belong to customers rather than employees, you need a different profile altogether, which I wrote about in IAM vs CIAM.

What to put in your request

  • The problem and the outcome, with a date attached.
  • The platforms involved: on-premises AD, Entra ID, the IGA tool, PAM.
  • Who in the business owns access policy, or the fact that nobody does.
  • Which rules apply, such as DORA or NIS2.
  • Whether the person needs to design, configure or build.

Not sure which profile fits? Our page on hiring an IAM specialist explains how we work, and for administrator accounts see PAM. Or give me a call or drop me an email and we will start by working out what the problem really is.

Frequently asked questions

IAM covers the identities and access of everyone in your organisation. PAM is the part that deals with administrator and emergency accounts holding elevated rights. Those accounts need extra controls: DORA requires that they are granted only when genuinely needed, that dedicated admin accounts are used where possible and that privileged access management is automated where feasible. A PAM specialist is therefore often a separate role alongside the IAM engineer.

For day-to-day management of Entra ID, often yes. On a migration, a new IGA platform or a complex hybrid estate, a generalist administrator tends to get stuck, because provisioning, federation and HR integrations are specialist work. My advice is to let an experienced IAM engineer set the project up with your own administrator working alongside, so the knowledge stays in-house once the contractor leaves.

Mathijs Visser

Mathijs Visser

Co-founder and Lead Consultant, MVPeople Group

Mathijs Visser founded MVPeople Group in 2022 and has recruited IT and cybersecurity professionals for Dutch enterprise organisations for more than 16 years. He specialises in interim CISO, IAM and GRC assignments.

Follow MVPeople Insights on Google

Add mvpeoplegroup.com as a preferred source to see our articles more often in Google's Top Stories and AI answers.

Want to know more?

Do you have questions about this article? Or would you like to discuss your specific situation? Get in touch with us, no strings attached.

READY TO FIND THE RIGHT CYBERSECURITY PROFESSIONAL?