Staff Engineer, Cloud

We need to output HTML fragment with sections: About the role? The description includes a paragraph about company and mission. Could be "About the role" or maybe "About the team". The instructions: use

for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). We need to include sections only when posting has real specific content. We have responsibilities (What You’ll Do) with sub-bullets. We have qualifications (What You’ll Bring) with experience and technical skills. Also Preferred Qualifications. Also Professional Qualities. Also How We Work (maybe not needed). Benefits: there is a "How We Reward You" section with benefits list. Pay and Schedule not mentioned. So we should not include Pay or Schedule sections. We need to preserve all substantive info, not invent. Remove boilerplate: EEO, equal opportunity, scam warning, etc. Also navigation/cookie etc. Also "Do the best work of your life..." maybe considered marketing fluff but it's substantive? Might be considered boilerplate? It's part of description but not essential? The instruction: Remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. The "Do the best work..." is not boilerplate but could be considered fluff; but it's part of the posting. Might keep as part of "About the role"? However we have to avoid filler. It's not filler; it's a motivational paragraph. Could be included under "About the role" as prose. We need to output only HTML fragment, no /. Use

for headings. Use

• for lists. Use

  for prose. We need to decide sections: About the role (intro paragraph). Responsibilities (What You’ll Do). Requirements (maybe combine What You’ll Bring + Technical Skills + Preferred Qualifications + Professional Qualities). Could separate Qualifications and Skills. But instructions: prefer few substantive sections over many thin ones. So we could have: About the role, Responsibilities, Qualifications (which includes experience, technical skills, preferred qualifications, professional qualities), Benefits. We must not repeat job title as heading. No Job ID. Let's extract content. Intro paragraph: "Recognized as the No. 1 site trusted by real estate professionals, Realtor.com® has been at the forefront of online real estate for over 25 years, connecting buyers, sellers, and renters with trusted insights and expert guidance to find their perfect home. Through its robust suite of tools, Realtor.com® not only makes a significant impact on the real estate industry at large, but for consumers, navigating the biggest purchase they will make in their life, by providing a user experience that is easy to use, easy to understand, and most of all, easy to make decisions. Join us on our mission to empower more people to find their way home by breaking barriers to entry, making the right connections, and building confidence through expert guidance." That's about the company and mission. Could be "About the role" or maybe "About the team". We'll use About the role. Then "We are seeking a Staff Software Engineer – Cloud Platform to join our growing infrastructure organization. This is a high-impact opportunity to help build and shape the Cloud Platform team and the foundational capabilities that support engineers across the company. You will be a senior technical contributor responsible for defining cloud standards, scaling platform capabilities, and improving the developer experience for teams building and operating products on AWS. You will take ownership of cloud governance, automated remediation, internal developer tooling, self-service infrastructure, and cost optimization, turning complex infrastructure requirements into practical capabilities that engineering teams can adopt. This is a high-impact opportunity with broad visibility across Engineering, Security, and Finance. You will help establish the operating model for a growing Cloud Platform team while maintaining a hands-on role in architecture, automation, and platform delivery. We believe in leveraging the best tools to solve problems faster. You will be expected to use AI coding assistants and LLMs to accelerate development, generate boilerplate, document systems, and troubleshoot complex problems. You will apply critical judgment to verify AI-generated output for security, performance, reliability, and accuracy." That's also part of role description; could be part of About the role or Responsibilities. But we have a separate "What You’ll Do" section with bullet points. So we could keep the introductory paragraph as About the role, and then Responsibilities as the bullet list under "What You’ll Do". However the bullet list includes subheadings like Cloud Platform Architecture & Standards etc. We need to output as list items; we can keep them as list items with maybe sub-bullets? The instruction: Use

  • for any list of duties/requirements/benefits. So we can flatten each bullet as
  • . If there are sub-bullets, we could nest
    inside
    • . That's okay. Thus Responsibilities section:

      Responsibilities

      then
      with each top-level bullet. Let's extract the bullet points from "What You’ll Do": - Cloud Platform Architecture & Standards - Define and evolve reusable cloud platform patterns for AWS infrastructure, production Kubernetes, account governance, networking, identity, security, and operational readiness. - Lead the design and implementation of infrastructure-as-code modules, templates, and reference architectures using Terraform, CloudFormation, CDK, or comparable tools. - Establish practical platform standards that balance developer autonomy with security, reliability, compliance, and cost requirements. - Partner with engineering leaders and technical teams to assess platform needs, make architecture tradeoffs, and guide adoption of shared capabilities. - Cloud Governance & Automated Remediation - Implement and maintain governance controls for security, tagging, resource lifecycle, account configuration, and compliance across AWS environments. - Build policy-as-code and automated remediation capabilities using Cloud Custodian, AWS Organizations, Service Control Policies, or equivalent technologies. - Create detection, reporting, and remediation workflows for configuration drift, cloud risk, orphaned resources, and cost issues. - Work with Security, Finance, and Engineering to translate governance requirements into automated, developer-friendly controls. - Internal Developer Platform & Paved Paths - Build and improve self-service platform capabilities that allow engineering teams to provision and operate infrastructure without unnecessary manual intervention. - Run and extend internal developer portal capabilities such as Backstage, including service catalogs, plugins, onboarding workflows, and platform documentation. - Integrate infrastructure-as-code, policy checks, security validation, and operational readiness into delivery workflows. - Develop reusable tooling, automation, and diagnostics that reduce developer friction and improve platform adoption. - AWS, Kubernetes, FinOps & Reliability - Define and maintain governance for AWS and production Kubernetes/EKS environments, including access, security, networking, upgrades, and lifecycle management. - Support reliable containerized workloads using Kubernetes, Docker, Helm, and related cloud-native technologies. - Drive cost optimization through rightsizing, utilization analysis, reserved capacity, Savings Plans, spot usage, autoscaling, and workload lifecycle management. - Build cost controls, dashboards, alerts, and reporting that help teams understand resource consumption and make cost-conscious architecture decisions. - Improve observability and contribute to incident response, post-incident reviews, runbooks, and reliability improvements for shared platform capabilities. - Technical Leadership & Collaboration - Provide technical leadership across multiple engineering teams through architecture reviews, design guidance, documentation, and hands-on delivery. - Mentor engineers in infrastructure automation, cloud governance, platform engineering, and operational best practices. - Build alignment across Engineering, Security, Finance, and other business partners. - Maintain an active coding footprint in Python, Go, Java, Bash, or similar languages used to build platform automation and internal tooling. Now Requirements/Qualifications: "What You’ll Bring" includes: - 8+ years of experience in cloud platform, DevOps, infrastructure, SRE, or software engineering roles with significant infrastructure ownership. - 4+ years of hands-on experience designing, provisioning, and troubleshooting AWS infrastructure in production environments. - 3+ years of experience managing production-grade Kubernetes or Amazon EKS environments. - Demonstrated experience building reusable platform capabilities, cloud governance systems, internal tooling, or self-service infrastructure used by multiple engineering teams. - Experience influencing technical standards and architecture across team boundaries without relying on formal management authority. Then "Technical Skills" list (maybe under Skills). Then "Preferred Qualifications" list. Then "Professional Qualities" list. We could combine into Qualifications section with sub-sections? But instruction: prefer few substantive sections over many thin ones. So maybe we have Qualifications (including experience, technical skills, preferred qualifications, professional qualities) as one section with nested lists. But we need to use
      • for any list. So we can have a
        with each top-level item; if we want to categorize, we could have headings inside
        • ? Not ideal. Better to have separate sections: Requirements, Skills, Preferred Qualifications, Professional Qualities. But that's many sections. However we can combine Technical Skills and Preferred Qualifications and Professional Qualities under Qualifications as subheadings using

          ? But only

          allowed for section headings per instruction? It says use

          for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). It doesn't forbid other headings, but suggests those as examples. Safer to stick to those headings. So we can have sections: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits. That's six sections. That's okay. We need to map content: - About the role: intro paragraph (company mission + seeking statement). - Responsibilities: the bullet list from What You’ll Do. - Requirements: the baseline experience requirements (8+ years, 4+ years AWS, 3+ years Kubernetes, demonstrated experience building reusable platform capabilities, experience influencing technical standards). That's the "What You’ll Bring" bullet list. - Qualifications: maybe we could treat as "Qualifications" but we already used Requirements for experience. Could rename Requirements to "Qualifications". But we need both Requirements and Qualifications? The instruction list includes both as possible headings. We could use Requirements for the experience, and Qualifications for technical skills? Or we could combine. Let's think: The posting has "What You’ll Bring" (experience) and then "Technical Skills", "Preferred Qualifications", "Professional Qualities". So we could map: - Requirements: the baseline experience (8+ years etc.) - Qualifications: maybe the "Technical Skills" list? But Qualifications heading is ambiguous. Could use Skills for technical skills, Qualifications for preferred qualifications and professional qualities? Hmm. Better to follow typical job posting structure: About the role, Responsibilities, Requirements (experience), Qualifications (skills/preferred), Benefits. But we have both Requirements and Qualifications headings allowed. Let's assign: - Requirements: the mandatory experience (8+ years etc.) - Qualifications: the technical skills list (AWS, EKS, etc.) maybe plus preferred qualifications? But we also have Preferred Qualifications separate. We could have: - Requirements: mandatory experience. - Skills: technical skills. - Preferred Qualifications: preferred qualifications. - Professional Qualities: professional qualities. That's four sections plus About the role and Responsibilities and Benefits = 7 sections. That's okay; not too many. But instruction: Prefer a few substantive sections over many thin ones. However we have substantive content for each; they are not thin. So it's fine. Let's list sections: - About the role - Responsibilities - Requirements - Skills - Preferred Qualifications - Professional Qualities - Benefits We need to ensure we don't create sections with filler like "commensurate with experience". We have real content. Now extract content for each. About the role: combine the introductory paragraph and the sentence "We are seeking a Staff Software Engineer – Cloud Platform to join our growing infrastructure organization. This is a high-impact opportunity..." Actually that sentence is more about the role; but we could include it in