Staff Product Manager - dbt v2
Fivetran · Oakland, CA · 1 mo ago
RemoteRemoteMarketing$227k–$283k/yrFull-time
We need to output HTML fragment with sections: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. Only include sections that have real specific content. We need to parse the posting.
The posting includes:
- About Us (intro) but not needed as heading? The instruction: use for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). So we need to map content to those headings. The posting has "About The Role" (that's similar to About the role). Then bullet list of responsibilities? Actually after "About The Role" there is description: "We're hiring a Product Manager to lead the dbt v2 roadmap..." then bullet list of responsibilities (starting with "In this role, you will Own and deliver...").
Then "What Success Looks Like" could be considered responsibilities? Or maybe it's more about expectations. Could treat as responsibilities.
Then "You're a good fit if you have ..." that's qualifications/requirements.
Then "Nice to have" could be skills or qualifications.
Then compensation range: Pay Range.
Then "Perks And Benefits": list of benefits.
Schedule not mentioned.
Thus we will include sections: About the role, Responsibilities, Requirements (or Qualifications?), Skills, Benefits, Pay. Possibly also Qualifications separate from Requirements? The instruction list includes both Requirements and Qualifications. We need to decide where to put content. Typically Requirements = mandatory qualifications; Qualifications = maybe nice-to-have? But we have "You're a good fit if you have ..." (mandatory) and "Nice to have ..." (preferred). So we can map mandatory to Requirements, nice-to-have to Qualifications or Skills. Skills could be separate for technical skills. But we can also put nice-to-have under Qualifications.
We need to avoid filler like "commensurate with experience". Not present.
We must not repeat job title as heading. Not include Job ID.
We must remove boilerplate like EEO etc. We'll strip those.
We need to preserve all substantive information.
Let's extract content.
About Us paragraphs: Could be considered "About the role"? Actually "About The Role" is a heading in the posting. We'll use that content under About the role section.
Content under About The Role:
"We're hiring a Product Manager to lead the dbt v2 roadmap — the future of dbt Labs' intellectual property and a critical driver of product-led growth. You will own net-new functionality in Fusion that identifies and monetizes local deployments of dbt, shipping net new features, many of which also land in dbt Core, as well as proprietary ELv2 plugins that integrate seamlessly with the dbt platform. This role is co-located with our dbt v2 engineering team in the US to accelerate execution, strengthen prioritization, and ensure tight alignment across product, engineering, and platform teams. You'll bridge open source product strategy with technical delivery and business impact, translating strategic investments into shipped features that drive the Fusion PLG motion."
Then bullet list after "In this role, you will": Actually the bullet list is:
- Own and deliver the dbt v2 roadmap, shipping net new functionality to dbt v2 like SQL comprehension, compute, governance, and SAO
- Define requirements for Fusion features that integrate seamlessly with the dbt platform and unlock enterprise value
- Keep the Fusion engineering team aligned, unblocked, and executing on a predictable cadence
- Contribute hands-on to the dbt Core / Fusion codebases, including code reviews, documentation, and small feature implementations
- Collaborate with OSS strategy leads, platform PM peers, and cross-functional stakeholders to deliver a unified roadmap
That seems responsibilities.
Then "What Success Looks Like" bullet list:
- Shipping net-new features on a predictable quarterly cadence
- Measurable contribution to Fusion PLG growth metrics, including identification and monetization of local dbt deployments
- Hands-on contributions to dbt Core and Fusion code bases, including merged PRs and meaningful improvements to the open source codebase
- Strong execution and alignment across the Fusion engineering team
These could also be responsibilities or expectations; we can include under Responsibilities as well.
Then "You're a good fit if you have ..." bullet list:
- 5+ years of product management experience in technical domains such as developer tooling, data platforms, or open source software
- Strong grasp of system architectures, particularly for local deployments and how they scale to enterprise use cases
- Understanding of how open source investments drive PLG growth and product strategy
- Ability to bridge technical delivery with business impact, translating features into revenue and growth metrics
- Experience working with engineering teams to define, prioritize, and ship complex technical features
- Strong communication skills with empathy for open source contributors and enterprise users alike
These are requirements/qualifications.
Then "Nice to have" bullet list:
- Hands-on experience with dbt or similar transformation frameworks
- Background in plugin architectures, extensibility systems, or platform ecosystems
- Understanding of PLG motions and freemium-to-paid conversion strategies
- Experience with SQL engines, query optimization, or compute systems
- Prior experience as an engineer whose worked with modern development frameworks (examples: React, Typescript, Python, etc.)
These could be skills or qualifications.
Then Pay Range: "$226,657—$283,322 USD" and also Oakland Pay Range "$243,936—$304,920 USD". There's duplication: first generic range then Oakland specific. We need to preserve all substantive info. Could present both: maybe note that range varies by location; include both.
Then Benefits list:
- 100% employer-paid medical insurance
- Generous paid time-off policy (PTO), plus paid sick time, inclusive parental leave policy, holidays (including a year end Global Week of Rest), and volunteer days off
- RSU stock grants*
- Professional development and training opportunities
- Company virtual happy hours, free food, and fun team-building activities
- Monthly cell phone stipend
- Access to an innovative mental health support platform that offers personalized care and resources in areas such as: therapy, coaching, and self-guided mindfulness exercises for all covered employees and their covered dependents.
- *May vary by country and worker type - please reach out to your recruiter for more information
Also a line: "Click here to learn more about Fivetran's Benefits by Region." That's a link; we may drop as it's navigation? It's a link to learn more; maybe considered boilerplate? It's not exactly navigation but it's a call to action; but we might keep as part of benefits? Probably drop as it's a link. The instruction: remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. This link is not exactly navigation but could be considered navigation; safer to drop.
Also there is a paragraph about valuation, core values, etc. That's boilerplate? It's about company culture; could be considered "About Us" but not required sections. We can drop as not part of required headings.
Also there is a paragraph about diversity etc. Drop.
Also there is a paragraph about candidate privacy policy, accommodations, etc. That's legal/EEO; drop.
Thus final HTML:
for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). So we need to map content to those headings. The posting has "About The Role" (that's similar to About the role). Then bullet list of responsibilities? Actually after "About The Role" there is description: "We're hiring a Product Manager to lead the dbt v2 roadmap..." then bullet list of responsibilities (starting with "In this role, you will Own and deliver...").
Then "What Success Looks Like" could be considered responsibilities? Or maybe it's more about expectations. Could treat as responsibilities.
Then "You're a good fit if you have ..." that's qualifications/requirements.
Then "Nice to have" could be skills or qualifications.
Then compensation range: Pay Range.
Then "Perks And Benefits": list of benefits.
Schedule not mentioned.
Thus we will include sections: About the role, Responsibilities, Requirements (or Qualifications?), Skills, Benefits, Pay. Possibly also Qualifications separate from Requirements? The instruction list includes both Requirements and Qualifications. We need to decide where to put content. Typically Requirements = mandatory qualifications; Qualifications = maybe nice-to-have? But we have "You're a good fit if you have ..." (mandatory) and "Nice to have ..." (preferred). So we can map mandatory to Requirements, nice-to-have to Qualifications or Skills. Skills could be separate for technical skills. But we can also put nice-to-have under Qualifications.
We need to avoid filler like "commensurate with experience". Not present.
We must not repeat job title as heading. Not include Job ID.
We must remove boilerplate like EEO etc. We'll strip those.
We need to preserve all substantive information.
Let's extract content.
About Us paragraphs: Could be considered "About the role"? Actually "About The Role" is a heading in the posting. We'll use that content under About the role section.
Content under About The Role:
"We're hiring a Product Manager to lead the dbt v2 roadmap — the future of dbt Labs' intellectual property and a critical driver of product-led growth. You will own net-new functionality in Fusion that identifies and monetizes local deployments of dbt, shipping net new features, many of which also land in dbt Core, as well as proprietary ELv2 plugins that integrate seamlessly with the dbt platform. This role is co-located with our dbt v2 engineering team in the US to accelerate execution, strengthen prioritization, and ensure tight alignment across product, engineering, and platform teams. You'll bridge open source product strategy with technical delivery and business impact, translating strategic investments into shipped features that drive the Fusion PLG motion."
Then bullet list after "In this role, you will": Actually the bullet list is:
- Own and deliver the dbt v2 roadmap, shipping net new functionality to dbt v2 like SQL comprehension, compute, governance, and SAO
- Define requirements for Fusion features that integrate seamlessly with the dbt platform and unlock enterprise value
- Keep the Fusion engineering team aligned, unblocked, and executing on a predictable cadence
- Contribute hands-on to the dbt Core / Fusion codebases, including code reviews, documentation, and small feature implementations
- Collaborate with OSS strategy leads, platform PM peers, and cross-functional stakeholders to deliver a unified roadmap
That seems responsibilities.
Then "What Success Looks Like" bullet list:
- Shipping net-new features on a predictable quarterly cadence
- Measurable contribution to Fusion PLG growth metrics, including identification and monetization of local dbt deployments
- Hands-on contributions to dbt Core and Fusion code bases, including merged PRs and meaningful improvements to the open source codebase
- Strong execution and alignment across the Fusion engineering team
These could also be responsibilities or expectations; we can include under Responsibilities as well.
Then "You're a good fit if you have ..." bullet list:
- 5+ years of product management experience in technical domains such as developer tooling, data platforms, or open source software
- Strong grasp of system architectures, particularly for local deployments and how they scale to enterprise use cases
- Understanding of how open source investments drive PLG growth and product strategy
- Ability to bridge technical delivery with business impact, translating features into revenue and growth metrics
- Experience working with engineering teams to define, prioritize, and ship complex technical features
- Strong communication skills with empathy for open source contributors and enterprise users alike
These are requirements/qualifications.
Then "Nice to have" bullet list:
- Hands-on experience with dbt or similar transformation frameworks
- Background in plugin architectures, extensibility systems, or platform ecosystems
- Understanding of PLG motions and freemium-to-paid conversion strategies
- Experience with SQL engines, query optimization, or compute systems
- Prior experience as an engineer whose worked with modern development frameworks (examples: React, Typescript, Python, etc.)
These could be skills or qualifications.
Then Pay Range: "$226,657—$283,322 USD" and also Oakland Pay Range "$243,936—$304,920 USD". There's duplication: first generic range then Oakland specific. We need to preserve all substantive info. Could present both: maybe note that range varies by location; include both.
Then Benefits list:
- 100% employer-paid medical insurance
- Generous paid time-off policy (PTO), plus paid sick time, inclusive parental leave policy, holidays (including a year end Global Week of Rest), and volunteer days off
- RSU stock grants*
- Professional development and training opportunities
- Company virtual happy hours, free food, and fun team-building activities
- Monthly cell phone stipend
- Access to an innovative mental health support platform that offers personalized care and resources in areas such as: therapy, coaching, and self-guided mindfulness exercises for all covered employees and their covered dependents.
- *May vary by country and worker type - please reach out to your recruiter for more information
Also a line: "Click here to learn more about Fivetran's Benefits by Region." That's a link; we may drop as it's navigation? It's a link to learn more; maybe considered boilerplate? It's not exactly navigation but it's a call to action; but we might keep as part of benefits? Probably drop as it's a link. The instruction: remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. This link is not exactly navigation but could be considered navigation; safer to drop.
Also there is a paragraph about valuation, core values, etc. That's boilerplate? It's about company culture; could be considered "About Us" but not required sections. We can drop as not part of required headings.
Also there is a paragraph about diversity etc. Drop.
Also there is a paragraph about candidate privacy policy, accommodations, etc. That's legal/EEO; drop.
Thus final HTML:
About the role
We're hiring a Product Manager to lead the dbt v2 roadmap — the future of dbt Labs' intellectual property and a critical driver of product-led growth. You will own net-new functionality in Fusion that identifies and monetizes local deployments of dbt, shipping net new features, many of which also land in dbt Core, as well as proprietary ELv2 plugins that integrate seamlessly with the dbt platform. This role is co-located with our dbt v2 engineering team in the US to accelerate execution, strengthen prioritization, and ensure tight alignment across product, engineering, and platform teams. You'll bridge open source product strategy with technical delivery and business impact, translating strategic investments into shipped features that drive the Fusion PLG motion.
Responsibilities
- Own and deliver the dbt v2 roadmap, shipping net new functionality to dbt v2 like SQL comprehension, compute, governance, and SAO
- Define requirements for Fusion features that integrate seamlessly with the dbt platform and unlock enterprise value
- Keep the Fusion engineering team aligned, unblocked, and executing on a predictable cadence
- Contribute hands-on to the dbt Core / Fusion codebases, including code reviews, documentation, and small feature implementations
- Collaborate with OSS strategy leads, platform PM peers, and cross-functional stakeholders to deliver a unified roadmap
- Shipping net-new features on a predictable quarterly cadence
- Measurable contribution to Fusion PLG growth metrics, including identification and monetization of local dbt deployments
- Hands-on contributions to dbt Core and Fusion code bases, including merged PRs and meaningful improvements to the open source codebase
- Strong execution and alignment across the Fusion engineering team
Requirements
- 5+ years of product management experience in technical domains such as developer tooling, data platforms, or open source software
- Strong grasp of system architectures, particularly for local deployments and how they scale to enterprise use cases
- Understanding of how open source investments drive PLG growth and product strategy
- Ability to bridge technical delivery with business impact, translating features into revenue and growth metrics
- Experience working with engineering teams to define, prioritize, and ship complex technical features
- Strong communication skills with empathy for open source contributors and enterprise users alike
Qualifications
- Hands-on experience with dbt or similar transformation frameworks
- Background in plugin architectures, extensibility systems, or platform ecosystems
- Understanding of PLG motions and freemium-to-paid conversion strategies
- Experience with SQL engines, query optimization, or compute systems
- Prior experience as an engineer who has worked with modern development frameworks (examples: React, Typescript, Python, etc.)
Benefits
- 100% employer-paid medical insurance
- Generous paid time-off policy (PTO), plus paid sick time, inclusive parental leave policy, holidays (including a year end Global Week of Rest), and volunteer days off
- RSU stock grants*
- Professional development and training opportunities
- Company virtual happy hours, free food, and fun team-building activities
- Monthly cell phone stipend
- Access to an innovative mental health support platform that offers personalized care and resources in areas such as: therapy, coaching, and self-guided mindfulness exercises for all covered employees and their covered dependents.
Pay
The compensation range displayed on this job posting reflects the minimum and maximum target for new hire compensation for the target position and level, and may include sales incentives or target bonuses depending on the role. Our compensation ranges are determined by role, level, and location. Our job titles may span more than one career level. Within the range, individual compensation is determined by additional factors, including job-related skills, experience, relevant education or training, business need, market demands. The compensation range is subject to change and may be modified in the future. Your recruiter can share more about the specific compensation range for your location during the hiring process.
Pay Range $226,657—$283,322 USD
Oakland Pay Range $243,936—$304,920 USD
We should not include Schedule section as not present. We need to ensure we didn't include any boilerplate like duplicated