Technical Product Manager

Overview At FlowFuse, the Technical Product Manager (TPM) bridges product strategy and technical execution. They turn complex technical challenges into measurable product outcomes, ensuring engineering delivers solutions that meet customer needs and quality standards. This role blends technical depth and product acumen. The TPM dives into architecture, weighs trade-offs, and uses data to guide decisions on debt, scalability, and performance. The Technical Product Manager reports to the Director of Product and is primarily responsible for: Bridging strategy and execution: Translate product strategy into clear, measurable technical outcomes and objectives. Defining requirements: Partner with engineering to balance user needs, feasibility, and business impact. Delivering outcomes: Set success metrics/KPIs, measure progress, and connect decisions to results. Own metrics: Define, track, and report adoption, performance, reliability, and business impact. Plan sprints and releases: Align roadmap, priorities, debt, and infrastructure with product strategy. Shape specs/architecture: Co-create technical specs and provide architectural input. Translate across teams: Bridge product, engineering, sales, and customer success. Prioritize with data: Use usage data, customer feedback, and capacity signals. Assess feasibility: Evaluate complexity, approaches, and technical risk. Advocate quality: Set and monitor quality, performance, and reliability targets. Writing production code or implementing features directly. Managing engineers or individual performance. Final technical architecture decisions (owned by CTO/engineering leadership). We believe setting clear expectations enables new teammates to thrive. Here’s what success looks like in your first 90 days at FlowFuse: Primary Objective Build deep understanding of product, users, architecture, and team dynamics. Join customer calls or review recordings Trusted relationships with engineering leads Primary Objective Shape execution via alignment, backlog clarity, and problem definition. Partner with leadership and engineering to set top quarterly priorities in your swimlanes. Sprint goal alignment and dependency surfacing Clear acceptance criteria and feedback loops Ensure tickets are actionable Success Signals by Day 60 TPM drives clarity, not just observing Engineering trusts prioritization inputs Backlog is execution-ready ✅ Shared working agreement + operating rhythm ✅ Updated Epic/PRD template ✅ Engineering-ready epic(s) owned end-to-end Primary Objective Own execution: prioritize, manage backlog, and ship with engineering. Co-own priority ordering, sprint readiness, and tradeoff decisions. Drive at least one major platform or customer-facing improvement to release. Solidify operating model and learning loops. Success Signals by Day 90 TPM + engineering leads run backlog prioritization Sprint planning is outcome-driven Execution cadence is faster and clearer ✅ Backlog actively managed weekly ✅ Now / Next / Later execution view ✅ Release + feedback capture Goal By day 90, the TPM has moved from learning → alignment → execution → shared backlog ownership, with clarity on WIN priorities and active backlog management. Technical depth: Understand architecture, APIs, databases, and SDLC; low-code/Node-RED is a plus. Outcome orientation: Define KPIs and use data to drive decisions and impact. Product/engineering fluency: Comfortable with user stories and technical implementation. Strategic to tactical: Convert strategy into deliverables and milestones. Analytical: Use qualitative and quantitative inputs for prioritization. Technical communication: Translate across technical and non-technical audiences. Collaborative problem solving: Partner with engineering to find pragmatic solutions. Trade-off judgment: Balance debt, features, performance, scalability, and business priorities. Director of Product interview (45m): product, technical fit, outcomes, communication. Engineering Manager interview (30m): technical collaboration and requirements clarity. Technical case study presentation with metrics and lessons learned. Final interview (optional) with VP of Sales or stakeholder. Offer. Please note: this job description has been cleaned of non-essential boilerplate to focus on responsibilities and qualifications. #J-18808-Ljbffr