Senior Cloud Engineer

We need to output HTML fragment with sections: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. Only include sections that have real specific content. From posting: - About the role: The first paragraph "Your Job The Senior Cloud Engineer at KBX is a high-impact individual contributor..." That's about the role. Could be "About the role". Should we include heading

About the role

then paragraph. - Responsibilities: The "What You Will Do" list includes many bullet points. Those are responsibilities. So we need a

Responsibilities

with

• items. - Requirements: There's "Who You Are (Basic Qualifications)" which lists qualifications/experience. That's requirements. Could be

  Requirements

  with list. - Qualifications: Possibly separate from Requirements? The posting also has "What Will Put You Ahead" which are preferred qualifications. Could be

  Qualifications

  or maybe "Preferred Qualifications". But we only have sections defined: Qualifications. We can treat "What Will Put You Ahead" as Qualifications (preferred). Also there are certifications listed there. - Skills: Not explicitly listed separate; but we could infer from responsibilities and requirements. However we should not create a Skills section unless posting actually states them. The posting does not have a dedicated "Skills" heading. So we should not create Skills section. - Benefits: There's "Our Benefits" paragraph describing benefits. So include

  Benefits

  with
  • items. - Pay: There's a paragraph about compensation range: "Any compensation range provided for a role is an estimate...". That's about pay but not a specific range. It says "Any compensation range provided for a role is an estimate...". It does not give actual numbers. According to rule: do NOT include Pay section unless posting actually states them. It does not state a specific range, just a disclaimer. So we should NOT include Pay section. - Schedule: No mention. So omit. Also need to include maybe a short paragraph for metadata like Job ID? Not needed. We must preserve all substantive information, not invent or summarize away detail. Must not include boilerplate like EEO, legal, etc. Remove duplicated lines. We need to output only HTML fragment, no markdown fences. Let's extract content. About the role paragraph: "Your Job The Senior Cloud Engineer at KBX is a high-impact individual contributor who designs, builds, and operates a modern AWS-first cloud platform that enables application teams to deliver products securely and efficiently. This senior-level role combines hands-on engineering with ownership across cloud infrastructure, advanced networking, Amazon EKS/Kubernetes, service mesh, automation, security, reliability, and cost optimization. Senior engineers help shape the platform strategy, establish engineering standards, lead the resolution of complex technical challenges, and influence cloud decisions for the organization." We can combine into one

    . Responsibilities bullet list from "What You Will Do". Let's list each sentence as bullet. - Design and evolve secure, scalable, highly available AWS infrastructure and multi-account platform solutions in alignment with enterprise security, compliance, reliability, and business requirements. - Lead the technical direction and lifecycle strategy of our cloud platform including the Kubernetes-based platform (Amazon EKS) and shared services, Istio, Amazon MSK/Kafka, and Redis/ElastiCache. - Build and govern Infrastructure as Code and GitOps practices using Terraform, Argo CD, Helm, and GitHub Actions to enable consistent, automated provisioning, testing, configuration, and deployment. - Assist in defining platform standards, reusable capabilities, and operational controls that enable application teams to adopt cloud and AI technologies securely, reliably, and at scale. - Design and implement cloud security guardrails, including IAM, , network policies, encryption, and secrets management, while proactively remediating vulnerabilities based on risk. (Note there is a stray comma after IAM; but we keep as is.) - Contribute to observability practices across logging, metrics, and tracing; use platform data to improve operational health. - Lead incident response and root-cause analysis for complex cloud and platform issues, driving durable improvements that reduce recurrence. - Partner with Software and Engineering, DevOps, Security, and IT leadership teams to translate requirements into platform solutions, accelerate onboarding, and remove infrastructure barriers to delivery. - Implement FinOps practices for cost allocation, tagging, budgeting, forecasting, and reporting; guide teams in balancing cost, performance, reliability, risk, and business value. - Provide hands-on technical leadership by producing high-quality infrastructure code, conducting architecture and code reviews, and modeling engineering best practices for security, reliability, and maintainability. - Mentor junior and mid-level engineers, raise technical standards, and influence cloud and platform architecture decisions across teams without relying on direct authority. - Evaluate emerging cloud technologies and strategic trade-offs, leading the adoption of tools, frameworks, and processes that support immediate needs and long-term platform strategy. We need to ensure we keep the exact text. Some bullet includes "IAM, ," double comma; we keep. Requirements bullet list from "Who You Are (Basic Qualifications)". Let's list each. - Experience designing, implementing, and supporting production AWS environments that use multiple accounts, VPCs, compute, storage, IAM roles, and network services. - Experience designing and troubleshooting AWS network connectivity and security using VPCs, subnets, route tables, security groups, PrivateLink, VPNs, or comparable services at enterprise scale - Experience deploying and operating production container workloads on Amazon EKS or ECS, including container networking and ingress configuration - Experience building and maintaining reusable cloud infrastructure with Terraform and automating deployments or operational workflows through GitHub Actions or another CI/CD platform. - Experience creating/maintaining automation using either Python or shell scripts - Experience applying cloud security and reliability practices(including IAM, encryption, secrets management, monitoring, logging, high availability, incident response, and root-cause analysis) - Experience making recommendations and solutioning for the companies cloud strategy Note there is missing space after practices(; but keep. Qualifications (preferred) from "What Will Put You Ahead". List: - Experience supporting an internal cloud or developer platform used by multiple application teams. - Experience implementing or operating a service mesh, such as Istio, and an API gateway, such as Gloo, kgateway, Kong, or a comparable technology, in a production environment. - Experience using GitOps practices and a tool such as Argo CD to deploy and manage workloads on Kubernetes. - Experience configuring Cloudflare or a comparable CDN, DNS, or web security platform for traffic management and application protection. - Experience integrating on-premises systems with AWS resources in a hybrid or multi-cloud environment, including network connectivity or identity federation. - AWS Certified Solutions Architect - Associate (or higher). - Certified Kubernetes Administrator (CKA) or similar Kubernetes certification. Also there is a paragraph about Koch companies entrepreneurs etc. That's not a section; could be part of About the role? It's more about company culture. Could be included in About the role paragraph? Might be considered "About the team" but we don't have a section for that. Could be omitted? The instruction: preserve ALL substantive information; do not invent or summarize away detail. So we need to include that info somewhere. Perhaps we can add another section like "About the Team" but not allowed headings list only includes specific ones. However we could incorporate into About the role or Responsibilities? The text: "At Koch companies, we are entrepreneurs. This means we openly challenge the status quo, find new ways to create value and get rewarded for our individual contributions." That's about company culture. Could be placed under About the role as additional paragraph. Also "Our Team" paragraph: "We partner closely with Software Engineering and DevOps, Security, and IT leadership to create secure, scalable, and reliable platform solutions, strengthen engineering practices, and accelerate the responsible adoption of cloud and AI technologies. We value technical curiosity, critical thinking, knowledge sharing, technical leadership, and a "can-do" attitude." This is about team. Could be part of About the role or maybe a separate section "About the Team" but not allowed. We could incorporate into About the role as additional paragraph. Also "Who We Are" paragraph about KBX Logistics etc. That's company description. Could be part of About the role? Might be considered "About the Company". Not a defined heading but we could add as paragraph under About the role? Might be okay. But we must not create new headings beyond the allowed list. So we can add multiple

    under About the role to include all these descriptive paragraphs. Similarly Benefits section: we have paragraph "Our goal is for each employee..." and list. We'll make

    • for each benefit item. Benefits list: "medical, dental, vision, flexible spending and health savings accounts, life insurance, ADD, disability, retirement, paid vacation/time off, educational assistance, and may also include infertility assistance, paid parental leave and adoption assistance." We need to split into list items. Could be each item separated by commas. Let's produce list items: - medical - dental - vision - flexible spending and health savings accounts - life insurance - ADD - disability - retirement - paid vacation/time off - educational assistance - infertility assistance (may also include) - paid parental leave (may also include) - adoption assistance (may also include) But we need to preserve the exact wording? The instruction: preserve ALL substantive information; do NOT invent or summarize away detail. We could keep the sentence as a single paragraph rather than list. However rule: Use
      • for any list of duties/requirements/benefits. So we need to turn the benefits into list. We must not lose detail. We can split as above but need to ensure we don't lose nuance like "may also include". Could add note in each item. Better: Keep as one

        for the benefits description, but rule says use

        • for any list of benefits. The benefits are indeed a list. So we should list them. We'll produce items exactly as they appear in the sentence, maybe keep the phrase "may also include infertility assistance, paid parental leave and adoption assistance." Could be one item: "may also include infertility assistance, paid parental leave and adoption assistance". That preserves. Thus list: - medical - dental - vision - flexible spending and health savings accounts - life insurance - ADD - disability - retirement - paid vacation/time off - educational assistance - may also include infertility assistance, paid parental leave and adoption assistance Now Pay: we decided not to include. Schedule: none. Now we need to output HTML fragment. Structure:

          About the role

          ... (multiple paragraphs maybe combine into one

          with line breaks? Could use multiple

          under same heading. That's fine. We'll do:

          About the role

          Your Job The Senior Cloud Engineer at KBX is a high-impact individual contributor who designs, builds, and operates a modern AWS-first cloud platform that enables application teams to deliver products securely and efficiently. This senior-level role combines hands-on engineering with ownership across cloud infrastructure, advanced networking, Amazon EKS/Kubernetes, service mesh, automation, security, reliability, and cost optimization. Senior engineers help shape the platform strategy, establish engineering standards, lead the resolution of complex technical challenges, and influence cloud decisions for the organization.

          Our Team We partner closely with Software Engineering and DevOps, Security, and IT leadership to create secure, scalable, and reliable platform solutions, strengthen engineering practices, and accelerate the responsible adoption of cloud and AI technologies. We value technical curiosity, critical thinking, knowledge sharing, technical leadership, and a "can-do" attitude.

          At Koch companies, we are entrepreneurs. This means we openly challenge the status quo, find new ways to create value and get rewarded for our individual contributions.

          Who We Are KBX Logistics, a Koch company and global leader in transportation, offers world-class, technology-driven capabilities across all modes of managed freight and transportation asset management. KBX is uniquely positioned to meet the challenges shippers face, leveraging decades of