Staff Platform Engineer

We need to output HTML fragment with sections: About the role? Actually the posting includes sections: About Reltio, About The Team, What Is Exciting About This Opportunity, Position Overview, Key Responsibilities, Qualifications, Preferred Qualifications, maybe Compensation? It says compensation N/A, but we should not create Pay/Schedule/Benefits sections unless posting actually states them. Compensation N/A is not specific; we should not include Pay section. Also we should not repeat job title as heading. We need to use

for section headings (e.g., About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). However we need to map content to appropriate headings. The instructions: use

for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). So we should use those exact headings? Probably we should use those headings where applicable. The posting has sections: About Reltio (could be About the role?), About The Team, What Is Exciting About This Opportunity, Position Overview, Key Responsibilities, Qualifications, Preferred Qualifications. We need to decide which headings to use. We should not invent sections. Use headings only when posting has real specific content. So we can have:

About the role

maybe combine About Reltio and About The Team and What Is Exciting About This Opportunity? But better to follow the posting's natural sections: About Reltio, About The Team, What Is Exciting About This Opportunity, Position Overview, Key Responsibilities, Qualifications, Preferred Qualifications. But the instruction says use headings like About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. It seems they expect us to map to those generic headings. However they also say "use

for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." That suggests we can use those exact headings, but we can also use other headings if they match content? The examples are just examples; we can use any appropriate heading but must be

. Probably we should use headings that reflect the content: About Reltio, About the Team, What Is Exciting About This Opportunity, Position Overview, Key Responsibilities, Qualifications, Preferred Qualifications. We must not repeat job title as heading. Also we must not include Job ID etc. We need to use

