Cloud Engineer/Site Reliability Architect

We need to output HTML fragment only, with sections for headings: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. Use

for each heading only if there is real content. Must not repeat job title. Must not include Job ID etc. Remove boilerplate: EEO, legal, etc. Must preserve all substantive info. We need to parse the posting. Content: Intro paragraph: "This is a Kubernetes-heavy platform engineering role supporting large-scale, multi-cloud GPU infrastructure. Success requires deep operational judgment, disciplined debugging, strong automation skills, and the ability to protect platform stability while capacity grows rapidly." Then "What You’ll Do" bullet list. Then "What You’ll Bring" bullet list. Then "About Us" paragraph. Then "Compensation and Benefits" paragraph with details. Also "We will accept applicants until 10/5/2026, or until the position is filled." That's application instruction? It's a deadline; maybe considered application instruction? The instruction says remove application instructions. This is a deadline; likely considered application instruction, so remove. Also "We are committed to pay transparency..." contact email etc. That's maybe part of compensation? It's about pay range contact. Might keep as part of Compensation and Benefits? It's about pay range contact. Could keep as part of Compensation and Benefits section. EEO and Accommodations: remove. Thus sections: - About the role: maybe the intro paragraph? Could be "About the role". We'll put that as

About the role

...intro...

- Responsibilities: the "What You’ll Do" list. - Requirements: maybe combine "What You’ll Bring" as Requirements? Could also split into Requirements and Qualifications and Skills. But we need to follow headings list; we can include only those with real content. We have "What You’ll Bring" which includes hands-on experience etc. Could map to Requirements (or Qualifications). We'll decide: Use Requirements for the bullet list of required experience. Could also have Skills for specific skills like Terraform, Python, etc. But the bullet list already includes many skills. To avoid thin sections, we can combine into Requirements. - Benefits: from Compensation and Benefits paragraph (benefits details). Also maybe include Pay: we have salary ranges. So we need Pay section if posting actually states them. Yes, they give salary ranges. So we need Pay section. - Schedule: not mentioned; no schedule info. So omit. - About Us: could be a section but not in headings list; headings list includes About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. About Us is not in list, but we could maybe put under About the role? The instruction says use those headings for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). It doesn't forbid other headings, but says use

for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). Likely they expect only those headings. So we should not include About Us as a separate heading; maybe incorporate its content into About the role or drop? The About Us paragraph is descriptive of company; could be considered part of About the role? Might be okay to include as part of About the role. But we must preserve ALL substantive information; we cannot drop it. So we need to include it somewhere. Could add a

About the company

but that's not in the list; risk of violating instruction. However instruction says "use

for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." The "e.g." suggests those are examples, not exclusive. But later: "IMPORTANT: include a section ONLY when the posting has real, specific content for it — never emit a heading followed by filler/placeholder text". It doesn't forbid other headings. Safer to include About Us as a section with heading About Us. But they gave list of examples; not strict. I'd include About Us as a section. But they said "Use

for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." So we can use those exact headings; maybe they expect only those. However About Us is not in list; but we could treat it as part of About the role. The About the role section could include both role description and company description. That would preserve all info. Let's do that: About the role includes intro paragraph + About Us paragraph. Thus:

About the role

This is a Kubernetes-heavy platform engineering role supporting large-scale, multi-cloud GPU infrastructure. Success requires deep operational judgment, disciplined debugging, strong automation skills, and the ability to protect platform stability while capacity grows rapidly.

Slalom is a fiercely human business and technology consulting company that leads with outcomes to bring more value, in all ways, always. From strategy through delivery, our agile teams across 52 offices in 12 countries partner with clients to co-create powerful customer experiences, modern ways of working, and meaningful impact. What sets us apart? We believe work should be challenging and fulfilling, not perfect, but possible. That’s why we prioritize purpose, flexibility, connection, and recognition, so our people can thrive and love what they do, most days.

Then Responsibilities: list from "What You’ll Do". Use

