Senior Manager, QA Engineering
About the role
with. - What You'll Be Doing: list of duties. That's responsibilities. Use
- .
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.
- What You Bring: requirements/qualifications/skills. We need to split into Requirements, Qualifications, Skills maybe. The instruction: Use headings for sections like Requirements, Qualifications, Skills. We need to decide what content goes where. The posting has "What You Bring" bullet list. Also "Nice-to-haves". Also "Enterprise software / workflow automation background." etc.
We can treat "What You Bring" as Requirements (must-haves). Then "Nice-to-haves" as Skills? Or Qualifications? Let's map:
Requirements (must-have):
- 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 maybe could be same? But we can also put "Enterprise software / workflow automation background." as Qualification. However we need to avoid duplication. Perhaps we put Requirements as the list above, Qualifications as maybe "Enterprise software / workflow automation background." but that's already in list. Could split: Requirements: leadership experience etc. Qualifications: technical background etc. Skills: aligning teams etc.
But we need to avoid filler. Let's think: The instruction: "Prefer a few substantive sections over many thin ones." So maybe we combine Requirements and Qualifications into one section? But headings are prescribed; we can omit sections if no real content. We could have only Requirements and Skills sections, and maybe Benefits and Pay.
We have Benefits & Perks section with details. Pay section: compensation ranges.
Schedule: not mentioned explicitly; remote & flexible is under Benefits. No explicit schedule like full-time etc. So we should not create Schedule section because no specific content.
Thus sections: About the role, Responsibilities, Requirements, Benefits, Pay.
We could also include Qualifications if we have distinct content. Let's see if we can extract qualifications: maybe "Ability and/or willingness to use our product." is more of a skill. "Proven track record leading QA..." is experience requirement. "Ability to define and implement end-to-end QA strategy..." is skill. "Comfort staying connected to hands-on QA execution while leading strategically." is skill. "Experience leveling up QA for complex technical products..." is experience/skill. "Skill aligning engineering, product, UX, documentation, and field teams around shared quality goals." is skill. "Enterprise software / workflow automation background." is qualification.
Thus we could have Requirements: leadership experience, track record, ability to define strategy, etc. Qualifications: enterprise software background. Skills: aligning teams, hands-on QA, etc. But that seems thin.
Better to have Requirements (must-haves) and Skills (nice-to-haves). But we also have Nice-to-haves list: deep understanding of Kubernetes, cloud, microservices, etc.; hands-on experience with Playwright, TestRail, CI/CD; chaos engineering; proven ability to drive cultural change in QA.
Thus we can have:
- Requirements: the "What You Bring" list (must-haves).
- Skills: the "Nice-to-haves" list.
Qualifications maybe not needed.
Thus sections: About the role, Responsibilities, Requirements, Skills, Benefits, Pay.
We must not include Schedule.
Now we need to format.
We need to use
for each section heading. Inside sections: use
for prose,
- for lists.
We must preserve all substantive information, not invent or summarize away detail. So we need to include all details from the posting.
Let's extract each piece.
About the role paragraph: we have the paragraph as above. Ensure we keep all details: "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'll put that in
. Responsibilities: list as above. Requirements: list of must-haves: - 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 need to keep punctuation exactly? We can keep as is. Skills (nice-to-haves): - 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 & Perks: we need to capture all details. 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 to our careers site, employees, or any other Camunda contact unless we have specifically engaged your firm for that search. Camunda will not pay fees related to unsolicited resumes." We need to remove boilerplate: cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. So we must remove EEO statement, scam warning, note for agencies, etc. Also remove "AI in our hiring process..." maybe that's not boilerplate? It's about hiring process but could be considered boilerplate? The instruction says remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. The AI hiring process note might be considered part of hiring process but not explicitly listed; however it's a statement about AI tools used in hiring. Might be considered boilerplate? Not sure. Safer to keep it? The instruction says remove application instructions. The AI hiring process note is not an instruction to apply, but it's a note about process. Might be okay to keep. However the EEO and scam warning definitely should be removed. Thus Benefits & Perks section should include the benefits details before the EEO etc. So we need to cut off at "Professional Growth: Up to $/€/£1,000 per year for self-driven learning: courses, certifications, books, you decide!" and maybe stop before the AI hiring process line? The AI hiring process line is after that. It's not a benefit; it's about hiring process. Could be considered not a benefit. So we should exclude it. Also exclude the "Everyone is welcome at Camunda..." EEO line. So we stop before that. Thus Benefits content: - 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 off
- for lists.
We must preserve all substantive information, not invent or summarize away detail. So we need to include all details from the posting.
Let's extract each piece.
About the role paragraph: we have the paragraph as above. Ensure we keep all details: "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'll put that in