Principal Software Engineer-Infrastructure

We need to output HTML fragment with sections: headings

for sections present: About the role? The description includes "Job Description" then paragraphs. We need sections: maybe "About the role", "Responsibilities", "Qualifications", "About Us", "About The Team"? The instruction: use

for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). Use

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

  for prose. Do NOT repeat the job title as a heading (the page already shows it) and do NOT put Job ID / requisition numbers as headings — fold minor metadata into a 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 decide which sections to include based on content. The posting includes: - Job Description (intro paragraph) - Our Approach (paragraph) - Engineers on this team... (maybe part of description) - Responsibilities (with subheadings: Key Responsibilities, then bullet points under categories: Infrastructure Engineering, Automation & Infrastructure as Code, Platform Integration, Observability & Reliability, Security & Access Management) - Qualifications (with bullet list) - About Us (paragraph) - About The Team (EEO statement) - this is boilerplate EEO, should be removed. We should not include EEO boilerplate. So we can drop "About The Team" section. We need to include sections: maybe "About the role" (intro + Our Approach?), "Responsibilities", "Qualifications", "About Us". Possibly also "Skills"? The qualifications include skills; but we can keep Qualifications section with list. We need to use

  for each section heading. We need to use

  • for any list of duties/requirements/benefits. So for Responsibilities we have bullet points under categories; we could flatten into a single list or keep subheadings? The instruction: Use
    • for any list of duties/requirements/benefits. It doesn't forbid having headings inside list? Probably better to have a list for responsibilities. Could also have subheadings as

      ? Not allowed? Only

      for section headings. Could still have

      but not specified; safer to avoid extra headings. Could present responsibilities as a list with items describing each area. But we need to preserve all substantive information; we can keep the categories as part of list items text. Similarly Qualifications: we have bullet list; we can output as

      • . We need to preserve all substantive information: include details like "Ten or more years of experience..." etc. We need to remove duplicated lines: there may be duplicate sentences. Let's extract content. First, intro paragraph: "We are building a modern, software‑defined infrastructure platform designed to support the next generation of applications across the organization. This platform is designed around open-source technologies, commodity hardware, and automation-first principles. It provides the core compute, storage, networking, and container runtime capabilities required to run distributed systems at scale across both data centers and cloud environments. This is a greenfield engineering effort focused on defining how infrastructure is built and operated using code, APIs, and declarative systems, with reliability, observability, and repeatability designed in from the start." Then "Our Approach" paragraph: "Emphasizes Linux-first systems design Kubernetes as a core abstraction layer Infrastructure-as-code and GitOps workflows Open observability standards (Prometheus, OpenTelemetry) Distributed, software-defined storage and networking Engineers on this team build and own foundational systems that applications across the organization rely on for secure, reliable operation." That seems like a list but not formatted; we can turn into a paragraph or list? It's a series of phrases separated by spaces. Could treat as a paragraph. Then "Responsibilities" heading. Under Responsibilities: "This role is responsible for designing, building, and operating the foundational infrastructure that powers the company’s technology platform. This includes compute, storage, networking, and container infrastructure supporting enterprise applications, internal platforms, and hybrid cloud environments. This role focuses on delivering reliable, scalable, and automated infrastructure platforms across data centers and cloud environments. Infrastructure engineers operate the foundational platforms that support modern workloads, including virtualization platforms, storage systems, networking, and container infrastructure such as Kubernetes clusters." Then "Work Location: Onsite at one of the listed locations; remote candidates may be considered." This is metadata; we can fold into a short

        maybe under Responsibilities or separate? The instruction: do NOT put Job ID / requisition numbers as headings — fold minor metadata into a short

        or drop it. Work Location is minor metadata; we can include as a short

        maybe after responsibilities. Then "Key Responsibilities" with subheadings: - Infrastructure Engineering - Design, deploy, and operate infrastructure platforms including compute, storage, networking, and container infrastructure - Build and maintain scalable infrastructure across on-premises data centers and cloud environments - Operate and support Kubernetes clusters and their underlying infrastructure - Ensure high availability, reliability, and performance of infrastructure systems - Support hybrid infrastructure environments and platform services that run on top of them - Automation & Infrastructure as Code - Develop and maintain infrastructure automation using modern programming languages (Go, Python, Java) - Implement infrastructure provisioning and configuration through infrastructure-as-code tools such as Terraform - Standardize infrastructure deployment and lifecycle management - Build tooling that improves operational efficiency and infrastructure reliability - Platform Integration - Support infrastructure dependencies for container platforms and distributed systems - Deploy, upgrade, and maintain Kubernetes clusters and related infrastructure components - Operate infrastructure services including IaaS platforms and storage systems - Collaborate with platform engineering teams supporting CI/CD, messaging, observability, and developer platforms - Observability & Reliability - Implement monitoring and observability using Prometheus, Grafana, and OpenTelemetry - Participate in incident response and root cause analysis - Contribute to reliability improvements and operational maturity - Security & Access Management - Implement infrastructure security best practices - Support identity and access management and secrets management systems - Collaborate with security teams to ensure infrastructure resilience and compliance We need to preserve all these bullet points. Could combine into a single list, but we might lose grouping. However instruction: Use

        • for any list of duties/requirements/benefits. It doesn't say we cannot have nested lists or headings inside. But to keep simple, we could make a single
          with each bullet as
          • . That preserves all points. Now Qualifications: "Bachelor's degree in management information systems (MIS), computer science, or related technical field; or equivalent work experience. (Typically four years of related, progressive work experience would be needed for candidates applying for this position who do not possess a bachelor's degree.) Ten or more years of experience in infrastructure, platform, or site reliability engineering roles Strong experience working with Linux systems and distributed infrastructure environments Proficiency in at least one modern programming language, such as Go, Python, or Java Core Technical Experience Experience across several of the following areas: Linux systems and core infrastructure fundamentals Kubernetes and container orchestration platforms Infrastructure as code and declarative system design (e.g., Terraform, GitOps) Distributed systems and large‑scale infrastructure environments Observability and monitoring using open‑source tooling (e.g., Prometheus, Grafana, OpenTelemetry) Distributed storage systems and concepts (e.g., Ceph or similar technologies) Networking fundamentals in distributed and cloud‑based environments API‑driven infrastructure and automation systems Infrastructure security practices, including identity, access, and secrets management Hybrid infrastructure spanning on‑premises data centers and cloud environments" We need to turn into list items. The qualifications include a paragraph plus a list of areas. We can output a
            with each qualification as
            • . Could split the first sentences as separate items: Bachelor's degree..., Ten or more years..., Strong experience..., Proficiency..., then each area as separate items. Now About Us: "MidAmerican Energy Company, a Midwest utility, provides regulated electric and natural gas service to more than 1.6 million customers in Illinois, Iowa, Nebraska and South Dakota. The company owns and operates a portfolio of power-generating assets, approximately 61% of which is wind generation." We can put as

              . We should exclude EEO boilerplate. Now we need to decide sections: About the role (intro + Our Approach), Responsibilities, Qualifications, About Us. We could also include a short paragraph for Work Location under Responsibilities or as its own section? The instruction says prefer few substantive sections over many thin ones. Work Location is minor metadata; we could fold into a short

              after Responsibilities. Thus final HTML:

              About the role

              We are building a modern, software‑defined infrastructure platform designed to support the next generation of applications across the organization. This platform is designed around open-source technologies, commodity hardware, and automation-first principles. It provides the core compute, storage, networking, and container runtime capabilities required to run distributed systems at scale across both data centers and cloud environments. This is a greenfield engineering effort focused on defining how infrastructure is built and operated using code, APIs, and declarative systems, with reliability, observability, and repeatability designed in from the start.

              Our Approach emphasizes Linux-first systems design, Kubernetes as a core abstraction layer, Infrastructure-as-code and GitOps workflows, open observability standards (Prometheus, OpenTelemetry), distributed, software-defined storage and networking. Engineers on this team build and own foundational systems that applications across the organization rely on for secure, reliable operation.

              Responsibilities

              This role is responsible for designing, building, and operating the foundational infrastructure that powers the company’s technology platform. This includes compute, storage, networking, and container infrastructure supporting enterprise applications, internal platforms, and hybrid cloud environments. This role focuses on delivering reliable, scalable, and automated infrastructure platforms across data centers and cloud environments. Infrastructure engineers operate the foundational platforms that support modern workloads, including virtualization platforms, storage systems, networking, and container infrastructure such as Kubernetes clusters.

              Work Location: Onsite at one of the listed locations; remote candidates may be considered.

              • Design, deploy, and operate infrastructure platforms including compute, storage, networking, and container infrastructure
              • Build and maintain scalable infrastructure across on-premises data centers and cloud environments
              • Operate and support Kubernetes clusters and their underlying infrastructure
              • Ensure high availability, reliability, and performance of infrastructure systems
              • Support hybrid infrastructure environments and platform services that run on top of them
              • Develop and maintain infrastructure automation using modern programming languages (Go, Python, Java)
              • Implement infrastructure provisioning and configuration through infrastructure-as-code tools such as Terraform
              • Standardize infrastructure deployment and lifecycle management
              • Build tooling that improves operational efficiency and infrastructure reliability
              • Support infrastructure dependencies for container platforms and distributed systems
              • Deploy, upgrade, and maintain Kubernetes clusters and related infrastructure components
              • Operate infrastructure services including IaaS platforms and storage systems
              • Collaborate with platform engineering teams supporting CI/CD, messaging, observability, and developer platforms
              • Implement monitoring and observability using Prometheus, Grafana, and OpenTelemetry
              • Participate in incident response and root cause analysis