Senior Manager, QA Engineering

We need to output HTML fragment with sections: headings

for sections: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. Only include sections with real content. We need to parse the posting. Job title: Senior Manager, QA Engineering (but we don't repeat as heading). We need sections: - About the role: The paragraph after "About The Role" describing role: "Camunda is hiring a Senior Manager, QA Engineering to lead the end-to-end QA strategy for Camunda 8 — elevating quality governance with rigorous quality gates, outcome-driven automation, and strategic reporting that guides roadmap and release decisions. They will manage two teams (functional and reliability) comprising 12 ICs, a principal engineer, and a manager; evolve the structure for scale; and ensure comprehensive coverage across business users, developers, and admins/operators in Kubernetes, cloud, and bare-metal environments. This first-of-its-kind role reports directly to the VP of Engineering." We can put that as

. - Responsibilities: The bullet list under "What You'll Be Doing". Items: Own and drive the end-to-end QA strategy for Camunda 8, establishing quality gates and cross-team accountability. Partner with principal engineering to mature reliability, performance, and resilience testing. Guide automation strategy and QA processes to enable teams to deliver high-quality outcomes efficiently. Develop actionable quality metrics, dashboards, and reports that inform leadership and roadmap decisions. Lead and scale QA teams — managers, principal engineers, and ICs — evolving structure for maximum impact. Influence cross-functional stakeholders (engineering, product, UX, documentation, field) to embed quality across the organization. We need

• for each. - Requirements: The "What You Bring" bullet list: Ability and/or willingness to use our product. Proven track record leading QA in engineering organizations of 100–500 people, with measurable impact. Ability to define and implement end-to-end QA strategy, quality gates, and data-informed decision-making across multiple teams. Comfort staying connected to hands-on QA execution while leading strategically. Experience leveling up QA for complex technical products, including developer/admin persona coverage and high-load, performance, resilience testing. Skill aligning engineering, product, UX, documentation, and field teams around shared quality goals. Enterprise software / workflow automation background. We can treat as Requirements. - Qualifications: maybe "Nice-to-haves" could be Qualifications? Actually Qualifications often include required and nice-to-have. But we have separate sections: Requirements (must-haves) and Qualifications (maybe nice-to-haves). The instruction: Use headings for sections like About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. So we need to map content. We have "Nice-to-haves" list: Deep understanding of Kubernetes, cloud, microservices, and related operational challenges. Hands-on experience with Playwright, TestRail, or CI/CD-integrated testing environments. Chaos engineering or advanced reliability/performance benchmarking experience. Proven ability to drive cultural change in QA. We could put those under Qualifications. Skills: maybe we could extract skills from requirements? But we already have Requirements and Qualifications; maybe Skills could be overlapping. However we should only include sections with real specific content. We have content for Skills? Not explicitly listed as a separate list. Could combine some items into Skills but we already have Requirements and Qualifications. Might be better to not include Skills if no distinct list. Pay: we have compensation details with salary ranges per region. That's concrete. So include Pay section with that info. Benefits: we have Benefits & Perks section with details. Include Benefits. Schedule: Not mentioned; no schedule info. So omit Schedule. Also maybe include "About the role" heading. We must not repeat job title as heading. We must not include boilerplate like EEO, scam warning, etc. We must preserve all substantive information; do not invent or summarize away detail. We need to output only HTML fragment. Let's craft:

  About the role

  Camunda is hiring a Senior Manager, QA Engineering to lead the end-to-end QA strategy for Camunda 8 — elevating quality governance with rigorous quality gates, outcome-driven automation, and strategic reporting that guides roadmap and release decisions. They will manage two teams (functional and reliability) comprising 12 ICs, a principal engineer, and a manager; evolve the structure for scale; and ensure comprehensive coverage across business users, developers, and admins/operators in Kubernetes, cloud, and bare-metal environments. This first-of-its-kind role reports directly to the VP of Engineering.

  Responsibilities

  • Own and drive the end-to-end QA strategy for Camunda 8, establishing quality gates and cross-team accountability.
  • Partner with principal engineering to mature reliability, performance, and resilience testing.
  • Guide automation strategy and QA processes to enable teams to deliver high-quality outcomes efficiently.
  • Develop actionable quality metrics, dashboards, and reports that inform leadership and roadmap decisions.
  • Lead and scale QA teams — managers, principal engineers, and ICs — evolving structure for maximum impact.
  • Influence cross-functional stakeholders (engineering, product, UX, documentation, field) to embed quality across the organization.

  Requirements

  • Ability and/or willingness to use our product.
  • Proven track record leading QA in engineering organizations of 100–500 people, with measurable impact.
  • Ability to define and implement end-to-end QA strategy, quality gates, and data-informed decision-making across multiple teams.
  • Comfort staying connected to hands-on QA execution while leading strategically.
  • Experience leveling up QA for complex technical products, including developer/admin persona coverage and high-load, performance, resilience testing.
  • Skill aligning engineering, product, UX, documentation, and field teams around shared quality goals.
  • Enterprise software / workflow automation background.

  Qualifications

  • Deep understanding of Kubernetes, cloud, microservices, and related operational challenges.
  • Hands-on experience with Playwright, TestRail, or CI/CD-integrated testing environments.
  • Chaos engineering or advanced reliability/performance benchmarking experience.
  • Proven ability to drive cultural change in QA.

  Benefits

  We invest in your wellbeing, growth, and ability to connect, along with perks that support you no matter where you’re based. Our benefits are globally designed and locally delivered where applicable. 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. In Person Connection: We invest in meaningful face time through our Annual Kickoff (Vienna in 2025, Madrid in 2026!), team offsites, and Camundi Connection Budgets, including contributing to meetups while travelling, and local gatherings with fellow Camundi. Health & Wellbeing: Access locally tailored healthcare, Modern Health for global mental wellbeing, and our Live Well Lifestyle Spending Account (LSA), a flexible, global benefit that puts you in control of your whole life, not just work, from: staying active, to caring for family, exploring personal passions, meaningful experiences, and investing in your financial wellbeing. The Live Well program launches in 2026 and scales to €1,000 annually from 2027. Financial Security: Retirement and pension plans (often with company contributions), plus life and disability insurance where relevant. Professional Growth: Up to $/€/£1,000 per year for self-driven learning: courses, certifications, books, you decide! AI in our hiring process: Camunda may use AI tools to aid the screening of applications and during the interview process. You can learn more here ”Everyone is welcome at Camunda” — it’s a celebrated component of our culture. We strive to create an inclusive environment that empowers our people. At Camunda, we honour diverse cultures and backgrounds and are proud to be an equal opportunity employer. All qualified applicants will receive consideration without regard to gender, race, ethnicity, religion, belief, sexual orientation, age, disability or any other protected characteristics under applicable law.

  But we need to remove EEO boilerplate? The instruction: Remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. The Benefits section includes some EEO statements at the end; we should remove that. Also the line about AI in hiring process maybe okay? It's not boilerplate? It's a statement about AI in hiring process; might be considered part of benefits? It's not EEO. It's okay to keep. The EEO statement at end should be removed. Also the line about "Everyone is welcome at Camunda" is part of EEO? It's a cultural statement; maybe not EEO but could be considered boilerplate. Safer to remove the EEO paragraph entirely. Also remove the line about scam warning etc. Already not included. Thus Benefits section should contain only the benefits description, not the EEO. Let's extract benefits description before the EEO. From text: "Benefits & Perks We invest in your wellbeing, growth, and ability to connect, along with perks that support you no matter where you’re based. Our benefits are globally designed and locally delivered where applicable. 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.In Person Connection: We invest in meaningful face time through our Annual Kickoff (Vienna in 2025, Madrid in 2026!), team offsites, and Camundi Connection Budgets, including contributing to meetups while travelling,, and local gatherings with fellow Camundi.Health & Wellbeing: Access locally tailored healthcare, Modern Health for global mental wellbeing, and our Live Well Lifestyle Spending Account (LSA), a flexible, global benefit that puts you in control of your whole life, not just work, from: staying active, to caring for family, exploring personal passions, meaningful experiences, and investing in your financial wellbeing. The Live Well program launches in 2026 and scales to €1,000 annually from 2027.Financial Security: Retirement and pension plans (often with company contributions), plus life and disability insurance where relevant.Professional Growth: Up to $/€/£1,000 per year for self-driven learning: courses, certifications, books, you decide! AI in our hiring process: Camunda may use AI tools to aid the screening of applications and during the interview process. You can learn more here ”Everyone is welcome at Camunda” — it’s a celebrated component of our culture. We strive to create an inclusive environment that empowers our people. At Camunda, we honour diverse cultures and backgrounds and are proud to be an equal opportunity employer. All qualified applicants will receive consideration without regard to gender, race, ethnicity, religion, belief, sexual orientation, age, disability or any other protected characteristics under applicable law. We are looking forward to your application! Come join us and be part of Camunda’s incredible journey: Make an impact at a pivotal moment in our story! Please be aware that scammers may impersonate Camunda by reaching out about job opportunities. Camunda will only contact candidates from an email address ending in @camunda.com or @talent.camunda.com. We will never ask candidates for bank account details, checks, payment, or other sensitive financial information as part of our hiring process. If you receive a suspicious message, please do not respond, click any links, or share personal information. Note for recruiting and placement agencies: Camunda does not accept unsolicited agency resumes. Please do not forward resumes