Your resume may say “Active Directory administration,” while your day-to-day work includes account recovery, access requests, group changes, onboarding, and recurring lockouts.
Make an inventory of those responsibilities before deciding you have no IAM experience. The useful detail is what you did, what you understood, and what you could explain in an interview.
This isn't permission to export company tickets into your personal files. Review only what you're authorized to access, then record general skills and anonymized patterns without taking confidential records.
Review patterns, not private records
Follow your employer's policies for accessing and using work information.
Don't export a ticket queue to your personal laptop or upload company records into an AI tool because you're working on your resume.
You can usually begin with a private list of the types of work you remember doing, without copying user names, internal systems, screenshots, or request details.
For example: “group membership changes with approval,” “account lockout investigation,” and “new-starter access requests.”
The aim is to identify categories of responsibility, not collect a shadow database of workplace information.
When there is uncertainty about what you may reuse, ask through the appropriate channel.
Sort tasks by the question they answer
Product names are a useful index, but they aren't the best explanation of your work.
Group the tasks by purpose. Some establish or recover an identity. Some change access. Some investigate why the expected result didn't happen. Some record approval or confirm a change.
This helps you see how a collection of ordinary tickets relates to broader identity responsibilities.
A group membership change, for example, is interesting because of what the group permits—not merely because you used an administrative console.
Ask what business requirement the action was intended to satisfy.
Separate tasks you performed from decisions you owned
For each category of work, identify your personal contribution. These descriptions represent different levels of responsibility:
| Your involvement | What you can accurately explain |
|---|---|
| Executed a request | The approved steps you followed and the result you checked |
| Investigated a failure | The evidence you collected and how you narrowed the cause |
| Recommended a change | Your reasoning, with approval and implementation ownership kept clear |
| Maintained or designed a process | The decisions you genuinely controlled |
You might find stronger experience than your resume currently communicates. You might also discover that a listed platform was something you only used occasionally.
Both findings are useful. An accurate inventory tells you what to emphasize and what still needs practice.
Keep this distinction in your notes so a future resume rewrite doesn't turn participation into ownership.
Turn one pattern into a question for a lab
Suppose group changes were a frequent part of your work, but you never saw the configuration behind the access they granted.
That is a useful learning gap. Create a fictional resource and test identities in a private lab. Explore how the membership and the resource permissions connect.
Or suppose you frequently escalated sign-in issues but never had permission to examine the relevant logs. A documented test environment can let you investigate a similar kind of problem without touching production.
You're using your work history to choose the question. You're not copying your employer's environment.
Make that distinction clear in anything you publish.
Build a small evidence ledger
For a few representative categories, record four things: the task type, your responsibility, what you learned, and how you could explain it safely.
Keep it short enough to review before an interview.
You might write: “Handled approved access requests; checked required authorization; verified completion with the requester; learned to distinguish account recovery from resource permission problems.”
Use only details that are true. A lab can have a separate entry with a link to your public explanation. Don't merge the lab result into the employment record.
Over time, the ledger becomes a way to notice progress instead of relying on memory when you're ready to change jobs.
Use the inventory to choose a direction
You may find a concentration in directory work, application access, or employee lifecycle tasks.
That doesn't dictate your career. It gives you a sensible place to start comparing IAM responsibilities with your background.
The Six-Figure IAM Career Playbook helps with that mapping, then provides projects for the gaps your existing work hasn't covered. The ebook is $9.
A ticket marked “resolved” is easy to forget.
The reasoning, responsibility, and technical understanding behind a series of those tickets may be exactly what you need to describe next.