Director, Product Management
for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). Use - for any list of duties/requirements/benefits, and
for prose. Do NOT repeat the job title as a heading (the page already shows it) and do NOT put Job ID / requisition numbers as headings — fold minor metadata into a short
or drop it. Preserve ALL substantive information; do NOT invent or summarize away detail. Remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. IMPORTANT: include a section ONLY when the posting has real, specific content for it — never emit a heading followed by filler/placeholder text (e.g. "commensurate with experience", "not specified", "N/A", "varies", "TBD") and never create Pay/Schedule/Benefits sections unless the posting actually states them. Prefer a few substantive sections over many thin ones. Output ONLY the HTML fragment — no /, no markdown code fences.
We need to parse the posting.
The posting includes:
- Intro: "Are you looking for an opportunity to help solve one of today's biggest business challenges? AI is changing the pace of business, and organizations everywhere are struggling to help their workforce, partners, and customers keep up. At Litmos, we're building the Learning Acceleration Platform that helps organizations build human capability faster—and we're looking for people who are passionate about making a meaningful impact for customers while growing alongside a collaborative, people-first team. Litmos is the Learning Acceleration Platform that helps organizations build capability faster, adapt at the speed business changes, and scale learning to anyone, anywhere. Combining an intuitive platform, AI-powered capabilities, trusted content, expert services, and a broad ecosystem of integrations, Litmos helps organizations accelerate workforce productivity, improve customer adoption and retention, enable high-performing partners, and reduce organizational risk through continuous learning. Organizations such as Hewlett Packard Enterprise, Graco, Sabre, and Russell Mineral Equipment trust Litmos to accelerate learning across their workforce, partners, and customers. Today, more than 11K customers with 30 million learners across 150 countries and 37 languages use Litmos to build the capabilities their organizations need to succeed. Backed by Francisco Partners, one of the world's leading technology investment firms, we're investing in the future of learning—and the people who are building it. Learn more at www.litmos.com."
That's about the company. Could be "About the role"? Actually "About the role" is for description of the role. The intro is more about company. Could be "About the role" includes both company and role? Usually "About the role" includes description of the role and maybe company. But we have a separate "Responsibilities" section later.
We need to decide sections: maybe "About the role" (company + role overview), "Responsibilities", "Qualifications", "Benefits", "Pay". The posting includes Salary Range: $160,000 - $175,000 plus 20% bonus. That's pay info. Benefits listed. So we should include Pay and Benefits sections.
We need to avoid filler like "commensurate with experience". Not present.
We need to remove EEO boilerplate at end: "We are an equal opportunity workplace employer..." etc. Remove that.
Also remove "As a learning company we believe in the potential of everyone; if you don't have experience in all the details mentioned in this job post, then we still encourage you to apply and we'll get back to you as soon as we can." That's like application encouragement; maybe considered boilerplate? It's not EEO but it's generic encouragement. The instruction says remove application instructions. This is not exactly instruction to apply but encouragement. Might be considered boilerplate? Safer to remove it as it's not substantive detail about role. It's more like "we encourage you to apply". Could be considered application instruction. We'll remove.
Also remove duplicated lines: there is a duplicated line "Serve as the primary escalation point for cross-functional blockers, priority conflicts, delivery risks, and revenue-impacting issues" appears twice? Actually appears in Responsibilities and later again under Go-to-Market Leadership & Launch Coordination? Let's check: Under Responsibilities: "Serve as the primary escalation point for cross-functional blockers, priority conflicts, delivery risks, and revenue-impacting issues". Then later under Go-to-Market Leadership & Launch Coordination: "Serve as the primary escalation point for cross-functional blockers, priority conflicts and delivery risks". Slightly different but similar. We'll keep both as they are distinct but similar; not duplicate exactly. Might keep.
We need to preserve all substantive info.
Let's extract sections:
- About the role: Could combine company overview and role overview: The first paragraph(s) describing Litmos and the role purpose: "Are you looking for an opportunity to help solve one of today's biggest business challenges? ... At Litmos, we're building the Learning Acceleration Platform ... we're looking for people who are passionate about making a meaningful impact for customers while growing alongside a collaborative, people-first team." Then description of Litmos platform, customers, etc. Then "We are seeking a Director, Product Management to serve as the SVP Product's operational partner and critical connector across product management, engineering, content production, marketing, sales, and customer success teams spanning distributed operations across the US, UK, Australia, and India (Pune). You will be accountable for a combination of working with other organizations to optimize our agentic product delivery cycle and operating our strategic vision for the Litmos platform. You’ll collaborate on setting the operational rhythm combined with delivery health, strategic planning and product investments. This is not a technical architecture role, but you will be empowered to build agentic solutions. You are the person who ensures the product vision translates into reliable execution across all functions, cross-team dependencies don't become surprises, revenue impact is maximized, and leadership has clear visibility into what's working and what isn't. You'll be the connective tissue bridging Product Management (roadmap building, product vision), Engineering teams (delivery execution), Production (digital content library), Product Marketing (messaging, launch coordination), Sales (enablement, feedback, field insights), and Customer Success (customer adoption, feedback loops, satisfaction metrics). Your role is to ensure alignment across these functions, manage interdependencies, translate customer and market insights back into product decisions, and provide the SVP Product and executive leadership with real-time visibility into product health, delivery confidence, market positioning, and revenue impact."
That's substantive. We'll put that under
About the role
with paragraphs.
- Responsibilities: The bullet list under "Key Responsibilities". There are subheadings: "Drive Cross-Functional Product Delivery & Execution", "Go-to-Market Leadership & Launch Coordination", "Customer Success & Adoption Leadership", "Marketing and Revenue Enablement Alignment & Positioning", "Provide Strategic Visibility & Leadership Support". Each has bullet points. We'll need to output a
- for each duty. Should we keep subheadings? The instruction: use
for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). Use - for any list of duties/requirements/benefits, and
for prose. It doesn't forbid subheadings inside responsibilities, but we could just list all responsibilities as list items. However we might lose some grouping. But it's okay to just list them. The instruction says "Prefer a few substantive sections over many thin ones." So we can have one Responsibilities section with a list.
We need to capture all responsibilities bullet points:
From text:
"Key Responsibilities Drive Cross-Functional Product Delivery & Execution Own delivery metrics, process health, and cross-functional dependency management between Product, Engineering, Production, Marketing, Sales, and Customer Success teams Serve as the primary escalation point for cross-functional blockers, priority conflicts, delivery risks, and revenue-impacting issues Manage the Continuous Discovery agentic planning cycle, roadmap alignment, and resource allocation to ensure product commitments are met and revenue targets are supported Coordinate handoffs between delivery, launch, sales enablement, and customer success to ensure smooth execution and adoption Go-to-Market Leadership & Launch Coordination Joint ownership of the end-to-end go-to-market planning and execution for major product releases and features, coordinating across product, marketing, sales, and customer success Track launch success metrics (adoption, engagement, customer feedback, revenue impact) and drive post-launch optimization and customer success initiatives Serve as the primary escalation point for cross-functional blockers, priority conflicts and delivery risks Customer Success & Adoption Leadership Collaborate with Product Marketing, Customer Success, and Product Operations leadership to develop customer adoption strategies aligned with product releases and organizational goals Establish mechanisms to collect and synthesize customer feedback, feature requests, and product insights from CS teams; translate into product insights and priorities Track customer metrics by feature; identify and address adoption blockers Facilitate cross-functional reviews of customer health and expand opportunities, ensuring product roadmap reflects customer success priorities Marketing and Revenue Enablement Alignment & Positioning Partner with Marketing leadership on product positioning, messaging strategy, and campaign planning for new releases and features Ensure product roadmap visibility and timing are understood by Marketing to support content planning, webinars, case studies, and thought leadership Coordinate messaging alignment across product documentation, marketing collateral, sales materials, and customer communications Provide Strategic Visibility & Leadership Support Provide the SVP of Product and Executive Leadership with comprehensive reporting on product health, delivery velocity, commitment reliability, organizational risks, and revenue impact Synthesize data and insights from product, engineering, marketing, sales, and customer success to inform strategic decision-making and executive visibility Drive strategic initiatives on behalf of the SVP of Product (organizational restructuring, tool adoption, process improvements, scaling production, GTM processes) Partner on hiring strategy, team structure decisions, and product/engineering/GTM organization culture and capability building Monitor competitive landscape, market trends, and customer feedback to advise leadership on strategic product and business positioning"
We need to split into sensible list items. Each sentence seems a responsibility. Let's break:
1. Own delivery metrics, process health, and cross-functional dependency management between Product, Engineering, Production, Marketing, Sales, and Customer Success teams.
2. Serve as the primary escalation point for cross-functional blockers, priority conflicts, delivery risks, and revenue-impacting issues.
3. Manage the Continuous Discovery agentic planning cycle, roadmap alignment, and resource allocation to ensure product commitments are met and revenue targets are supported.
4. Coordinate handoffs between delivery, launch, sales enablement, and customer success to ensure smooth execution and adoption.
5. Joint ownership of the end-to-end go-to-market planning and execution for major product releases and features, coordinating across product, marketing, sales, and customer success.
6. Track launch success metrics (adoption, engagement, customer feedback, revenue impact) and drive post-launch optimization and customer success initiatives.
7. Serve as the primary escalation point for cross-functional blockers, priority conflicts and delivery risks. (duplicate but keep)
8. Collaborate with Product Marketing, Customer Success, and Product Operations leadership to develop customer adoption strategies aligned with product releases and organizational goals.
9. Establish mechanisms to collect and synthesize customer feedback, feature requests, and product insights from CS teams; translate into product insights and priorities.
10. Track customer metrics by feature; identify and address adoption blockers.
11. Facilitate cross-functional reviews of customer health and expand opportunities, ensuring product roadmap reflects customer success priorities.
12. Partner with Marketing leadership on product positioning, messaging strategy, and campaign planning for new releases and features.
13. Ensure product roadmap visibility and timing are understood by Marketing to support content planning, webinars, case studies, and thought leadership.
14. Coordinate messaging alignment across product documentation, marketing collateral, sales materials, and customer communications.
for prose. Do NOT repeat the job title as a heading (the page already shows it) and do NOT put Job ID / requisition numbers as headings — fold minor metadata into a short
or drop it. Preserve ALL substantive information; do NOT invent or summarize away detail. Remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. IMPORTANT: include a section ONLY when the posting has real, specific content for it — never emit a heading followed by filler/placeholder text (e.g. "commensurate with experience", "not specified", "N/A", "varies", "TBD") and never create Pay/Schedule/Benefits sections unless the posting actually states them. Prefer a few substantive sections over many thin ones. Output ONLY the HTML fragment — no /, no markdown code fences. We need to parse the posting. The posting includes: - Intro: "Are you looking for an opportunity to help solve one of today's biggest business challenges? AI is changing the pace of business, and organizations everywhere are struggling to help their workforce, partners, and customers keep up. At Litmos, we're building the Learning Acceleration Platform that helps organizations build human capability faster—and we're looking for people who are passionate about making a meaningful impact for customers while growing alongside a collaborative, people-first team. Litmos is the Learning Acceleration Platform that helps organizations build capability faster, adapt at the speed business changes, and scale learning to anyone, anywhere. Combining an intuitive platform, AI-powered capabilities, trusted content, expert services, and a broad ecosystem of integrations, Litmos helps organizations accelerate workforce productivity, improve customer adoption and retention, enable high-performing partners, and reduce organizational risk through continuous learning. Organizations such as Hewlett Packard Enterprise, Graco, Sabre, and Russell Mineral Equipment trust Litmos to accelerate learning across their workforce, partners, and customers. Today, more than 11K customers with 30 million learners across 150 countries and 37 languages use Litmos to build the capabilities their organizations need to succeed. Backed by Francisco Partners, one of the world's leading technology investment firms, we're investing in the future of learning—and the people who are building it. Learn more at www.litmos.com." That's about the company. Could be "About the role"? Actually "About the role" is for description of the role. The intro is more about company. Could be "About the role" includes both company and role? Usually "About the role" includes description of the role and maybe company. But we have a separate "Responsibilities" section later. We need to decide sections: maybe "About the role" (company + role overview), "Responsibilities", "Qualifications", "Benefits", "Pay". The posting includes Salary Range: $160,000 - $175,000 plus 20% bonus. That's pay info. Benefits listed. So we should include Pay and Benefits sections. We need to avoid filler like "commensurate with experience". Not present. We need to remove EEO boilerplate at end: "We are an equal opportunity workplace employer..." etc. Remove that. Also remove "As a learning company we believe in the potential of everyone; if you don't have experience in all the details mentioned in this job post, then we still encourage you to apply and we'll get back to you as soon as we can." That's like application encouragement; maybe considered boilerplate? It's not EEO but it's generic encouragement. The instruction says remove application instructions. This is not exactly instruction to apply but encouragement. Might be considered boilerplate? Safer to remove it as it's not substantive detail about role. It's more like "we encourage you to apply". Could be considered application instruction. We'll remove. Also remove duplicated lines: there is a duplicated line "Serve as the primary escalation point for cross-functional blockers, priority conflicts, delivery risks, and revenue-impacting issues" appears twice? Actually appears in Responsibilities and later again under Go-to-Market Leadership & Launch Coordination? Let's check: Under Responsibilities: "Serve as the primary escalation point for cross-functional blockers, priority conflicts, delivery risks, and revenue-impacting issues". Then later under Go-to-Market Leadership & Launch Coordination: "Serve as the primary escalation point for cross-functional blockers, priority conflicts and delivery risks". Slightly different but similar. We'll keep both as they are distinct but similar; not duplicate exactly. Might keep. We need to preserve all substantive info. Let's extract sections: - About the role: Could combine company overview and role overview: The first paragraph(s) describing Litmos and the role purpose: "Are you looking for an opportunity to help solve one of today's biggest business challenges? ... At Litmos, we're building the Learning Acceleration Platform ... we're looking for people who are passionate about making a meaningful impact for customers while growing alongside a collaborative, people-first team." Then description of Litmos platform, customers, etc. Then "We are seeking a Director, Product Management to serve as the SVP Product's operational partner and critical connector across product management, engineering, content production, marketing, sales, and customer success teams spanning distributed operations across the US, UK, Australia, and India (Pune). You will be accountable for a combination of working with other organizations to optimize our agentic product delivery cycle and operating our strategic vision for the Litmos platform. You’ll collaborate on setting the operational rhythm combined with delivery health, strategic planning and product investments. This is not a technical architecture role, but you will be empowered to build agentic solutions. You are the person who ensures the product vision translates into reliable execution across all functions, cross-team dependencies don't become surprises, revenue impact is maximized, and leadership has clear visibility into what's working and what isn't. You'll be the connective tissue bridging Product Management (roadmap building, product vision), Engineering teams (delivery execution), Production (digital content library), Product Marketing (messaging, launch coordination), Sales (enablement, feedback, field insights), and Customer Success (customer adoption, feedback loops, satisfaction metrics). Your role is to ensure alignment across these functions, manage interdependencies, translate customer and market insights back into product decisions, and provide the SVP Product and executive leadership with real-time visibility into product health, delivery confidence, market positioning, and revenue impact." That's substantive. We'll put that under
About the role
withparagraphs. - Responsibilities: The bullet list under "Key Responsibilities". There are subheadings: "Drive Cross-Functional Product Delivery & Execution", "Go-to-Market Leadership & Launch Coordination", "Customer Success & Adoption Leadership", "Marketing and Revenue Enablement Alignment & Positioning", "Provide Strategic Visibility & Leadership Support". Each has bullet points. We'll need to output a
- for each duty. Should we keep subheadings? The instruction: use
for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). Use
- for any list of duties/requirements/benefits, and
for prose. It doesn't forbid subheadings inside responsibilities, but we could just list all responsibilities as list items. However we might lose some grouping. But it's okay to just list them. The instruction says "Prefer a few substantive sections over many thin ones." So we can have one Responsibilities section with a list. We need to capture all responsibilities bullet points: From text: "Key Responsibilities Drive Cross-Functional Product Delivery & Execution Own delivery metrics, process health, and cross-functional dependency management between Product, Engineering, Production, Marketing, Sales, and Customer Success teams Serve as the primary escalation point for cross-functional blockers, priority conflicts, delivery risks, and revenue-impacting issues Manage the Continuous Discovery agentic planning cycle, roadmap alignment, and resource allocation to ensure product commitments are met and revenue targets are supported Coordinate handoffs between delivery, launch, sales enablement, and customer success to ensure smooth execution and adoption Go-to-Market Leadership & Launch Coordination Joint ownership of the end-to-end go-to-market planning and execution for major product releases and features, coordinating across product, marketing, sales, and customer success Track launch success metrics (adoption, engagement, customer feedback, revenue impact) and drive post-launch optimization and customer success initiatives Serve as the primary escalation point for cross-functional blockers, priority conflicts and delivery risks Customer Success & Adoption Leadership Collaborate with Product Marketing, Customer Success, and Product Operations leadership to develop customer adoption strategies aligned with product releases and organizational goals Establish mechanisms to collect and synthesize customer feedback, feature requests, and product insights from CS teams; translate into product insights and priorities Track customer metrics by feature; identify and address adoption blockers Facilitate cross-functional reviews of customer health and expand opportunities, ensuring product roadmap reflects customer success priorities Marketing and Revenue Enablement Alignment & Positioning Partner with Marketing leadership on product positioning, messaging strategy, and campaign planning for new releases and features Ensure product roadmap visibility and timing are understood by Marketing to support content planning, webinars, case studies, and thought leadership Coordinate messaging alignment across product documentation, marketing collateral, sales materials, and customer communications Provide Strategic Visibility & Leadership Support Provide the SVP of Product and Executive Leadership with comprehensive reporting on product health, delivery velocity, commitment reliability, organizational risks, and revenue impact Synthesize data and insights from product, engineering, marketing, sales, and customer success to inform strategic decision-making and executive visibility Drive strategic initiatives on behalf of the SVP of Product (organizational restructuring, tool adoption, process improvements, scaling production, GTM processes) Partner on hiring strategy, team structure decisions, and product/engineering/GTM organization culture and capability building Monitor competitive landscape, market trends, and customer feedback to advise leadership on strategic product and business positioning" We need to split into sensible list items. Each sentence seems a responsibility. Let's break: 1. Own delivery metrics, process health, and cross-functional dependency management between Product, Engineering, Production, Marketing, Sales, and Customer Success teams. 2. Serve as the primary escalation point for cross-functional blockers, priority conflicts, delivery risks, and revenue-impacting issues. 3. Manage the Continuous Discovery agentic planning cycle, roadmap alignment, and resource allocation to ensure product commitments are met and revenue targets are supported. 4. Coordinate handoffs between delivery, launch, sales enablement, and customer success to ensure smooth execution and adoption. 5. Joint ownership of the end-to-end go-to-market planning and execution for major product releases and features, coordinating across product, marketing, sales, and customer success. 6. Track launch success metrics (adoption, engagement, customer feedback, revenue impact) and drive post-launch optimization and customer success initiatives. 7. Serve as the primary escalation point for cross-functional blockers, priority conflicts and delivery risks. (duplicate but keep) 8. Collaborate with Product Marketing, Customer Success, and Product Operations leadership to develop customer adoption strategies aligned with product releases and organizational goals. 9. Establish mechanisms to collect and synthesize customer feedback, feature requests, and product insights from CS teams; translate into product insights and priorities. 10. Track customer metrics by feature; identify and address adoption blockers. 11. Facilitate cross-functional reviews of customer health and expand opportunities, ensuring product roadmap reflects customer success priorities. 12. Partner with Marketing leadership on product positioning, messaging strategy, and campaign planning for new releases and features. 13. Ensure product roadmap visibility and timing are understood by Marketing to support content planning, webinars, case studies, and thought leadership. 14. Coordinate messaging alignment across product documentation, marketing collateral, sales materials, and customer communications.
- for any list of duties/requirements/benefits, and