Senior Cloud Software Engineer

We need to output HTML fragment with sections: headings

for section headings like About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We must include only sections that have real specific content. The posting includes: Mission Impact (maybe About the role?), What You’ll Do (Day‑to‑Day) (Responsibilities), You’ll Be a Great Fit If You… (maybe Requirements/Qualifications?), Responsibilities (Expanded) (more responsibilities), Minimum Qualifications, Preferred/Bonus Experience, Security Clearance (maybe as a note). No explicit Pay, Schedule, Benefits. So we should not create those sections. We need to use

for section headings. Use

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

  for prose. We must preserve all substantive information; do not invent or summarize away detail. Remove boilerplate etc. We need to decide headings: "About the role" could be the Mission Impact paragraph. "Responsibilities" could combine What You’ll Do (Day‑to‑Day) and Responsibilities (Expanded). Could be one Responsibilities section with combined bullet list. "Qualifications" could be Minimum Qualifications. "Skills" could be Preferred/Bonus Experience? Or maybe "Skills" for preferred experience. "Requirements" maybe same as Qualifications. But we need to follow instruction: use headings for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). We can choose which to include based on content. We have content for About the role (Mission Impact). Responsibilities (What You’ll Do + Expanded). Requirements/Qualifications (Minimum Qualifications). Skills (Preferred/Bonus Experience). Possibly also Security Clearance could be part of Requirements or a note; but we can include as a short

  under Requirements or Qualifications. We must not repeat job title as heading. No Job ID. We must not include Pay/Benefits/Schedule sections because not present. We must not include placeholder text. We need to output only HTML fragment. Let's extract content. Mission Impact paragraph: "Mission Impact At MTSI, you’ll build and enhance enterprise catalog and metadata services that power intelligence discovery across the Air Force and Intelligence Community. Your work will modernize how analysts access, curate, search, and share mission data, enabling rapid, secure, cloud‑native information flow across domains and security enclaves, directly strengthening decision advantage in contested environments." That's prose. What You’ll Do (Day‑to‑Day) list: - Architect and deliver scalable, cloud‑native microservices across AWS, Azure, or GCP. - Lead containerization, Kubernetes deployment strategies, multi‑cluster operations, and service‑mesh integrations. - Design enterprise CI/CD pipelines with automated testing, secure packaging, artifact governance, and multi‑enclave deployments. - Drive cloud security posture improvements (IAM, secrets management, network policies, compliance controls). - Partner with product teams, SREs, cybersecurity, and mission stakeholders to align cloud solutions with system‑of‑systems architecture. - Troubleshoot high‑complexity production issues across distributed systems, networking, and cloud infrastructure. - Produce high‑quality architecture diagrams, operational runbooks, technical approaches, and decision rationale for leadership. - Mentor junior and mid‑level engineers; elevate team cloud practices and engineering standards. You’ll Be a Great Fit If You… list: - Excel at owning cloud architectures end‑to‑end and enjoy guiding teams through complex technical challenges. - Have deep experience with Kubernetes, distributed systems, and secure, scalable cloud design patterns. - Thrive in mission‑focused environments where reliability, automation, and security are central to success. - Can balance hands‑on engineering with architectural vision, technical leadership, and mentoring. - Enjoy collaborating across multiple organizations and disciplines to deliver cloud solutions that actually get used in the field. Responsibilities (Expanded) list: - Lead design and development of cloud‑native services, including microservices architectures, API interfaces, and distributed data flows. - Manage full Kubernetes lifecycle—cluster architecture, networking, autoscaling, observability stacks, and cluster hardening. - Define and maintain CI/CD architecture that supports multiple enclaves, automated quality gates, SBOM generation, and mission‑ready release pipelines. - Implement infrastructure‑as‑code solutions (Terraform, Helm, Kustomize) that ensure consistent, auditable, repeatable deployments. - Integrate advanced telemetry, including distributed tracing, metrics pipelines, operational dashboards, and automated alerting. - Ensure compliance with cloud security frameworks, zero‑trust principles, and enclave‑specific access controls. - Lead technical planning, architecture reviews, risk analysis, and trade studies to shape long‑term cloud roadmaps. - Mentor engineers, guide code reviews, improve team processes, and evangelize best practices across cloud engineering and DevSecOps. Minimum Qualifications list: - Bachelor’s degree in Computer Science, Software Engineering, Information Systems, or equivalent experience. - 5+ years of professional cloud engineering experience, including hands‑on work with AWS, Azure, or GCP. - Strong proficiency with Kubernetes (deployments, networking, scaling, operators, observability). - Deep experience with containerization (Docker) and microservice design patterns. - Proficiency in a modern programming language (Python, C++ preferred). - Experience designing and maintaining CI/CD pipelines with automated testing and secure release workflows. - Solid understanding of distributed systems, cloud networking, and API design. - Ability to obtain and maintain any required security clearances. Preferred/Bonus Experience list: - Experience architecting mission‑critical or highly regulated cloud systems (DoD, IC, aerospace, critical infrastructure, etc.). - Expertise in Kubernetes multi‑cluster management, service mesh (Istio/Linkerd), or advanced cluster hardening. - Proficiency with IaC (Terraform, Helm, CloudFormation) and GitOps workflows. - Experience with event‑driven or streaming architectures (Kafka, Kinesis, Pub/Sub). - Strong background in cloud security design: IAM, boundary protection, key management, policy‑as‑code. - Experience leading technical teams, driving architecture decisions, or serving as a technical SME. - Cloud certifications: AWS Solutions Architect, Azure Architect, GCP Professional Cloud Engineer, CKA/CKAD/CKS. Security Clearance note: "United States citizenship is required with the ability to obtain a secret security clearance #MTSI #onsite". This is a requirement; we can include as a short

  under Requirements or Qualifications. We need to avoid duplication: Some items appear in both What You’ll Do and Responsibilities (Expanded). We should preserve all substantive information; but we can combine them to avoid duplication? The instruction: "Preserve ALL substantive information; do NOT invent or summarize away detail." If we combine, we might lose some nuance but not summarizing away detail; we could merge lists but keep all items. Duplication across sections is okay to keep but we could combine to avoid repeating same bullet twice. However there are overlapping items: Mentor appears in both; also design CI/CD etc. To preserve all detail, we could keep both sections separate but that would duplicate some bullets. The instruction says remove duplicated lines. So we should remove duplicated lines. So we need to deduplicate. Let's list all unique bullets from both responsibility sections. From What You’ll Do: 1. Architect and deliver scalable, cloud‑native microservices across AWS, Azure, or GCP. 2. Lead containerization, Kubernetes deployment strategies, multi‑cluster operations, and service‑mesh integrations. 3. Design enterprise CI/CD pipelines with automated testing, secure packaging, artifact governance, and multi‑enclave deployments. 4. Drive cloud security posture improvements (IAM, secrets management, network policies, compliance controls). 5. Partner with product teams, SREs, cybersecurity, and mission stakeholders to align cloud solutions with system‑of‑systems architecture. 6. Troubleshoot high‑complexity production issues across distributed systems, networking, and cloud infrastructure. 7. Produce high‑quality architecture diagrams, operational runbooks, technical approaches, and decision rationale for leadership. 8. Mentor junior and mid‑level engineers; elevate team cloud practices and engineering standards. From Responsibilities (Expanded): 1. Lead design and development of cloud‑native services, including microservices architectures, API interfaces, and distributed data flows. 2. Manage full Kubernetes lifecycle—cluster architecture, networking, autoscaling, observability stacks, and cluster hardening. 3. Define and maintain CI/CD architecture that supports multiple enclaves, automated quality gates, SBOM generation, and mission‑ready release pipelines. 4. Implement infrastructure‑as‑code solutions (Terraform, Helm, Kustomize) that ensure consistent, auditable, repeatable deployments. 5. Integrate advanced telemetry, including distributed tracing, metrics pipelines, operational dashboards, and automated alerting. 6. Ensure compliance with cloud security frameworks, zero‑trust principles, and enclave‑specific access controls. 7. Lead technical planning, architecture reviews, risk analysis, and trade studies to shape long‑term cloud roadmaps. 8. Mentor engineers, guide code reviews, improve team processes, and evangelize best practices across cloud engineering and DevSecOps. Now deduplicate: Mentor appears in both but slightly different wording. We can keep one combined bullet that captures both: "Mentor junior and mid‑level engineers; elevate team cloud practices and engineering standards; guide code reviews, improve team processes, and evangelize best practices across cloud engineering and DevSecOps." That's merging details, not losing info. That's acceptable. Other duplicates: CI/CD pipelines design appears in both but with different specifics: first: "Design enterprise CI/CD pipelines with automated testing, secure packaging, artifact governance, and multi‑enclave deployments." second: "Define and maintain CI/CD architecture that supports multiple enclaves, automated quality gates, SBOM generation, and mission‑ready release pipelines." They are similar but not identical; we can keep both as they add nuance. Could combine but better to keep both to preserve detail. However they are somewhat overlapping; but we can keep both as they are not exact duplicates. Cloud security posture improvements vs Ensure compliance with cloud security frameworks etc. Both are similar but distinct; keep both. Now we need to format responsibilities as

  • . Now About the role: we have mission impact paragraph. Now Requirements/Qualifications: Minimum Qualifications list plus maybe Security Clearance note. We could have a section "Requirements" with the Minimum Qualifications list plus security clearance note as a paragraph. Or we could have "Qualifications" for Minimum Qualifications and "Skills" for Preferred/Bonus Experience. Let's decide: -

    About the role

    Mission Impact...

    -

    Responsibilities

    ...
    -

    Qualifications

    Minimum Qualifications list
    plus maybe a

    for security clearance. -

    Skills

    Preferred/Bonus Experience list
    We should not include Requirements heading if we already have Qualifications; but we could include both if we split. However instruction: "Prefer a few substantive sections over many thin ones." So maybe combine Qualifications and Skills into one section? But they ask to use headings like Qualifications, Skills etc. We can include both if they have content. We have content for Qualifications (Minimum Qualifications) and Skills (Preferred/Bonus Experience). So we can include both. We must not include Benefits, Pay, Schedule. Now ensure we don't include any boilerplate like "#MTSI #onsite" maybe we can keep as part of security clearance note but it's a hashtag; we can keep as text. Now produce HTML. Let's craft. First, About the role:

    Mission Impact At MTSI, you’ll build and enhance enterprise catalog and metadata services that power intelligence discovery across the Air Force and Intelligence Community. Your work will modernize how analysts access, curate, search, and share mission data, enabling rapid, secure, cloud‑native information flow across domains and security enclaves, directly strengthening decision advantage in contested environments.