Senior IAM Engineer - (Entra ID/AD)
for section headings: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. Only include sections if posting has real specific content. We must preserve all substantive info, not invent. Remove boilerplate: EEO, legal, etc. Also remove application instructions, navigation, cookie, etc. Also remove duplicated lines. We need to extract content.
Let's parse posting:
First paragraph: "CLA is a top 10 national professional services firm where our purpose is to create opportunities every day, for our clients, our people, and our communities through industry-focused wealth advisory, digital, audit, tax, consulting, and outsourcing services. Even with more than 8,500 people, 130 U.S. locations, and a global reach, we promise to know you and help you. CLA is dedicated to building a culture that invites different beliefs and perspectives to the table, so we can truly know and help our clients, communities, and each other. CLA is growing and seeking to hire an experienced Identity & Access Management (IAM) Senior Engineer to join our talented Information Technology team. The position offers growth, flexibility and a collaborative work environment."
We can treat that as "About the role" maybe. Or "About the role" could be description of role and company. We'll include an About the role section with that content.
Next: "How you’ll create opportunities in this Identity & Access Management (IAM) Senior Engineer position" then bullet list of responsibilities. Those are responsibilities.
Then sections: "Identity Governance & Access Management", "Identity Architecture & Platform Administration", "Infrastructure Automation & Engineering". Those are more detailed responsibilities/sub-sections. We could combine them under Responsibilities.
Then "Technical Competencies" list of required skills/experience. That could be Requirements or Skills.
Then "Experience As our ideal candidate, you have:" list of required experience. That's Requirements.
Then "Preferred Qualifications" list.
Then "Education Bachelor's degree is required..." That's Qualifications/Education.
Then "Wellness at CLA" benefits description: health, dental, vision, 401k and much more. That's Benefits.
No explicit Pay or Schedule mentioned. So we should not include Pay or Schedule sections.
We must not repeat job title as heading. Already not.
We must not include Job ID etc.
We must not include boilerplate like Equal Opportunity Employer etc. Remove that.
Also remove "Wellness at CLA" maybe we keep as Benefits.
We need to output only HTML fragment, using for each section heading, - for lists,
for prose.
We need to preserve all substantive info. Let's extract.
About the role: combine first paragraph plus maybe sentence about position offers growth etc.
Let's extract:
"CLA is a top 10 national professional services firm where our purpose is to create opportunities every day, for our clients, our people, and our communities through industry-focused wealth advisory, digital, audit, tax, consulting, and outsourcing services. Even with more than 8,500 people, 130 U.S. locations, and a global reach, we promise to know you and help you. CLA is dedicated to building a culture that invites different beliefs and perspectives to the table, so we can truly know and help our clients, communities, and each other. CLA is growing and seeking to hire an experienced Identity & Access Management (IAM) Senior Engineer to join our talented Information Technology team. The position offers growth, flexibility and a collaborative work environment."
That's prose.
Responsibilities: list from "How you’ll create opportunities..." plus the three sub-sections.
Let's gather all responsibility bullet points:
From "How you’ll create opportunities...":
- Execute the implementation and maintenance of complex Identity & Access Management (IAM) infrastructure.
- Plan and execute IAM projects and programs, ensuring alignment with business requirements, security standards, and delivery timelines.
- Automate and optimize identity lifecycle management processes, access provisioning, and governance controls.
- Integrate Entra ID with enterprise systems, cloud platforms, and third-party applications.
- Collaborate with cross-functional teams to support and drive IAM program goals and enterprise security initiatives.
- Monitor, troubleshoot, and maintain IAM infrastructure, ensuring optimal performance, reliability, and security.
- Document and maintain comprehensive IAM architecture, workflows, standards, and operating procedures.
- Implement and enforce IAM security, compliance, governance, and risk management best practices.
- Provide technical leadership and mentorship to junior team members.
- Participate in an on-call rotation supporting critical IAM systems and services.
Then "Identity Governance & Access Management" bullet points:
- Design and support Role-Based Access Control (RBAC) models and access governance frameworks.
- Manage Privileged Identity Management (PIM) processes and privileged access controls.
- Implement and support passwordless authentication, managed identities, and modern identity security practices.
- Develop and maintain identity lifecycle processes, including onboarding, transfers, and offboarding.
- Ensure access controls comply with regulatory, audit, and security requirements.
- Support Identity Governance and Administration (IGA) capabilities and access certification processes.
Then "Identity Architecture & Platform Administration":
- Administer and support Microsoft Entra ID, Active Directory, and hybrid identity environments.
- Manage on-premises Active Directory infrastructure, including Domain Controllers, organizational units, and directory services.
- Design, maintain, and enforce Group Policy Objects (GPOs) to support enterprise security and operational requirements.
- Design, implement, and maintain identity federation and authentication solutions.
- Support SAML, OAuth, and OpenID Connect integrations across enterprise applications.
- Implement and maintain Entra B2B, Entra External Identity, and Conditional Access Policies.
- Partner with business and technical teams to evaluate identity and access requirements for new systems and applications.
- Develop scalable and secure identity solutions that support cloud and hybrid environments.
Then "Infrastructure Automation & Engineering":
- Develop and maintain Infrastructure as Code (IaC) solutions utilizing Terraform and related automation frameworks.
- Create and support automation solutions using PowerShell, Python, and Bash scripting.
- Improve operational efficiency through automation and process standardization.
- Support Active Directory, Group Policy, DNS, Entra ID, and Azure identity services across the enterprise.
- Continuously evaluate and implement improvements to IAM infrastructure and operational processes.
All these are responsibilities.
Now Requirements/Skills: "Technical Competencies" list:
- Strong hands-on experience administering Active Directory, Domain Controllers, Group Policy Objects (GPO), and DNS services.
- Strong hands-on experience with Microsoft Entra ID administration and identity lifecycle management.
- Advanced PowerShell scripting and automation experience.
- Experience designing and managing Conditional Access Policies.
- Experience with Identity Governance and Administration (IGA) platforms and controls.
- Knowledge of SAML, OAuth, OpenID Connect, and modern authentication protocols.
- Experience with RBAC, PIM, passwordless authentication, managed identities, and identity governance technologies.
- Experience with Terraform, Infrastructure as Code (IaC), and automation frameworks.
- Experience supporting cloud, hybrid, and enterprise IAM environments.
- Experience with PingOne is preferred.
That's a mix of required and preferred; but we can treat as Requirements/Skills.
Then "Experience As our ideal candidate, you have:" list:
- 4+ years of experience required
- Experience managing hybrid identity environments across Microsoft Entra ID and Active Directory.
- Experience administering Domain Controllers, Group Policy, DNS, and enterprise authentication services.
- Experience implementing Conditional Access, RBAC, PIM, and identity governance solutions.
- Experience developing PowerShell automations and Infrastructure as Code solutions.
- Experience integrating enterprise applications using SAML, OAuth, and OpenID Connect.
That's required experience.
Then "Preferred Qualifications":
- Experience with PingOne and other enterprise identity platforms.
- Experience with Entra B2B and Entra External Identity.
- Experience supporting identity governance, access certification, and compliance programs.
- Relevant Microsoft, Security, Identity, or Cloud certifications preferred.
Then Education:
- Bachelor's degree is required.
- Combination of relevant experience, education, and training may be accepted in lieu of degree.
- Degrees in Computer Science, Information Technology, or a related field are preferred.
We could have sections: Requirements (maybe combine experience and technical competencies), Qualifications (education), Skills (maybe technical competencies), Preferred Qualifications.
But we must not create thin sections; better to combine similar content.
We have headings allowed: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule.
We need to decide mapping.
We could do:
- About the role: company overview and role summary.
- Responsibilities: all responsibility bullets.
- Requirements: required experience (4+ years, hybrid IAM, AD, etc.) plus technical competencies (maybe treat as skills). But we could separate Skills and Requirements.
Given we have both Skills and Requirements headings allowed, we could put technical competencies under Skills, and experience under Requirements. Qualifications for education. Preferred Qualifications maybe could be included under Requirements or Skills as a subsection but we must not create extra headings; we could incorporate preferred qualifications into Requirements or Skills as a list but note they are preferred. However we must not invent headings; we can include them as part of the same section with a note.
But the instruction: "Prefer a few substantive sections over many thin ones." So maybe we combine Requirements and Qualifications into one section? But we have separate headings allowed; we could still use both if they have substantive content.
Let's think: We have substantive content for:
- About the role
- Responsibilities
- Requirements (experience)
- Skills (technical competencies)
- Qualifications (education)
- Benefits
Preferred Qualifications could be merged into Requirements or Skills as a subsection but we need to keep heading? Could add a
inside the section noting "Preferred qualifications include..." but not a separate heading.
We must not create Pay or Schedule sections.
Thus final HTML:
About the role
...
Responsibilities
- ...
...
Requirements
- 4+ years of experience required
- Experience managing hybrid identity environments across Microsoft Entra ID and Active Directory.
- Experience administering Domain Controllers, Group Policy, DNS, and enterprise authentication services.
- Experience implementing Conditional Access, RBAC, PIM, and identity governance solutions.
- Experience developing PowerShell automations and Infrastructure as Code solutions.
- Experience integrating enterprise applications using SAML, OAuth, and OpenID Connect.
Maybe also include "Experience with PingOne is preferred." as part of Requirements? But it's preferred; we could add a note: Preferred qualifications include experience with PingOne and other enterprise identity platforms, Entra B2B and Entra External Identity, supporting identity governance, access certification, and compliance programs, and relevant Microsoft, Security, Identity, or Cloud certifications.
inside Requirements or Skills.
Better to put under Skills? Actually technical competencies are skills. Preferred qualifications could be added as a note under Skills.
Let's do:
Skills
- Strong hands-on experience administering Active Directory, Domain Controllers, Group Policy Objects (GPO), and DNS services.
- Strong hands-on experience with Microsoft Entra ID administration and identity lifecycle management.
- Advanced PowerShell scripting and automation experience.
- Experience designing and managing Conditional Access Policies.
- Experience with Identity Governance and Administration (IGA) platforms and controls.
- Knowledge of SAML, OAuth, OpenID Connect, and modern authentication protocols.
- Experience with RBAC, PIM, passwordless authentication, managed identities, and identity governance technologies.
- Experience with Terraform, Infrastructure as Code (IaC), and automation frameworks.
- Experience supporting cloud, hybrid, and enterprise IAM environments.
- Experience with PingOne is preferred.
- for lists,
for prose. We need to preserve all substantive info. Let's extract. About the role: combine first paragraph plus maybe sentence about position offers growth etc. Let's extract: "CLA is a top 10 national professional services firm where our purpose is to create opportunities every day, for our clients, our people, and our communities through industry-focused wealth advisory, digital, audit, tax, consulting, and outsourcing services. Even with more than 8,500 people, 130 U.S. locations, and a global reach, we promise to know you and help you. CLA is dedicated to building a culture that invites different beliefs and perspectives to the table, so we can truly know and help our clients, communities, and each other. CLA is growing and seeking to hire an experienced Identity & Access Management (IAM) Senior Engineer to join our talented Information Technology team. The position offers growth, flexibility and a collaborative work environment." That's prose. Responsibilities: list from "How you’ll create opportunities..." plus the three sub-sections. Let's gather all responsibility bullet points: From "How you’ll create opportunities...": - Execute the implementation and maintenance of complex Identity & Access Management (IAM) infrastructure. - Plan and execute IAM projects and programs, ensuring alignment with business requirements, security standards, and delivery timelines. - Automate and optimize identity lifecycle management processes, access provisioning, and governance controls. - Integrate Entra ID with enterprise systems, cloud platforms, and third-party applications. - Collaborate with cross-functional teams to support and drive IAM program goals and enterprise security initiatives. - Monitor, troubleshoot, and maintain IAM infrastructure, ensuring optimal performance, reliability, and security. - Document and maintain comprehensive IAM architecture, workflows, standards, and operating procedures. - Implement and enforce IAM security, compliance, governance, and risk management best practices. - Provide technical leadership and mentorship to junior team members. - Participate in an on-call rotation supporting critical IAM systems and services. Then "Identity Governance & Access Management" bullet points: - Design and support Role-Based Access Control (RBAC) models and access governance frameworks. - Manage Privileged Identity Management (PIM) processes and privileged access controls. - Implement and support passwordless authentication, managed identities, and modern identity security practices. - Develop and maintain identity lifecycle processes, including onboarding, transfers, and offboarding. - Ensure access controls comply with regulatory, audit, and security requirements. - Support Identity Governance and Administration (IGA) capabilities and access certification processes. Then "Identity Architecture & Platform Administration": - Administer and support Microsoft Entra ID, Active Directory, and hybrid identity environments. - Manage on-premises Active Directory infrastructure, including Domain Controllers, organizational units, and directory services. - Design, maintain, and enforce Group Policy Objects (GPOs) to support enterprise security and operational requirements. - Design, implement, and maintain identity federation and authentication solutions. - Support SAML, OAuth, and OpenID Connect integrations across enterprise applications. - Implement and maintain Entra B2B, Entra External Identity, and Conditional Access Policies. - Partner with business and technical teams to evaluate identity and access requirements for new systems and applications. - Develop scalable and secure identity solutions that support cloud and hybrid environments. Then "Infrastructure Automation & Engineering": - Develop and maintain Infrastructure as Code (IaC) solutions utilizing Terraform and related automation frameworks. - Create and support automation solutions using PowerShell, Python, and Bash scripting. - Improve operational efficiency through automation and process standardization. - Support Active Directory, Group Policy, DNS, Entra ID, and Azure identity services across the enterprise. - Continuously evaluate and implement improvements to IAM infrastructure and operational processes. All these are responsibilities. Now Requirements/Skills: "Technical Competencies" list: - Strong hands-on experience administering Active Directory, Domain Controllers, Group Policy Objects (GPO), and DNS services. - Strong hands-on experience with Microsoft Entra ID administration and identity lifecycle management. - Advanced PowerShell scripting and automation experience. - Experience designing and managing Conditional Access Policies. - Experience with Identity Governance and Administration (IGA) platforms and controls. - Knowledge of SAML, OAuth, OpenID Connect, and modern authentication protocols. - Experience with RBAC, PIM, passwordless authentication, managed identities, and identity governance technologies. - Experience with Terraform, Infrastructure as Code (IaC), and automation frameworks. - Experience supporting cloud, hybrid, and enterprise IAM environments. - Experience with PingOne is preferred. That's a mix of required and preferred; but we can treat as Requirements/Skills. Then "Experience As our ideal candidate, you have:" list: - 4+ years of experience required - Experience managing hybrid identity environments across Microsoft Entra ID and Active Directory. - Experience administering Domain Controllers, Group Policy, DNS, and enterprise authentication services. - Experience implementing Conditional Access, RBAC, PIM, and identity governance solutions. - Experience developing PowerShell automations and Infrastructure as Code solutions. - Experience integrating enterprise applications using SAML, OAuth, and OpenID Connect. That's required experience. Then "Preferred Qualifications": - Experience with PingOne and other enterprise identity platforms. - Experience with Entra B2B and Entra External Identity. - Experience supporting identity governance, access certification, and compliance programs. - Relevant Microsoft, Security, Identity, or Cloud certifications preferred. Then Education: - Bachelor's degree is required. - Combination of relevant experience, education, and training may be accepted in lieu of degree. - Degrees in Computer Science, Information Technology, or a related field are preferred. We could have sections: Requirements (maybe combine experience and technical competencies), Qualifications (education), Skills (maybe technical competencies), Preferred Qualifications. But we must not create thin sections; better to combine similar content. We have headings allowed: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We need to decide mapping. We could do: - About the role: company overview and role summary. - Responsibilities: all responsibility bullets. - Requirements: required experience (4+ years, hybrid IAM, AD, etc.) plus technical competencies (maybe treat as skills). But we could separate Skills and Requirements. Given we have both Skills and Requirements headings allowed, we could put technical competencies under Skills, and experience under Requirements. Qualifications for education. Preferred Qualifications maybe could be included under Requirements or Skills as a subsection but we must not create extra headings; we could incorporate preferred qualifications into Requirements or Skills as a list but note they are preferred. However we must not invent headings; we can include them as part of the same section with a note. But the instruction: "Prefer a few substantive sections over many thin ones." So maybe we combine Requirements and Qualifications into one section? But we have separate headings allowed; we could still use both if they have substantive content. Let's think: We have substantive content for: - About the role - Responsibilities - Requirements (experience) - Skills (technical competencies) - Qualifications (education) - Benefits Preferred Qualifications could be merged into Requirements or Skills as a subsection but we need to keep heading? Could add a
inside the section noting "Preferred qualifications include..." but not a separate heading. We must not create Pay or Schedule sections. Thus final HTML:
About the role
...
Responsibilities
- ... ...
Requirements
- 4+ years of experience required
- Experience managing hybrid identity environments across Microsoft Entra ID and Active Directory.
- Experience administering Domain Controllers, Group Policy, DNS, and enterprise authentication services.
- Experience implementing Conditional Access, RBAC, PIM, and identity governance solutions.
- Experience developing PowerShell automations and Infrastructure as Code solutions.
- Experience integrating enterprise applications using SAML, OAuth, and OpenID Connect.
Preferred qualifications include experience with PingOne and other enterprise identity platforms, Entra B2B and Entra External Identity, supporting identity governance, access certification, and compliance programs, and relevant Microsoft, Security, Identity, or Cloud certifications.
inside Requirements or Skills. Better to put under Skills? Actually technical competencies are skills. Preferred qualifications could be added as a note under Skills. Let's do:Skills
- Strong hands-on experience administering Active Directory, Domain Controllers, Group Policy Objects (GPO), and DNS services.
- Strong hands-on experience with Microsoft Entra ID administration and identity lifecycle management.
- Advanced PowerShell scripting and automation experience.
- Experience designing and managing Conditional Access Policies.
- Experience with Identity Governance and Administration (IGA) platforms and controls.
- Knowledge of SAML, OAuth, OpenID Connect, and modern authentication protocols.
- Experience with RBAC, PIM, passwordless authentication, managed identities, and identity governance technologies.
- Experience with Terraform, Infrastructure as Code (IaC), and automation frameworks.
- Experience supporting cloud, hybrid, and enterprise IAM environments.
- Experience with PingOne is preferred.