Agent Identity and Permissions Architect
Also called Agent Identity & Permissions Architect · Non-Human Identity Engineer
This person designs how AI agents prove who they are and what they may do. They keep access narrow as agent numbers grow, so one compromised agent cannot become a company-wide breach.
What they do
The work starts with a simple question: what is this agent, who does it act for, and what may it touch? From there, the architect designs identity and credential issuance for agents, including short-lived tokens, scoped permissions and clear delegation from a human or service. They write patterns that engineering teams can adopt, review how agents call tools and protocols, and test for abuse such as prompt-driven privilege escalation. They set up revocation, logging and audit trails. When something goes wrong, they help trace which agent did what, and shut it down quickly.
What a strong hire delivers
In the first months, a strong hire maps every place agents currently hold credentials and shows where access is too broad. They produce a workable identity model for agents, with agreed rules for issuing, scoping and revoking access. They get at least one high-risk agent onto short-lived, least-privilege credentials. They also leave behind logging that lets the team answer who acted, for whom, and why.
How you can tell they are good
Ask them to design access for an agent that reads email, calls internal tools and acts for a user. Listen for delegation, scoping, expiry and revocation before anything else. Good candidates talk about how the model can be manipulated, not only how a person can. Ask what they would log. Worry if they reach for one shared service account or treat agents as ordinary users.
Why it is hard to fill
The title barely exists yet. The work is usually done by someone labelled IAM engineer, security architect or platform security lead, with agents as a side project. Few people combine deep identity knowledge with hands-on experience of how agents misbehave. Demand is high and the best candidates are often well placed where they are, so approaches need a clear, specific reason to move.
Where to find them
Look first at senior identity and access management engineers who have moved into workload or machine identity. Application security engineers, threat detection specialists and security researchers with agent or red teaming experience are the other main route. They sit in large enterprises, IAM and security vendors, cloud platform teams and AI product companies. Titles often say non-human identity, zero trust or security architecture.
Indicative pay
Not enough published evidence yet to give a fair range for this role, which is common for work this new. We benchmark it for you as part of a search.
Interview questions for an Agent Identity and Permissions Architect
- Describe an identity or access system you designed for non-human actors. What broke first once it was in use?
A strong answer is specific about workloads, service accounts or tokens, and honest about failures such as sprawl, stale credentials or over-broad scopes. Worry if they only describe policy documents or cannot name a real incident or lesson.
- How would you give an agent access to a user's calendar and email without giving it everything the user can do?
Look for delegation, narrow scopes, short-lived credentials, user consent and clear audit. Good answers separate the agent's identity from the user's. Worry if they suggest reusing the user's own session or a broad shared key.
4 more questions, with what a strong answer covers, are in the Role Kit.
Job description you can post
We are building products where AI agents act on behalf of people and systems. We need someone to design how those agents are identified, authenticated and limited in what they can do. You will set the model that engineering teams follow as agent use grows.
What you will do
- Design identity and credential issuance for AI agents
- Define least-privilege and delegation patterns for agent access to tools and data
- Build revocation, logging and audit so agent actions can be traced
- Review agent and tool integrations for privilege escalation and misuse
- Test controls with red team exercises against agent behaviour
- Support incident response when an agent is compromised or misbehaves
- Give engineering teams clear patterns and guidance they can adopt
What you will bring
- Demonstrated work designing identity and access for workloads, services or other non-human actors
- Hands-on security engineering experience in application security, detection or research
- Working knowledge of zero trust, token-based authentication and PKI
- Understanding of how agents call tools and protocols, and how they can be manipulated
- Experience handling security incidents and improving controls afterwards
- Ability to turn security requirements into patterns engineers will use
Nice to have
- Experience red teaming AI systems or agents
- Background at an IAM or security vendor
- Experience running identity systems at very large scale
Free to use and adapt. If it saves you time, a link back to this page is appreciated.
Skills that matter
- Security engineeringWorkingProtect systems, identities and sensitive assets
- AI red teamingWorkingTest systems adversarially under authorisation
- Tool and protocol integrationWorkingConnect models to external data and capabilities
- Reliability and incident responseWorkingDetect failures, restore service and prevent recurrence
Other roles in aI application security and misuse defence
Related roles in other families
How we wrote this
Role definitions are our own editorial work, checked against occupational classifications, standards, research and employer pages. Titles vary by company, and this is a description of the work, not a job advert.
← AI application security and misuse defenceAll new job families
Start a search
Hiring an Agent Identity and Permissions Architect?
Tell us the work. We find the people already doing it, whatever their job title says, and you meet them already interviewed for your role.
Role Kit
Agent Identity and Permissions Architect: the Role Kit
- What the role is and what a strong hire delivers
- Every interview question, with what a strong answer covers
- A ready-to-post job description
- Where to find the people, and the other titles they use
We email you a copy too. You are only added to Insights if you tick the box.
It is downloading now.
A copy is on its way to your inbox. If you are hiring for this, we would be glad to help.
Meet Beth
Tell Beth who you're hiring. She'll show you how we'd approach it.
Beth knows how we work inside out and keeps up with your market as it moves: who's raising, who's hiring, what roles pay. Ask her anything, right here. In a few minutes you'll know how we'd go about your hire, and you'll have a time in the diary to start it.
Hi, I'm Beth. Hiring an Agent Identity and Permissions Architect? Tell me what you need them to do and I'll show you how we'd find the people already doing it.
- Answers day or night
- Knows your market this week
- No fee unless you hire
- Books your call there and then
- Type or talk, your choice