Your current job can help you develop IAM skills, but production systems are not your personal practice lab.
Ask for an authorized, bounded opportunity. Learn the process, perform only the work you're permitted to do, and keep operational evidence in the approved systems.
A useful career example does not require publishing internal screenshots or copying company data into a personal repository. The judgment you show around permissions and confidentiality is part of the capability an identity employer needs to see.
Ask for a bounded opportunity, not unrestricted access
Identify a responsibility connected to your current role and the direction you want to explore.
You might ask to help improve an onboarding checklist, observe an application-access investigation, or assist with testing an approved change under supervision.
Be specific about the task and the learning goal. Clarify who owns the work, what permissions you need, and what you are authorized to do.
A request for a defined contribution is easier to evaluate than asking for broad administrative rights so you can “learn IAM.”
Keep experimentation inside an approved environment
If the task requires testing, use the organization's designated test environment and change process.
Do not intentionally break production authentication, create unnecessary accounts, or alter permissions to generate a troubleshooting example. Even a small identity change can affect other people or connected systems.
When an approved test environment is unavailable, reproduce the general concept independently using fictional identities and your own resources.
That separate lab can support your learning without exposing the employer to an experiment it did not authorize.
Document the work without exporting private evidence
Keep the operational record in your employer's approved system.
| Record internally | Keep out of personal tools unless explicitly authorized |
|---|---|
| What you were asked to do | Ticket exports and customer details |
| Checks performed and results | Logs and internal screenshots |
| Escalations and unresolved limits | Configuration files and access records |
For your own career inventory, retain only the high-level descriptions you're permitted to keep. You may be able to describe an approved responsibility without taking the underlying records with you.
Don't assume redaction makes an export acceptable. Ask the appropriate owner when permission is unclear, including before using an AI service to summarize internal material.
Your educational purpose does not remove the information's sensitivity. A public portfolio should never depend on taking data that your employer has not authorized you to use.
Separate a resume description from a public case study
You may be able to describe a responsibility on your resume without being allowed to publish the underlying evidence.
For example, a truthful high-level description might explain that you processed approved lifecycle changes or helped document a troubleshooting process. The exact wording should reflect your role and the employer's rules.
A public case study has a different disclosure boundary. It may require explicit review and permission, or it may be inappropriate altogether.
The distinction between public portfolio material and private operational evidence helps keep those uses separate.
Rebuild the concept with fictional data when necessary
Suppose an authorized workplace task teaches you why access should change when someone moves teams.
You can create an independent lab around a fictional employee and dummy resources, using a design that does not reveal proprietary details. Label it as a personal exercise inspired by a general problem, not as the employer's implementation.
Do not copy internal scripts, diagrams, or procedures and merely replace the company name.
The value is in demonstrating your understanding of the concept while respecting the boundary around the organization's information.
Use the experience to choose your next responsibility
After the task, ask what you learned and what remains outside your scope.
Did you enjoy the technical investigation, the process design, or the coordination with application owners? Which part would you need to practice before taking broader responsibility?
Those observations can make your career plan more grounded than studying a specialty only from the outside.
The Six-Figure IAM Career Playbook helps map existing work to IAM lanes and provides three independent lab areas for building additional proof. The $9 guide gives you a way to develop relevant evidence without treating an employer's systems or confidential information as material for a personal project.