Technical Program Manager, Software Operations
for section headings: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We must include sections only when posting has real specific content. We have content for responsibilities (What You'll Do), basic qualifications (What You'll Need), preferred qualifications, benefits, pay, schedule (hybrid, 3 days a week). Also maybe "About the role" could be the introductory paragraph. We must not repeat job title as heading. No Job ID etc. Remove boilerplate like EEO, visa sponsorship, etc. Also remove application instructions, legal, etc.
We need to preserve all substantive information. So we need to include the description about Sonos mission, team, role description, responsibilities list, qualifications list, preferred qualifications list, benefits list, pay range, schedule.
We need to format using headings and - for lists,
for prose.
We must not create sections with filler like "commensurate with experience". We have actual pay range and schedule.
We must not include sections like Skills if not present; but we have qualifications split into basic and preferred; maybe combine as Requirements? The instruction says use headings like Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We can decide to use "Responsibilities" for What You'll Do, "Requirements" for Basic Qualifications, "Preferred Qualifications" maybe as "Qualifications"? But we have both basic and preferred; we could put basic under Requirements and preferred under Qualifications (or Skills). However we have a separate "Skills" heading; we could put preferred qualifications under Skills. But we need to follow instruction: Use headings for those categories if content exists. We have content for responsibilities, basic qualifications, preferred qualifications, benefits, pay, schedule. Also we have an introductory paragraph about Sonos mission and team; could be "About the role". So sections: About the role, Responsibilities, Requirements (basic qualifications), Qualifications (preferred), Benefits, Pay, Schedule.
We must not include sections with placeholder text. All good.
Now we need to strip boilerplate: remove visa sponsorship, EEO, equal opportunity, legal, accommodation request, notice to US job applicants, etc. Also remove "Inclusion: Research shows..." maybe keep? It's about encouraging applicants; could be considered boilerplate but it's substantive? It's a generic statement; maybe remove as it's not specific to role. Safer to remove. Also remove "Your profile will be reviewed..." etc. Also remove "Note: No amount of pay..." etc. Also remove "We also offer a comprehensive benefits program..." but we need to keep benefits details. The paragraph after that lists benefits; we keep that. The earlier sentence about benefits program is generic; we can keep as part of benefits intro? Might be okay. But we need to preserve all substantive information; the generic sentence about benefits program is not specific but still part of benefits description; we can keep it as prose in Benefits section.
We must also remove duplicated lines.
Now craft HTML.
Structure:
About the role
At Sonos we want to create the ultimate listening experience for our customers and know that it starts by listening to each other. As part of the Sonos team, you’ll collaborate with people of all styles, skill sets, and backgrounds to realize our vision while fostering a community where everyone feels included and empowered to do the best work of their lives. The Software Operations team designs, builds, and continuously improves the operating systems that help Sonos software teams plan, develop, measure, and deliver great products. As a Technical Program Manager on this team, you won't be assigned to a single program to run meetings and track status — instead, you'll work across the software development organization to improve how engineering itself works. You'll help build an AI-enabled software development lifecycle, improve developer workflows and engineering metrics, automate repetitive operational work, and create scalable processes that allow teams to operate with greater autonomy, predictability, and transparency. This is a hands-on role for someone who is passionate about understanding how software organizations work and making them meaningfully better. This position is considered hybrid, allowing for a combination of remote work and in-office collaboration. Qualified applicants must live within commuting distance of our Boston office location and should expect to be in office 3 days a week.
Responsibilities
- Design, build, and continuously improve the processes, workflows, tools, and operating mechanisms used across the Sonos software development organization.
- Help build an AI-enabled software development lifecycle, using AI agents, automation, APIs, and deterministic workflows to reduce manual work and make engineering processes easier to use.
- Develop engineering metrics and feedback systems that help teams understand developer productivity, quality, flow, predictability, and organizational health.
- Help define and operate the planning and execution mechanisms that allow multiple autonomous software teams and programs to work effectively within a shared development model.
- Work directly with engineering teams to identify friction and bottlenecks, understand root causes, implement improvements, and measure outcomes.
- Turn complex or manual organizational processes into scalable systems that teams can use without requiring constant coordination or facilitation.
- Use data to evaluate the effectiveness of operational changes and communicate findings to technical and non-technical stakeholders.
- Contribute to the roadmapping, work tracking, and capacity planning systems that enable better investment and execution decisions.
Requirements
- 4-7 years of experience in software engineering, software operations, developer productivity, technical program management, product operations, platform engineering, or a similar role focused on improving how software teams work.
- Experience designing and improving processes, workflows, tools, or operating systems — not just administering established ones.
- Hands-on experience with software development tools such as Jira, Confluence, GitHub, CI/CD platforms, cloud services, or similar engineering systems.
- Practical experience using AI tools in your work and an interest in applying AI and automation to engineering workflows.
- Experience using data and metrics to understand problems, evaluate improvements, and drive decisions.
- Ability to work effectively with engineers and technical leaders while communicating clearly across technical and non-technical audiences.
- Qualified applicants must be able to work from the office 3 days per week.
Qualifications
- Experience building workflow automation, API integrations, scripts, AI agents, or other internal productivity tools.
- Familiarity with Python, SQL, JavaScript, or another scripting or programming language.
- Experience with AI-assisted software development tools such as Claude Code, GitHub Copilot, Cursor, or similar platforms.
- Familiarity with engineering effectiveness frameworks and metrics such as DORA, SPACE, flow metrics, developer experience metrics, or software quality measures.
- Experience with Agile software development, CI/CD, DevSecOps, and modern software delivery practices.
- Experience administering or configuring Jira, Jira Product Discovery, Confluence, GitHub, Jenkins, AWS, or similar engineering platforms.
- Experience working across a large or complex software engineering organization.
- Experience with consumer software, embedded software, or connected-device development.
Benefits
We also offer a comprehensive benefits program with choice and flexibility in mind to help support the health, wealth, and overall well-being of our employees. Regular full time employees in the US are eligible for benefits on day one, including:
- Medical, Dental, and Vision Insurance
- A 401(k) plan with company matching and immediate vesting
- An Open Time Off policy (OTO) so you have maximum opportunity to disconnect and recharge, with no tenure-based vacation accruals required
- 80 hours of sick time upon hire, refreshed annually
- Up to 12 paid holidays per calendar year
- Sonos offers a generous paid leave program for new parents or to care for a family member with a serious health condition, as well as short- and long-term disability for your own medical condition
- Company-paid Disability, Life, and AD&D Insurance
- Voluntary benefits, including Voluntary Life, AD&D, Accident, and Pet Insurance
- Mental health benefits to support your holistic well-being
- A generous employee discount program & Sonos Radio HD - on us!
Pay
The base pay range for this role based off geographic location is: $118,000 and $146,900. The specific pay offered will depend on the candidate’s geographic location, as well as qualifications and experience. We apply geographic pay differentials based on the cost of labor in the market. Employees in high-cost locations may be compensated at the upper end of the range, while those in medium or low cost markets may be compensated at the lower end of the range. Your recruiter can provide more details about the specific salary range for your location during the hiring process. Please note that compensation details listed in US job postings reflect the base salary only, and do not include bonus, equity, or benefits.
Schedule
This position is considered hybrid, allowing for a combination of remote work and in-office collaboration. Qualified applicants must live within commuting distance of our Boston office location and should expect to be in office 3 days a week.
We need to ensure no duplicate content: The schedule appears also in About the role; we have repeated. Might be okay but we should avoid duplication. The About the role already mentions hybrid and 3 days a week. The Schedule section repeats same. Could we keep only one? The instruction: Preserve ALL substantive information; do NOT invent or summarize away detail. If we remove the schedule section, we lose the explicit statement about schedule? But it's already in About the role. However the schedule section is redundant; we could keep it but it's duplicate. The instruction says remove duplicated lines. So we should avoid duplicating the same sentence. We could keep schedule section but rephrase? But that would be inventing? Better to keep only one mention. Since About the role already includes schedule info, we can omit Schedule section. However the instruction says include a section ONLY when the posting has real, specific content for it — never emit a heading followed by filler/placeholder text. The schedule content exists; we could keep it but we need to avoid duplication. We could keep About the role without schedule details, and put schedule in Schedule section. But About the role currently includes schedule; we could move that detail to Schedule section and keep About the role more generic. Let's adjust: In About the role, we can keep the description but remove the hybrid/schedule sentence, and put that in Schedule section. That avoids duplication.
Thus About the role paragraph: remove "This position is considered hybrid, allowing for a combination of remote work and in-office collaboration. Qualified applicants must live within commuting distance of our Boston office location and should expect to be in office 3 days a week." We'll keep rest.
Then Schedule section will contain that sentence.
Now check for any other duplicated content: Benefits paragraph includes generic sentence about benefits program; that's fine.
Now ensure we removed boilerplate: visa sponsorship, inclusion encouragement, profile review, note about pay, notice to US job applicants, EEO, accommodation request, etc.
We kept the sentence about base pay range and note that compensation details reflect base salary only; that's substantive.
We kept the sentence about benefits program.
Now produce final HTML.
Be careful to escape any special characters like & in benefits list: we used & for "Sonos Radio HD - on us!" Actually we need to keep the ampersand; we should encode as &. Already did.
Check for any other ampersand: "Medical, Dental, and Vision Insurance" fine.
- for lists,
for prose. We must not create sections with filler like "commensurate with experience". We have actual pay range and schedule. We must not include sections like Skills if not present; but we have qualifications split into basic and preferred; maybe combine as Requirements? The instruction says use headings like Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We can decide to use "Responsibilities" for What You'll Do, "Requirements" for Basic Qualifications, "Preferred Qualifications" maybe as "Qualifications"? But we have both basic and preferred; we could put basic under Requirements and preferred under Qualifications (or Skills). However we have a separate "Skills" heading; we could put preferred qualifications under Skills. But we need to follow instruction: Use headings for those categories if content exists. We have content for responsibilities, basic qualifications, preferred qualifications, benefits, pay, schedule. Also we have an introductory paragraph about Sonos mission and team; could be "About the role". So sections: About the role, Responsibilities, Requirements (basic qualifications), Qualifications (preferred), Benefits, Pay, Schedule. We must not include sections with placeholder text. All good. Now we need to strip boilerplate: remove visa sponsorship, EEO, equal opportunity, legal, accommodation request, notice to US job applicants, etc. Also remove "Inclusion: Research shows..." maybe keep? It's about encouraging applicants; could be considered boilerplate but it's substantive? It's a generic statement; maybe remove as it's not specific to role. Safer to remove. Also remove "Your profile will be reviewed..." etc. Also remove "Note: No amount of pay..." etc. Also remove "We also offer a comprehensive benefits program..." but we need to keep benefits details. The paragraph after that lists benefits; we keep that. The earlier sentence about benefits program is generic; we can keep as part of benefits intro? Might be okay. But we need to preserve all substantive information; the generic sentence about benefits program is not specific but still part of benefits description; we can keep it as prose in Benefits section. We must also remove duplicated lines. Now craft HTML. Structure:
About the role
At Sonos we want to create the ultimate listening experience for our customers and know that it starts by listening to each other. As part of the Sonos team, you’ll collaborate with people of all styles, skill sets, and backgrounds to realize our vision while fostering a community where everyone feels included and empowered to do the best work of their lives. The Software Operations team designs, builds, and continuously improves the operating systems that help Sonos software teams plan, develop, measure, and deliver great products. As a Technical Program Manager on this team, you won't be assigned to a single program to run meetings and track status — instead, you'll work across the software development organization to improve how engineering itself works. You'll help build an AI-enabled software development lifecycle, improve developer workflows and engineering metrics, automate repetitive operational work, and create scalable processes that allow teams to operate with greater autonomy, predictability, and transparency. This is a hands-on role for someone who is passionate about understanding how software organizations work and making them meaningfully better. This position is considered hybrid, allowing for a combination of remote work and in-office collaboration. Qualified applicants must live within commuting distance of our Boston office location and should expect to be in office 3 days a week.
Responsibilities
- Design, build, and continuously improve the processes, workflows, tools, and operating mechanisms used across the Sonos software development organization.
- Help build an AI-enabled software development lifecycle, using AI agents, automation, APIs, and deterministic workflows to reduce manual work and make engineering processes easier to use.
- Develop engineering metrics and feedback systems that help teams understand developer productivity, quality, flow, predictability, and organizational health.
- Help define and operate the planning and execution mechanisms that allow multiple autonomous software teams and programs to work effectively within a shared development model.
- Work directly with engineering teams to identify friction and bottlenecks, understand root causes, implement improvements, and measure outcomes.
- Turn complex or manual organizational processes into scalable systems that teams can use without requiring constant coordination or facilitation.
- Use data to evaluate the effectiveness of operational changes and communicate findings to technical and non-technical stakeholders.
- Contribute to the roadmapping, work tracking, and capacity planning systems that enable better investment and execution decisions.
Requirements
- 4-7 years of experience in software engineering, software operations, developer productivity, technical program management, product operations, platform engineering, or a similar role focused on improving how software teams work.
- Experience designing and improving processes, workflows, tools, or operating systems — not just administering established ones.
- Hands-on experience with software development tools such as Jira, Confluence, GitHub, CI/CD platforms, cloud services, or similar engineering systems.
- Practical experience using AI tools in your work and an interest in applying AI and automation to engineering workflows.
- Experience using data and metrics to understand problems, evaluate improvements, and drive decisions.
- Ability to work effectively with engineers and technical leaders while communicating clearly across technical and non-technical audiences.
- Qualified applicants must be able to work from the office 3 days per week.
Qualifications
- Experience building workflow automation, API integrations, scripts, AI agents, or other internal productivity tools.
- Familiarity with Python, SQL, JavaScript, or another scripting or programming language.
- Experience with AI-assisted software development tools such as Claude Code, GitHub Copilot, Cursor, or similar platforms.
- Familiarity with engineering effectiveness frameworks and metrics such as DORA, SPACE, flow metrics, developer experience metrics, or software quality measures.
- Experience with Agile software development, CI/CD, DevSecOps, and modern software delivery practices.
- Experience administering or configuring Jira, Jira Product Discovery, Confluence, GitHub, Jenkins, AWS, or similar engineering platforms.
- Experience working across a large or complex software engineering organization.
- Experience with consumer software, embedded software, or connected-device development.
Benefits
We also offer a comprehensive benefits program with choice and flexibility in mind to help support the health, wealth, and overall well-being of our employees. Regular full time employees in the US are eligible for benefits on day one, including:
- Medical, Dental, and Vision Insurance
- A 401(k) plan with company matching and immediate vesting
- An Open Time Off policy (OTO) so you have maximum opportunity to disconnect and recharge, with no tenure-based vacation accruals required
- 80 hours of sick time upon hire, refreshed annually
- Up to 12 paid holidays per calendar year
- Sonos offers a generous paid leave program for new parents or to care for a family member with a serious health condition, as well as short- and long-term disability for your own medical condition
- Company-paid Disability, Life, and AD&D Insurance
- Voluntary benefits, including Voluntary Life, AD&D, Accident, and Pet Insurance
- Mental health benefits to support your holistic well-being
- A generous employee discount program & Sonos Radio HD - on us!
Pay
The base pay range for this role based off geographic location is: $118,000 and $146,900. The specific pay offered will depend on the candidate’s geographic location, as well as qualifications and experience. We apply geographic pay differentials based on the cost of labor in the market. Employees in high-cost locations may be compensated at the upper end of the range, while those in medium or low cost markets may be compensated at the lower end of the range. Your recruiter can provide more details about the specific salary range for your location during the hiring process. Please note that compensation details listed in US job postings reflect the base salary only, and do not include bonus, equity, or benefits.
Schedule
This position is considered hybrid, allowing for a combination of remote work and in-office collaboration. Qualified applicants must live within commuting distance of our Boston office location and should expect to be in office 3 days a week.
We need to ensure no duplicate content: The schedule appears also in About the role; we have repeated. Might be okay but we should avoid duplication. The About the role already mentions hybrid and 3 days a week. The Schedule section repeats same. Could we keep only one? The instruction: Preserve ALL substantive information; do NOT invent or summarize away detail. If we remove the schedule section, we lose the explicit statement about schedule? But it's already in About the role. However the schedule section is redundant; we could keep it but it's duplicate. The instruction says remove duplicated lines. So we should avoid duplicating the same sentence. We could keep schedule section but rephrase? But that would be inventing? Better to keep only one mention. Since About the role already includes schedule info, we can omit Schedule section. However the instruction says include a section ONLY when the posting has real, specific content for it — never emit a heading followed by filler/placeholder text. The schedule content exists; we could keep it but we need to avoid duplication. We could keep About the role without schedule details, and put schedule in Schedule section. But About the role currently includes schedule; we could move that detail to Schedule section and keep About the role more generic. Let's adjust: In About the role, we can keep the description but remove the hybrid/schedule sentence, and put that in Schedule section. That avoids duplication. Thus About the role paragraph: remove "This position is considered hybrid, allowing for a combination of remote work and in-office collaboration. Qualified applicants must live within commuting distance of our Boston office location and should expect to be in office 3 days a week." We'll keep rest. Then Schedule section will contain that sentence. Now check for any other duplicated content: Benefits paragraph includes generic sentence about benefits program; that's fine. Now ensure we removed boilerplate: visa sponsorship, inclusion encouragement, profile review, note about pay, notice to US job applicants, EEO, accommodation request, etc. We kept the sentence about base pay range and note that compensation details reflect base salary only; that's substantive. We kept the sentence about benefits program. Now produce final HTML. Be careful to escape any special characters like & in benefits list: we used & for "Sonos Radio HD - on us!" Actually we need to keep the ampersand; we should encode as &. Already did. Check for any other ampersand: "Medical, Dental, and Vision Insurance" fine.