As asked
You inherit a cloud estate where every team uses admin-like roles in a shared account. How would you redesign access without blocking delivery?
Sample answer outline
Start by separating environments and blast radii: production from non-production, shared platform from application accounts, and human access from workload identity. Define roles around actions people actually need, then enforce least privilege with permission boundaries, short-lived credentials, and break-glass access that is audited. Use infrastructure-as-code and policy-as-code so access changes are reviewed, repeatable, and testable. Strong answers mention migration sequencing because cutting everyone over in one move usually breaks deployments. Candidates often trip up by describing perfect IAM theory without a path from the current unsafe state.
Expect these follow-ups
- How do you handle a senior engineer who insists they need admin for debugging?
- Where would you use service control policies or organisation policies?
- What audit signals tell you the new model is working?