Job Opportunities API

The Lead Product Manager owns one area of the FlowFuse product outright and runs it end to end: vision, roadmap, backlog, prioritization, sprint sequencing, refinement, and the GitHub issues engineers build from. The area of ownership is assigned based on company priorities and can shift over time. It may be Certified Nodes and the protocols that connect customers to their industrial systems (OPC UA, S7, MQTT), the core platform, the infrastructure underneath it, or how FlowFuse applies AI for its users. The shape of the role stays constant regardless of the area: a single owner who lives in their domain and runs it like it's theirs. This role builds on the  code]:outline-0 [&>code]:border-dashed hover:[&>code]:border-primary hover:[&>code]:text-primary focus-visible:[&>code]:border-primary focus-visible:[&>code]:text-primary transition-colors [&>code]:transition-colors" href="https://flowfuse.com/handbook/peopleops/job-descriptions/product-manager/">Product Manager  role. Where the base role defines product strategy across FlowFuse, the Lead Product Manager applies that craft with full ownership of a single area, working hands-on and directly with engineers. The Lead Product Manager is primarily responsible for: ul]:my-0">Continuous Discovery: Sitting in on sales and customer calls, reviewing call recordings, and talking to users directly to find the problem behind each request. The Lead PM develops deep knowledge of FlowFuse customers and the industrial IoT domain, and keeps that knowledge current. ul]:my-0">Owning the Area Roadmap: Holding the one-to-three-year view for their area and breaking it into work that ships in the current sprint. ul]:my-0">Running the Area Day to Day: Triaging the backlog and incoming ideas, prioritizing, sequencing, and moving work into sprints. ul]:my-0">Writing Exacting Specifications: Producing precise, technical, unambiguous GitHub issues. Engineers should never have to guess what "done" means. There is no PM/designer/engineer trio at FlowFuse; the Lead PM writes the spec and the ticket, and what they write is what gets built. ul]:my-0">Running Refinement with Their Engineering Squad: Arriving prepared, making product calls within their area, and unblocking the team quickly. ul]:my-0">Filtering and Translating Input: Leadership, peers, and active customer deals generate ideas at high volume. The Lead PM absorbs that input, turns it into a clear and sequenced plan, and protects their engineering team's focus. The Lead Product Manager reports to the Engineering Manager. a]:focus-visible:outline-primary [&>a>code]:border-dashed hover:[&>a>code]:border-primary hover:[&>a>code]:text-primary [&>a>code]:text-lg/6 [&>a>code]:font-bold [&>a>code]:transition-colors"> What is the Lead Product Manager not responsible for? The base  code]:outline-0 [&>code]:border-dashed hover:[&>code]:border-primary hover:[&>code]:text-primary focus-visible:[&>code]:border-primary focus-visible:[&>code]:text-primary transition-colors [&>code]:transition-colors" href="https://flowfuse.com/handbook/peopleops/job-descriptions/product-manager/">Product Manager  exclusions apply, with the following clarifications: ul]:my-0">People management: The Lead PM leads product decisions and runs refinement for their squad, but does not manage the engineers implementing the work. Building and managing a product team is a potential growth path for this role, not part of the starting scope. ul]:my-0">Technical decisions on how the product is built or architected. ul]:my-0">Effort estimations, the Lead Product Manager provides effort estimation when creating issues. However, the DRI for this process is the CTO. a]:focus-visible:outline-primary [&>a>code]:border-dashed hover:[&>a>code]:border-primary hover:[&>a>code]:text-primary [&>a>code]:text-xl/7 [&>a>code]:font-bold [&>a>code]:tra