Manager, Identity & Access Management
for sections like About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We must only include sections that have real specific content. The posting includes a mission summary, responsibilities (What you’ll be doing), requirements (What we’re looking for), bonus points, location, salary range, benefits. Also maybe "About the role" could be mission summary. We'll need to map.
We must not repeat job title as heading. No Job ID etc. Remove boilerplate like EEO, E-Verify, etc. Also remove application instructions (none present). Remove duplicated lines.
We need to preserve all substantive information.
We need to use - for any list of duties/requirements/benefits, and
for prose.
We need to decide sections:
- About the role: could be mission summary paragraph(s). Could be a
describing the role.
- Responsibilities: list of duties from "What you’ll be doing:" bullet points (though they are paragraphs). We'll extract each bullet as list items.
- Requirements: from "What we’re looking for:" list of experience etc. Could be list.
- Skills: maybe combine with requirements? But we can separate: maybe "Qualifications" for experience, "Skills" for technical skills. However we must only create sections if there is real specific content. The posting includes both experience and skills. Could combine into Requirements and Skills.
- Benefits: list of benefits mentioned: medical, dental, vision, 401k with company match, health saving accounts, life insurance, pet insurance, and more. Also maybe mention eligibility for Motional’s benefits program.
- Pay: salary range $125,000 USD - $167,000 USD.
- Schedule: "This role is based in our Las Vegas office and requires in-office days each week." That's schedule info (in-office days). Could be schedule.
We also have location info maybe not needed as heading; could be in About the role paragraph.
We must not create sections with filler like "commensurate with experience". Not present.
We must not include bonus points as separate section unless we decide to include under Requirements or Skills. Bonus points are not required but still substantive; we could include them under "Preferred Qualifications" but we don't have that heading. Could include under Requirements as additional notes. But we must not invent headings not listed. Allowed headings: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. So we can put bonus points under Skills or Requirements. Probably under Skills.
We need to ensure we don't repeat content.
Let's extract:
Mission Summary paragraph: "We are seeking a hands-on results-driven Manager of Identity & Access Management (IAM) to lead and modernize our enterprise identity ecosystem. As an Autonomous Vehicle (AV) company, our security footprint spans complex cloud environments, edge computing, vehicle-to-cloud infrastructure, federated ecosystem partners, and a diverse workforce. You will provide technical thought leadership while managing Identity Governance and Administration (IGA), identity federation, SCIM integrations, custom IAM development, and our core Okta enterprise architecture. This role requires close cross-functional collaboration with HR, Engineering and End-User Services (EUS) to establish operational SLAs, track key metrics, transition OAuth security posture, and automate workforce lifecycle processes."
That's About the role.
Responsibilities: list items from "What you’ll be doing:" each sentence after colon? Let's break:
- Thought Leadership & Governance: Define the long-term enterprise IAM roadmap, aligning identity security with Zero Trust principles, regulatory compliance, and the unique security demands of autonomous fleet operations.
- OAuth Security Strategy: Drive the strategic transition from user-consent to admin-consent frameworks across all SaaS and enterprise applications, establishing strict OAuth consent policies to minimize dynamic consent risks.
- Identity Federation & SSO: Architect and maintain secure identity federation across multi-cloud environments, B2B partner ecosystems, vendor portals, and external services utilizing SAML 2.0, OAuth 2.0, and OpenID Connect (OIDC).
- Cross-Functional Collaboration: Serve as the primary liaison to HR teams to streamline Joiner-Mover-Leaver (JML) workflows via HRIS integrations, and collaborate with End-User Services (EUS) & Endpoint Engineering to optimize identity lifecycle requests, service desk escalations, and user onboarding/offboarding experiences.
- SLAs & Metrics (KPIs): Define, track, and enforce operational SLAs for access request fulfillments, incident resolution, and account deprovisioning. Establish key performance indicators (KPIs) measuring IAM system uptime, adoption of MFA/SSO, automation rates, and compliance readiness.
- Agentic IAM Strategy: Establish the enterprise identity foundation for governing autonomous AI systems and agentic identities. Define runtime authorization, least-privilege scoping, dynamic delegation, and auditability frameworks to ensure AI agents, autonomous models, and machine-learning workloads operate within secure, verifiable access boundaries.
- Okta Enterprise Management: Serve as the primary subject matter expert for Okta, managing SSO, Adaptive MFA, Lifecycle Management, and Workflows to ensure seamless, secure access.
- IGA & Compliance: Oversee enterprise Identity Governance and Administration (IGA) strategies across human workforce and non-human identities (service accounts, bots, microservices, and vehicle-to-cloud identities), lead RBAC/ABAC maturity, access recertification campaigns, and automated least-privilege enforcement.
- SCIM & Provisioning: Standardize and implement SCIM-based provisioning protocols across internal tooling, SaaS platforms, and proprietary AV operational software.
- Team Leadership: Mentor and manage an IAM engineering team, fostering a culture of innovation, continuous learning, and robust security practices.
We'll put each as
- .
Requirements: from "What we’re looking for:" list:
- Experience: 5+ years in Identity & Access Management, with 2+ years in a leadership or managerial role leading IAM operations and cross-functional initiatives.
- OAuth & Application Consent Governance: Proven experience implementing admin-consent workflows, constraining user-consent permissions, and auditing third-party OAuth app integrations.
- Identity Federation: Deep expertise in architecting complex identity federation models across multi-tenant environments, hybrid clouds, and third-party partner applications.
- Okta Expertise: Deep hands-on and architectural experience with Okta (Certification such as Okta Certified Administrator or Consultant is a plus).
- Cross-Functional Integration: Proven track record of working closely with HR (HRIS integrations like Workday/OracleHCM) and IT Operations/EUS teams to design seamless lifecycle processes.
- Operations & Metrics: Demonstrated ability to define, manage, and report on operational SLAs and enterprise IAM metrics/KPIs.
- Development Skills: Strong background in software development/scripting for custom identity integrations and API development.
- Identity Standards: Expert knowledge of SCIM, OAuth 2.0, OpenID Connect (OIDC), SAML 2.0, WS-Federation, and IGA frameworks.
- Communication: Exceptional stakeholder management skills with the ability to bridge technical requirements with HR, EUS, and executive priorities.
We'll put each as
- under Requirements.
Skills: maybe combine bonus points and some technical skills not covered? Bonus points: Okta Certified Administrator or Certified Identity and Access Manager; Okta (Workflows, Event Hooks, SDKs, OEL), CyberArk (REST APIs, Conjur, CCP, CPM Plugins), Active Directory, JumpCloud; Familiarity or previous experience in the automotive or autonomous vehicle industry.
We'll put those as
- under Skills.
Benefits: list: medical, dental, vision, 401k with a company match, health saving accounts, life insurance, pet insurance, and more. Also mention eligibility for Motional’s benefits program.
We'll put as
- .
Pay: salary range $125,000 USD - $167,000 USD. We'll put as
.
Schedule: "This role is based in our Las Vegas office and requires in-office days each week." We'll put as
.
We also might include location in About the role paragraph? Already included in mission summary? Not exactly. Could add a sentence about location in About the role or schedule. We'll keep schedule as above.
Now produce HTML fragment: start with maybe but not required. Just output headings and content.
We must not include or . Just output the fragment.
We'll structure:
About the role
...
Responsibilities
- ...
...
Requirements
...
Skills
...
Benefits
...
Pay
$125,000 USD - $167,000 USD
Schedule
This role is based in our Las Vegas office and requires in-office days each week.
Check for any duplicated content: Ensure we didn't repeat mission summary in responsibilities etc.
Now craft the About the role paragraph: combine mission summary sentences into one or two paragraphs. Use .
Let's write:
We are seeking a hands-on results-driven Manager of Identity & Access Management (IAM) to lead and modernize our enterprise identity ecosystem. As an Autonomous Vehicle (AV) company, our security footprint spans complex cloud environments, edge computing, vehicle-to-cloud infrastructure, federated ecosystem partners, and a diverse workforce. You will provide technical thought leadership while managing Identity Governance and Administration (IGA), identity federation, SCIM integrations, custom IAM development, and our core Okta enterprise architecture. This role requires close cross-functional collaboration with HR, Engineering and End-User Services (EUS) to establish operational SLAs, track key metrics, transition OAuth security posture, and automate workforce lifecycle processes.
That's fine.
Now responsibilities list items: each as - with the text exactly as given.
We'll copy each bullet.
Responsibilities list:
- Thought Leadership & Governance: Define the long-term enterprise IAM roadmap, aligning identity security with Zero Trust principles, regulatory compliance, and the unique security demands of autonomous fleet operations.
- OAuth Security Strategy: Drive the strategic transition from user-consent to admin-consent frameworks across all SaaS and enterprise applications, establishing strict OAuth consent policies to minimize dynamic consent risks.
- Identity Federation & SSO: Architect and maintain secure identity federation across multi-cloud environments, B2B partner ecosystems, vendor portals, and external services utilizing SAML 2.0, OAuth 2.0, and OpenID Connect (OIDC).
- Cross-Functional Collaboration: Serve as the primary liaison to HR teams to streamline Joiner-Mover-Leaver (JML) workflows via HRIS integrations, and collaborate with End-User Services (EUS) & Endpoint Engineering to optimize identity lifecycle requests, service desk escalations, and user onboarding/offboarding experiences.
- SLAs & Metrics (KPIs): Define, track, and enforce operational SLAs for access request fulfillments, incident resolution, and account deprovisioning. Establish key performance indicators (KPIs) measuring IAM system uptime, adoption of MFA/SSO, automation rates, and compliance readiness.
- Agentic IAM Strategy: Establish the enterprise identity foundation for governing autonomous AI systems and agentic identities. Define runtime authorization, least-privilege scoping, dynamic delegation, and auditability frameworks to ensure AI agents, autonomous models, and machine-learning workloads operate within secure, verifiable access boundaries.
- Okta Enterprise Management: Serve as the primary subject matter expert for Okta, managing SSO, Adaptive MFA, Lifecycle Management, and Workflows to ensure seamless, secure access.
- IGA & Compliance: Oversee enterprise Identity Governance and Administration
for prose. We need to decide sections: - About the role: could be mission summary paragraph(s). Could be a
describing the role. - Responsibilities: list of duties from "What you’ll be doing:" bullet points (though they are paragraphs). We'll extract each bullet as list items. - Requirements: from "What we’re looking for:" list of experience etc. Could be list. - Skills: maybe combine with requirements? But we can separate: maybe "Qualifications" for experience, "Skills" for technical skills. However we must only create sections if there is real specific content. The posting includes both experience and skills. Could combine into Requirements and Skills. - Benefits: list of benefits mentioned: medical, dental, vision, 401k with company match, health saving accounts, life insurance, pet insurance, and more. Also maybe mention eligibility for Motional’s benefits program. - Pay: salary range $125,000 USD - $167,000 USD. - Schedule: "This role is based in our Las Vegas office and requires in-office days each week." That's schedule info (in-office days). Could be schedule. We also have location info maybe not needed as heading; could be in About the role paragraph. We must not create sections with filler like "commensurate with experience". Not present. We must not include bonus points as separate section unless we decide to include under Requirements or Skills. Bonus points are not required but still substantive; we could include them under "Preferred Qualifications" but we don't have that heading. Could include under Requirements as additional notes. But we must not invent headings not listed. Allowed headings: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. So we can put bonus points under Skills or Requirements. Probably under Skills. We need to ensure we don't repeat content. Let's extract: Mission Summary paragraph: "We are seeking a hands-on results-driven Manager of Identity & Access Management (IAM) to lead and modernize our enterprise identity ecosystem. As an Autonomous Vehicle (AV) company, our security footprint spans complex cloud environments, edge computing, vehicle-to-cloud infrastructure, federated ecosystem partners, and a diverse workforce. You will provide technical thought leadership while managing Identity Governance and Administration (IGA), identity federation, SCIM integrations, custom IAM development, and our core Okta enterprise architecture. This role requires close cross-functional collaboration with HR, Engineering and End-User Services (EUS) to establish operational SLAs, track key metrics, transition OAuth security posture, and automate workforce lifecycle processes." That's About the role. Responsibilities: list items from "What you’ll be doing:" each sentence after colon? Let's break: - Thought Leadership & Governance: Define the long-term enterprise IAM roadmap, aligning identity security with Zero Trust principles, regulatory compliance, and the unique security demands of autonomous fleet operations. - OAuth Security Strategy: Drive the strategic transition from user-consent to admin-consent frameworks across all SaaS and enterprise applications, establishing strict OAuth consent policies to minimize dynamic consent risks. - Identity Federation & SSO: Architect and maintain secure identity federation across multi-cloud environments, B2B partner ecosystems, vendor portals, and external services utilizing SAML 2.0, OAuth 2.0, and OpenID Connect (OIDC). - Cross-Functional Collaboration: Serve as the primary liaison to HR teams to streamline Joiner-Mover-Leaver (JML) workflows via HRIS integrations, and collaborate with End-User Services (EUS) & Endpoint Engineering to optimize identity lifecycle requests, service desk escalations, and user onboarding/offboarding experiences. - SLAs & Metrics (KPIs): Define, track, and enforce operational SLAs for access request fulfillments, incident resolution, and account deprovisioning. Establish key performance indicators (KPIs) measuring IAM system uptime, adoption of MFA/SSO, automation rates, and compliance readiness. - Agentic IAM Strategy: Establish the enterprise identity foundation for governing autonomous AI systems and agentic identities. Define runtime authorization, least-privilege scoping, dynamic delegation, and auditability frameworks to ensure AI agents, autonomous models, and machine-learning workloads operate within secure, verifiable access boundaries. - Okta Enterprise Management: Serve as the primary subject matter expert for Okta, managing SSO, Adaptive MFA, Lifecycle Management, and Workflows to ensure seamless, secure access. - IGA & Compliance: Oversee enterprise Identity Governance and Administration (IGA) strategies across human workforce and non-human identities (service accounts, bots, microservices, and vehicle-to-cloud identities), lead RBAC/ABAC maturity, access recertification campaigns, and automated least-privilege enforcement. - SCIM & Provisioning: Standardize and implement SCIM-based provisioning protocols across internal tooling, SaaS platforms, and proprietary AV operational software. - Team Leadership: Mentor and manage an IAM engineering team, fostering a culture of innovation, continuous learning, and robust security practices. We'll put each as
. Schedule: "This role is based in our Las Vegas office and requires in-office days each week." We'll put as
. We also might include location in About the role paragraph? Already included in mission summary? Not exactly. Could add a sentence about location in About the role or schedule. We'll keep schedule as above. Now produce HTML fragment: start with maybe but not required. Just output headings and content. We must not include or . Just output the fragment. We'll structure:
About the role
...
Responsibilities
- ... ...
Requirements
- ...
Skills
- ...
Benefits
- ...
Pay
$125,000 USD - $167,000 USD
Schedule
This role is based in our Las Vegas office and requires in-office days each week.
Check for any duplicated content: Ensure we didn't repeat mission summary in responsibilities etc. Now craft the About the role paragraph: combine mission summary sentences into one or two paragraphs. Use. Let's write:
We are seeking a hands-on results-driven Manager of Identity & Access Management (IAM) to lead and modernize our enterprise identity ecosystem. As an Autonomous Vehicle (AV) company, our security footprint spans complex cloud environments, edge computing, vehicle-to-cloud infrastructure, federated ecosystem partners, and a diverse workforce. You will provide technical thought leadership while managing Identity Governance and Administration (IGA), identity federation, SCIM integrations, custom IAM development, and our core Okta enterprise architecture. This role requires close cross-functional collaboration with HR, Engineering and End-User Services (EUS) to establish operational SLAs, track key metrics, transition OAuth security posture, and automate workforce lifecycle processes.
That's fine. Now responsibilities list items: each as