Senior Site Reliability 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. We must not repeat job title. Must not include Job ID etc. Must not include boilerplate like EEO, scam warning, etc. Must preserve all substantive info. We need to parse the posting. Content: - Intro paragraph about Camunda (company description). Should we include? It's not part of sections; we can include as a

before sections? The instruction: "Output ONLY the HTML fragment — no /, no markdown code fences." We can include any content as needed, but we must follow rules: use

for section headings,

• for any list of duties/requirements/benefits,

  for prose. Do NOT repeat job title as heading. Do NOT put Job ID / requisition numbers as headings — fold minor metadata into a short

  or drop it. We need to preserve all substantive information. So we need to include company description? It's substantive but not part of sections. Could be a

  before sections. We need sections: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We need to see what content maps. About the role: The posting has "About The Role" paragraph: "We're looking for a Senior Site Reliability Engineer who's passionate about building reliable, scalable infrastructure that helps developers ship better software faster. You'll design and maintain our Kubernetes-based multi-cloud platform, improve our monitoring and observability tools, and collaborate with product and engineering teams to solve real problems in real time. This is a role where you'll own the systems that power Camunda, drive automation that raises the bar for everyone, and mentor others who want to do the same. If you thrive on building things that work well and don't break when they shouldn't, we'd love to talk." That's about the role. Responsibilities: The "What You’ll Be Doing" bullet list. We need to convert each bullet into

