Senior Identity & Access Management Engineer

We need to output HTML fragment with sections: About the role? The posting includes description paragraphs. We need to use

for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). We need to decide which sections have content. We have: - Intro about company and role: could be "About the role" or maybe "About the role" includes description of responsibilities? The posting includes responsibilities list after "As a Senior IAM Engineer, You Will ..." which is a list of duties. So we can have a section "Responsibilities" with

• for each bullet. - "Required" section: "To be successful, you will need:" list of required qualifications. That's "Requirements" or "Qualifications". We'll use "Requirements" for required. - "Preferred" section: list of preferred qualifications. Could be "Preferred Qualifications" or "Skills". The instruction says use headings like Skills, Benefits, Pay, Schedule. We can use "Skills" for preferred? But better to separate Required and Preferred? The allowed headings list includes Requirements, Qualifications, Skills. We could use "Requirements" for required, "Preferred Qualifications" maybe not allowed but we could use "Skills" for preferred? However we need to preserve all substantive info; we can combine required and preferred into one "Requirements" section with sub-bullets? But better to have two sections: "Requirements" and "Preferred Qualifications". The instruction says use headings e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. It doesn't forbid other headings? It says use

  for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). Likely they expect those headings only. But we can still use "Qualifications" for required and "Skills" for preferred? Or we could put both required and preferred under "Requirements" and "Qualifications". Let's think. We have Education and Certifications also. Could be under "Qualifications". The posting includes Education and Certifications under "Education" and "Certifications Preferred". Could be part of Qualifications. We have Benefits section: "Financial Benefits Sharing rewards..." etc. That's definitely Benefits. We have Pay? Not mentioned explicitly; only "Competitive CompensationMonthly Bonuses for Eligible Employees". That is compensation info, could be considered Pay. The instruction says only create Pay/Schedule/Benefits sections if posting actually states them. It does state compensation: "Competitive CompensationMonthly Bonuses for Eligible Employees". So we can include a Pay section. Schedule? Not mentioned; no schedule info. So we omit Schedule. We also have "About the role" maybe a brief intro about company and role. Could be used. Thus sections: About the role, Responsibilities, Requirements, Qualifications, Skills?, Benefits, Pay. But we need to avoid duplication and filler. Let's extract content. About the role: The first paragraph(s) describing GreatAmerica and the role: "GreatAmerica is a highly successful entrepreneurial company providing equipment financing to businesses across the United States. Our exemplary customer service, our principle-centered business philosophy and our team-based operating approach are key to our success and growth. We have also recently become a bank! We are looking to add a key member to our Identity & Access Management Team! The Senior Identity & Access Management (IAM) Engineer is responsible for designing, implementing, and continuously enhancing GreatAmerica's identity governance, access management, and privileged access capabilities. This role serves as a senior technical specialist, ensuring identity and access controls are secure, scalable, automated, and aligned with regulatory, audit, and risk management requirements. Working across SailPoint, CyberArk, Okta, and related technologies, the Senior IAM Engineer develops and maintains enterprise identity lifecycle processes, role-based access controls, privileged access solutions, and authentication services. The role partners closely with Security, Audit, Compliance, Infrastructure, and Application teams to translate security and control requirements into effective technical solutions while advancing automation, operational efficiency, and governance maturity. The Senior IAM Engineer plays a key role in strengthening GreatAmerica's identity security program by improving access governance, supporting regulatory compliance, reducing access-related risk, and ensuring the reliability and effectiveness of identity services across the organization." That's a good About the role. Responsibilities: The bullet list after "As a Senior IAM Engineer, You Will". Let's extract each bullet: - Build and maintain automated identity lifecycle workflows, certification campaigns, and connectors within SailPoint IdentityNow, including connector development and integration with enterprise applications (ServiceNow, ILS). - Design, build, and roll out role-based access control (RBAC) models, including role mining, role engineering, and ongoing role lifecycle governance. - Integrate and administer Okta as the enterprise identity provider, including single sign-on (SSO), multi-factor authentication (MFA), and lifecycle management through SCIM provisioning. - Implement and support CyberArk privileged access management (PAM), including credential vaulting, session isolation and monitoring, just-in-time (JIT) elevation policy administration, elimination of standing privileges, and privileged account onboarding. - Support the migration from self-hosted CyberArk PAS to CyberArk Privilege Cloud, report and integration transition, and updates to operational procedures. - Develop self-service and automated access request workflows spanning request intake, approval routing, and fulfillment. - Automate joiner, mover, and leaver (JML) provisioning and deprovisioning processes across enterprise systems to ensure timely and accurate access changes. - Execute recurring access certification campaigns and quarterly configuration reviews (privileged access, password and authentication settings), producing audit-ready evidence for ICFR logical access controls. - Support SOX-related access controls, segregation of duties (SoD) enforcement, and the generation of audit evidence for Internal Control over Financial Reporting (ICFR). - Develop PowerShell and REST API automation for entitlement extracts, reconciliation, reporting, and audit evidence generation. - Apply FFIEC IT examination handbook guidance to identity governance, access control design, and third-party access risk. - Partner with security, audit, compliance, and application teams to translate control requirements into engineered, testable technical solutions. - Troubleshoot, tune, and document IAM integrations and workflows to ensure reliability, performance, and auditability. That's many bullets. Requirements: The "Required" list: - 5+ years of hands-on experience in Identity and Access Management engineering or administration roles. - 3+ years of direct, hands-on experience with SailPoint (IdentityIQ and/or IdentityNow), including lifecycle workflows, certification campaigns, and connector development or integration. - Demonstrated experience designing and deploying RBAC models, including role mining, role engineering, and role lifecycle governance. - Working experience with CyberArk PAM, including vaulting, session isolation and monitoring, and privileged account onboarding. - Strong PowerShell scripting and REST API experience for automation, entitlement extracts, reconciliation, and audit evidence generation. - Proven ability to build access request automation covering requests, approvals, and fulfillment. - Experience automating JML provisioning and deprovisioning across multiple enterprise systems. Qualifications: Could include Education and Certifications? The posting includes: Education: Bachelor's degree with a major in cybersecurity, computer science or related field preferred, but not required. Information security experience may be substituted for requisite education. Certifications Preferred, not required: SailPoint Certified IdentityNow/IdentityIQ Engineer; CyberArk Defender or Sentry; Okta Certified Professional or Administrator; CISSP or equivalent. We could put Education and Certifications under "Qualifications". Or we could have a separate "Qualifications" section for education and certifications. Preferred: The "Preferred" list: - Practical experience integrating and administering Okta as an identity provider, including SSO, MFA, and SCIM-based lifecycle provisioning (depth in two of SailPoint / CyberArk / Okta required; ability to develop depth in the third). - Experience in a financial services environment, with a solid understanding of the regulatory and control landscape applicable to banking or financial institutions. - Experience supporting ICFR and SOX access controls, including segregation of duties and audit evidence preparation. - Familiarity with FFIEC IT examination guidance as it relates to identity governance and logical access. We could treat these as "Preferred Qualifications" but we don't have that heading. Could put under "Skills"? But Skills heading is for skills. However we could also put them under "Qualifications" as preferred. But we need to avoid duplication. Perhaps we can have "Requirements" for required, "Preferred Qualifications" for preferred (though not in list). The instruction says use headings e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. It doesn't forbid other headings but says "Use

  for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." That suggests those are the allowed headings. So we should stick to those. Thus we need to map content to those headings. We have: - About the role: intro. - Responsibilities: duties list. - Requirements: required experience list. - Qualifications: education and certifications? Could also include preferred? But we have Skills heading for skills; maybe we put preferred experience under Skills? But Skills heading is for skills, not experience. However we could treat preferred items as skills. The preferred list includes practical experience integrating Okta, experience in financial services, experience supporting ICFR/SOX, familiarity with FFIEC guidance. Those could be considered skills or qualifications. We could put them under "Skills". That would be nice to have". But heading "Skills" is allowed. Thus we can have: - Skills: preferred items. - Benefits: benefits list. - Pay: compensation info. We should not include Schedule. Now we need to ensure we don't repeat job title as heading. We'll not. We need to strip boilerplate: cookie/navigation/legal/EEO etc. The posting ends with "If your experience aligns closely, please apply..." etc. That's application instructions; we need to remove that. Also "We value diverse backgrounds..." etc. Also "Please note, applicants must be authorized to work..." etc. Those are boilerplate; remove. Also remove duplicated lines. Now produce HTML fragment. We'll wrap each section in

  heading then content. For lists, use

  • . For prose, use

    . We need to preserve all substantive information; do not invent or summarize away detail. Thus we need to include all bullet points exactly as given (maybe minor punctuation). Ensure we keep details like (ServiceNow, ILS), (SSO), (MFA), (SCIM provisioning), etc. Let's craft. About the role: combine paragraphs into one

    maybe multiple

    but we can keep as one

    with sentences. Responsibilities:

    with each bullet as
    • . Requirements:
      with each required bullet. Skills:
      with each preferred bullet. Benefits: list of benefits. The posting includes many benefits under "Financial Benefits Sharing rewards..." then bullet list: Competitive Compensation, Monthly Bonuses for Eligible Employees, 401(k) and Company Match, Annual Profit Sharing, Paid Time Off, Health, Wellbeing, And Family Planning Benefits, Paid Vacation, Paid Sick Days, Paid Holidays, Gym Reimbursement, Health Insurance, Dental Insurance, Vision Insurance, Short-Term and Long-Term Disability, Company Paid Life Insurance, Flexible Spending Accounts (FSA), Health Savings Accounts (HSA), Employee Assistance Program, Parental Leave, Education And Career Planning Benefits, Tuition Assistance, Networking Opportunities, Leadership Development Opportunities, Perks, Paid Parking, Service Awards, Hybrid work arrangements, Business casual environment, A strong organizational culture focused on our greatest asset: you! We need to preserve all. We'll make a
      with each benefit as
      • . Some lines are phrases like "Financial Benefits Sharing rewards is an integral part