ICAM Security Engineer

We need to output HTML fragment with sections: headings

for sections like About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. Only include sections that have real specific content. We must not repeat job title as heading. No Job ID etc. Remove boilerplate, navigation, legal, EEO, scam warning, duplicated lines, application instructions. Preserve all substantive info. We need to parse the description. Key content: - Description: Leidos seeking ICAM/Identity Engineer, Air Traffic Business Area, Homeland Sector, supporting L-CAP development. L-CAP is mission-critical future-ready automation platform built on hybrid cloud data mesh architecture, enabling next-gen air traffic management. Building with AI-first engineering mindset, SAFe/Agile framework, part of ART delivering iterative value. Requires ability to obtain and maintain favorable Public Trust investigation. Hybrid position requiring 3 days onsite and 2 days WFH if within commutable distance ( for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." So we can include those headings as appropriate. We should not include headings with filler. So we will include:

About the role

with paragraph summarizing role, L-CAP, hybrid work, etc.

Responsibilities

with

• items for each responsibility.

  Requirements

  with
  • items for core technical qualifications.

    Qualifications

    with
    • items for preferred/desired qualifications.

      Skills

      maybe we could omit if we think it's thin; but we could include skills like programming languages, etc. However those are already in Requirements. Might be redundant. Better to omit Skills section to avoid thin.

      Benefits

      with
      • items: competitive compensation, Health and Wellness programs, Income Protection, Paid Leave, Retirement.

        Pay

        with

        containing the pay range and note.

        Schedule

        with

        describing hybrid/remote. We must not repeat job title as heading. No Job ID etc. We must preserve all substantive information; do not invent or summarize away detail. So we need to keep details like specific locations (Gaithersburg, MD; Eagan, MN; Egg Harbor Township, NJ). Also mention that if not within commutable distance, may be considered for 100% remote role. Also mention that role requires ability to obtain and maintain favorable Public Trust investigation. Also mention U.S. citizenship required, etc. Also mention Must meet FAA facility and information system access requirements, including continuous U.S. residency for at least 3 of the previous 5 years. Also mention that the role operates within SAFe/Agile framework as part of an Agile Release Train delivering iterative value. Also mention that L-CAP is mission-critical, future-ready automation platform built on a hybrid cloud data mesh architecture, enabling next-gen air traffic management capabilities. Building with AI-first engineering mindset. Also mention that this position supports government programs. Also mention that the role implements identity, credential, and access management (ICAM) layer that governs every user and service interaction with L-CAP. Also mention that you will integrate platform with government-provided ICAM services, enforce per-session authorization across distributed mission services, and build access control and audit foundations. Also mention that you will support security authorization and continuous monitoring by producing ICAM control evidence, resolving identity integration issues across distributed services, and leveraging AI-assisted development and automation to improve quality and delivery. Also mention that the posting date: Original Posting September 21, 2026. But we should not include posting date? It's metadata but maybe not needed. The instruction: do NOT put Job ID / requisition numbers as headings — fold minor metadata into a short

        or drop it. Posting date could be considered minor metadata; we could drop it or include in a short p under About the role. Probably drop it to keep concise. Also mention Pay Range note: "The Leidos pay range for this job level is a general guideline only and not a guarantee of compensation or salary. Additional factors considered..." We should keep that note. Also mention "Pay And Benefits" section: we already have Benefits and Pay. Also mention "Securing Your Data" and "Commitment to Non-Discrimination" are boilerplate; remove. Also mention "Why Leidos?" paragraph: could be included under About the role or maybe separate but we can incorporate. We need to ensure we preserve all substantive information. Let's list all substantive points: From description: - Leidos seeking ICAM/Identity Engineer to join Air Traffic Business Area within Homeland Sector, supporting development of Leidos Common Automation Platform (L-CAP). - L-CAP is mission-critical, future-ready automation platform built on a hybrid cloud data mesh architecture, enabling next-gen air traffic management capabilities. - Building with AI-first engineering mindset, embracing emerging AI capabilities and modern development practices to accelerate delivery, improve software quality, continuously evolve how we design and build mission-critical systems. - Role operates within SAFe/Agile framework as part of an Agile Release Train (ART) delivering iterative value across the program. - Position supports government programs and requires ability to obtain and maintain a favorable Public Trust investigation. - Hybrid position requiring 3 days onsite and 2 days working from home, if located within commutable distance (<1 hour drive one-way) from Gaithersburg, MD; Eagan, MN; or Egg Harbor Township, NJ. If not within commutable distance, may be considered for 100% remote role. - In this role, you will implement the identity, credential, and access management (ICAM) layer that governs every user and service interaction with L-CAP. - You will integrate the platform with government-provided ICAM services, enforce per-session authorization across distributed mission services, and build the access control and audit foundations that operational and support users depend on. - What You’ll Do: * Integrate L-CAP services with government-provided ICAM services using OAuth 2.0 and OpenID Connect, including token issuance, validation, and claims mapping. * Implement and maintain identity federation and user stores (Keycloak or equivalent), including role-based test account provisioning. * Implement per-session authentication and authorization for user-to-service and service-to-service requests, enforcing default-deny access regardless of network location. * Implement mutual TLS (mTLS), service mesh/workload identity, and certificate lifecycle management, including issuance, rotation, expiration monitoring, and revocation. * Design and implement role-based (RBAC) and attribute-based (ABAC) access controls aligned to operational and support roles.