Security Authorization Lead

We need to output only HTML fragment, using

for section headings: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. Include sections only when posting has 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. We need to preserve all substantive information. Let's parse the posting. Key sections: - Description: includes overview, role details, hybrid position, location, remote possibility, etc. This could be "About the role" or maybe "Responsibilities". We'll need to decide. - "What You’ll Do": list of duties. - "Core Technical Qualifications": list of qualifications. - "Preferred / Desired Qualifications": list. - "Why Leidos?": narrative about mission, maybe "About Leidos" or "Why Leidos?" but we have sections: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We need to map content. Probably: - About the role: overview of role, mission, hybrid, location, etc. - Responsibilities: the "What You’ll Do" bullet list. - Requirements: maybe core technical qualifications (must-have). - Qualifications: maybe preferred/desired qualifications. - Skills: maybe combine? But we have separate sections for Skills; we could put technical skills there. - Benefits: from "Pay And Benefits" section: mention competitive compensation, Health and Wellness programs, Income Protection, Paid Leave and Retirement. Also maybe mention "Why Leidos?" but that's more culture. - Pay: from "Pay Range" section: $107,900.00 - $195,050.00. - Schedule: hybrid position requiring 3 days onsite and 2 days WFH, if within commutable distance; else 100% remote. We need to ensure we don't create sections with filler like "commensurate with experience". We have actual content. We must not include boilerplate like "Securing Your Data", "Commitment to Non-Discrimination", "About Leidos" (maybe we can include as "About the role"? Actually "About Leidos" is company overview, not role. Could be omitted as not required? The instruction: "Prefer a few substantive sections over many thin ones." We could include About Leidos as part of About the role? But we have a specific heading "About the role". The company overview may be considered not role-specific; but we could still include it under About the role? Might be okay. However we must not invent sections; we can include About the role with role overview, not company overview. The "About Leidos" paragraph is generic; could be omitted as not required? The instruction: "Preserve ALL substantive information; do NOT invent or summarize away detail." So we must keep all substantive info. The "About Leidos" paragraph is substantive about company; but we don't have a heading for company overview. Could we put it under "About the role"? That would be mixing. Better to create a section "About Leidos" but not in allowed headings list. The allowed headings are only those eight. So we must fit content into those headings. Perhaps we can put company overview under "About the role" as part of role context. That may be acceptable. Similarly, "Why Leidos?" and "ATMC" etc are motivational; could be part of About the role or maybe omitted? But we must preserve all substantive information. That includes motivational statements. We could incorporate them into About the role or maybe under Responsibilities? Probably About the role. "Step 10 is ancient history..." etc is fluff; could be omitted? It's part of Why Leidos? Might be considered boilerplate? It's still part of posting. Might be considered fluff but still substantive? The instruction says remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. This motivational text is not those categories; it's part of the posting's culture. We should keep it. Thus we need to embed that text somewhere. Let's plan sections:

About the role

Leidos is seeking a Security Authorization Lead to join the Air Traffic Business Area within the Homeland Sector, supporting the development of the Leidos Common Automation Platform (L-CAP). L-CAP is a mission-critical, future-ready automation platform built on a hybrid cloud data mesh architecture, enabling next-generation air traffic management capabilities. We are building with an AI-first engineering mindset, embracing emerging AI capabilities and modern development practices to accelerate delivery, improve software quality, and continuously evolve how we design and build mission-critical systems. This role operates within a SAFe/Agile framework as part of an Agile Release Train (ART) delivering iterative value across the program. This position supports government programs and requires the ability to obtain and maintain a favorable Public Trust investigation. This is a hybrid position requiring 3 days onsite and 2 days working from home, if you are located within a commutable distance (Less than 1 hour's drive one-way during normal traffic) from Gaithersburg, MD; Eagan, MN; or Egg Harbor Township, NJ. However, if you do not reside within a commutable distance, you may be considered for a 100% remote role.

Maybe also include "Why Leidos?" and motivational text inside same paragraph or separate

. We could add another

after that: "You’ll work on systems where performance, precision, and reliability matter — every second. This is not experimental AI for prototypes. This is disciplined, responsible AI applied to mission-critical software that supports national infrastructure. If you’re excited by solving complex problems in regulated, real-world environments — and using AI as a force multiplier rather than a shortcut — we’d like to talk. ATMC If you're looking for comfort, keep scrolling. At Leidos, we outthink, outbuild, and outpace the status quo — because the mission demands it. We're not hiring followers. We're recruiting the ones who disrupt, provoke, and refuse to fail. Step 10 is ancient history. We're already at step 30 — and moving faster than anyone else dares." But note "ATMC" maybe a typo; keep as is. Now Responsibilities: list from "What You’ll Do". Use

• . Responsibilities: - Lead the government network connection and RMF/ATO authorization process for L-CAP workloads on government-provided cloud infrastructure, including security assessments, architecture reviews, control evidence, and assessor coordination. - Own and maintain the security authorization package, including architecture briefings, data flow/security boundary diagrams, ports/protocols/services matrices, SBOMs, vulnerability/CVE dispositions, and POA&Ms. - Define and defend security control inheritance across cloud provider, government platform, and Leidos application layers, maintaining the Customer Responsibility Matrix. - Serve as the primary interface with government security reviewers, ISSOs, assessors, and Authorizing Official staff. - Manage the POA&M and continuous monitoring lifecycle, including findings, risk characterization, remediation milestones, closure evidence, and security status reporting. - Maintain the authorization boundary as architecture evolves, assess security impacts of proposed changes, and translate requirements into actionable engineering backlog items. - Coordinate cross-ART compliance across four Agile Release Trains to ensure consistent control implementation and evidence quality. - Support FedRAMP and agency-specific authorization requirements across cloud environments. - Coordinate personnel security and facility access eligibility with program security and Talent Acquisition. - Champion an AI-first engineering culture through AI-assisted development, automation, and emerging practices that improve productivity, code quality, testing, and delivery. Now Requirements: maybe "Core Technical Qualifications". Use
  • . Core Technical Qualifications: - Bachelor’s degree in Cybersecurity, Computer Science, IT, or related field with 6+ years of relevant cybersecurity, compliance, or security authorization experience, or a Master’s degree with 4+ years.(additional experience, education and training may be considered in lieu of degree) - Demonstrated experience leading a federal information system through RMF to ATO or equivalent authorization, including NIST 800-53 Rev. 5 control implementation and assessment. - Experience developing and defending authorization packages, including SSPs, POA&Ms, Security Assessment Reports, and authorization boundary diagrams. - Experience with FedRAMP cloud control inheritance, Customer Responsibility Matrices, vulnerability management, CVE disposition, and remediation tracking. - Experience working directly with government security reviewers, ISSOs, and/or Authorizing Official staff. - Ability to translate security requirements into actionable engineering backlog items and coordinate compliance across multiple Agile engineering teams. - Strong technical writing skills with experience producing government-facing security documentation. - Ability to obtain and maintain a Public Trust and successfully complete required government background investigations. - U.S. citizenship required, including eligibility for FAA facility and information system access (continuous U.S. residency for at least 3 of the previous 5 years). Now Qualifications: maybe "Preferred / Desired Qualifications". Use
    • . Preferred / Desired Qualifications: - CISSP, CGRC (formerly CAP), CISM, or equivalent certification (strongly preferred) - FAA or aviation-sector security authorization experience, including familiarity with FAA ATO processes and security governance organizations - Experience with continuous ATO (cATO) or ongoing authorization models - Experience defining authorization boundaries for Kubernetes and containerized workloads - Familiarity with FedRAMP High and GovCloud inheritance models - Security authorization experience for safety-critical or real-time operational systems - Experience with compliance automation and evidence tooling, including OSCAL, eMASS, Xacta, or equivalent - Knowledge of software supply chain security, including SBOM, artifact signing, and provenance - Experience with SAFe or large-scale Agile compliance integration Now Skills: maybe we could combine some technical skills not covered; but we already covered many. Could leave Skills empty? But we must not create a section with filler. If we have no specific skills beyond those already listed, we could omit Skills section. However we might want to include "AI-first engineering mindset", "SAFe/Agile", "technical writing". Those are already in qualifications. Could still create Skills section with items like: AI-assisted development, automation, emerging practices, SAFe/Agile, technical writing, stakeholder communication. But those are already covered. To avoid duplication, maybe we omit Skills. Benefits: from "Pay And Benefits" section: "Employment benefits include competitive compensation, Health and Wellness programs, Income Protection, Paid Leave and Retirement. More details are available at www.leidos.com/careers/pay-benefits." We should keep that. Pay: from "Pay Range": "$107,900.00 - $195,050.00". Also note disclaimer: "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 as part of Pay section. Schedule: hybrid position details: "This is a hybrid position requiring 3 days onsite and 2 days working from home, if you are located within a commutable distance (Less than 1 hour's drive one-way during normal traffic) from Gaithersburg, MD; Eagan, MN; or Egg Harbor Township, NJ. However, if you do not reside within a commutable distance, you may be considered for a 100% remote role." We already included schedule in About the role; but we need a Schedule section per allowed headings. We should not duplicate content? The instruction: "Preserve ALL substantive information". If we put schedule in About the role, we still need to include it somewhere; we could keep it in About the role and also have Schedule section referencing same? That would duplicate. Better to move schedule details to Schedule section and keep About the role without schedule details. Let's adjust. Thus About the role: overview of role, mission, AI-first, SaFe/Agile, location hybrid mention? Actually we can