Cloud Operations Engineer

We need to output HTML fragment with sections: headings

for sections like About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. Use

• for any list of duties/requirements/benefits, and

  for prose. Do NOT repeat job title as heading. Do NOT put Job ID/requisition numbers as headings — fold minor metadata into short

  or drop it. Preserve ALL substantive information; do NOT invent or summarize away detail. Remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. IMPORTANT: include a section ONLY when the posting has real, specific content for it — never emit a heading followed by filler/placeholder text (e.g. "commensurate with experience", "not specified", "N/A", "varies", "TBD") and never create Pay/Schedule/Benefits sections unless the posting actually states them. Prefer a few substantive sections over many thin ones. We need to extract substantive content: The job description includes an introductory paragraph about passion, mission, etc. Then "As a Cloud Platform Engineer, you will:" followed by bullet-like list (but not bullet points). Then "Qualifications - External" with details: "This position has been posted at multiple levels..." then "Requisition Qualifications: Typically requires a bachelor’s degree..." then list of qualifications. Then "Requisition Preferences: ..." then "Why Join Our Team?" with bullet list: "Excellent personal and professional career growth", "9/80 work schedule (every other Friday off), when applicable", "Onsite cafeteria (breakfast & lunch)", "Much, much more!" Also "For more information on our partnership with NASA at Johnson Space Center (JSC), please visit www.wehavespaceforyou.com". Then "Proof of U.S. Citizenship or US Permanent Residency may be a requirement for this position Must be able to complete a U.S. government background investigation. Management has the prerogative to select at any level for which the position is advertised". Then "Compensation Details: ITS The compensation range or hourly rate listed for this position is provided as a good-faith estimate...". Then "Benefits Overview: Our health and welfare benefits are designed to support you and your priorities. Offerings include: Health, dental, and vision insurance Paid time off and holidays Retirement benefits (including 401(k) matching) Educational reimbursement Parental leave Employee stock purchase plan Tax-saving options Disability and life insurance Pet insurance Note: Benefits may vary based on employment type, location, and applicable agreements." Then "Original Posting: 09/26/2026 - Until Filled Amentum anticipates this job requisition will remain open for at least three days, with a closing date no earlier than three days after the original posting. This timeline may change based on business needs. Amentum is proud to be an Equal Opportunity Employer..." (EEO boilerplate to remove). Also "Learn more about your rights under Federal laws and supplemental language at Labor Laws Posters." (remove). We need to remove EEO/legal boilerplate, duplicated lines, application instructions (like "Click on the below links to view just a small sample of all that we do! Come join our team and be part of our future. We look forward to seeing you!" maybe considered application instructions? It's more promotional but not instructions to apply. Might keep? The instruction says remove application instructions. The phrase "Click on the below links to view just a small sample of all that we do! Come join our team and be part of our future. We look forward to seeing you!" is not an instruction to apply but promotional. Might keep? Safer to remove as it's fluff. Also "Why Join Our Team?" heading is present; we can keep that as a section maybe Benefits? Actually "Why Join Our Team?" includes bullet list of benefits: career growth, schedule, cafeteria. So we could treat that as Benefits section. But we also have a separate Benefits Overview later with health etc. So we could combine? The instruction: prefer few substantive sections over many thin ones. So we could have sections: About the role (intro), Responsibilities (list of duties), Qualifications (education/experience + technical skills), Benefits (work schedule, cafeteria, health benefits etc). Pay: there is compensation details but it's vague: "The compensation range or hourly rate listed for this position is provided as a good-faith estimate..." No actual numbers. That's placeholder-ish; we should not create Pay section unless posting actually states them. It does not give a range, just says it's provided as estimate. That's not specific; we should omit Pay section. Schedule: we have 9/80 work schedule mentioned under Why Join Our Team; that's schedule info. Could be part of Benefits or Schedule section. Since we have schedule info, we could create a Schedule section with that detail. But we also have other benefits. The instruction: prefer few substantive sections over many thin ones. So maybe combine schedule into Benefits. But we also have separate Benefits Overview with health etc. So we could have Benefits section that includes both health benefits and schedule/cafeteria. That seems reasonable. Thus sections: About the role (intro paragraph), Responsibilities (list of duties), Qualifications (education/experience + technical skills + preferences), Benefits (work schedule, cafeteria, health benefits etc). Possibly also a section for "NASA Missions" but that's part of responsibilities. We must not repeat job title as heading. Use

  for section headings. We need to use

  • for any list of duties/requirements/benefits, and

    for prose. We need to preserve ALL substantive information; do not invent or summarize away detail. We need to remove duplicated lines: there is duplicate "Developing best practices for cloud-native application development and promoting them within the organization" appears twice; we should keep only one instance. Also duplicate "Working with Managed Kubernetes offering across all three major cloud providers" appears once; fine. We need to preserve all substantive info: include the NASA missions (Orion, Lunar Gateway, Artemis). Include "Administering NASA cloud networks and managing requests for deployment of COTS and Cloud Native applications into cloud environments". Include "Writing quality code, providing quality and engaged code reviews for peers". Include "Integrating cloud managed AI and data services with other bespoke and open-source Kubernetes applications". Include "Identifying opportunities to abstract Prospective Project requirements and develop Enterprise-grade, multi-tenant Platform Services". Include "Collaborate with NASA security and compliance teams to ensure teams are adhering to industry best practices and regulatory requirements". Include "Working directly with NASA human spaceflight missions like Orion, Lunar Gateway, Artemis". Include "Perform other duties as required". Also include the introductory paragraph about passion etc. Qualifications: "Typically requires a bachelor’s degree or equivalent certification in a related area and normally possess 15 years of experience in the field or in a related area." Then list: Strong experience with Kubernetes in production; Ability to manage and use GitLab (preferably very proficient); Hands-on experience with CI/CD pipeline tools; Observability Monitoring tools such as Grafana and SuperSet; Proficiency with Infrastructure-as-Code utilizing Terraform for infrastructure automation and/or open source alternatives (OpenTofu); Extensive Linux experience (familiarity with Windows also preferred, but not required); Expert in at least one programming language (Go and Python is preferred); Experience with Python, SQL (and R is preferable); Working understanding of Machine Learning Model Lifecycle management (is preferred). Then Requisition Preferences: Solution-oriented mindset, accepts feedback with enthusiasm; Effectively communicates with team members: clear status updates to direct report, regularly establishes unanimous decisions with peers; Self-motivated and self-managing, with strong organizational skills; Experience architecting and building cloud-native applications; Demonstrable success and confidence in owning the full project lifecycle; Good instincts for identifying opportunities for abstraction; Balances individual project development tasks at hand with overall platform and company goals. We need to keep all that. Benefits: from "Why Join Our Team?" we have: Excellent personal and professional career growth; 9/80 work schedule (every other Friday off), when applicable; Onsite cafeteria (breakfast & lunch); Much, much more! (that's vague; maybe we can keep "Much, much more!" as placeholder? It's not specific; maybe we should omit as filler. The instruction: never emit a heading followed by filler/placeholder text. But within a list, "Much, much more!" is vague; maybe we should omit that line. We'll keep the specific ones. Then Benefits Overview: Health, dental, and vision insurance; Paid time off and holidays; Retirement benefits (including 401(k) matching); Educational reimbursement; Parental leave; Employee stock purchase plan; Tax-saving options; Disability and life insurance; Pet insurance. Also note: Benefits may vary based on employment type, location, and applicable agreements. That's a note; we can include as prose. We also have "For more information on our partnership with NASA at Johnson Space Center (JSC), please visit www.wehavespaceforyou.com". That's a link; we can keep as

    with a link. We also have "Proof of U.S. Citizenship or US Permanent Residency may be a requirement for this position Must be able to complete a U.S. government background investigation." That's a requirement; we could include under Qualifications maybe as a separate bullet? It's a requirement. We'll include as a bullet under Qualifications or maybe a separate section "Requirements"? But we already have Qualifications; we can add bullet. Also "Management has the prerogative to select at any level for which the position is advertised" - that's more about level; we could include as note. We need to remove EEO boilerplate and legal stuff. Now structure:

    About the role

    Intro paragraph(s) about passion, mission, etc.

    Responsibilities

    • Developing new cloud-native platform services spanning all three major cloud environments
    • Developing best practices for cloud-native application development and promoting them within the organization
    • Administering NASA cloud networks and managing requests for deployment of COTS and Cloud Native applications into cloud environments
    • Writing quality code, providing quality and engaged code reviews for peers
    • Working with Managed Kubernetes offering across all three major cloud providers
    • Integrating cloud managed AI and data services with other bespoke and open-source Kubernetes applications
    • Identifying opportunities to abstract Prospective Project requirements and develop Enterprise-grade, multi-tenant Platform Services
    • Collaborate with NASA security and compliance teams to ensure teams are adhering to industry best practices and regulatory requirements
    • Working directly with NASA human spaceflight missions like Orion, Lunar Gateway, Artemis
    • Perform other duties as required

    Qualifications

    Typically requires a bachelor’s degree or equivalent certification in a related area and normally possess 15 years of experience in the field or in a related area.

    • Strong experience with Kubernetes in production
    • Ability to manage and use GitLab (preferably very proficient)
    • Hands-on experience with CI/CD pipeline tools
    • Observability Monitoring tools such as Grafana and SuperSet
    • Proficiency with Infrastructure-as-Code utilizing Terraform for infrastructure automation and/or open source alternatives (OpenTofu)
    • Extensive Linux experience (familiarity with Windows also preferred, but not required)
    • Expert in at least one programming language (Go and Python is preferred)
    • Experience with Python, SQL (and R is preferable)
    • Working understanding of Machine Learning Model Lifecycle management (is preferred)
    • Solution-oriented mindset, accepts feedback with enthusiasm
    • Effectively communicates with team members: