Jobs · North Carolina

Senior IAM Engineer (Ping Identity/CIAM)

Deloitte · Charlotte, NC · 4 wk ago
HybridFull-time
We need to produce HTML fragment with headings

for sections present: About the role? The posting includes "Work you'll do" description. Could treat as "About the role" or " maybe "Work you'll do". Use

for section headings like About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We need to include sections only when posting has real specific content. We have content: description of work: "In this interesting and diverse role, you'll be engaging in the development, implementation and support of systems that manage digital identities, access controls and authentication processes. This position collaborates with team members to: ensure secure and efficient access to Deloitte applications while upholding cyber security best practices define the future vision of how identities and assigned access is managed, enforced and reported upon across all functional business units" Also "On call 24x7 responsibilities" maybe a line. Then "The team Deloitte Technology works at the forefront..." that's about team. Then Qualifications list. We need to map to sections: Possibly "About the role" (description), "Responsibilities" (the bullet list), "Qualifications" (the list), maybe "Skills" (some of the qualifications could be skills). But we should not create thin sections. Better to have: About the role (description), Responsibilities (the bullet list), Qualifications (the list). Possibly also "On-call schedule" as part of responsibilities? There's a line "Willingness to participate in a rotating 24x7x365 on-call schedule." That's a qualification/requirement. Could be part of Qualifications. We should not create Pay/Benefits/Schedule sections because not specified. 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, not invent or summarize away detail. Remove boilerplate etc. We need to output only HTML fragment. Let's extract content: First paragraph: "In this interesting and diverse role, you'll be engaging in the development, implementation and support of systems that manage digital identities, access controls and authentication processes. This position collaborates with team members to: ensure secure and efficient access to Deloitte applications while upholding cyber security best practices define the future vision of how identities and assigned access is managed, enforced and reported upon across all functional business units" Note there is missing punctuation between best practices and define. We'll keep as is. Second: "On call 24x7 responsibilities" maybe heading? Actually it's a line: "On call 24x7 responsibilities". Might be a heading for responsibilities? Could treat as part of responsibilities. Then paragraph about team: "The team Deloitte Technology works at the forefront of technology development and processes to support and protect Deloitte around the world. In this truly global environment, we operate not in "what is" but rather "what can be" to help Deloitte deliver and connect with its clients, its communities, and one another in ways not previously conceived." Then Qualifications heading: "Qualifications Do you possess the following?:" Then list items: - Minimum 5 years' experience with leading CIAM vendors preferably Azure Entra Id and Ping Identity Platform. - Minimum 2 years' hands-on Java development experience (Java/J2EE); familiarity with Groovy and/or JavaScript. - Proven experience customizing PingAM UI, writing scripts, and developing code to retrieve/assert values from multiple data sources. - Experience building, testing (functional and robustness), and promoting custom Java components using the PingAM and PingIDM SDK to production (for example: modules, trees, STS, policies, connectors, scripts). - Hands-on experience installing and configuring Identity and Access Management (IAM/CIAM) products. - Working knowledge of authentication standards and frameworks: SAML, OAuth 2.0, and OpenID Connect (OIDC). - Willingness to participate in a rotating 24x7x365 on-call schedule. - Advanced knowledge of LDAP and directory services, application servers, and network infrastructure. - Experience integrating and deploying IAM solutions for web and mobile applications to support authentication and authorization, including SSO integrations with internal and third-party applications. - Experience with container technologies: Docker installation and configuration, and orchestration using Kubernetes. - Limited immigration sponsorship may be available. We need to decide sections: About the role (first paragraph + team paragraph?), Responsibilities (the bullet list after "This position collaborates with team members to:" maybe includes the two bullet points? Actually that list is two items: ensure secure... and define the future vision...). Could treat those as responsibilities. Qualifications: the list. We could also include a short paragraph about team as part of About the role. Thus sections:

    About the role

    In this interesting and diverse role, you'll be engaging in the development, implementation and support of systems that manage digital identities, access controls and authentication processes. This position collaborates with team members to: ensure secure and efficient access to Deloitte applications while upholding cyber security best practices define the future vision of how identities and assigned access is managed, enforced and reported upon across all functional business units

    The team Deloitte Technology works at the forefront of technology development and processes to support and protect Deloitte around the world. In this truly global environment, we operate not in "what is" but rather "what can be" to help Deloitte deliver and connect with its clients, its communities, and one another in ways not previously conceived.

    Responsibilities

    • ensure secure and efficient access to Deloitte applications while upholding cyber security best practices
    • define the future vision of how identities and assigned access is managed, enforced and reported upon across all functional business units

    Qualifications

    • Minimum 5 years' experience with leading CIAM vendors preferably Azure Entra Id and Ping Identity Platform.
    • Minimum 2 years' hands-on Java development experience (Java/J2EE); familiarity with Groovy and/or JavaScript.
    • Proven experience customizing PingAM UI, writing scripts, and developing code to retrieve/assert values from multiple data sources.
    • Experience building, testing (functional and robustness), and promoting custom Java components using the PingAM and PingIDM SDK to production (for example: modules, trees, STS, policies, connectors, scripts).
    • Hands-on experience installing and configuring Identity and Access Management (IAM/CIAM) products.
    • Working knowledge of authentication standards and frameworks: SAML, OAuth 2.0, and OpenID Connect (OIDC).
    • Willingness to participate in a rotating 24x7x365 on-call schedule.
    • Advanced knowledge of LDAP and directory services, application servers, and network infrastructure.
    • Experience integrating and deploying IAM solutions for web and mobile applications to support authentication and authorization, including SSO integrations with internal and third-party applications.
    • Experience with container technologies: Docker installation and configuration, and orchestration using Kubernetes.
    • Limited immigration sponsorship may be available.
    We should not include any extra headings like Benefits, Pay, Schedule. Check that we preserved all substantive info: yes. We removed boilerplate like "Deloitte Global is the engine of the Deloitte network..." Actually that is substantive? It's about Deloitte Global. Might be considered boilerplate but it's descriptive of the company. The instruction: remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. The first sentence about Deloitte Global is not boilerplate; it's about the organization. Might be okay to keep? It's not a section heading but could be part of About the role? Could include as a paragraph before About the role? But we already have About the role paragraph. Could we incorporate that sentence into About the role? It says "Deloitte Global is the engine of the Deloitte network. Our professionals reach across disciplines and borders to develop and lead global initiatives. We deliver strategic programs and services that unite our organization." That's more about the company, not the role. Could be considered boilerplate? It's not legal/EEO, but it's generic marketing. The instruction says remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. This is not those categories. It's okay to keep. But we need to decide where to put it. Could be a short paragraph before About the role, maybe as part of About the role? The instruction says use

    for section headings (e.g. About the role, Responsibilities...). So we could have a section "About the role" that includes both the role description and maybe the company overview. However the company overview is not about the role. Might be better to include as a separate section like "About Deloitte"? But we only allowed certain headings list; we could still use

    for any heading, but the instruction says use

    for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). It doesn't forbid other headings, but suggests those as examples. Safer to stick to those. The company overview could be placed in a

    before the first heading, as introductory text. That's allowed: we can have prose outside headings. The instruction: Output ONLY the HTML fragment — no /, no markdown code fences. So we can have leading

    then headings. Thus we can start with a paragraph: "Deloitte Global is the engine of the Deloitte network. Our professionals reach across disciplines and borders to develop and lead global initiatives. We deliver strategic programs and services that unite our organization." Then

    About the role

    with the role description paragraph. Then maybe we keep the team paragraph as part of About the role? Could be separate

    after the role description but still under About the role heading? Actually after heading we can have multiple

    elements. So we can put both paragraphs under About the role. Thus final HTML:

    Deloitte Global is the engine of the Deloitte network. Our professionals reach across disciplines and borders to develop and lead global initiatives. We deliver strategic programs and services that unite our organization.

    About the role

    In this interesting and diverse role, you'll be engaging in the development, implementation and support of systems that manage digital identities, access controls and authentication processes. This position collaborates with team members to: ensure secure and efficient access to Deloitte applications while upholding cyber security best practices define the future vision of how identities and assigned access is managed, enforced and reported upon across all functional business units

    The team Deloitte Technology works at the forefront of technology development and processes to support and protect Deloitte around the world. In this truly global environment, we operate not in "what is" but rather "what can be" to help Deloitte deliver and connect with its clients, its communities, and one another in ways not previously conceived.

    Responsibilities

    • ensure secure and efficient access to Deloitte applications while upholding cyber security best practices
    • define the future vision of how identities and assigned access is managed, enforced and reported upon across all functional business units

    Qualifications

    • Minimum 5 years' experience with leading CIAM vendors preferably Azure Entra Id and Ping Identity Platform.
    • Minimum 2 years' hands-on Java development experience (Java/J2EE); familiarity with Groovy and/or JavaScript.
    • Proven experience customizing PingAM UI, writing scripts, and developing code to retrieve/assert values from multiple data sources.
    • Experience building,

Similar jobs