Manager of Identity & Access Management

The user wants me to reformat a job posting into clean, well-structured semantic HTML. Let me analyze the content and apply the rules: 1. Use

for section headings (About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule) 2. Use

• for lists,

  for prose 3. Do NOT repeat job title as heading 4. Do NOT put Job ID/requisition numbers as headings - fold minor metadata into short

  or drop 5. Preserve ALL substantive information 6. Remove boilerplate (cookie/navigation/legal/EEO/equal-opportunity/scam-warning, duplicated lines, application instructions) 7. Include section ONLY when posting has real, specific content - never emit heading followed by filler/placeholder text 8. Never create Pay/Schedule/Benefits sections unless posting actually states them 9. Prefer few substantive sections over many thin ones 10. Output ONLY HTML fragment - no /, no markdown code fences Let me parse the job posting: Title: IAM Manager Location: Arlington, TX - Hybrid 3 days onsite Tues-Thurs Duration: Full Time Compensation: $135k - $145k Work Requirements: U.S. Citizen, GC Holders, or Authorized to Work in the U.S. Skillset/Experience section - this is "About the role" content Key Responsibilities - multiple subsections Required Qualifications Preferred Qualifications About INSPYR Solutions - this is company boilerplate, should be removed EEO statement - boilerplate, remove Privacy policy/consent - boilerplate, remove Sections I should create: - About the role (from Skillset/Experience) - Responsibilities (from Key Responsibilities - has multiple subsections) - Requirements (from Required Qualifications) - Qualifications (from Preferred Qualifications) - or combine with Requirements? The rules say "Qualifications" as a heading option. I'll keep them separate since they're distinct in the posting. - Pay (compensation is stated: $135k - $145k) - Schedule (hybrid 3 days onsite Tues-Thurs) - Location (Arlington, TX) - but not a standard heading. Could fold into a short p. The rules mention headings: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. I have: - About the role: yes - Responsibilities: yes - Requirements: yes (Required Qualifications) - Qualifications: yes (Preferred Qualifications) - Skills: not explicitly a separate section, but skills are mentioned throughout - Benefits: not mentioned - Pay: yes ($135k - $145k) - Schedule: yes (Hybrid 3 days onsite Tues-Thurs) I should include Pay and Schedule sections since they're explicitly stated. For location and work requirements (citizenship), I'll fold into a short

  at the top or in About the role. Let me structure:

  Location: Arlington, TX — Hybrid (3 days onsite Tue–Thu). Full-time. U.S. citizens, green-card holders, or work-authorized individuals only.

  About the role

  ...content from Skillset/Experience...

  Responsibilities

  • IAM Strategy & Technical Leadership: ...
  • SailPoint & Identity Governance: ...
  • Enterprise IAM Engineering & Integrations: ...
  • Security, Compliance & Operational Excellence: ...
  But the responsibilities have many bullet points under each subsection. I should preserve all substantive information. The rules say use
  • for any list of duties. The subsections are categories with multiple bullets each. I could make nested lists or separate lists with headings. But the rule says use

    for section headings, not subsections. I could use

    but not specified. Better to keep as

    • with the category as bold or part of the li. But the rule says use
      • for any list of duties/requirements/benefits. I think I should create a list for each major responsibility area, with the area as a heading? But only

        allowed for headings. Could use within

        or just include as prose. Let me re-read: "Use

        for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). Use

        • for any list of duties/requirements/benefits, and

          for prose." So for Responsibilities section, I can have a

          with each top-level responsibility as a
          • , but each has sub-bullets. I could nest
            inside
            • . That's valid HTML. Let me do that. Similarly for Requirements and Qualifications. Now, the "About INSPYR Solutions" and EEO/privacy are boilerplate - remove. Let me write the HTML. First, a short

              for metadata: location, schedule, work authorization, compensation? But compensation and schedule have their own sections. The rules say include Pay and Schedule sections when posting states them. So I'll create those sections. But the metadata paragraph could include location and work authorization. Let me draft:

              Location: Arlington, TX — Hybrid (3 days onsite Tue–Thu). Full-time. Work authorization: U.S. citizens, green-card holders, or individuals authorized to work in the U.S.

              About the role

              We are seeking an experienced Identity & Access Management (IAM) Engineering Manager to lead enterprise identity security initiatives within a large, complex technology environment. This individual will oversee IAM engineering operations, guide technical teams, and drive improvements across identity governance, access management, authentication, and security integrations. The ideal candidate brings a strong technical foundation in SailPoint, broad experience across IAM technologies, and proven success leading engineering teams. This position requires someone who can operate at both a strategic and technical level, translating business requirements into scalable identity solutions while providing direction to engineers and cross-functional stakeholders. This is not a hands-on development position. We are looking for a technical leader who understands IAM architecture, can evaluate complex integrations, troubleshoot critical issues, and develop a long-term vision for enterprise identity management.

              Responsibilities

              • IAM Strategy & Technical Leadership
                • Lead and mentor a team of IAM engineers and analysts responsible for enterprise identity security platforms and integrations.
                • Develop and execute IAM strategies that improve security, automation, operational efficiency, and scalability.
                • Provide technical oversight across SailPoint, CyberArk, Okta, Active Directory, and related identity technologies.
                • Partner with business leaders, application owners, cybersecurity teams, and engineering groups to identify IAM requirements and implement solutions.
                • Evaluate existing IAM processes, identify technology gaps, and establish improvement initiatives.
                • Oversee platform capacity, licensing, vendor relationships, and resource planning to support continued enterprise growth.
                • Lead technical investigations into complex IAM incidents, partnering with engineers and business analysts to identify root causes and implement permanent solutions.
              • SailPoint & Identity Governance
                • Serve as a technical leader for SailPoint IdentityIQ and Identity Security Cloud environments.
                • Oversee application onboarding, identity provisioning, access certifications, and identity lifecycle automation.
                • Guide the design and optimization of Joiner/Mover/Leaver (JML) processes, role-based access controls, and entitlement management.
                • Partner with application and engineering teams to integrate enterprise applications into identity governance frameworks.
                • Evaluate automation opportunities to streamline access requests, approvals, provisioning, and deprovisioning.
                • Ensure SailPoint solutions align with business requirements, security standards, and enterprise architecture.
                • Provide technical guidance on complex SailPoint integrations without serving as the primary developer.
              • Enterprise IAM Engineering & Integrations
                • Oversee identity and access management capabilities across on-premises, cloud, and hybrid environments.
                • Provide architectural direction for Active Directory, Okta, CyberArk, and certificate management services.
                • Guide the integration of IAM platforms with enterprise applications, HR systems, IT service management tools, and cloud technologies.
                • Oversee authentication and access security capabilities, including SSO, MFA, privileged access management, and directory services.
                • Establish technical standards and best practices for secure, scalable IAM implementations.
                • Support the modernization of existing identity platforms and the adoption of new technologies.
              • Security, Compliance & Operational Excellence
                • Ensure IAM processes and platforms support enterprise security policies, regulatory requirements, and audit expectations.
                • Identify access-related vulnerabilities, control gaps, and operational risks while developing appropriate remediation strategies.
                • Support access reviews, compliance assessments, and audit activities.
                • Establish operational metrics and reporting to evaluate IAM platform performance, reliability, and security.
                • Collaborate with cybersecurity and infrastructure leadership to strengthen identity controls and reduce organizational risk.
                • Drive continuous improvement across IAM engineering, incident management, and service delivery.

              Requirements

              • 3+ years of formal IT or cybersecurity leadership experience.
              • 5+ years of experience in Identity & Access Management, including experience supporting complex enterprise environments.
              • Proven experience leading IAM engineers, analysts, or technical teams.
              • Strong technical expertise with SailPoint IdentityIQ and/or Identity Security Cloud, including identity governance, provisioning, integrations, and lifecycle management.
              • Working knowledge of additional IAM technologies such as CyberArk, Okta, Active Directory, and Azure AD/Entra ID.
              • Experience overseeing enterprise application onboarding and identity automation initiatives.
              • Strong understanding of IAM architecture, identity governance, privileged access management, and authentication technologies.
              • Ability to evaluate technical designs, guide engineering teams, and troubleshoot complex identity-related issues.
              • Experience developing IAM roadmaps, managing priorities, and supporting enterprise technology initiatives.
              • Strong communication skills with the ability to engage both technical engineering teams and nontechnical business stakeholders.
              • Understanding of security frameworks, access controls, compliance requirements, and risk management.
              • Experience managing vendor relationships, platform licensing, or technology investments.
              • Bachelor's degree in a related field or equivalent professional experience.

              Qualifications

              • Experience supporting IAM environments with hundreds or thousands of integrated applications.
              • Familiarity with PKI, certificate management, and hybrid directory architectures.
              • Experience leading IAM modernization, automation, or large-scale application integration initiatives.
              • Knowledge of ServiceNow integrations and enterprise identity workflows.