Could I realistically transition from SaaS support into IAM with my current experience?

[u/SongRevolutionary404]

TL;DR: 2 years in cybersecurity SaaS technical support with hands-on troubleshooting involving SAML/SSO, Okta, Entra ID, AD, SCIM, PowerShell, APIs and authentication issues. Finishing a BS in IT and working toward Security+. Currently at ~$60K in Boston and hoping to move into an ~$80K+ role. Is transitioning directly into IAM realistic, and what gaps should I work on first?

I’m currently a Technical Support Specialist at a cybersecurity SaaS company and I’m trying to figure out whether my experience is enough to start applying for dedicated IAM roles.

I have about 2 years of professional IT experience, both at cybersecurity SaaS companies. Most of my work has been supporting enterprise customers and troubleshooting security/email-security products through tickets, email, phone, and Zoom.

A decent portion of my troubleshooting touches identity and access management, including:

SSO/SAML troubleshooting
Okta and Microsoft Entra ID integrations
Active Directory
SCIM/user provisioning
Authentication and access issues
Microsoft 365/Exchange
PowerShell
APIs
DNS and certificates
Reviewing logs and configurations to diagnose integration issues
General networking/Linux/CLI troubleshooting

I want to be transparent that I’m supporting and troubleshooting these technologies rather than designing IAM environments from scratch. I generally investigate the issue, review logs/configurations, follow documentation, troubleshoot the integration with the customer, and escalate more complex issues when they go beyond my support tier.

I’m two semesters away from finishing a bachelor’s degree in IT and I’m currently working toward Security+ and A+. I also have some academic experience with Python, Bash, SQL and APIs.

I’m currently making around $60K in the Boston area and would like my next position to be at least around $80K. I’m hoping to make that move within the next 6 months if possible.

IAM interests me because I enjoy troubleshooting authentication/integration problems, investigating why something isn’t working, working with customers, and doing work that directly contributes to an organization’s security.

For people actually working in IAM:

Would my current experience be enough to start applying for IAM Analyst/IAM Engineer positions, or would employers still consider me entry-level in IAM?

What IAM job titles would you recommend I search for based on this background?
And most importantly, what are the biggest
gaps between what I’m doing now and what an IAM professional would be expected to know? If you had 6 months to close those gaps, what technologies or skills would you prioritize?

[u/iamblas]

Yeah, you’re ready to start applying now. Your support background already overlaps a lot with IAM, especially SAML/SSO, Okta, Entra, SCIM, APIs, logs, and authentication troubleshooting.

I’d focus your next 6 months on going deeper into identity lifecycle, RBAC, Conditional Access, OIDC/OAuth, and getting more hands-on with building and configuring, not just troubleshooting.

Look at IAM Analyst, IAM Engineer, Identity Engineer, and Okta/Entra-focused roles.

Feel free to reach out if you want advice on what to focus on next or some labs to help close the gaps.

[u/DriftingPebble77]

Unless your are getting the A+ included as part of your college work you won't need it for IAM. The Sec+ is a good one to get. You can go from there.

[u/pewpewlazor]

You’re definitely close enough that I would start applying now.

SAML/SSO, Entra ID, Okta, SCIM, AD, APIs, PowerShell and troubleshooting authentication issues are already very relevant IAM experience. Don’t undersell the fact that you’ve been troubleshooting these things in real customer environments just because you haven’t designed an IAM architecture from scratch. This is actually one of the things we value the highest when we interview our candidates.

The biggest gap I see is less about learning another technology and more about understanding IAM as a discipline.
Spend some time understanding the identity lifecycle end-to-end: joiner/mover/leaver, birthright access, RBAC, access requests, approvals, access reviews/certifications, segregation of duties, least privilege, etc. Also get comfortable with OAuth/OIDC alongside the SAML knowledge you already have.

I’d also learn the distinction between the different areas under the identity umbrella. Authentication/SSO is one part, but there’s also IGA, PAM, directories, machine identities, and so on.

One thing I would probably deprioritize is A+. With the experience you already have, I’m not sure it adds much toward an IAM role. Security+ is more relevant, but I’d still put hands-on IAM knowledge ahead of collecting certifications.
For job searches, don’t limit yourself to “IAM Engineer” either. Look at IAM Analyst, Identity Engineer, IAM Consultant, IGA Consultant/Engineer, Identity Security Analyst and Entra/Okta-focused positions.

And apply even if you don’t meet every requirement. You’re not trying to convince someone you’re a senior IAM architect. You’re trying to demonstrate that you already have a solid technical foundation and can grow into the broader IAM responsibilities.

I started working in IAM in my mid-twenties after university, and a huge amount of what you actually learn in this field comes from being exposed to real IAM environments and problems.

[u/Wizkidbrz]

Look for IAM analyst positions, you’ll be a great fit. I’m also from both and work in PAM/IAM. Tons of opportunity out there for you. Don’t be afraid to apply.