Kubernetes Architect

for section headings. We must use

• for any list of duties/requirements/benefits. For prose use

  . We must preserve ALL substantive information; do not invent or summarize away detail. We need to ensure we keep all details from the description, responsibilities, qualifications, etc. Let's extract each piece. About the role: Paragraph: "Leidos is pursuing the A1 Multi-Cloud Ecosystem (A1 MCE) Managed Services Support contract and currently has an opening for a Kubernetes Architect to provide technical leadership and architectural oversight for large-scale Kubernetes production environments. This is an exciting opportunity to apply deep Kubernetes and cloud-native expertise to help modernize a global-scale, multi-cloud environment supporting a critical U.S. Air Force mission. The Kubernetes Architect will play a key role in ensuring platform resiliency, security, scalability, reliability, and cost effectiveness while providing technical direction across engineering teams." Location: "This position will be hybrid remote. The candidate may be required to work onsite as needed. Preference will be given to candidates located near Lackland AFB in San Antonio, TX." We can combine into About the role section: include both paragraphs. Responsibilities: list bullet points from "Primary Responsibilities". Let's extract each sentence: - Architect, build, and support large-scale Kubernetes production environments. - Provide architectural oversight for Kubernetes infrastructure, including control plane components, worker nodes, networking, storage, security, scalability, and availability. - Support the availability, capacity, performance, and reliability of on-premises Kubernetes infrastructure and systems. - Serve as a Kubernetes Subject Matter Expert (SME), providing architectural guidance, technical leadership, and best practices to engineering and operations teams. - Identify technical and resource requirements, including hardware, software, tools, and supplemental staffing needs. - Collaborate with cybersecurity, infrastructure, networking, cloud, and development teams to ensure secure, compliant, and reliable platform operations. - Support DevSecOps practices, automation, CI/CD integration, and container security across the environment. - Identify opportunities to improve platform performance, resiliency, operational efficiency, and cost effectiveness. - Provide technical guidance for troubleshooting and resolution of complex Kubernetes and platform issues. We need to keep each as

• . Requirements (Minimum Qualifications): - Bachelor’s degree with 12+ years of relevant experience, or Master’s degree with 10+ years of relevant experience. Additional experience may be considered in lieu of a degree, as permitted by the contract. - Active Secret clearance required to start and ability to maintain the required clearance throughout employment. - U.S. citizenship required. - Extensive hands-on experience designing, implementing, and supporting Kubernetes environments. - Strong knowledge of Kubernetes architecture, including control plane components, worker node design, scheduling, networking, storage, and security. - Strong understanding of DevSecOps methodologies, CI/CD pipelines, automation frameworks, and container security best practices. - Demonstrated experience troubleshooting complex platform issues and optimizing performance, availability, and reliability. - Ability to provide technical leadership and architectural guidance across multidisciplinary engineering teams. - CompTIA Security+ or equivalent IAT Level II certification. We need to keep each as
• . Qualifications (Preferred Qualifications): - Experience supporting U.S. Air Force Cloud One and/or Platform One environments. - Experience designing or supporting multi-cloud and hybrid-cloud environments. - Experience with Zero Trust Architecture and cloud-native security principles. - Experience with Kubernetes automation, observability, monitoring, and platform reliability engineering. - Cloud certification in AWS, Microsoft Azure, Google Cloud, or Oracle Cloud Infrastructure. - Kubernetes-related certification, such as Certified Kubernetes Administrator (CKA) or Certified Kubernetes Security Specialist (CKS). Each as
• . Benefits: From "Pay And Benefits": "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 can make a

  with that sentence. Pay: From "Pay Range Pay Range $154,050.00 - $278,475.00". Also note the 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 in extending an offer include (but are not limited to) responsibilities of the job, education, experience, knowledge, skills, and abilities, as well as internal equity, alignment with market data, applicable bargaining agreement (if any), or other law." We should preserve all substantive info. So include the range and the disclaimer as prose. Schedule: From location: hybrid remote, may be required to work onsite as needed. Also maybe mention preference for near Lackland AFB. That's location but schedule wise: hybrid remote, possible onsite. We'll put schedule: "This position is hybrid remote; the candidate may be required to work onsite as needed. Preference is given to candidates located near Lackland AFB in San Antonio, TX." We need to ensure we don't duplicate location info already in About the role. But we could keep location in About the role and schedule separate? Might duplicate. However the instruction: preserve ALL substantive information; do not invent or summarize away detail. If we put location in About the role, we still need to convey schedule info. Could we incorporate schedule info into About the role? The About the role section could include location and schedule. Then we might not need a separate Schedule section. But we need to decide if we have enough content for Schedule section separate. The posting does mention hybrid remote and onsite as needed; that's schedule. If we already included location in About the role, we could still have Schedule section with that info, but that would duplicate. Duplication is not prohibited but might be considered redundant. The instruction: preserve ALL substantive information; do NOT invent or summarize away detail. Duplication is not forbidden but could be considered unnecessary. However they said "Prefer a few substantive sections over many thin ones." So better to avoid duplication. So we could include location and schedule in About the role, and not have a separate Schedule section. But then we would omit Schedule section entirely, which is okay if we don't have separate schedule content beyond what's already in About the role. However the instruction: "include a section ONLY when the posting has real, specific content for it — never emit a heading followed by filler/placeholder text". If we don't have separate schedule content beyond what's already covered, we could omit Schedule section. But we need to decide if we consider schedule as distinct content. The posting does mention hybrid remote and onsite as needed; that is schedule info. If we put it in About the role, we still have covered it. So we can omit Schedule section. Thus sections: About the role, Responsibilities, Requirements, Qualifications, Benefits, Pay. Check if we need Skills section: we could incorporate skill details into Requirements/Qualifications; no separate Skills needed. Now we must ensure we don't include boilerplate: remove "Original Posting September 16, 2026", "For U.S. Positions: While subject to change...", "About Leidos" paragraph, "Pay And Benefits" we already used benefits paragraph but we need to ensure we don't include the "About Leidos" paragraph. Also remove "Securing Your Data", "Commitment to Non-Discrimination", "#Remote". Also remove the fluff paragraph starting with "If you're looking for comfort, keep scrolling." etc. Now produce HTML fragment. Structure:

  About the role

  Leidos is pursuing the A1 Multi-Cloud Ecosystem (A1 MCE) Managed Services Support contract and currently has an opening for a Kubernetes Architect to provide technical leadership and architectural oversight for large-scale Kubernetes production environments. This is an exciting opportunity to apply deep Kubernetes and cloud-native expertise to help modernize a global-scale, multi-cloud environment supporting a critical U.S. Air Force mission. The Kubernetes Architect will play a key role in ensuring platform resiliency, security, scalability, reliability, and cost effectiveness while providing technical direction across engineering teams. This position will be hybrid remote.