User creation, group changes, MFA support, access troubleshooting, and offboarding all connect to identity work. Your general IT role may already contain experience worth discussing in an IAM application.
The next step is to inventory what you actually did, how much responsibility you held, and what you can explain.
That inventory can reveal a sensible starting role. It can also reveal gaps. Recognizing transferable experience doesn't mean assuming every IAM position is already within reach.
Start with tasks you can explain without a script
List the identity-related work you actually performed during a typical month.
Do not begin by copying keywords from a job posting. Start with the actions: prepared a user account from an approved request, checked membership when access failed, helped a user register an authentication method, or removed a specified permission during offboarding.
Then ask whether you can explain why the action was needed and how you knew it was complete.
A familiar screen is a starting point. Understanding the responsibility behind it makes the experience easier to describe accurately.
Explain the checks behind account creation
Creating an account is more informative when you can explain the request and controls around it.
Consider:
- Where did the onboarding request come from?
- Who confirmed the person's role and required details?
- Which access was approved, and by whom?
- What attributes or assignments did you check?
- Where did your responsibility end?
An accurate description might be: “Created accounts from authorized onboarding requests and checked the required attributes before handing them over.” Use that wording only if it reflects your work.
Executing a defined process is legitimate operational experience. It is different from designing the process or choosing the organization's access model.
Keep that distinction visible. The useful career story is the responsibility you actually exercised and understood, not a more senior-sounding description of clicking through an account form.
Access troubleshooting can reveal a broader understanding
Think about a time someone could sign in but could not use a resource.
What did you inspect? Account state, group membership, a resource permission, application assignment, or evidence from the relevant system?
Which checks were yours, and where did you escalate? What information made that escalation useful?
A clear description of the investigation may be more relevant to an identity role than the final ticket category. Avoid claiming that you diagnosed the entire authentication stack when your responsibility covered only one stage.
MFA support includes an authorization boundary
Helping someone regain access is not simply a matter of making the prompt disappear.
In your actual work, what process authorized the change? How did you confirm you were handling the correct account? Which actions were allowed within your role?
Describe the approved procedure you followed without publishing sensitive recovery details or encouraging shortcuts.
If your experience was limited to guiding enrollment, say that. Enrollment assistance, policy administration, and designing an authentication rollout are different levels of responsibility.
Departures reveal whether you understand completion
For offboarding work, distinguish the requested action from the broader outcome.
You may have disabled an account or removed specified memberships. That does not automatically prove every application session, independent account, or delegated access path was terminated.
State your scope and how you confirmed the actions you owned. Then identify the questions you would need answered to evaluate the wider process.
The limits of what a routine password reset proves illustrate the same principle: a real task can be relevant without establishing expertise across the entire specialty.
Turn the inventory into a gap map
Choose one suitable IAM role and compare its responsibilities with your list.
Mark each item as something you have performed, something you have practiced independently, or something you still need to learn. Keep the evidence attached to the claim.
You now have a more useful starting point than “I have no IAM experience” or “I already know IAM.” Both statements can hide important detail.
The Six-Figure IAM Career Playbook helps connect existing IT responsibilities to IAM lanes, three practical labs, and a 90-day plan. The $9 guide is designed for this kind of transition: keep the experience that genuinely transfers, then build evidence for the responsibilities you have not handled yet.