Senior ICAM Engineer
for section headings like About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We should map content accordingly.
We must not repeat job title as heading. No Job ID. Remove boilerplate: cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, application instructions. Also remove disclaimer? The disclaimer includes EEO etc. Should be removed. Also remove "About Capgemini"? That's not a required heading but could be considered "About the role"? Actually "About Capgemini" is company description, not role. We could include as a paragraph maybe under a generic section? The instruction: include a section ONLY when the posting has real, specific content for it — never emit a heading followed by filler/placeholder text. We have content for Responsibilities, Requirements (maybe Required Qualifications), Qualifications (maybe Technical Expertise), Skills (maybe Technical Expertise), Benefits, Pay, Schedule. The posting includes salary range and benefits info. So we can create sections: Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay. Schedule not present, so omit.
We need to use for each section heading. Use - for any list of duties/requirements/benefits. Use
for prose.
We must preserve ALL substantive information; do not invent or summarize away detail. So we need to include all details from responsibilities, qualifications, technical expertise, benefits, pay.
We need to format responsibilities as list items. Required Qualifications as list? Could be list. Technical Expertise as list? Could be list.
Benefits: "Full time regular employees are eligible for paid time off, medical/dental/vision insurance, 401(k), and any other benefits to eligible employees." That's a sentence; could be list.
Pay: "The base salary range for the tagged location is $110k - $130k. This role may be eligible for other compensation including variable compensation, bonus, or commission." That's prose.
We need to omit boilerplate: disclaimer, EEO, etc. Also remove "About Capgemini" maybe? It's not required heading but could be considered as "About the role"? Actually "About the role" is like position overview. We have Position Overview paragraph. Could be placed under a heading "About the role". The instruction: use
for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). So we should include About the role heading with the Position Overview paragraph.
Thus sections: About the role (position overview), Responsibilities, Requirements (maybe Required Qualifications), Qualifications (maybe Technical Expertise?), Skills (maybe also Technical Expertise?), Benefits, Pay.
But we need to avoid duplication. We have Required Qualifications and Technical Expertise. Could map Required Qualifications to Requirements section, and Technical Expertise to Skills section. Qualifications heading maybe for education/experience? Actually we have both Required Qualifications (education, experience, clearance, certifications) and Technical Expertise (skills). So we can have Requirements (for Required Qualifications) and Skills (for Technical Expertise). The Qualifications heading maybe not needed if we already have Requirements. But we could also have Qualifications for education/experience and Skills for technical expertise. However we have only one set of qualifications. Let's decide: Use Requirements for Required Qualifications (education, experience, clearance, certifications). Use Skills for Technical Expertise (directory tech, scripting, etc.). We'll omit Qualifications heading to avoid duplication.
Thus sections: About the role, Responsibilities, Requirements, Skills, Benefits, Pay.
Now we need to ensure we don't include filler like "commensurate with experience". Not present.
Now produce HTML fragment.
Structure:
About the role
Position Overview The Senior ICAM Engineer specializes in designing, deploying, and maintaining Master Entitlement Records (MER) and authoritative identity pipelines using the Radiant Logic RadiantOne Virtual Directory Server (VDS) / FID platform. This role is responsible for virtualizing, unifying, and correlating disparate identity, group, and access entitlement data across heterogeneous enterprise data stores, directories, databases, and cloud environments. The engineer ensures the creation of a centralized, real-time "single source of identity truth" (Master Entitlement Record) to support fine-grained access control, Attribute-Based Access Control (ABAC), Identity Governance and Administration (IGA), and Zero Trust Architecture (ZTA) initiatives.
But note the Position Overview paragraph includes "Position Overview". Might be redundant; we can keep the content but maybe remove the phrase "Position Overview". The instruction: preserve ALL substantive information; do not invent or summarize away detail. So we should keep the exact text? It says "Position Overview The Senior ICAM Engineer...". If we remove "Position Overview" we are removing some text. Might be considered boilerplate? It's a section heading but we already have heading. Safer to keep the sentence as is, but we could keep "Position Overview" as part of paragraph. It's not harmful.
Thus paragraph: "Position Overview The Senior ICAM Engineer specializes in designing, deploying, and maintaining Master Entitlement Records (MER) and authoritative identity pipelines using the Radiant Logic RadiantOne Virtual Directory Server (VDS) / FID platform. This role is responsible for virtualizing, unifying, and correlating disparate identity, group, and access entitlement data across heterogeneous enterprise data stores, directories, databases, and cloud environments. The engineer ensures the creation of a centralized, real-time "single source of identity truth" (Master Entitlement Record) to support fine-grained access control, Attribute-Based Access Control (ABAC), Identity Governance and Administration (IGA), and Zero Trust Architecture (ZTA) initiatives."
Now Responsibilities: list each responsibility.
We need to extract each bullet from the responsibilities paragraph which is a long sentence separated by periods. Let's split:
- Design, build, configure, and maintain Radiant Logic RadiantOne FID/VDS instances across complex hybrid environments (on-premises and cloud).
- Develop, manage, and optimize unified identity views, object mapping, schema extensions, and entitlement aggregation models to support downstream authorization and governance engines.
- Connect, join, translate, and synthesize identity data from disparate sources including Active Directory, Microsoft Entra ID, LDAP directories, relational databases (SQL, Oracle), web services/APIs, and flat files.
- Write and maintain advanced mapping, join logic, cascading rules, computed attributes, and real-time synchronization pipelines using Radiant Logic native tools and custom scripting.
- Implement dynamic context and attribute feeds to power Policy Decision Points (PDP) and Policy Enforcement Points (PEP) across the enterprise identity mesh.
- Perform load balancing, context caching, indexing optimization, cluster synchronization, and performance tuning for Radiant Logic clusters to maintain low-latency response times for high-volume authentication/authorization queries.
- Manage platform upgrades, version migrations, cluster health checks, backup/disaster recovery procedures, and security hardings (STIG compliance).
- Serve as the senior technical escalation point for data synchronization failures, identity resolution edge cases, schema inconsistencies, and directory performance degradation.
Now Requirements (Required Qualifications):
- Bachelor’s Degree in Cybersecurity, Computer Science, Information Technology, Systems Engineering, or a related technical discipline.
- Minimum of six (6) years of professional experience in Identity, Credential, and Access Management (ICAM), with at least three (3) years dedicated to hands-on engineering and administration of Radiant Logic RadiantOne (FID/VDS) platforms.
- Must possess an active (Secret clearance required).
- Active IAT Level II Baseline Certification in accordance with DoD 8570.01-M / DoD 8140 (e.g., CompTIA Security+ CE, CySA+, GSEC, CCNA Security, or higher level certifications like CISSP or CASP+).
Now Skills (Technical Expertise):
- Deep understanding of directory technologies, schema structures, and protocols: LDAP, Active Directory, Azure AD/Entra ID, SAML, OAuth, OIDC, and REST/SOAP web services.
- Practical experience designing complex joins, user unions, auto-generated attributes, and complex hierarchy transformations in Radiant Logic.
- Solid working knowledge of relational database structures and query languages (SQL Server, Oracle, PostgreSQL).
- Familiarity with scripting languages (PowerShell, Bash, Python) for operational automation and data validation.
- Exceptional analytical problem-solving skills, precision in data modeling, and the ability to articulate identity infrastructure concepts to both technical leads and program managers.
- Direct experience supporting Federal ICAM (FICAM), DoD ICAM, or enterprise Zero Trust Architecture (ZTA) implementations.
- Integration experience connecting Radiant Logic to IGA platforms (e.g., SailPoint), Access Managers (e.g., Ping, Okta, ForgeRock), or PAM solutions (e.g., CyberArk).
Now Benefits:
- Full time regular employees are eligible for paid time off, medical/dental/vision insurance, 401(k), and any other benefits to eligible employees.
Now Pay:
- The base salary range for the tagged location is $110k - $130k. This role may be eligible for other compensation including variable compensation, bonus, or commission.
We need to output as HTML fragment. Use headings, - for lists,
for prose. For Benefits and Pay we could use
or
. Since they are sentences, we can use . But the instruction: Use
- for any list of duties/requirements/benefits, and
for prose. Benefits is a list? It's a single sentence but could be considered a list of benefits. Safer to use
for prose. Pay also prose.
Thus:
About the role
Position Overview The Senior ICAM Engineer specializes in designing, deploying, and maintaining Master Entitlement Records (MER) and authoritative identity pipelines using the Radiant Logic RadiantOne Virtual Directory Server (VDS) / FID platform. This role is responsible for virtualizing, unifying, and correlating disparate identity, group, and access entitlement data across heterogeneous enterprise data stores, directories, databases, and cloud environments. The engineer ensures the creation of a centralized, real-time "single source of identity truth" (Master Entitlement Record) to support fine-grained access control, Attribute-Based Access Control (ABAC), Identity Governance and Administration (IGA), and Zero Trust Architecture (ZTA) initiatives.
Responsibilities
- Design, build, configure, and maintain Radiant Logic RadiantOne FID/VDS instances across complex hybrid environments (on-premises and cloud).
- Develop, manage, and optimize unified identity views, object mapping, schema extensions, and entitlement aggregation models to support downstream authorization and governance engines.
- Connect, join, translate, and synthesize identity data from disparate sources including Active Directory, Microsoft Entra ID, LDAP directories, relational databases (SQL, Oracle), web services/APIs, and flat files.
- Write and maintain advanced mapping, join logic, cascading rules, computed attributes, and real-time synchronization pipelines using Radiant Logic native tools and custom scripting.
- Implement dynamic context and attribute feeds to power Policy Decision Points (PDP) and Policy Enforcement Points (PEP) across the enterprise identity mesh.
- Perform load balancing, context caching, indexing optimization, cluster synchronization, and performance tuning for Radiant Logic clusters to maintain low-latency response times for high-volume authentication/authorization queries.
- Manage platform upgrades, version migrations, cluster health checks, backup/disaster recovery procedures, and security hardings (STIG compliance).
- Serve as the senior technical
- for any list of duties/requirements/benefits. Use
for prose. We must preserve ALL substantive information; do not invent or summarize away detail. So we need to include all details from responsibilities, qualifications, technical expertise, benefits, pay. We need to format responsibilities as list items. Required Qualifications as list? Could be list. Technical Expertise as list? Could be list. Benefits: "Full time regular employees are eligible for paid time off, medical/dental/vision insurance, 401(k), and any other benefits to eligible employees." That's a sentence; could be list. Pay: "The base salary range for the tagged location is $110k - $130k. This role may be eligible for other compensation including variable compensation, bonus, or commission." That's prose. We need to omit boilerplate: disclaimer, EEO, etc. Also remove "About Capgemini" maybe? It's not required heading but could be considered as "About the role"? Actually "About the role" is like position overview. We have Position Overview paragraph. Could be placed under a heading "About the role". The instruction: use
for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). So we should include About the role heading with the Position Overview paragraph. Thus sections: About the role (position overview), Responsibilities, Requirements (maybe Required Qualifications), Qualifications (maybe Technical Expertise?), Skills (maybe also Technical Expertise?), Benefits, Pay. But we need to avoid duplication. We have Required Qualifications and Technical Expertise. Could map Required Qualifications to Requirements section, and Technical Expertise to Skills section. Qualifications heading maybe for education/experience? Actually we have both Required Qualifications (education, experience, clearance, certifications) and Technical Expertise (skills). So we can have Requirements (for Required Qualifications) and Skills (for Technical Expertise). The Qualifications heading maybe not needed if we already have Requirements. But we could also have Qualifications for education/experience and Skills for technical expertise. However we have only one set of qualifications. Let's decide: Use Requirements for Required Qualifications (education, experience, clearance, certifications). Use Skills for Technical Expertise (directory tech, scripting, etc.). We'll omit Qualifications heading to avoid duplication. Thus sections: About the role, Responsibilities, Requirements, Skills, Benefits, Pay. Now we need to ensure we don't include filler like "commensurate with experience". Not present. Now produce HTML fragment. Structure:
About the role
Position Overview The Senior ICAM Engineer specializes in designing, deploying, and maintaining Master Entitlement Records (MER) and authoritative identity pipelines using the Radiant Logic RadiantOne Virtual Directory Server (VDS) / FID platform. This role is responsible for virtualizing, unifying, and correlating disparate identity, group, and access entitlement data across heterogeneous enterprise data stores, directories, databases, and cloud environments. The engineer ensures the creation of a centralized, real-time "single source of identity truth" (Master Entitlement Record) to support fine-grained access control, Attribute-Based Access Control (ABAC), Identity Governance and Administration (IGA), and Zero Trust Architecture (ZTA) initiatives.
But note the Position Overview paragraph includes "Position Overview". Might be redundant; we can keep the content but maybe remove the phrase "Position Overview". The instruction: preserve ALL substantive information; do not invent or summarize away detail. So we should keep the exact text? It says "Position Overview The Senior ICAM Engineer...". If we remove "Position Overview" we are removing some text. Might be considered boilerplate? It's a section heading but we already have heading. Safer to keep the sentence as is, but we could keep "Position Overview" as part of paragraph. It's not harmful. Thus paragraph: "Position Overview The Senior ICAM Engineer specializes in designing, deploying, and maintaining Master Entitlement Records (MER) and authoritative identity pipelines using the Radiant Logic RadiantOne Virtual Directory Server (VDS) / FID platform. This role is responsible for virtualizing, unifying, and correlating disparate identity, group, and access entitlement data across heterogeneous enterprise data stores, directories, databases, and cloud environments. The engineer ensures the creation of a centralized, real-time "single source of identity truth" (Master Entitlement Record) to support fine-grained access control, Attribute-Based Access Control (ABAC), Identity Governance and Administration (IGA), and Zero Trust Architecture (ZTA) initiatives." Now Responsibilities: list each responsibility. We need to extract each bullet from the responsibilities paragraph which is a long sentence separated by periods. Let's split: - Design, build, configure, and maintain Radiant Logic RadiantOne FID/VDS instances across complex hybrid environments (on-premises and cloud). - Develop, manage, and optimize unified identity views, object mapping, schema extensions, and entitlement aggregation models to support downstream authorization and governance engines. - Connect, join, translate, and synthesize identity data from disparate sources including Active Directory, Microsoft Entra ID, LDAP directories, relational databases (SQL, Oracle), web services/APIs, and flat files. - Write and maintain advanced mapping, join logic, cascading rules, computed attributes, and real-time synchronization pipelines using Radiant Logic native tools and custom scripting. - Implement dynamic context and attribute feeds to power Policy Decision Points (PDP) and Policy Enforcement Points (PEP) across the enterprise identity mesh. - Perform load balancing, context caching, indexing optimization, cluster synchronization, and performance tuning for Radiant Logic clusters to maintain low-latency response times for high-volume authentication/authorization queries. - Manage platform upgrades, version migrations, cluster health checks, backup/disaster recovery procedures, and security hardings (STIG compliance). - Serve as the senior technical escalation point for data synchronization failures, identity resolution edge cases, schema inconsistencies, and directory performance degradation. Now Requirements (Required Qualifications): - Bachelor’s Degree in Cybersecurity, Computer Science, Information Technology, Systems Engineering, or a related technical discipline. - Minimum of six (6) years of professional experience in Identity, Credential, and Access Management (ICAM), with at least three (3) years dedicated to hands-on engineering and administration of Radiant Logic RadiantOne (FID/VDS) platforms. - Must possess an active (Secret clearance required). - Active IAT Level II Baseline Certification in accordance with DoD 8570.01-M / DoD 8140 (e.g., CompTIA Security+ CE, CySA+, GSEC, CCNA Security, or higher level certifications like CISSP or CASP+). Now Skills (Technical Expertise): - Deep understanding of directory technologies, schema structures, and protocols: LDAP, Active Directory, Azure AD/Entra ID, SAML, OAuth, OIDC, and REST/SOAP web services. - Practical experience designing complex joins, user unions, auto-generated attributes, and complex hierarchy transformations in Radiant Logic. - Solid working knowledge of relational database structures and query languages (SQL Server, Oracle, PostgreSQL). - Familiarity with scripting languages (PowerShell, Bash, Python) for operational automation and data validation. - Exceptional analytical problem-solving skills, precision in data modeling, and the ability to articulate identity infrastructure concepts to both technical leads and program managers. - Direct experience supporting Federal ICAM (FICAM), DoD ICAM, or enterprise Zero Trust Architecture (ZTA) implementations. - Integration experience connecting Radiant Logic to IGA platforms (e.g., SailPoint), Access Managers (e.g., Ping, Okta, ForgeRock), or PAM solutions (e.g., CyberArk). Now Benefits: - Full time regular employees are eligible for paid time off, medical/dental/vision insurance, 401(k), and any other benefits to eligible employees. Now Pay: - The base salary range for the tagged location is $110k - $130k. This role may be eligible for other compensation including variable compensation, bonus, or commission. We need to output as HTML fragment. Useheadings,
- for lists,
for prose. For Benefits and Pay we could use
or
- . Since they are sentences, we can use
- for any list of duties/requirements/benefits, and
for prose. Benefits is a list? It's a single sentence but could be considered a list of benefits. Safer to use
for prose. Pay also prose. Thus:
About the role
Position Overview The Senior ICAM Engineer specializes in designing, deploying, and maintaining Master Entitlement Records (MER) and authoritative identity pipelines using the Radiant Logic RadiantOne Virtual Directory Server (VDS) / FID platform. This role is responsible for virtualizing, unifying, and correlating disparate identity, group, and access entitlement data across heterogeneous enterprise data stores, directories, databases, and cloud environments. The engineer ensures the creation of a centralized, real-time "single source of identity truth" (Master Entitlement Record) to support fine-grained access control, Attribute-Based Access Control (ABAC), Identity Governance and Administration (IGA), and Zero Trust Architecture (ZTA) initiatives.
Responsibilities
- Design, build, configure, and maintain Radiant Logic RadiantOne FID/VDS instances across complex hybrid environments (on-premises and cloud).
- Develop, manage, and optimize unified identity views, object mapping, schema extensions, and entitlement aggregation models to support downstream authorization and governance engines.
- Connect, join, translate, and synthesize identity data from disparate sources including Active Directory, Microsoft Entra ID, LDAP directories, relational databases (SQL, Oracle), web services/APIs, and flat files.
- Write and maintain advanced mapping, join logic, cascading rules, computed attributes, and real-time synchronization pipelines using Radiant Logic native tools and custom scripting.
- Implement dynamic context and attribute feeds to power Policy Decision Points (PDP) and Policy Enforcement Points (PEP) across the enterprise identity mesh.
- Perform load balancing, context caching, indexing optimization, cluster synchronization, and performance tuning for Radiant Logic clusters to maintain low-latency response times for high-volume authentication/authorization queries.
- Manage platform upgrades, version migrations, cluster health checks, backup/disaster recovery procedures, and security hardings (STIG compliance).
- Serve as the senior technical
. But the instruction: Use
- for any list of duties/requirements/benefits, and
- for lists,