If you've worked help desk, there's a good chance you've performed tasks that fall under Identity and Access Management (IAM).
Password resets, MFA support, account unlocks, user provisioning, and group changes all touch identity.
That experience can help you move into an IAM role. But here's the important distinction:
Performing an identity task isn't the same as designing or managing an identity system.
Knowing exactly where you stand helps you write a better resume and choose the right skills to learn next.
A password reset involves more than clicking a button
Think about an account-recovery request you've handled at work.
A responsible process may involve:
- Verifying the person making the request.
- Checking which account and system are involved.
- Following the approved recovery procedure.
- Confirming that the person can regain appropriate access.
- Escalating when the request seems suspicious or outside your authority.
If you've done that, you have legitimate identity operations experience.
You shouldn't dismiss it because the task happened in a help desk queue.
You also shouldn't turn it into “designed enterprise authentication architecture” unless you actually owned that work.
Both accuracy and relevance matter.
Use four levels to describe what you know
Take five tasks you've performed: password resets, account creation, group membership changes, MFA troubleshooting, and employee offboarding.
For each task, identify your real level of experience:
| Level | What you can claim |
|---|---|
| Performed | Followed the approved process and completed the task. |
| Explained | Understand why the steps and checks exist. |
| Troubleshot | Investigated failures and used evidence to find the cause. |
| Designed | Made decisions about the system or process itself. |
You can be at different levels for different tasks.
Maybe you regularly troubleshoot account lockouts but only follow a standard procedure for changing group membership.
That's normal. The table shows both your transferable experience and your gaps.
Explain one support ticket as an identity problem
Suppose someone says, “My password works, but I can't open the finance folder.”
A basic response is to try another password reset.
A better investigation asks:
- Can the person authenticate successfully?
- What resource are they trying to access?
- Which group or policy grants permission?
- Was the person ever supposed to have that access?
- What evidence confirms the result?
This reveals an important IAM distinction.
Authentication helps establish who a user is. Authorization determines what they are allowed to do. A successful sign-in doesn't prove access to every resource is appropriate.
Microsoft's authorization overview covers that separation.
If you're used to recovering accounts, learning to trace the access decision is a sensible next step.
Build a small lab to demonstrate the difference
You don't need production administrator privileges to practice this concept.
Create two fictional users in an isolated test environment. Give one access to a shared folder through an appropriate group. Leave the other without permission.
Then:
- Confirm that both accounts can sign in.
- Test whether each can open the folder.
- Record the successful and denied results.
- Change a permission and retest.
You now have a project that demonstrates sign-in versus access control, not just account recovery.
Document it honestly as a lab. It demonstrates a skill; it doesn't become enterprise production experience because you published screenshots.
Put the right experience on your resume
Weak: “Reset passwords.”
More informative, if accurate: “Handled account-recovery requests under identity-verification procedures and confirmed restored user access.”
If you investigated repeated failures, describe what you checked. If you escalated, explain what evidence you collected. Don't invent ownership or performance numbers.
Your job title might understate the IAM work you've touched. Specific examples help employers see the connection.
The Six-Figure IAM Career Playbook shows how to map existing IT tasks to identity roles, identify meaningful gaps, and build three projects to demonstrate new skills. It's a $9 guide for making the next move with a clearer plan.
Don't claim you already know everything in IAM. Show exactly what you know—and what you're building next.