twobotechnologies

Careers in Identity and Access Management

Identity is one of the steadiest specialties in security. This page describes the work, the roles and how people get into it. Twobo Technologies itself is not hiring.

Every application needs sign-in, every company needs to remove leavers' access, and every API needs tokens. That steady demand makes identity and access management a solid career path, with work that ranges from protocol details to large organizational programs.

What roles exist?

Role Day-to-day work Core skills
IAM engineer Configure IdPs, federation, MFA, SCIM SAML, OIDC, OAuth, directories, scripting
Identity architect Design target state, standards, patterns Broad protocol knowledge, threat modeling
CIAM developer Customer sign-up, sign-in, consent OIDC, UX, privacy law, fraud defenses
IGA analyst / engineer Lifecycle, access reviews, roles Business processes, connectors, reporting
Privileged access engineer Admin access, vaulting, JIT elevation OS and cloud permissions, auditing
Application security engineer (identity focus) Review OAuth flows, token handling Code review, OWASP, RFC 9700
Standards contributor Write and review specifications Deep protocol expertise, writing

Which skills matter most?

HTTP and TLS fundamentals, the core protocols, directories, and the ability to read a specification.

  • Read and debug HTTP redirects, cookies and headers in browser developer tools.
  • Explain the OAuth authorization code flow with PKCE from memory. Practice with the Authorization URL Builder and PKCE Generator.
  • Decode and validate JWTs and SAML assertions. Try the JWT Decoder and SAML Decoder.
  • LDAP and Active Directory basics.
  • Scripting for automation (PowerShell, Python) and APIs.

How do I build experience?

  1. Run an open-source identity server locally and connect a sample app with OIDC and another with SAML.
  2. Implement SCIM provisioning to a test app.
  3. Read RFC 6749, RFC 7636, RFC 9700 and OpenID Connect Core end to end.
  4. Follow working group discussions; see identity standards bodies and communities.
  5. Write up what you learn. Explaining a flow clearly is a skill employers notice.

The glossary and the IAM building blocks are good study companions.

Common questions

Do I need a security background to work in IAM?

No. Many identity engineers come from system administration, software development or directory services. Understanding HTTP, TLS, directories and at least one programming or scripting language matters more than a security title.

Which certifications are relevant?

General security certifications such as CISSP cover IAM as one domain. Vendor certifications exist for major identity platforms and cloud providers. The IDPro Certified Identity Professional (CIDPRO) program focuses on identity specifically.