AVP IAM & Governance

We need to output HTML fragment with sections: About the role? The posting includes "Our Mission", "Overview", "How You Can Make a Difference", "What You’ll Be Doing", "What You’ll Need to be Successful", "Certifications, Licenses, Registrations", "Travel Requirements", "Salary Range", "Benefits & Perks", "Onboarding & Travel", "Why work with HealthEquity". We must use

for section headings (e.g., About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). But we should only include sections when posting has real specific content. We need to map content to these headings. We have mission and overview maybe "About the role". The "How You Can Make a Difference" could be part of overview. The "What You’ll Be Doing" is responsibilities. "What You’ll Need to be Successful" is qualifications/requirements. "Certifications, Licenses, Registrations" could be part of qualifications. "Travel Requirements" maybe schedule? Actually travel is not schedule; but we could put under "Schedule"? Not exactly. The instruction says use headings for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). So we can choose appropriate ones: About the role (mission/overview), Responsibilities (What You’ll Be Doing), Requirements (What You’ll Need to be Successful), Skills (maybe specialized knowledge), Benefits (Benefits & Perks), Pay (Salary Range), Schedule (Travel Requirements? maybe not). But we should only include sections if posting has real specific content. Travel Requirements is present: "Occasional travel to attend training, industry conferences, or meetings may be required." Also "This is a remote position." So schedule could include remote and travel. We'll include Schedule section with that info. We must not repeat job title as heading. Not include Job ID etc. Remove boilerplate: EEO, legal, etc. Also remove duplicated lines, navigation, cookie, etc. Also remove application instructions (like "Click here to learn more", "You belong at HealthEquity!", etc). Also remove EEO statements, drug-free workplace, etc. Also remove the Microsoft Copilot transcription stuff. Also remove the final mission repeat at end. We need to preserve all substantive information. So we need to keep mission, overview, responsibilities, qualifications, certifications, travel, salary, benefits, onboarding, why work? The "Why work with HealthEquity" includes vision statement etc. Might be considered substantive but could be considered boilerplate? It's about company vision; maybe keep as part of About the role? But we should not include fluff? The instruction: remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. The "Why work with HealthEquity" is not exactly boilerplate; it's a motivational statement. Might be okay to keep as part of About the role. We need to output only HTML fragment, no /, no markdown fences. We'll structure:

About the role

Our mission is to SAVE AND IMPROVE LIVES BY EMPOWERING HEALTHCARE CONSUMERS. Come be part of remarkable. Overview How You Can Make a Difference The AVP, Identity & Access Management, the enterprise authority on identity — the architect, evangelist, and operational owner of an identity-first security model in which identity is the control plane for a cloud-first, zero trust enterprise. This leader defines and executes a multi-year B2E IAM strategy spanning identity governance and administration (IGA), privileged access management (PAM), customer and workforce access management, non-human/machine identity, and identity threat detection and response (ITDR), and is accountable for the engineering rigor, control effectiveness, and audit posture of the entire identity fabric. This is a role for a practitioner-leader and recognized thought leader: someone who has designed and operated identity programs at scale, who is fluent in modern identity standards and protocols (OAuth 2.0, OIDC, SAML 2.0, SCIM, FIDO2/WebAuthn), who can whiteboard an authorization model one hour and defend a control posture to auditors and executives the next, and who actively shapes the direction of the identity discipline — inside the organization and in the broader industry — through published points of view, standards engagement, and community leadership.

But we need to avoid duplication: The overview repeats some content from responsibilities. Might be okay. Better to separate: About the role includes mission and overview. Responsibilities separate. Let's craft. Responsibilities: list items from "What You’ll Be Doing". Use

