Repository navigation
Handbook: add VP of Product job description #5965
Description
Overview
Add a VP of Product page to the FlowFuse handbook under People Ops → Job Descriptions, using the supplied Google Doc as the source of truth. This is a new handbook role page.
Content
- Source: VP of Product job description
- Source last updated: 2026-10-15.
- Target file:
nuxt/content/handbook/peopleops/job-descriptions/vp-product.md. - Formatting reference: VP of Sales for leadership-role presentation and Lead Product Manager for the full section structure.
Use the current Job Descriptions conventions: a Markdown page with title front matter, one H1 role title, and H2 sections for Job Description, Skills, 90 Day Plan, and Hiring Plan. Use ordinary paragraphs and Markdown lists, with H3/H4 subsections where helpful. Preserve the supplied role scope and qualifications.
The repository now stores handbook content under nuxt/content/handbook/. Follow the existing handbook layout and sidebar behavior; do not add a new page design or a global website navigation item.
Content mapping and editorial notes
- Move “The opportunity” into
Job Descriptionand retain the CEO reporting line. - Retain all seven responsibility areas, including the Product/CTO relationship and the interface with solutions engineering and forward deployed engineering in GTM.
- Retain “What success could look like in your first year” as a subsection under
Job Description. These are first-year outcomes and must not be relabeled as the 90-day plan. - Map “What you bring” to
Skills, including the final paragraph about experience with customer delivery organizations. - The source does not provide a 90-day plan or hiring process. Completing those sections with the hiring owner is part of this issue.
- The source's location preference (“United States preferred; Western Europe considered”) is specific to the current hire. Keep it in the recruiting source/job posting, consistent with the handbook convention that geographic requirements may live in Greenhouse.
- Add a separate page; do not replace or change the existing Product Manager or Lead Product Manager roles.
Handbook content draft
The draft below preserves the supplied role content while applying the handbook structure. HTML comments identify missing content to resolve during implementation. Do not publish those comments, empty sections, or invented hiring commitments.
Expand the Markdown page draft
---
title: "VP of Product"
---
# VP of Product
## Job Description
The VP of Product reports to the CEO.
FlowFuse is building software that helps manufacturers and other industrial enterprises solve operational problems and scale those solutions across their businesses.
We are looking for a VP of Product to lead our next stage of product development. As our most senior product leader, you will own the product vision, strategy, and roadmap, building on our existing platform to define how new capabilities, modules, and products fit together.
This role requires both a clear view of where industrial software is going and the judgment to translate that vision into practical investment decisions. You will work directly with customers, our CTO and engineering team, and the solutions engineers and forward deployed engineers within our go-to-market organization.
### Product vision and strategy
Define a compelling direction for FlowFuse’s platform and product portfolio. Identify the enterprise customer problems we are best positioned to solve, establish priorities, and connect near-term delivery to a coherent long-term strategy.
### Product architecture and portfolio development
Determine how new features, modules, and products extend the existing platform. Partner with the CTO to establish shared capabilities, clear product boundaries, and extension points that support both reusable products and customer-specific solutions. Make deliberate decisions about what to build, integrate, or support through partners.
### Partnership with Engineering
Work closely with the CTO and engineering team to turn product strategy into well-defined, achievable plans. Bring clear customer problems, business context, and priorities, and involve engineers early in discovery and solution design. Make tradeoffs together around scope, sequencing, technical investment, and delivery commitments. Establish a shared understanding of success while giving Engineering the context and autonomy to determine how solutions are built.
### The connection between field delivery and product development
Establish a close working relationship with solutions engineering and forward deployed engineering within GTM. Use customer deployments to uncover recurring needs and test product opportunities. Own product investment decisions informed by customer value, repeatability, strategic fit, delivery effort, and ongoing maintenance.
Define a practical path for moving successful field-developed capabilities into supported products, including ownership, documentation, and lifecycle expectations.
### Enterprise customer needs
Build a deep understanding of how large industrial companies evaluate, deploy, govern, and expand software. Translate the needs of operational users, IT and OT teams, and executive buyers into product priorities. Account for integration, security, reliability, deployment flexibility, and rollout across multiple sites.
### Roadmap and execution
Turn strategy into a focused roadmap with clear outcomes and tradeoffs. Work closely with engineering to scope and deliver meaningful improvements, validate adoption, and adjust priorities as evidence develops.
### Commercial alignment and product leadership
Partner with the CEO and GTM leadership on positioning, packaging, and expansion opportunities. Build the product practices and team needed as the company grows, while remaining directly involved in discovery, product decisions, and delivery.
### What success could look like in your first year
* A clear product vision and portfolio strategy that guides investment decisions across the company.
* An agreed direction for extending the existing platform through shared capabilities, modules, and products.
* A consistent process for evaluating field-developed solutions and deciding what becomes supported product.
* Delivery of priority capabilities validated with enterprise customers and reused across deployments.
* Evidence that customers and field teams can deliver and expand solutions with less repeated development effort.
* Product measures that connect adoption and customer outcomes to deployment effort, reuse, and enterprise expansion.
## Skills
* Experience leading enterprise software products for manufacturing or other industrial markets, with a strong understanding of operational environments and complex buying organizations.
* A track record of evolving an established platform and building multiple products or solutions on shared foundations.
* The technical fluency to make informed product architecture decisions with engineering leadership, including tradeoffs around extensibility, integration, deployment, and maintainability.
* Evidence of turning customer-specific requirements into reusable capabilities adopted across customers.
* Strong commercial judgment about where standardization creates value and where customer-specific development remains appropriate.
* Experience guiding enterprise deployments from an initial use case toward broader adoption across teams, facilities, or business units.
* The ability to articulate a long-term vision, make difficult prioritization decisions, and remain close to day-to-day product work.
* Experience building and leading product teams, with the willingness to operate hands-on as the function develops.
Experience working directly with forward deployed engineers, solutions engineers, or a comparable customer delivery organization is particularly valuable. We are interested in the decisions you made together and the products that resulted.
## 90 Day Plan
<!-- Complete with the hiring owner before publication. The source has first-year outcomes, not a 90-day plan. -->
## Hiring Plan
<!-- Complete with the hiring owner before publication. The source does not define the interview process. -->Visuals
Use the existing handbook page template. No new illustrations, screenshots, buttons, or custom layout are required.
Proposed URL slug
/handbook/peopleops/job-descriptions/vp-product/
Include in main navigation?
No.
Navigation section
Handbook → People Ops → Job Descriptions. Ensure the new page appears in the existing handbook sidebar, using the current navigation mechanism.
Notes
Acceptance criteria
- Add the new Markdown page at the target path with the correct front matter and role title.
- Preserve the supplied responsibilities, requirements and role boundaries, allowing the documented formatting and copy corrections.
- Complete the role-specific 90-day plan and any missing hiring-plan details with the hiring owner before publication. Do not infer these from another role or treat first-year outcomes as a 90-day plan.
- Match the existing handbook hierarchy, typography, lists, breadcrumbs, table of contents and sidebar navigation.
- Retain the CEO reporting line and all first-year success outcomes; leave the existing Product Manager and Lead Product Manager pages unchanged.
- Verify the page and navigation links in the site preview and run the repository's applicable content/build checks.
- Remove implementation-only comments and ensure no empty sections or unresolved placeholders are published.
Activity
MichaelBDavis commentedon Oct 20, 2026
Superseded by draft PR #5967. The handbook page, remaining 90-day and hiring-plan details, and review are now tracked in that PR. Closing this separate tracking issue as requested.