• . Then Requirements: list from "What You’ll Bring". Use
  • . Then Benefits: from Compensation and Benefits paragraph describing benefits. Use
    • maybe each benefit as list. Then Pay: salary ranges. Could be a

      with the ranges. We must not include schedule. We must not include application deadline, EEO, accommodations, contact email for pay transparency? The contact email is part of compensation transparency; maybe keep as part of Pay section? It's not boilerplate; it's about pay range contact. Could include as a

      after salary ranges. But the instruction: "Remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions." The contact email is not exactly boilerplate; it's for pay questions. Might be okay to keep. We'll include Pay section with salary ranges and note about discretionary bonus and contact. Now ensure no repeated lines. Let's extract details. Responsibilities bullet points: - Operate Kubernetes platforms at significant scale across providers, including Amazon Elastic Kubernetes Service (EKS), CoreWeave Kubernetes Service (CKS), and Google Kubernetes Engine (GKE). - Own the Kubernetes cluster lifecycle, including node-pool design and management, scheduler troubleshooting, container network interface (CNI) and network-policy troubleshooting, capacity planning, and safe rolling upgrades across large fleets. - Develop, review, and maintain infrastructure as code with Terraform, along with Python tooling and automation that improve reliability, repeatability, and operational efficiency. - Define and maintain service-level indicators (SLIs) and service-level objectives (SLOs); build monitoring and alerting that surface meaningful risks before they affect workloads. - Debug complex distributed-system failures by forming hypotheses, testing them methodically, and separating temporal correlation from causation. - Provision high-performance computing (HPC) and GPU infrastructure through the Conveyor CI/CD system across AWS, CoreWeave, Google Cloud Platform (GCP), and Oracle Cloud Infrastructure (OCI), with additional providers as the platform expands. - Coordinate daily with Networking, Storage, Security, and AI/ML platform teams to resolve cross-system dependencies and improve the end-to-end developer and researcher experience. - Bring forward well-reasoned proposals, solutions, and informed opinions; use available tools and resources to self-unblock and drive issues to resolution. Requirements bullet points (What You’ll Bring): - Hands-on Kubernetes experience including node pool sizing, scheduler debugging, CNI troubleshooting, and rolling upgrades across fleets. - Strong Terraform proficiency and experience writing and reviewing production infrastructure as code on a daily basis. - Practical Python skills for tooling and automation, including the ability to write code without relying on artificial intelligence assistance. - Strong critical-thinking and debugging skills, with a disciplined approach to forming hypotheses, validating evidence, and isolating root causes. - Ability to read unfamiliar code, understand its behavior, and diagnose issues effectively. - Resourcefulness and a consistent ability to self-unblock using documentation, telemetry, code, peers, and available tooling. - A proactive working style: you arrive with proposals, formulate solutions, and communicate informed technical opinions. - Clear communication and effective collaboration across engineering teams and technical stakeholders. - Working knowledge of AWS or similar Cloud services relevant to compute and data-intensive platforms, including Amazon EC2, Amazon S3, Amazon EFS, and Amazon FSx for Lustre. - Experience designing or operating CI/CD pipelines and automated infrastructure provisioning workflows. - Knowledge of cloud networking, storage, security, observability, reliability engineering, and platform governance. - Nice-to-have: Experience using AI coding tools responsibly: you remain accountable for the solution, validate generated code, identify edge cases, and reject unnecessary or incorrect output. We could keep the nice-to-have as part of Requirements (maybe as a sub bullet). Keep as is. Benefits paragraph: "Slalom prides itself on helping team members thrive in their work and life. As a result, Slalom is proud to invest in benefits that include meaningful time off and paid holidays, parental leave, 401(k) with a match, a range of choices for highly subsidized health, dental, & vision coverage, adoption and fertility assistance, and short/long-term disability. We also offer yearly $350 reimbursement account for any well-being-related expenses, as well as discounted home, auto, and pet insurance." We can turn each benefit into list items. Pay paragraph: includes salary ranges and bonus and contact. Let's extract: "Slalom is committed to fair and equitable compensation practices. For this role, we are hiring at the following levels and targeted base pay salary ranges: The target base salary range for Senior Consultant in East Bay, Silicon Valley, and San Francisco is $149,000-$185,000. The target base salary range for Senior Consultant in is $149,000-$185,000. The target base salary range in San Diego, Los Angeles, Orange County, Seattle, Houston, New Jersey, New York City, Westchester, Boston, Washington DC for Senior Consultant is $136,500-$169,500. The target base salary range for Senior Consultant in all other US based Slalom locations is $125,000-$155,500. In addition, individuals may be eligible for an annual discretionary bonus. Actual compensation will depend upon an individual’s skills, experience, qualifications, location, and other relevant factors. The salary pay range is subject to change and may be modified at any time. We will accept applicants until 10/5/2026, or until the position is filled.We are committed to pay transparency and compliance with applicable laws. If you have questions or concerns about the pay range or other compensation information in this posting, please contact us at: peopleone@slalom.com. Please note, this recipient is not able to support recruitment inquiries beyond this purpose." We need to remove application instruction line: "We will accept applicants until 10/5/2026, or until the position is filled." So remove that sentence. Also maybe remove duplicated line: "The target base salary range for Senior Consultant in is $149,000-$185,000." That seems weird: missing location; maybe it's a duplicate; but we must preserve all substantive information; it's still substantive albeit weird. We'll keep it as is. We'll produce Pay section with

      containing the salary ranges and bonus and contact