Senior Director Product Management, Growth
for section headings: e.g., About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule.
We need to parse the posting and extract content for each section.
The posting includes:
- About The Role (intro paragraph)
- What You’ll Do (list of responsibilities)
- What We Look For (list of qualifications/requirements)
- About MongoDB (company description)
- Compensation and benefits (Pay and Benefits)
- Possibly schedule? Not mentioned.
We need to decide which sections to include: About the role (intro), Responsibilities (What You’ll Do), Requirements/Qualifications/Skills (What We Look For). Benefits and Pay (compensation and benefits). Schedule not present, so omit.
We must not include boilerplate like EEO, accommodations, REQ ID, etc. Also remove duplicated lines.
We need to preserve all substantive information.
We need to format lists using - . Use
for prose.
We must not invent or summarize away detail. Must not include placeholder text.
We need to ensure we don't include headings with empty content.
Let's extract:
About the role paragraph: "We’re looking for a Senior Director of Product Management to help define and drive our next phase of growth. Our team owns the end-to-end product-led growth journey, from developer acquisition and onboarding through activation, adoption, monetization, retention, expansion, and sales handoffs. We use customer insight, data, and experimentation to reduce friction, accelerate time-to-value, grow revenue, and increase long-term customer value. This is a high-impact, strategic role that requires strong leadership, creativity, strong product sense, and the ability to mentor a team of high-performing Product Managers. You’ll be expected to lead your team, but also influence across the Product and Technology and Marketing teams, build cross-functional relationships, and elevate the team’s overall strategic thinking and execution."
That's the About the role section.
Responsibilities (What You’ll Do): list of bullet points (though they are sentences separated by line breaks). We need to convert each sentence into
- . Let's extract each bullet:
- Develop a clear, cohesive product-led growth strategy for both MongoDB Community Edition and MongoDB Atlas translating that strategy into testable hypotheses, measurable growth outcomes, and a prioritized experimentation roadmap
- Identify and validate opportunities to expand into new user segments, improve onboarding and activation, accelerate time-to-value, and strengthen product education across the developer journey
- Own the growth measurement and experimentation framework across acquisition, activation, adoption, retention, expansion, and sales handoffs, using product and customer insights, rapid testing, and structured learning loops to identify friction, prioritize investments, measure impact, and scale what works
- Mentor and guide Product Managers to think more broadly and creatively about the customer journey, instilling a culture of innovation and strategic problem-solving
- Partner closely with Engineering, Design, Marketing, Sales, Finance, and other go-to-market teams to shape and launch growth initiatives, align product and GTM strategy, and identify opportunities across packaging, pricing, and monetization that accelerate self-service adoption and broader customer expansion
- Collaborate with engineering leaders beyond the dedicated Growth team to align technical roadmaps, resource allocation and cross-product investments required to deliver growth outcomes
- Work closely with product leadership in other areas of the organization to build consensus, identify cross-product growth opportunities, and rally support for initiatives that span the MongoDB developer journey
- Present updates and learnings in monthly and quarterly business reviews, influencing executive stakeholders and guiding critical decisions
- Stay close to developers and customers through direct research, feedback, usage insights, and market engagement, translating those signals into differentiated product opportunities and growth priorities
We need to ensure we keep all details.
Requirements/Qualifications/Skills (What We Look For): This is a long list. We need to decide how to split into sections: maybe Requirements (experience), Qualifications (education/background), Skills (specific abilities). But we can combine into one section "Requirements" if we want fewer sections. However guidelines: prefer a few substantive sections over many thin ones. We could have sections: About the role, Responsibilities, Requirements (including experience, background, skills), Benefits, Pay.
But we also have a separate "About MongoDB" company description. Should we include that? It's substantive but not a standard heading. Could be placed under "About the company" but not in list of allowed headings. The allowed headings are About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. There's no "About the company". We could incorporate that into About the role? But that would be mixing. Perhaps we can treat "About MongoDB" as part of the role description? But it's not about the role. The instruction says: use those headings for section headings. It doesn't forbid other headings? It says: use
for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). It implies we should use those headings for sections. It doesn't say we cannot add other headings, but likely we should stick to those. However we need to preserve all substantive information. The "About MongoDB" paragraph is substantive. Where to put it? Could be placed under a generic
without a heading? The instruction says: 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 having prose without a heading. So we can include a
for the About MongoDB description without a heading, or we could put it under a heading like "About MongoDB" but that's not in the list. Safer to just include as a
without a heading.
Similarly, the compensation and benefits paragraph: we need to extract Pay and Benefits sections.
Pay: "MongoDB’s base salary range for this role in the U.S. is: $162,000—$319,000 USD". Also earlier: "MongoDB’s base salary range for this role is posted below. Compensation at the time of offer is unique to each candidate and based on a variety of factors such as skill set, experience, qualifications, and work location. Salary is one part of MongoDB’s total compensation and benefits package." That's prose about pay. We can include that in Pay section.
Benefits: list: "Other benefits for eligible employees may include: equity, participation in the employee stock purchase program, flexible paid time off, 20 weeks fully-paid gender-neutral parental leave, fertility and adoption assistance, 401(k) plan, mental health counseling, access to transgender-inclusive health insurance coverage, and health benefits offerings." Also note: "Please note, the base salary range listed below and the benefits in this paragraph are only applicable to U.S.-based candidates." That's a note.
We should include Benefits section with a
- list of benefits.
We should not include the REQ ID, EEO, accommodations, etc.
We should not include duplicated lines.
Now, we need to decide on headings:
-
About the role
with the intro paragraph.
- Responsibilities
with - list.
-
Requirements
maybe combine qualifications and skills. But we have a long list that includes experience, background, strategic vision, leadership, passion, familiarity, communication, data-driven, research, programmatic product experiences, UI/UX, AI/ML, etc. Could split into Requirements (experience, background) and Skills (specific abilities). But we can keep as one Requirements section with a - list.
Alternatively, we could have Requirements and Skills separate. But guidelines: prefer a few substantive sections over many thin ones. Having one Requirements section with all the bullet points is fine.
Thus:
Requirements
with - list.
We need to extract each bullet from "What We Look For". Let's list them:
- Passion for MongoDB with a strong understanding of software engineering concepts and the developer audience
- 10+ years of Product Management experience, including 4+ years leading Product-Led Growth, Growth Product, or adjacent self-service growth motions at SaaS, cloud or developer-centric companies
- Deep understanding of product-led growth mechanics across acquisition, onboarding, activation, retention, expansion, and monetization, ideally within self-service, freemium, subscription, or consumption-based products
- Background in engineering (computer science, electrical, software)
- Strategic Vision & Creativity - A track record of crafting innovative growth strategies that expand market reach and build long-term product differentiation
- Influential Leadership - Ability to lead cross-functional teams and develop your team. You’re skilled at aligning diverse stakeholders around a shared vision
- Passion for deeply understanding developer needs and delivering seamless onboarding, education, adoption and product experiences
- Familiarity with open-source software, self-service, subscription, and consumption based cloud models
- Excellent written and verbal communication skills — you’ll need to distill complex product ideas, rally teams, and evangelize new growth initiatives across the org
- Data-driven and business-minded — you can define meaningful growth metrics, interpret funnel and usage behavior, evaluate experiments, and connect product decisions to key metrics
- Strong research and analytical skills with the ability to identify insights, uncover opportunities, and translate findings into actionable strategies
- Experience building programmatic product experiences with a deep understanding of developer-centric requirements, including IAM, integrations, and automation use cases
- Experience with how to leverage UI/UX design and/or user research teams
- Familiarity with AI/ML products or cloud-based platforms like AWS, GCP, or Azure. Comfort using AI-native tools and workflows to accelerate research, experimentation, prototyping, and product decision-making is a plus
Note: Some bullets have hyphen and then description. We'll keep as is.
Now Benefits section:
Benefits
with - list:
- equity
- participation in the employee stock purchase program
- flexible paid time off
- 20 weeks fully-paid gender-neutral parental leave
- fertility and adoption assistance
- 401(k) plan
- mental health counseling
- access to transgender-inclusive health insurance coverage
- health benefits offerings
We could also include note about US-based only, but that's a note; we could include as a
after list.
Pay section:
Pay
with containing the prose about salary range and note about compensation uniqueness.
We could also include the note: "Please note, the base salary range listed below and the benefits in this paragraph are only applicable to U.S.-based candidates." That's a note about both pay and benefits; we could put it in a
after the list.
Now About MongoDB description: we can include as a
without heading, or maybe under a heading like "About MongoDB" but not in allowed list. Safer to just include as a
.
We must not include any boilerplate like "MongoDB is committed to providing any necessary accommodations..." etc. Also remove REQ ID line.
Now ensure we don't repeat the job title as a heading. Already we are not.
Now output only HTML fragment.
Let's craft:
About the role
We’re looking for a Senior Director of Product Management to help define and drive our next phase of growth. Our team owns the end-to-end product-led growth journey, from developer acquisition and onboarding through activation, adoption, monetization, retention, expansion, and sales handoffs. We use customer insight, data, and experimentation to reduce friction, accelerate time-to-value, grow revenue, and increase long-term customer value. This is a high-impact, strategic role that requires strong leadership, creativity, strong product
for prose. We must not invent or summarize away detail. Must not include placeholder text. We need to ensure we don't include headings with empty content. Let's extract: About the role paragraph: "We’re looking for a Senior Director of Product Management to help define and drive our next phase of growth. Our team owns the end-to-end product-led growth journey, from developer acquisition and onboarding through activation, adoption, monetization, retention, expansion, and sales handoffs. We use customer insight, data, and experimentation to reduce friction, accelerate time-to-value, grow revenue, and increase long-term customer value. This is a high-impact, strategic role that requires strong leadership, creativity, strong product sense, and the ability to mentor a team of high-performing Product Managers. You’ll be expected to lead your team, but also influence across the Product and Technology and Marketing teams, build cross-functional relationships, and elevate the team’s overall strategic thinking and execution." That's the About the role section. Responsibilities (What You’ll Do): list of bullet points (though they are sentences separated by line breaks). We need to convert each sentence into
for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). It implies we should use those headings for sections. It doesn't say we cannot add other headings, but likely we should stick to those. However we need to preserve all substantive information. The "About MongoDB" paragraph is substantive. Where to put it? Could be placed under a generic
without a heading? The instruction says: 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 having prose without a heading. So we can include a
for the About MongoDB description without a heading, or we could put it under a heading like "About MongoDB" but that's not in the list. Safer to just include as a
without a heading.
Similarly, the compensation and benefits paragraph: we need to extract Pay and Benefits sections.
Pay: "MongoDB’s base salary range for this role in the U.S. is: $162,000—$319,000 USD". Also earlier: "MongoDB’s base salary range for this role is posted below. Compensation at the time of offer is unique to each candidate and based on a variety of factors such as skill set, experience, qualifications, and work location. Salary is one part of MongoDB’s total compensation and benefits package." That's prose about pay. We can include that in Pay section.
Benefits: list: "Other benefits for eligible employees may include: equity, participation in the employee stock purchase program, flexible paid time off, 20 weeks fully-paid gender-neutral parental leave, fertility and adoption assistance, 401(k) plan, mental health counseling, access to transgender-inclusive health insurance coverage, and health benefits offerings." Also note: "Please note, the base salary range listed below and the benefits in this paragraph are only applicable to U.S.-based candidates." That's a note.
We should include Benefits section with a
- list of benefits.
We should not include the REQ ID, EEO, accommodations, etc.
We should not include duplicated lines.
Now, we need to decide on headings:
-
About the role
with the intro paragraph.
- Responsibilities
with - list.
-
Requirements
maybe combine qualifications and skills. But we have a long list that includes experience, background, strategic vision, leadership, passion, familiarity, communication, data-driven, research, programmatic product experiences, UI/UX, AI/ML, etc. Could split into Requirements (experience, background) and Skills (specific abilities). But we can keep as one Requirements section with a - list.
Alternatively, we could have Requirements and Skills separate. But guidelines: prefer a few substantive sections over many thin ones. Having one Requirements section with all the bullet points is fine.
Thus:
Requirements
with - list.
We need to extract each bullet from "What We Look For". Let's list them:
- Passion for MongoDB with a strong understanding of software engineering concepts and the developer audience
- 10+ years of Product Management experience, including 4+ years leading Product-Led Growth, Growth Product, or adjacent self-service growth motions at SaaS, cloud or developer-centric companies
- Deep understanding of product-led growth mechanics across acquisition, onboarding, activation, retention, expansion, and monetization, ideally within self-service, freemium, subscription, or consumption-based products
- Background in engineering (computer science, electrical, software)
- Strategic Vision & Creativity - A track record of crafting innovative growth strategies that expand market reach and build long-term product differentiation
- Influential Leadership - Ability to lead cross-functional teams and develop your team. You’re skilled at aligning diverse stakeholders around a shared vision
- Passion for deeply understanding developer needs and delivering seamless onboarding, education, adoption and product experiences
- Familiarity with open-source software, self-service, subscription, and consumption based cloud models
- Excellent written and verbal communication skills — you’ll need to distill complex product ideas, rally teams, and evangelize new growth initiatives across the org
- Data-driven and business-minded — you can define meaningful growth metrics, interpret funnel and usage behavior, evaluate experiments, and connect product decisions to key metrics
- Strong research and analytical skills with the ability to identify insights, uncover opportunities, and translate findings into actionable strategies
- Experience building programmatic product experiences with a deep understanding of developer-centric requirements, including IAM, integrations, and automation use cases
- Experience with how to leverage UI/UX design and/or user research teams
- Familiarity with AI/ML products or cloud-based platforms like AWS, GCP, or Azure. Comfort using AI-native tools and workflows to accelerate research, experimentation, prototyping, and product decision-making is a plus
Note: Some bullets have hyphen and then description. We'll keep as is.
Now Benefits section:
Benefits
with - list:
- equity
- participation in the employee stock purchase program
- flexible paid time off
- 20 weeks fully-paid gender-neutral parental leave
- fertility and adoption assistance
- 401(k) plan
- mental health counseling
- access to transgender-inclusive health insurance coverage
- health benefits offerings
We could also include note about US-based only, but that's a note; we could include as a
after list.
Pay section:
Pay
with containing the prose about salary range and note about compensation uniqueness.
We could also include the note: "Please note, the base salary range listed below and the benefits in this paragraph are only applicable to U.S.-based candidates." That's a note about both pay and benefits; we could put it in a
after the list.
Now About MongoDB description: we can include as a
without heading, or maybe under a heading like "About MongoDB" but not in allowed list. Safer to just include as a
.
We must not include any boilerplate like "MongoDB is committed to providing any necessary accommodations..." etc. Also remove REQ ID line.
Now ensure we don't repeat the job title as a heading. Already we are not.
Now output only HTML fragment.
Let's craft:
About the role
We’re looking for a Senior Director of Product Management to help define and drive our next phase of growth. Our team owns the end-to-end product-led growth journey, from developer acquisition and onboarding through activation, adoption, monetization, retention, expansion, and sales handoffs. We use customer insight, data, and experimentation to reduce friction, accelerate time-to-value, grow revenue, and increase long-term customer value. This is a high-impact, strategic role that requires strong leadership, creativity, strong product
for prose. It doesn't forbid having prose without a heading. So we can include a
for the About MongoDB description without a heading, or we could put it under a heading like "About MongoDB" but that's not in the list. Safer to just include as a
without a heading. Similarly, the compensation and benefits paragraph: we need to extract Pay and Benefits sections. Pay: "MongoDB’s base salary range for this role in the U.S. is: $162,000—$319,000 USD". Also earlier: "MongoDB’s base salary range for this role is posted below. Compensation at the time of offer is unique to each candidate and based on a variety of factors such as skill set, experience, qualifications, and work location. Salary is one part of MongoDB’s total compensation and benefits package." That's prose about pay. We can include that in Pay section. Benefits: list: "Other benefits for eligible employees may include: equity, participation in the employee stock purchase program, flexible paid time off, 20 weeks fully-paid gender-neutral parental leave, fertility and adoption assistance, 401(k) plan, mental health counseling, access to transgender-inclusive health insurance coverage, and health benefits offerings." Also note: "Please note, the base salary range listed below and the benefits in this paragraph are only applicable to U.S.-based candidates." That's a note. We should include Benefits section with a
- list of benefits.
We should not include the REQ ID, EEO, accommodations, etc.
We should not include duplicated lines.
Now, we need to decide on headings:
-
About the role
with the intro paragraph. -Responsibilities
with- list.
-
Requirements
maybe combine qualifications and skills. But we have a long list that includes experience, background, strategic vision, leadership, passion, familiarity, communication, data-driven, research, programmatic product experiences, UI/UX, AI/ML, etc. Could split into Requirements (experience, background) and Skills (specific abilities). But we can keep as one Requirements section with a- list.
Alternatively, we could have Requirements and Skills separate. But guidelines: prefer a few substantive sections over many thin ones. Having one Requirements section with all the bullet points is fine.
Thus:
Requirements
with- list.
We need to extract each bullet from "What We Look For". Let's list them:
- Passion for MongoDB with a strong understanding of software engineering concepts and the developer audience
- 10+ years of Product Management experience, including 4+ years leading Product-Led Growth, Growth Product, or adjacent self-service growth motions at SaaS, cloud or developer-centric companies
- Deep understanding of product-led growth mechanics across acquisition, onboarding, activation, retention, expansion, and monetization, ideally within self-service, freemium, subscription, or consumption-based products
- Background in engineering (computer science, electrical, software)
- Strategic Vision & Creativity - A track record of crafting innovative growth strategies that expand market reach and build long-term product differentiation
- Influential Leadership - Ability to lead cross-functional teams and develop your team. You’re skilled at aligning diverse stakeholders around a shared vision
- Passion for deeply understanding developer needs and delivering seamless onboarding, education, adoption and product experiences
- Familiarity with open-source software, self-service, subscription, and consumption based cloud models
- Excellent written and verbal communication skills — you’ll need to distill complex product ideas, rally teams, and evangelize new growth initiatives across the org
- Data-driven and business-minded — you can define meaningful growth metrics, interpret funnel and usage behavior, evaluate experiments, and connect product decisions to key metrics
- Strong research and analytical skills with the ability to identify insights, uncover opportunities, and translate findings into actionable strategies
- Experience building programmatic product experiences with a deep understanding of developer-centric requirements, including IAM, integrations, and automation use cases
- Experience with how to leverage UI/UX design and/or user research teams
- Familiarity with AI/ML products or cloud-based platforms like AWS, GCP, or Azure. Comfort using AI-native tools and workflows to accelerate research, experimentation, prototyping, and product decision-making is a plus
Note: Some bullets have hyphen and then description. We'll keep as is.
Now Benefits section:
Benefits
with- list:
- equity
- participation in the employee stock purchase program
- flexible paid time off
- 20 weeks fully-paid gender-neutral parental leave
- fertility and adoption assistance
- 401(k) plan
- mental health counseling
- access to transgender-inclusive health insurance coverage
- health benefits offerings
We could also include note about US-based only, but that's a note; we could include as a
after list. Pay section:
Pay
withcontaining the prose about salary range and note about compensation uniqueness. We could also include the note: "Please note, the base salary range listed below and the benefits in this paragraph are only applicable to U.S.-based candidates." That's a note about both pay and benefits; we could put it in a
after the list. Now About MongoDB description: we can include as a
without heading, or maybe under a heading like "About MongoDB" but not in allowed list. Safer to just include as a
. We must not include any boilerplate like "MongoDB is committed to providing any necessary accommodations..." etc. Also remove REQ ID line. Now ensure we don't repeat the job title as a heading. Already we are not. Now output only HTML fragment. Let's craft:
About the role
We’re looking for a Senior Director of Product Management to help define and drive our next phase of growth. Our team owns the end-to-end product-led growth journey, from developer acquisition and onboarding through activation, adoption, monetization, retention, expansion, and sales handoffs. We use customer insight, data, and experimentation to reduce friction, accelerate time-to-value, grow revenue, and increase long-term customer value. This is a high-impact, strategic role that requires strong leadership, creativity, strong product
- list:
- equity
- participation in the employee stock purchase program
- flexible paid time off
- 20 weeks fully-paid gender-neutral parental leave
- fertility and adoption assistance
- 401(k) plan
- mental health counseling
- access to transgender-inclusive health insurance coverage
- health benefits offerings
We could also include note about US-based only, but that's a note; we could include as a
- list.
We need to extract each bullet from "What We Look For". Let's list them:
- Passion for MongoDB with a strong understanding of software engineering concepts and the developer audience
- 10+ years of Product Management experience, including 4+ years leading Product-Led Growth, Growth Product, or adjacent self-service growth motions at SaaS, cloud or developer-centric companies
- Deep understanding of product-led growth mechanics across acquisition, onboarding, activation, retention, expansion, and monetization, ideally within self-service, freemium, subscription, or consumption-based products
- Background in engineering (computer science, electrical, software)
- Strategic Vision & Creativity - A track record of crafting innovative growth strategies that expand market reach and build long-term product differentiation
- Influential Leadership - Ability to lead cross-functional teams and develop your team. You’re skilled at aligning diverse stakeholders around a shared vision
- Passion for deeply understanding developer needs and delivering seamless onboarding, education, adoption and product experiences
- Familiarity with open-source software, self-service, subscription, and consumption based cloud models
- Excellent written and verbal communication skills — you’ll need to distill complex product ideas, rally teams, and evangelize new growth initiatives across the org
- Data-driven and business-minded — you can define meaningful growth metrics, interpret funnel and usage behavior, evaluate experiments, and connect product decisions to key metrics
- Strong research and analytical skills with the ability to identify insights, uncover opportunities, and translate findings into actionable strategies
- Experience building programmatic product experiences with a deep understanding of developer-centric requirements, including IAM, integrations, and automation use cases
- Experience with how to leverage UI/UX design and/or user research teams
- Familiarity with AI/ML products or cloud-based platforms like AWS, GCP, or Azure. Comfort using AI-native tools and workflows to accelerate research, experimentation, prototyping, and product decision-making is a plus
Note: Some bullets have hyphen and then description. We'll keep as is.
Now Benefits section:
- list.
Alternatively, we could have Requirements and Skills separate. But guidelines: prefer a few substantive sections over many thin ones. Having one Requirements section with all the bullet points is fine.
Thus:
- list.
-