Processing access requests and designing access systems are both useful, but they involve different decisions.
Operations applies an established process to an approved request. Design examines how many requests should become appropriate access, including exceptions, ownership, and verification.
To move toward engineering or design, look for a responsibility that develops that broader understanding. Handling more tickets alone doesn't establish it, and a new profile title doesn't replace the missing experience.
Execution applies an existing decision
An operator may receive an approved request, confirm the required information, apply the correct role or group, and verify the result.
That work requires care. An incorrect identity, scope, or permission can create a real problem.
The operator may also identify exceptions and escalate requests that don't fit the established process.
Describe those responsibilities accurately. Following a process well is relevant experience, even when you didn't design the process or decide the organization's access policy.
Design defines how decisions should become access
Design work asks what roles exist, how approval is obtained, how assignments are implemented, and what happens when requirements change.
It also considers failures: missing information, unavailable approvers, application errors, conflicting permissions, or access that should expire.
The designer needs to understand the business need and the technical mechanism.
A diagram of a workflow is not enough if nobody can explain who owns the decisions or how the system detects an incomplete outcome.
Use one request to expose the larger design
Take a fictional request for temporary project access.
An operator needs to know which permission to grant and whether approval is valid. A designer needs to decide how the request captures the end date, how the permission maps to the project role, and who handles expiry failures.
The same case reveals both kinds of work.
Create a small table of “decision already supplied” versus “decision the process must define.” That makes the boundary clearer than a generic comparison of analyst and engineer titles.
Propose a bounded improvement without exceeding your authority
Repeated ambiguity in requests can reveal a process problem. It doesn't give you permission to redesign production access controls on your own.
Use a clear contribution:
- Describe the problem: What information is repeatedly missing or misunderstood?
- Identify the owner: Who can approve a process or access-rule change?
- Propose a limited improvement: A clearer requirement, test, or documentation step.
- Record your role: What did you contribute, and which decisions belonged to someone else?
An approved improvement to testing or requirements can develop design understanding even if you don't own the entire system.
Don't automate production changes merely to create an engineering story. The stronger example is an authorized contribution with a clear boundary, a useful result, and accurate credit for the work performed.
Practice design reasoning in a fictional lab
Model the request, approval, assignment, verification, and removal for one resource.
Include a normal case and an exception. Explain what information each step needs and what should happen when that information is missing.
Implement the parts your environment supports and label simulated steps. The lab can demonstrate reasoning without pretending to reproduce enterprise-scale operations.
Use the difference between creating a user and designing access to connect the workflow to the underlying permission model.
Target the next responsibility, not just a new label
When reading roles, look for whether the employer expects execution, process improvement, integration development, or broader design ownership.
Choose a position that fits your existing evidence and adds a manageable next responsibility. You don't need to call yourself an architect to show that you're beginning to think beyond individual requests.
A credible progression can include operations experience, focused projects, and increasingly complete ownership.
The Six-Figure IAM Career Playbook helps map those directions to skills, labs, and positioning. The $9 guide includes a 90-day plan for building the next piece of evidence.
Be clear about the decisions you currently execute and the decisions you're learning to design. That distinction makes both your experience and your ambition easier to evaluate.