Senior Manager, QA Engineering
for section headings. Use - for any list of duties/requirements/benefits. Use
for prose.
We need to preserve all substantive info, not invent or summarize away detail. So we need to include the paragraphs exactly? We can rephrase? The instruction: "Preserve ALL substantive information; do NOT invent or summarize away detail." Means we should keep the information, not omit details. We can keep the same sentences but maybe restructure into HTML. It's okay to keep same wording.
We need to avoid filler like "commensurate with experience". Not present.
We'll create sections:
About the role
... paragraph(s) ...
Then Responsibilities: Responsibilities
- ... each bullet ...
What You'll Be Doing bullet list: we have multiple sentences each starting with a verb. We'll turn each into - .
Then Requirements:
Requirements
- ... each bullet from "What You Bring" ...
Then Skills: maybe Nice-to-haves: Skills
- ... each nice-to-have bullet ...
Benefits: Benefits
- ... each benefit bullet ...
Pay: Pay
... compensation ranges ...
Schedule: Schedule
... remote & flexible details ...
We must not include sections with no content. All have content.
We need to ensure we don't include duplicated lines. The posting includes some repeated lines like "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." We'll include that once.
Also "In Person Connection: ..." etc.
We'll need to capture all benefit bullets.
Let's extract content.
About The Role paragraph:
"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 keep that as .
Responsibilities bullet list (What You'll Be Doing):
- 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 bullet list (What You Bring):
- 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.
Nice-to-haves (Skills):
- 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 each bullet.
From text:
"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."
Note there is a double comma after travelling, but we keep as is.
"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/equal-opportunity boilerplate. So we should remove that paragraph about equal opportunity. Also remove scam warning etc. Also remove "AI in our hiring process" maybe not boilerplate? It's substantive? It mentions AI tools usage. Might be considered substantive but could be considered boilerplate? The instruction: "Remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions." The AI hiring process line is not exactly EEO but could be considered a note about process. It's not explicitly listed to remove, but it's somewhat procedural. However it's not a benefit. It might be considered part of the posting but not a benefit. The instruction says to remove application instructions. This line is about AI in hiring process, maybe considered application instructions? It's about screening. Safer to remove it as it's not a benefit or core role info. Also the quote “Everyone is welcome at Camunda” is part of EEO. So we remove that.
Thus Benefits section should include the bullets: Remote & Flexible, In Person Connection, Health & Wellbeing, Financial Security, Professional Growth.
We need to format each as
- under
.
Pay section: compensation ranges.
We have:
"Compensation What We Have to Offer: We offer competitive, fair, and transparent compensation. Salary ranges are location-based, with Standard and Major markets (global tech hubs) reflecting local competition. The Annual Total Target Cash (base salary + 100% variable target, where applicable) shown below spans from the minimum in a Standard market to the maximum in a Major market. Final offers depend on skills, experience, and location, and we typically hire in the first half of the range to allow room for growth: United States: $175,600.00 to $283,100.00 United Kingdom: £110,200.00 to £181,300.00 Singapore: S$218,100.00 to S$327,100.00 Canada: C$186,400.00 to C$306,700.00 If you’re based elsewhere, you’ll be hired via Remote.com (our global employer partner), and your Talent Acquisition Partner will provide a personalized Total Rewards Calculator after your first interview. Equity: We also offer equity (where applicable) through our Virtual Stock Option Plan (VSOP)."
We need to keep all substantive info. So we can put that as a under Pay.
Schedule section: Remote & Flexible details already captured in Benefits. But schedule could be separate. However we already used Remote & Flexible as a benefit. The instruction: "Prefer a few substantive sections over many thin ones." Could combine remote flexible into Benefits. Schedule section may be redundant. Since we already have Remote & Flexible under Benefits, we might not need separate Schedule. But the instruction says include Schedule section only if posting actually states them. It does state remote/flexible work arrangement. Could be considered schedule. However we already used that content in Benefits. To avoid duplication, we could move it to Schedule and not duplicate in Benefits. But Benefits also includes other items like In Person Connection, Health & Wellbeing, etc. We could keep Remote & Flexible under Benefits as it's a benefit. The instruction says use
- for any list of duties/requirements/benefits. So Remote & Flexible is a benefit. So we keep it there. Then Schedule section may be omitted because we don't have separate schedule info beyond that. The posting does not mention specific schedule like core hours, etc. So we can omit Schedule section.
Thus sections: About the role, Responsibilities, Requirements, Skills (nice-to-haves), Benefits, Pay.
Check if any other sections like "Qualifications" maybe same as Requirements. We'll use Requirements.
Now produce HTML.
We must not include or . Just fragment.
Let's craft.
Be careful to escape any HTML special characters? The text includes ampersand (&) in "Enterprise software / workflow automation background." No issue. Also includes "–" (en dash) and "—" (em dash). Those are fine.
We need to ensure proper nesting.
Let's write:
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.
for prose. We need to preserve all substantive info, not invent or summarize away detail. So we need to include the paragraphs exactly? We can rephrase? The instruction: "Preserve ALL substantive information; do NOT invent or summarize away detail." Means we should keep the information, not omit details. We can keep the same sentences but maybe restructure into HTML. It's okay to keep same wording. We need to avoid filler like "commensurate with experience". Not present. We'll create sections:
About the role
... paragraph(s) ...
Then Responsibilities:Responsibilities
- ... each bullet ...
Requirements
- ... each bullet from "What You Bring" ...
Skills
- ... each nice-to-have bullet ...
Benefits
- ... each benefit bullet ...
Pay
... compensation ranges ...
Schedule:Schedule
... remote & flexible details ...
We must not include sections with no content. All have content. We need to ensure we don't include duplicated lines. The posting includes some repeated lines like "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." We'll include that once. Also "In Person Connection: ..." etc. We'll need to capture all benefit bullets. Let's extract content. About The Role paragraph: "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 keep that as. Responsibilities bullet list (What You'll Be Doing): - 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 bullet list (What You Bring): - 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. Nice-to-haves (Skills): - 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 each bullet. From text: "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." Note there is a double comma after travelling, but we keep as is. "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/equal-opportunity boilerplate. So we should remove that paragraph about equal opportunity. Also remove scam warning etc. Also remove "AI in our hiring process" maybe not boilerplate? It's substantive? It mentions AI tools usage. Might be considered substantive but could be considered boilerplate? The instruction: "Remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions." The AI hiring process line is not exactly EEO but could be considered a note about process. It's not explicitly listed to remove, but it's somewhat procedural. However it's not a benefit. It might be considered part of the posting but not a benefit. The instruction says to remove application instructions. This line is about AI in hiring process, maybe considered application instructions? It's about screening. Safer to remove it as it's not a benefit or core role info. Also the quote “Everyone is welcome at Camunda” is part of EEO. So we remove that. Thus Benefits section should include the bullets: Remote & Flexible, In Person Connection, Health & Wellbeing, Financial Security, Professional Growth. We need to format each as
- .
Pay section: compensation ranges.
We have:
"Compensation What We Have to Offer: We offer competitive, fair, and transparent compensation. Salary ranges are location-based, with Standard and Major markets (global tech hubs) reflecting local competition. The Annual Total Target Cash (base salary + 100% variable target, where applicable) shown below spans from the minimum in a Standard market to the maximum in a Major market. Final offers depend on skills, experience, and location, and we typically hire in the first half of the range to allow room for growth: United States: $175,600.00 to $283,100.00 United Kingdom: £110,200.00 to £181,300.00 Singapore: S$218,100.00 to S$327,100.00 Canada: C$186,400.00 to C$306,700.00 If you’re based elsewhere, you’ll be hired via Remote.com (our global employer partner), and your Talent Acquisition Partner will provide a personalized Total Rewards Calculator after your first interview. Equity: We also offer equity (where applicable) through our Virtual Stock Option Plan (VSOP)."
We need to keep all substantive info. So we can put that as a
- for any list of duties/requirements/benefits. So Remote & Flexible is a benefit. So we keep it there. Then Schedule section may be omitted because we don't have separate schedule info beyond that. The posting does not mention specific schedule like core hours, etc. So we can omit Schedule section.
Thus sections: About the role, Responsibilities, Requirements, Skills (nice-to-haves), Benefits, Pay.
Check if any other sections like "Qualifications" maybe same as Requirements. We'll use Requirements.
Now produce HTML.
We must not include or . Just fragment.
Let's craft.
Be careful to escape any HTML special characters? The text includes ampersand (&) in "Enterprise software / workflow automation background." No issue. Also includes "–" (en dash) and "—" (em dash). Those are fine.
We need to ensure proper nesting.
Let's write:
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.
under Pay. Schedule section: Remote & Flexible details already captured in Benefits. But schedule could be separate. However we already used Remote & Flexible as a benefit. The instruction: "Prefer a few substantive sections over many thin ones." Could combine remote flexible into Benefits. Schedule section may be redundant. Since we already have Remote & Flexible under Benefits, we might not need separate Schedule. But the instruction says include Schedule section only if posting actually states them. It does state remote/flexible work arrangement. Could be considered schedule. However we already used that content in Benefits. To avoid duplication, we could move it to Schedule and not duplicate in Benefits. But Benefits also includes other items like In Person Connection, Health & Wellbeing, etc. We could keep Remote & Flexible under Benefits as it's a benefit. The instruction says use