Director, Growth & Product Strategy
for sections: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. Only include sections that have real specific content. The posting includes "About This Role" (which is about the role), "Key Responsibilities", "Ideal Candidate Profile" (which includes experience, etc.), "What Success Looks Like" (maybe could be considered part of responsibilities or qualifications). There's no explicit Benefits, Pay, Schedule. So we should not create those sections. Also we should not repeat job title. We need to preserve all substantive info, remove boilerplate like EEO, etc. The "Additional Information" includes EEO statement, which we should drop. Also "About Kaseya" is company description; maybe we can include as part of About the role? The instruction: use for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Skills, Benefits, Pay, Schedule). So we need to map content to those headings. Likely sections: About the role (company description + role description), Responsibilities (Key Responsibilities), Requirements (Ideal Candidate Profile maybe includes experience), Qualifications (maybe also part of Ideal Candidate Profile?), Skills (maybe communication skills etc). But we must not create sections with filler. We need to decide what content belongs where.
We have:
- About Kaseya (company overview)
- About This Role (role description)
- Key Responsibilities (list)
- Ideal Candidate Profile (list of experience, skills, etc.)
- What Success Looks Like (description of success metrics)
- Additional Information (EEO) -> drop.
We need to map to headings: About the role (could combine About Kaseya and About This Role). Responsibilities (Key Responsibilities). Requirements (maybe the experience requirement: 10+ years etc). Qualifications (maybe the same as Requirements? Could split). Skills (maybe communication, analytical, etc). But we must avoid duplication and filler.
We need to preserve all substantive info. So we need to include all points from Ideal Candidate Profile and What Success Looks Like somewhere.
We could create sections:
About the role
-> include About Kaseya paragraph and About This Role paragraph(s).
Responsibilities
-> list from Key Responsibilities.
Requirements
-> include the 10+ years experience, track record, etc. Possibly also include "Software, B2B / B2B2C SaaS, MSP, IT management, cybersecurity, or product-led growth experience is strongly preferred but not required."
Qualifications
-> maybe include the success metrics? Or we could treat What Success Looks Like as Qualifications? But Qualifications usually about education/certifications; not present. Could skip Qualifications if no specific content. But we need to avoid empty headings. So we should not include Qualifications if no real content. Similarly Skills: we could extract communication, analytical, problem-framing, synthesis, customer orientation, etc. Those are skills. So we could have a Skills section.
Benefits, Pay, Schedule: none, so omit.
Thus final sections: About the role, Responsibilities, Requirements, Skills.
We need to use - for any list of duties/requirements/benefits. For prose, use
.
We need to preserve all substantive info; not invent or summarize away detail. So we need to keep the exact phrasing? Probably we can keep the content but can rephrase? The instruction: "Preserve ALL substantive information; do NOT invent or summarize away detail." So we should keep the details, but we can format them. Likely we can copy sentences as is.
Let's extract:
About Kaseya paragraph: "Kaseya is the leading provider of AI-powered IT management and cybersecurity software, serving Managed Service Providers (MSPs) and internal IT organizations worldwide. Our comprehensive platform helps organizations efficiently manage, secure, and automate their IT environments, driving operational efficiency and long-term business success. Backed by Insight Partners, a leading global software investor, Kaseya has experienced sustained double-digit growth and continues to expand its global footprint. Today, Kaseya supports customers in more than 20 countries and manages over 15 million endpoints worldwide. Founded in 2000, Kaseya was built by builders - and we're still building. We look for people who create rather than wait, who see a hard problem and lean in, and who treat challenges as raw material. At Kaseya, everyone plays a role in shaping the future of IT: whether you're in engineering, product, sales, marketing, customer support, or operations, your work helps protect, defend, and optimize IT environments across the globe. We're building teams that grow, perform, and make an impact. If you're driven by the itch to make things better - a product, a process, a career - you'll fit right in. At Kaseya, we don't just raise the bar. We build it."
About This Role: "As Kaseya continues to scale, the Growth & Product Strategy function, part of the CTO's organization, is being built to sharpen where the company plays, how it wins, and how customer-backed insight translates into Product, Go-To-Market, and revenue outcomes. This is a hands-on Director role for a senior operator who will personally drive Kaseya's product strategy work — working directly with executives, engaging deeply with customers and field teams, and structuring ambiguous business questions into clear recommendations that accelerate near-term ARR while shaping Kaseya's multi-year direction. Operating at the intersection of customer insight, product strategy, market opportunity, competitive positioning, and go-to-market execution, this person drives the work personally today and builds a Product Strategy team to scale it over time. The decisions this role informs — where to invest, which segments to win, how to price and position — shape a meaningful share of Kaseya's growth. This is a seat with real leverage on the company's trajectory, and, for the right person, a path toward senior Product or Go-To-Market leadership. This role reports to the SVP, Growth & Product Strategy."
Key Responsibilities list (bullet points):
- Develop customer-backed growth strategy. Draw on customer insight — from direct engagement with MSP and Direct IT customers and field leaders, and from the company's research, NPS, win/loss, and market signals — to build a clear view of customer needs, buying behaviour, pain points, churn drivers, and expansion opportunities.
- Frame the highest-value strategic questions. Bring structure to ambiguous business problems — define the real decision, build hypotheses, identify what evidence matters, and land clear recommendations in compelling narratives that senior leaders can act on quickly.
- Translate insight into strategy and execution. Convert customer, product, market, and competitive insight into practical strategies that support near-term ARR growth while shaping Kaseya's three-year strategic direction.
- Partner across the org and with senior stakeholders. Collaborate with teams and leaders across Product, GTM, Customer Success, Finance, and Operations, bringing fact-based analysis and clear narratives.
- Build and scale the capability. Do the work directly — the analysis, the customer engagement, the recommendations — and progressively build the people, processes, and operating model needed to turn Product Strategy into a durable, scaled function.
Ideal Candidate Profile:
- 10+ years of experience in product strategy, product management, strategy consulting, corporate strategy, or a comparable senior strategic or operating leadership role, with a track record of owning ambiguous, high-stakes problems end to end.
- Operates as a peer to senior leaders — owning a point of view and driving the decisions that follow.
- Exceptional problem-framing, analytical, and synthesis skills; able to identify the real question, isolate the key drivers, and determine what evidence matters.
- Strong customer orientation with firsthand experience using customer discovery, research, design thinking, experimentation, product data, and field insight to inform strategy.
- Outstanding written and verbal communication skills, including the ability to create strong narratives, memos, and presentations with clarity and conviction.
- High operating discipline, strong ownership mindset, and comfort operating as a hands-on individual driver today while building toward and leading a team over time, in a fast-paced, high-expectation environment where priorities shift quickly and quality is always critical.
- Software, B2B / B2B2C SaaS, MSP, IT management, cybersecurity, or product-led growth experience is strongly preferred but not required.
What Success Looks Like:
- Draws a clear line from strategy work to ARR — every major recommendation ties to a specific near-term revenue or expansion opportunity, with the expected impact quantified.
- Helps develop and refine Kaseya's 3&1 strategy — the company's three-year direction and one-year operating plan — pressure-testing and sharpening it as customer and market insight evolves, so the core plan stays grounded in evidence.
- Builds trust with senior leadership by bringing structure, rigor, and reliable analysis to the company’s most important growth questions.
- Creates a repeatable approach for customer-backed strategy & product work that matures into a durable Product Strategy operating model and the team to run it.
- Produces recommendations that directly inform product priorities, GTM choices, customer segmentation, revenue opportunities, and investment decisions.
- Balances speed with rigor, delivering useful recommendations quickly while continuing to sharpen the answer as additional evidence emerges.
- This is a rare opportunity to build a new strategic capability inside one of the most operationally intense software companies in the market. The right leader will have direct exposure to senior leadership, ownership of the company’s most important growth questions, and the mandate to turn customer truth into strategies that move the business. This is an exciting role in itself, and, as noted above, for the right person, a path toward senior Product or Go-To-Market leadership.
We need to decide where to put What Success Looks Like. Could be part of Responsibilities or maybe a separate section like "Expectations". But only allowed headings are the given list. Could fit under Responsibilities (as they are outcomes). Or under Requirements? Probably better to include under Responsibilities as they describe what success looks like. But we already have Responsibilities list; we could add additional bullet points under Responsibilities for success metrics. However the instruction: "Use
- for any list of duties/requirements/benefits". So we can have multiple lists.
Thus we can have Responsibilities section with two lists: one for Key Responsibilities, another for What Success Looks Like (maybe as "Success Metrics"). But we need to keep headings only; we can have multiple
under same heading.
Alternatively we could create a separate section "Qualifications" for What Success Looks Like? Not ideal.
Better to keep Responsibilities as the duties, and maybe add a separate section "Expectations" but not allowed. So we incorporate success metrics into Responsibilities as additional bullet points.
Now Skills: we can extract skills from Ideal Candidate Profile: problem-framing, analytical, synthesis, customer orientation, written and verbal communication, operating discipline, ownership mindset, etc. Also maybe "hands-on individual driver". We'll create a Skills section with a list.
Requirements: we can include the experience requirement (10+ years) and the preferred experience note. Also maybe "operates as a peer to senior leaders" etc. But that is more of a skill. We'll keep Requirements as the experience and track record.
We need to avoid duplication. Let's parse:
Ideal Candidate Profile bullet points:
1. 10+ years experience ... (requirement)
2. Operates as a peer to senior leaders ... (skill/behavior)
3. Exceptional problem-framing, analytical, and synthesis skills ... (skill)
4. Strong customer orientation ... (skill)
5. Outstanding written and verbal communication skills ... (skill)
6. High operating discipline, strong ownership mindset, and comfort operating as a hands-on individual driver ... (skill)
7. Software, B2B / B2B2C SaaS, MSP, IT management, cybersecurity, or product-led growth experience is strongly preferred but not required. (preferred experience)
Thus we can put #1 and #7 under Requirements (experience
About the role
-> include About Kaseya paragraph and About This Role paragraph(s).Responsibilities
-> list from Key Responsibilities.Requirements
-> include the 10+ years experience, track record, etc. Possibly also include "Software, B2B / B2B2C SaaS, MSP, IT management, cybersecurity, or product-led growth experience is strongly preferred but not required."Qualifications
-> maybe include the success metrics? Or we could treat What Success Looks Like as Qualifications? But Qualifications usually about education/certifications; not present. Could skip Qualifications if no specific content. But we need to avoid empty headings. So we should not include Qualifications if no real content. Similarly Skills: we could extract communication, analytical, problem-framing, synthesis, customer orientation, etc. Those are skills. So we could have a Skills section. Benefits, Pay, Schedule: none, so omit. Thus final sections: About the role, Responsibilities, Requirements, Skills. We need to use- for any list of duties/requirements/benefits. For prose, use
. We need to preserve all substantive info; not invent or summarize away detail. So we need to keep the exact phrasing? Probably we can keep the content but can rephrase? The instruction: "Preserve ALL substantive information; do NOT invent or summarize away detail." So we should keep the details, but we can format them. Likely we can copy sentences as is. Let's extract: About Kaseya paragraph: "Kaseya is the leading provider of AI-powered IT management and cybersecurity software, serving Managed Service Providers (MSPs) and internal IT organizations worldwide. Our comprehensive platform helps organizations efficiently manage, secure, and automate their IT environments, driving operational efficiency and long-term business success. Backed by Insight Partners, a leading global software investor, Kaseya has experienced sustained double-digit growth and continues to expand its global footprint. Today, Kaseya supports customers in more than 20 countries and manages over 15 million endpoints worldwide. Founded in 2000, Kaseya was built by builders - and we're still building. We look for people who create rather than wait, who see a hard problem and lean in, and who treat challenges as raw material. At Kaseya, everyone plays a role in shaping the future of IT: whether you're in engineering, product, sales, marketing, customer support, or operations, your work helps protect, defend, and optimize IT environments across the globe. We're building teams that grow, perform, and make an impact. If you're driven by the itch to make things better - a product, a process, a career - you'll fit right in. At Kaseya, we don't just raise the bar. We build it." About This Role: "As Kaseya continues to scale, the Growth & Product Strategy function, part of the CTO's organization, is being built to sharpen where the company plays, how it wins, and how customer-backed insight translates into Product, Go-To-Market, and revenue outcomes. This is a hands-on Director role for a senior operator who will personally drive Kaseya's product strategy work — working directly with executives, engaging deeply with customers and field teams, and structuring ambiguous business questions into clear recommendations that accelerate near-term ARR while shaping Kaseya's multi-year direction. Operating at the intersection of customer insight, product strategy, market opportunity, competitive positioning, and go-to-market execution, this person drives the work personally today and builds a Product Strategy team to scale it over time. The decisions this role informs — where to invest, which segments to win, how to price and position — shape a meaningful share of Kaseya's growth. This is a seat with real leverage on the company's trajectory, and, for the right person, a path toward senior Product or Go-To-Market leadership. This role reports to the SVP, Growth & Product Strategy." Key Responsibilities list (bullet points): - Develop customer-backed growth strategy. Draw on customer insight — from direct engagement with MSP and Direct IT customers and field leaders, and from the company's research, NPS, win/loss, and market signals — to build a clear view of customer needs, buying behaviour, pain points, churn drivers, and expansion opportunities. - Frame the highest-value strategic questions. Bring structure to ambiguous business problems — define the real decision, build hypotheses, identify what evidence matters, and land clear recommendations in compelling narratives that senior leaders can act on quickly. - Translate insight into strategy and execution. Convert customer, product, market, and competitive insight into practical strategies that support near-term ARR growth while shaping Kaseya's three-year strategic direction. - Partner across the org and with senior stakeholders. Collaborate with teams and leaders across Product, GTM, Customer Success, Finance, and Operations, bringing fact-based analysis and clear narratives. - Build and scale the capability. Do the work directly — the analysis, the customer engagement, the recommendations — and progressively build the people, processes, and operating model needed to turn Product Strategy into a durable, scaled function. Ideal Candidate Profile: - 10+ years of experience in product strategy, product management, strategy consulting, corporate strategy, or a comparable senior strategic or operating leadership role, with a track record of owning ambiguous, high-stakes problems end to end. - Operates as a peer to senior leaders — owning a point of view and driving the decisions that follow. - Exceptional problem-framing, analytical, and synthesis skills; able to identify the real question, isolate the key drivers, and determine what evidence matters. - Strong customer orientation with firsthand experience using customer discovery, research, design thinking, experimentation, product data, and field insight to inform strategy. - Outstanding written and verbal communication skills, including the ability to create strong narratives, memos, and presentations with clarity and conviction. - High operating discipline, strong ownership mindset, and comfort operating as a hands-on individual driver today while building toward and leading a team over time, in a fast-paced, high-expectation environment where priorities shift quickly and quality is always critical. - Software, B2B / B2B2C SaaS, MSP, IT management, cybersecurity, or product-led growth experience is strongly preferred but not required. What Success Looks Like: - Draws a clear line from strategy work to ARR — every major recommendation ties to a specific near-term revenue or expansion opportunity, with the expected impact quantified. - Helps develop and refine Kaseya's 3&1 strategy — the company's three-year direction and one-year operating plan — pressure-testing and sharpening it as customer and market insight evolves, so the core plan stays grounded in evidence. - Builds trust with senior leadership by bringing structure, rigor, and reliable analysis to the company’s most important growth questions. - Creates a repeatable approach for customer-backed strategy & product work that matures into a durable Product Strategy operating model and the team to run it. - Produces recommendations that directly inform product priorities, GTM choices, customer segmentation, revenue opportunities, and investment decisions. - Balances speed with rigor, delivering useful recommendations quickly while continuing to sharpen the answer as additional evidence emerges. - This is a rare opportunity to build a new strategic capability inside one of the most operationally intense software companies in the market. The right leader will have direct exposure to senior leadership, ownership of the company’s most important growth questions, and the mandate to turn customer truth into strategies that move the business. This is an exciting role in itself, and, as noted above, for the right person, a path toward senior Product or Go-To-Market leadership. We need to decide where to put What Success Looks Like. Could be part of Responsibilities or maybe a separate section like "Expectations". But only allowed headings are the given list. Could fit under Responsibilities (as they are outcomes). Or under Requirements? Probably better to include under Responsibilities as they describe what success looks like. But we already have Responsibilities list; we could add additional bullet points under Responsibilities for success metrics. However the instruction: "Use
- for any list of duties/requirements/benefits". So we can have multiple lists.
Thus we can have Responsibilities section with two lists: one for Key Responsibilities, another for What Success Looks Like (maybe as "Success Metrics"). But we need to keep headings only; we can have multiple
- under same heading.
Alternatively we could create a separate section "Qualifications" for What Success Looks Like? Not ideal.
Better to keep Responsibilities as the duties, and maybe add a separate section "Expectations" but not allowed. So we incorporate success metrics into Responsibilities as additional bullet points.
Now Skills: we can extract skills from Ideal Candidate Profile: problem-framing, analytical, synthesis, customer orientation, written and verbal communication, operating discipline, ownership mindset, etc. Also maybe "hands-on individual driver". We'll create a Skills section with a list.
Requirements: we can include the experience requirement (10+ years) and the preferred experience note. Also maybe "operates as a peer to senior leaders" etc. But that is more of a skill. We'll keep Requirements as the experience and track record.
We need to avoid duplication. Let's parse:
Ideal Candidate Profile bullet points:
1. 10+ years experience ... (requirement)
2. Operates as a peer to senior leaders ... (skill/behavior)
3. Exceptional problem-framing, analytical, and synthesis skills ... (skill)
4. Strong customer orientation ... (skill)
5. Outstanding written and verbal communication skills ... (skill)
6. High operating discipline, strong ownership mindset, and comfort operating as a hands-on individual driver ... (skill)
7. Software, B2B / B2B2C SaaS, MSP, IT management, cybersecurity, or product-led growth experience is strongly preferred but not required. (preferred experience)
Thus we can put #1 and #7 under Requirements (experience
- for any list of duties/requirements/benefits". So we can have multiple lists.
Thus we can have Responsibilities section with two lists: one for Key Responsibilities, another for What Success Looks Like (maybe as "Success Metrics"). But we need to keep headings only; we can have multiple