• for any list of duties/requirements/benefits. So for Key Responsibilities list, we need
  • . For Qualifications list, also
    • . For Preferred Qualifications also list. We need to use

      for prose. We must preserve ALL substantive information; do not invent or summarize away detail. Remove boilerplate: cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. So we need to cut out the "Ready to apply? Review the details above and continue to the employer's site to start your application." and also the duplicated "Role snapshot Compensation N/A Location ..." and the repeated technologies list maybe? We need to keep substantive info: About Reltio paragraph, About The Team paragraph, What Is Exciting About This Opportunity bullet-like sentences? Actually it's a paragraph with semicolons. We'll keep as prose. Position Overview paragraph. Key Responsibilities list (each bullet). Qualifications list (each bullet). Preferred Qualifications list. We also need to keep location list? The location appears in the role snapshot and also earlier. It's substantive: location Raleigh, NC; Austin, TX; Dallas, TX; Florida; Boston, MA. Should we include? It's not a heading but we can include in a

      maybe under About the role? The instruction says we can include minor metadata into a short

      or drop it. Location is not minor? It's location info. Could be included in a short

      . We'll include a

      with location. Compensation N/A: we should not create Pay section because it's N/A. So we can drop compensation. Technologies list: maybe we can include as a short

      under About the role or as a separate section? The instruction says we should not create Pay/Schedule/Benefits sections unless posting actually states them. Technologies is not one of those headings; we could include as a

      under About the role or as a separate section like "Technologies". But the instruction only gave examples of headings; we can still use other headings if needed. However to keep minimal, we could include technologies in a

      under About the role. We must not include duplicated lines: there is a duplicated "Role snapshot Compensation N/A Location ..." and also later "Ready to apply?" etc. We'll remove those. Now produce HTML fragment. Structure:

      About the role

      About Reltio ...

      About The Team ...

      What Is Exciting About This Opportunity ...

      Position Overview ...

      Then maybe

      Responsibilities

      with
      • ... each responsibility. Then

        Qualifications

        with
        • ... each qualification. Then

          Preferred Qualifications

          with
          • ... each preferred. Optionally include location and technologies in a

            under About the role or separate

            About the role> includes them. We need to ensure we don't repeat content. Let's extract the prose. About Reltio paragraph: "At Reltio®, an SAP Company, we believe data should fuel your success in the enterprise AI era. Our Context Intelligence Platform turns fragmented data into a trusted, connected context so AI agents and systems can act with expert-level judgement at enterprise scale. Reltio’s cloud-native SaaS platform harmonizes, unifies, and governs data across sources and formats—including unstructured data—in real time, turning them into data assets that can be mobilized in milliseconds to any application, user, or AI agent. Trusted by more than 200 of the world’s largest brands across industries such as life sciences, financial services, healthcare, and technology, we fuel frictionless operations and help enterprises accelerate innovation and reduce risk. At Reltio, our values guide everything we do. With an unyielding commitment to prioritizing our “Customer First”, we strive to ensure their success. We embrace our differences and are “Better Together” as One Reltio. We are always looking to “Simplify and Share” our knowledge when we collaborate to remove obstacles for each other. We hold ourselves accountable for our actions and outcomes and strive for excellence. We “Own It”. Every day, we innovate and evolve, so that today is “Always Better Than Yesterday”. If you share and embody these values, we invite you to join our team at Reltio and contribute to our mission of excellence. Reltio has earned numerous awards and industry and analyst recognition for our technology, our culture and our people. Reltio was founded on a distributed workforce and offers flexible work arrangements to help our people manage their personal and professional lives. If you’re ready to work on unrivaled technology where your desire to be part of a collaborative team is met with a laser-focused mission to enable digital transformation with connected data, let’s talk!" That's long but we keep. About The Team paragraph: "The Reltio TechOps team is committed to delivering best-in-class DevSecOps capabilities and developer experience. You will be responsible for helping the company scale its cloud-based services through refining our internal platform, with a heavy focus on automation, and continuous delivery. Help TechOps to set time-bound, clear, and concise maturity and strategic goals and execute against the strategy to improve developer experience and level up DevSecOps maturity." What Is Exciting About This Opportunity paragraph: "Dynamic pace and opportunity to work with the hottest technology, K8S CI/CD, and infrastructure-as-code tools in AWS, GCP, and Azure.Be a key participant in implementing tools and strategies used to revolutionize Reltio’s internal infrastructure platform.Reltio’s product roadmap is targeted directly towards AI enablement for enterprise customers. Reltio is committed to AI-enabled tooling and processes.Exposure to challenging problems in blending MDM and Big Data worlds with a focus on cost efficiency, reliability, and availability.Have the opportunity to bring new automated approaches to scalability, capacity management, cost optimization, and elasticity." Note there are missing spaces after periods; we keep as is. Position Overview paragraph: "Staff Platform Engineer/SME in infrastructure, security management, and services for Reltio cloud services - MDM, RIQ, RDM, and other services or components that create the foundation of the core Reltio Product line. Platform Engineering is the first line of investigation and troubleshooting of the service reliability issues pertaining to DevSecOps." Key Responsibilities list (each bullet): - Design, implement, and manage infrastructure as code (IaC) solutions using tools like Crossplane, Terraform, and Helm Charts to provision and manage cloud resources. - Collaborate with product managers, developers, InfoSec, and other stakeholders to define platform requirements, scope, and priorities. - Collaborate with development, operations, and quality assurance teams to streamline the software delivery process and ensure high-quality releases. - Monitor, troubleshoot, and optimize the performance and cost of our DevOps tools and platforms to ensure reliability, availability, and scalability. - Design zero-downtime maintenance strategies for fleets of Kubernetes clusters and cloud resources. - Evaluate industry trends and recommend new tools, technologies, and best practices to improve our DevOps processes and workflows. - Mentor junior platform engineers, providing guidance, mentorship, and support to foster their growth and development. - Act as a force multiplier to engineers and development teams by providing expert guidance on integrating with the internal platform, best practices, tools, and methodologies. - Collaborate with security teams to integrate security controls and best practices into our DevOps processes and infrastructure. - Document technical designs, procedures, and configurations to ensure knowledge sharing and maintain system integrity. - Contribute to a culture of innovation, collaboration, and continuous improvement within the TechOps team and across the organization. - Eliminate toil through the automation of existing processes with modern tooling, including AI tools and agentic workflows. Qualifications list: - Bachelor's degree in Computer Science, Engineering, or related field; or equivalent work experience. - 8+ years of experience working as a Cloud Engineer, or similar role, with a strong background in software development and infrastructure operations. - Proficiency with containerization technologies (Docker, Kubernetes) and orchestration tools. - Proficiency with declarative management tools such as Terraform, Crossplane, or CloudFormation. - Experience with cloud platforms such as AWS, Azure, or Google Cloud Platform. - Experience in scripting and programming languages such as Go, Python, or Bash. - Hands-on experience with CI/CD tools such as Jenkins or ArgoCD. - Exceptional troubleshooting and problem-solving skills, with the ability to quickly diagnose and resolve technical issues. - Exceptional communication and collaboration skills, with the ability to work effectively in a cross-functional team environment. - Proven track record of driving process improvements and implementing best practices in DevOps methodologies. Preferred Qualifications list: - Experience with monitoring and logging tools such as Prometheus, Grafana, or OpenTelemetry. - Knowledge of security best practices and compliance requirements in cloud environments. - Experience with agile development methodologies and DevOps practices in a fast-paced, dynamic environment. Location: "Raleigh, NC; Austin, TX; Dallas, TX; Florida; Boston, MA" Technologies: "AWSAzureGCPKubernetesDockerTerraformJenkinsPythonBash" (but we can format as list or just string). We'll include as a short

            . Now produce HTML. We need to ensure we don't include any markdown fences. Let's craft:

            About the role

            About Reltio ...

            About The Team ...

            What Is