• inside
  . Responsibilities content: - Design and maintain our infrastructure – You'll evolve our Kubernetes-based, multi-cloud platform architecture, ensuring it's available, scalable, and fault-tolerant. You'll establish configuration best practices and network services that our teams rely on. - Build observability that matters – Implement and improve monitoring and alerting tools that give both SREs and developers real visibility into system health and performance. Make it easy for teams to understand what's happening across our stack. - Own your systems end-to-end – You'll adopt a "you build it, you run it" mentality, which means participating in on-call rotations and being the go-to person when things need quick fixes. You'll create runbooks and automation that turn complex problems into manageable processes. - Ship features and improvements with product teams – Work cross-functionally with product engineering, product management, and support to define and deliver features that move the needle. Bring your expertise to the table early and often. - Push automation to the next level – Identify repetitive work and automate it away. Share what you learn with your teammates so everyone gets better at their craft. We measure progress by the quality of our systems, not hours worked. - Be the expert others learn from – Help less experienced engineers tackle complex infrastructure challenges. Break down technical problems into clear steps and support others in growing their skills. We'll put these as list items. Requirements: The "What You Bring" Must Haves list. We need to decide if we treat Must Haves as Requirements. Could also have Qualifications separate. The instruction: Use sections for Requirements, Qualifications, Skills. We need to decide mapping. We have Must Haves (deep hands-on experience with Kubernetes, IaC expertise, monitoring and observability, strong 3rd-level support and incident response skills, passion for automation, responsible use of AI tools). Those could be Requirements. Nice-to-haves: Experience with major cloud providers, ArgoCD or GitOps workflows, proficiency in Python, Go, or similar languages, Experience with SLOs and alerting frameworks. Those could be Qualifications or Skills. We could put Must Haves under Requirements, Nice-to-haves under Qualifications, and maybe Skills under a separate section if we have specific skills list (like Kubernetes, Terraform, Prometheus, Grafana, Python, Go, etc). But we might combine. We need to avoid thin sections. Let's see if we have enough content for each. We could do: - About the role (section) - Responsibilities (section) - Requirements (section) = Must Haves - Qualifications (section) = Nice-to-haves - Skills (section) = maybe list specific technologies: Kubernetes, Terraform, Prometheus, Grafana, Python/Go, ArgoCD, AWS EKS, GKE, etc. But we might be duplicating. Better: Use Requirements for Must Haves, Qualifications for Nice-to-haves, and Skills maybe not needed if we already covered. But we need to include a section only when posting has real specific content for it. If we don't have distinct Skills beyond those already listed, we could omit Skills section. Benefits: The "Benefits & Perks" section with details. Pay: The "Compensation" section with salary ranges. Schedule: Not mentioned explicitly; maybe remote/flexible work schedule? There's "Remote & Flexible: Work from anywhere with the setup that suits you, home office budget, co-working space support, and flexible time off to recharge when you need it." That could be considered Schedule (flexible time off). But the instruction: never create Pay/Schedule/Benefits sections unless the posting actually states them. The posting does mention flexible time off, remote work, etc. So we could include Schedule section with that info. But we also have Benefits section covering remote & flexible, health & wellbeing, financial security, professional growth, etc. So we could combine remote/flexible into Benefits. However Schedule could be separate if we want to highlight flexible time off. But we might avoid duplication. We need to decide: include Benefits section with all perks; include Pay section with salary ranges; maybe omit Schedule because flexible time off is part of Benefits. The instruction: prefer a few substantive sections over many thin ones. So we can combine remote/flexible into Benefits. Thus sections: About the role, Responsibilities, Requirements, Qualifications, Benefits, Pay. We need to ensure we don't include fluff like "commensurate with experience". Not present. Now we need to format. We'll start with a

  for company intro? The intro paragraph about Camunda is substantive. We'll include as a

  before sections. Then

  About the role

  ...

  Then

  Responsibilities

  • ...
  ...
  Then

  Requirements

  • ...
  ...
  Then

  Qualifications

  • ...
  ...
  Then

  Benefits

  • ...
  ...
  (list each benefit bullet) Then

  Pay

  ...

  (salary ranges) We must not include any boilerplate like EEO, scam warning, etc. So we need to cut those out. Now let's extract precise text. Company intro paragraph: "Camunda is the enterprise platform for agentic orchestration, enabling organizations to coordinate AI agents, people, and systems across complex, end-to-end business processes. With built-in governance, auditability, and human oversight, Camunda gives enterprises the control they need to move AI from pilots to production — safely and at scale. Trusted by over 700 organizations worldwide, including 9 of top 10 US banks, Camunda helps enterprises boost operational efficiency, accelerate time-to-value, and deliver better customer experiences. Fully remote and global, we are in the middle of something bigger: transforming into an AI-first organisation, built on our own platform. We use Agentic AI to automate, orchestrate intelligent processes, and elevate human contribution across every team. Named GP Bullhound’s Top 100 Next Unicorn list, 2025 Great Place to Work certified. Visionary in 2025 Gartner® Magic Quadrant™ for Business Orchestration and Automation Technologies. ranked 3rd in Flexa's 2026 Most Flexible Companies, We’re growing fast and looking for top talent to join our team. If you want meaningful work, visible impact and put something genuinely rare on your CV, keep reading." We need to keep all that. Might be long but okay. Now About the role paragraph: "We're looking for a Senior Site Reliability Engineer who's passionate about building reliable, scalable infrastructure that helps developers ship better software faster. You'll design and maintain our Kubernetes-based multi-cloud platform, improve our monitoring and observability tools, and collaborate with product and engineering teams to solve real problems in real time. This is a role where you'll own the systems that power Camunda, drive automation that raises the bar for everyone, and mentor others who want to do the same. If you thrive on building things that work well and don't break when they shouldn't, we'd love to talk." Now Responsibilities bullets: we need to copy each bullet exactly as in posting. Let's list them: 1. Design and maintain our infrastructure – You'll evolve our Kubernetes-based, multi-cloud platform architecture, ensuring it's available, scalable, and fault-tolerant. You'll establish configuration best practices and network services that our teams rely on. 2. Build observability that matters – Implement and improve monitoring and alerting tools that give both SREs and developers real visibility into system health and performance. Make it easy for teams to understand what's happening across our stack. 3. Own your systems end-to-end – You'll adopt a "you build it, you run it" mentality, which means participating in on-call rotations and being the go-to person when things need quick fixes. You'll create runbooks and automation that turn complex problems into manageable processes. 4. Ship features and improvements with product teams – Work cross-functionally with product engineering, product management, and support to define and deliver features that move the needle. Bring your expertise to the table early and often. 5. Push automation to the next level – Identify repetitive work and automate it away. Share what you learn with your teammates so everyone gets better at their craft. We measure progress by the quality of our systems, not hours worked. 6. Be the expert others learn from – Help less experienced engineers tackle complex infrastructure challenges. Break down technical problems into clear steps and support others in growing their skills. Now Requirements (Must Haves): - Deep hands-on experience with Kubernetes – You've built, deployed, and maintained Kubernetes clusters in production environments. You understand how to manage workloads, networking, and storage at scale. - Infrastructure as code expertise – You're fluent in tools like Terraform (or similar IaC tools) and know how to version, test, and safely deploy infrastructure changes. - Demonstrated experience in monitoring and observability – You've worked with tools like Prometheus, Grafana, or similar platforms to instrument systems and alert on what matters. - Strong 3rd-level support and incident response skills – You've responded to production incidents, diagnosed complex issues, and communicated clearly with stakeholders under pressure. You understand root cause analysis and how to prevent issues from happening again. - A passion for automation and raising the quality bar – You see manual work as a problem to be solved. You care deeply about building systems that are reliable, maintainable, and easy to understand. - Responsible use of AI tools – You leverage AI for research, code review, documentation, test generation, and automation to improve your effectiveness. You know how to validate AI outputs against requirements, never share confidential or personal data with AI systems without authorization, and always retain human accountability for decisions and deliverables. Now Qualifications (Nice-to-haves): - Experience with major cloud providers – You've worked with AWS (EKS), Google Cloud Platform (GKE