When an interviewer says you don't have IAM experience, find out which experience they think is missing before defending your background.
They may mean production Entra administration, SSO integrations, access reviews, or independent incident handling. A story about password resets won't answer every concern.
Clarify the gap, describe your closest genuine evidence, and be direct about what you haven't done. That creates a more useful conversation than insisting all IT work is equivalent to identity engineering.
Ask which part of IAM experience concerns them
A useful response is: “Which part of the identity work is the main concern?”
Listen for the responsibility behind the label:
- Platform experience: Have you administered the system in production?
- Integration ownership: Have you configured and supported an application connection?
- Governance work: Have you handled approvals, reviews, or lifecycle controls?
- Independent troubleshooting: Can you investigate without someone directing every check?
This isn't a technique for dodging a requirement. It helps you answer the question they're actually asking.
Once the concern is clear, give the closest accurate example and identify its limits. A lab may support your understanding of an integration; it does not become production ownership. Relevant support experience may demonstrate investigation skills without proving architecture-level responsibility.
Present the closest honest evidence
Once the requirement is clear, connect it to something specific.
For example: “My current role includes approved account and group changes, plus initial investigation of sign-in failures. I haven't owned your identity platform in production.”
Then explain the relevant example in enough detail to show your contribution: the problem, your authority, the evidence you gathered, and the outcome.
Don't hide the limitation in a long speech. A clear boundary is more credible than trying to make a support task sound like a full deployment.
Use lab work to demonstrate learning, not replace history
You might add: “To build the integration knowledge, I configured a test application, documented the login flow, and reproduced a controlled failure in a lab.”
That gives the interviewer something concrete to examine. It does not erase a requirement for production experience when the employer genuinely needs it.
Be ready to explain the decisions and tests. A lab you cannot discuss independently is unlikely to resolve the concern.
Use lab evidence without presenting it as production work to keep the distinction clear.
Ask what level of support the role allows
Some positions are designed for someone who can learn the environment with supervision. Others require immediate independent ownership.
Ask how the team expects a new hire to become effective and which responsibilities must already be familiar on day one.
This helps both sides assess the fit. A role may be too large a jump now even when you have strong transferable experience.
That is useful information, not a verdict that you can never work in identity. It may point toward a more appropriate bridge role.
Avoid three responses that weaken your case
Don't argue that the title is irrelevant when the interviewer is describing a real capability gap. Titles can be misleading, but responsibilities still matter.
Don't promise you can learn the entire environment in a weekend. Explain a credible learning example instead.
Don't respond with a long certification list unless the credentials address the specific concern. A badge may support your foundation, but it doesn't automatically demonstrate the missing responsibility.
The strongest response is relevant evidence, not more volume.
Leave with a clearer next decision
If the employer needs experience you don't have, ask which responsibilities would make a future candidate better prepared. They may not provide detailed feedback, and you shouldn't pressure them to do so.
Use what you learn to refine the role target or the next project. If the concern was actually unclear positioning, improve the way your resume explains the relevant work.
The Six-Figure IAM Career Playbook helps map existing IT experience, choose a suitable identity lane, and build missing proof. The $9 guide is designed to make this conversation more concrete before you reach the interview.
You don't need to win an argument about whether you “count” as an IAM professional. You need to show which parts of the work you can credibly perform and understand the parts you still need to develop.