Lead CIAM Architect (Okta / Auth0)
This is the employer's own posting, not a copy on a job board.
What we know
Is it still open?
Not yet checked
This listing has not been re-checked yet. It was seen at its source just now.
The employer's own board was still advertising this when we last read it, though our own check is not current.
How old is it?
Posted 1h ago
The date the source published, not the day we noticed it (2026-11-20). Last seen at its source just now.
Is it remote?
Remote
That is the location the employer filed this posting under. Quoted as written — we do not re-word the source's own location.
Who may apply?
Not stated
The description states no restriction of its own. This is the source's own tag.
Pay
$170k–180k/yr
Read out of the job description by us, not from a structured field. Shown in the posting's own currency and period; we never convert.
Skills named in the ad
Recognised terms only, from a fixed vocabulary — this is what CV matching compares against.
Carried by 1 source
-
Greenhouse employer's own board first seen just now · last seen just now
The listing
We're seeking a hands- on Lead CIAM Architect to technically lead the implementation of a greenfield Okta Customer Identity Cloud (Auth0) foundation for a large organization in a regulated US industry, with multiple separately branded customer identity domains. Given a baseline target- state design, this person will figure out the technical specifics to build the production- ready platform, delivery automation, and operating model that later application migration waves will use. The architect refines technical standards and directs work across delivery and client engineering teams. This is both a technical leadership and delivery role; the primary focus is serving as the subject- matter expert on the Okta/ Auth0 products and providing design and technical direction to the delivery team.
Required
- Okta CIC / Auth0 architecture and implementation at enterprise scale: Universal Login customization, Actions, Organizations, custom domains, attack protection, MFA policy, and multi- tenant/ multi- environment topology (ideally Auth0 Private Cloud)
- Deep protocol expertise: OIDC, OAuth 2.0 (including client credentials and API authorization), SAML 2.0 as IdP, SP, and broker, JWT claims design and token/ session isolation
- Working knowledge of the Auth0/ Okta Management APIs and automation coverage, enough to define which platform objects can be managed as code and to partner with a DevOps team that owns the pipelines
- CIAM journey design: self- registration, MFA enrollment and step- up (including passkey/ passwordless readiness), account recovery, forgot- username, and API- driven identity creation with idempotency and duplicate handling
- Customer identity data modeling: immutable person identifiers, account linking/ correlation where email is not unique, and governed match/ merge decisions
- Administrative security design: least- privilege admin and help- desk role models, break- glass, separation of duties, and workforce SSO for administrators
- Experience in regulated US industries with NIST- aligned identity controls, threat modeling, and remediating vulnerability- scan findings
Strongly preferred
- Integrating CIAM platforms with enterprise security and operations tooling: SIEM, privileged access management (PAM), identity governance (IGA), WAF/ DDoS edge protection, EDR, certificate lifecycle management, and synthetic monitoring
- Observability and resilience design: SLOs, alerting, key/ certificate rotation, recovery testing
- Producing deliverable- based documentation (HLD/ LLD, runbooks, acceptance evidence) under fixed- scope engagements
Nice to have
- Identity- as- code: Terraform (Auth0/ Okta providers), GitHub- based workflows, Harness or similar CI/ CD promotion pipelines, drift detection, and rollback
- IBM ISAM/ ISVA and IBM SDS/ LDAP background (useful context for future migration phases)
- Okta Workforce Identity or PingOne
- Okta/ Auth0 certifications