• . We need to capture all bullet-like sentences. The text includes paragraphs with colon headings: Identity Strategy & Thought Leadership:, Organizational Leadership:, Identity Governance & Administration (IGA):, Authentication, Authorization & Directory Architecture:, Privileged Access & Non-Human Identity:, IAM Platform Engineering & Operations:, Risk, Compliance & Assurance:. We'll turn each into li. We'll need to preserve details. Qualifications: "What You’ll Need to be Successful" includes Education And Experience, Specialized Knowledge, Skills, And Abilities, Certifications, Licenses, Registrations. We'll split maybe into Requirements (education/experience) and Skills (specialized knowledge). But we have headings: Requirements, Qualifications, Skills. We can use Requirements for education/experience, Qualifications for specialized knowledge, Skills for certifications? Or combine. Simplify: Use

  Requirements

  for Education And Experience.

  Skills

  for Specialized Knowledge, Skills, And Abilities.

  Certifications

  for Certifications, Licenses, Registrations. Travel Requirements: maybe under Schedule. Benefits: Benefits & Perks. Pay: Salary Range. Schedule: Travel Requirements + remote. Onboarding & Travel: maybe part of Schedule? But we have separate Onboarding & Travel content. Could be under Schedule as well. But we already have Schedule; we could add onboarding details there. Why work with HealthEquity: maybe include in About the role as extra paragraph. We must not include boilerplate like "Click here to learn more", "You belong at HealthEquity!", EEO statements, drug-free workplace, Microsoft Copilot transcription, final mission repeat. Let's extract substantive content. I'll rewrite sections concisely but preserve all details. About the role paragraph: combine mission, overview, how you can make a difference. Mission: "Our mission is to SAVE AND IMPROVE LIVES BY EMPOWERING HEALTHCARE CONSUMERS. Come be part of remarkable." Overview: The AVP, Identity & Access Management, the enterprise authority on identity — the architect, evangelist, and operational owner of an identity-first security model in which identity is the control plane for a cloud-first, zero trust enterprise. This leader defines and executes a multi-year B2E IAM strategy spanning identity governance and administration (IGA), privileged access management (PAM), customer and workforce access management, non-human/machine identity, and identity threat detection and response (ITDR), and is accountable for the engineering rigor, control effectiveness, and audit posture of the entire identity fabric. This is a role for a practitioner-leader and recognized thought leader: someone who has designed and operated identity programs at scale, who is fluent in modern identity standards and protocols (OAuth 2.0, OIDC, SAML 2.0, SCIM, FIDO2/WebAuthn), who can whiteboard an authorization model one hour and defend a control posture to auditors and executives the next, and who actively shapes the direction of the identity discipline — inside the organization and in the broader industry — through published points of view, standards engagement, and community leadership. How You Can Make a Difference: maybe redundant; we can incorporate into overview. We'll just keep overview. Responsibilities: list each section. Let's extract bullet points: Identity Strategy & Thought Leadership: - Own and evangelize a multi-year AI led identity strategy and reference architecture that treats identity as the primary security perimeter, aligned to zero trust principles (NIST SP 800-207) and enterprise business objectives. - Serve as the organization's most senior voice on identity: publish internal position papers and architectural decision records, brief executive leadership and the Board on identity risk, and represent the company externally through industry forums, standards bodies, conference speaking, and peer communities. - Anticipate and translate emerging shifts — decentralized identity, verifiable credentials, passwordless/phishing-resistant authentication, AI-agent and workload identity, continuous access evaluation (CAEP/Shared Signals) — into pragmatic roadmap decisions with clear build/buy/retire rationale. Organizational Leadership: - Build, lead, and mentor a high-performing team of IAM architects, engineers, and analysts; establish engineering career paths, on-call/operational maturity, and a culture of automation-first identity operations. - Operate identity as a product: define OKRs and SLOs for identity services (provisioning latency, certification completion, authentication availability, orphaned-account rates), and manage a prioritized backlog with IT, HR, Legal, Compliance, and business-line stakeholders. Identity Governance & Administration (IGA): - Architect and operate the full identity lifecycle — joiner/mover/leaver (JML) automation driven by authoritative HR sources, birthright provisioning, SCIM-based downstream integration, and deprovisioning SLAs measured in minutes to hours. - Design and mature the enterprise access model using Agentic AI capabilities: role engineering and role mining, RBAC evolving toward attribute- and policy-based access control (ABAC/PBAC), segregation-of-duties (SoD) rulesets, and risk-based, evidence-quality access certifications that eliminate rubber-stamping. - Own governance of entitlement sprawl across SaaS, IaaS, and on-prem estates, including cloud infrastructure entitlement management (CIEM) and least-privilege enforcement in AWS/Azure environments. Authentication, Authorization & Directory Architecture: - Set the enterprise standard for authentication: phishing-resistant MFA (FIDO2/WebAuthn), passwordless adoption, adaptive/risk-based authentication, and session management policies calibrated to data sensitivity. - Own federation and SSO architecture (SAML 2.0, OIDC/OAuth 2.0), token security and lifetime strategy, and conditional access policy design across the enterprise application portfolio. - Govern directory and identity-store architecture — Entra ID and Active Directory hardening (tiered administration, attack-path reduction), hybrid identity synchronization, and rationalization of legacy identity repositories. - Advance externalized, policy-as-code authorization patterns (e.g., OPA/Rego, Cedar) for fine-grained, auditable access decisions in modern applications. Privileged Access & Non-Human Identity: - Own the privileged access management program: credential vaulting, session isolation and recording, just-in-time/zero-standing-privilege elevation, and break-glass governance. - Establish lifecycle governance for non-human identities — service accounts, API keys, certificates, workload identities, and emerging AI-agent identities — including inventory, ownership attestation, secrets management, and automated rotation. IAM Platform Engineering & Operations: - Lead evaluation, selection, and engineering of the IAM technology stack — IGA, access management/IdP, PAM, CIEM, and ITDR platforms — with a bias toward API-first integration, infrastructure-as-code deployment, and CI/CD-managed identity configuration. - Ensure availability, resilience, and disaster recovery of identity services as tier-zero infrastructure; identity outages are business outages. - Instrument the identity fabric end to end: stream identity telemetry to SIEM, define detections for identity-centric attack techniques (credential stuffing, token theft, MFA fatigue, golden ticket/SAML forging, privilege escalation), and partner with the SOC on ITDR playbooks. Risk, Compliance & Assurance: - Own identity-related control design and operating effectiveness for HIPAA Security Rule safeguards, HITRUST CSF, SOC 1/SOC 2, SOX ITGCs, and applicable state privacy regimes; serve as primary identity interface for