Senior IAM Engineer

Identity & Access Management Engineer (with Actual AI Chops)

Coventry + Home

Let’s get this out of the way: this isn’t an IAM role for someone who once reset a password and now identifies as a “security professional”.

This is for someone who knows their way around Microsoft Entra ID, Active Directory, identity governance, and - crucially - AI‐driven IAM without breaking into a sweat.

If your idea of AI is asking ChatGPT to write a PowerShell script, this won’t be your happy place.

What you’ll actually be doing

You’ll be the person who can look at identity telemetry and see patterns the rest of us miss. You’ll design and lead AI‐driven IAM initiatives, build controls that actually reduce risk, and help us drag identity governance into the future - not just patch the past.

You’ll work with engineers, product managers, security teams, analysts, architects, and the occasional stakeholder who still thinks “the cloud” is just someone else’s computer. You’ll mentor, coach, unblock, architect, and occasionally explain why “just give them admin rights” is not a strategy.

The non‐negotiables

If you don’t have these, you’ll hate the job and we’ll hate hiring you:

• Identity & Access Management principles - authentication, authorisation, RBAC/ABAC/PBAC, lifecycle management, Zero Trust.
• AI in IAM - hands‐on experience designing or leading AI‐driven initiatives in IAM or cybersecurity.
• Identity telemetry analysis - logs, access data, sign‐in patterns, the whole messy lot.
• Microsoft Entra ID mastery - users, groups, service principals, app registrations, tenants, objects, attributes, Conditional Access, MFA, passwordless, access packages, governance.
• Active Directory engineering - GPOs, LDAP, OU design, hybrid identity, tiering, DC recovery.
• Identity governance tooling - Saviynt, SailPoint, or similar.
• Agentic AI governance - lifecycle, controls, risk reduction.
• Threat landscape awareness — and how AI can help detect and mitigate it.
• Ability to turn vague stakeholder wishes into actual requirements engineers can build.
• Ability to mentor, coach, and raise the bar for the team.
• Ability to communicate complex things without sounding like a textbook.

The “nice to have but we won’t cry if you don’t” list

• AI/ML for identity analytics - anomaly detection, risk‐based access, intelligent access reviews.
• Microsoft security tooling - Sentinel, Log Analytics, Azure Monitor.
• Ethical AI - because using AI in security without ethics is how Netflix documentaries get made.
• Privileged Access Management exposure.
• Data governance - especially where AI models consume identity data.
• Relevant certifications - Microsoft, CISSP, CISM, AI/data analytics, etc.

Who this role is actually for

Someone who:

• Has a strong technical mindset and doesn’t crumble when faced with complexity.
• Can make sound architectural decisions without needing a committee of 12.
• Removes blockers instead of creating them.
• Builds trust with engineers, security teams, and business stakeholders.
• Is committed to continuous learning because IAM + AI evolves faster than job titles.

Who this role is not for

• People who think AI will “replace all security jobs”.
• People who want to “own IAM” but don’t want to talk to stakeholders.
• People who think Entra ID and Active Directory are basically the same thing.
• People who still say “we’ve always done it this way”.

If you’re still reading and haven’t self‐eliminated, you might actually be the person we’re looking for.