From 0edb7c3a6688a089b85e22f49c0c7e46b0345c42 Mon Sep 17 00:00:00 2001 From: "copilot-swe-agent[bot]" <198982749+Copilot@users.noreply.github.com> Date: Mon, 2 Feb 2026 16:19:02 +0000 Subject: [PATCH 1/6] Initial plan From ea2e06a4b3b53a15ba2fa314710993ffc90aab77 Mon Sep 17 00:00:00 2001 From: "copilot-swe-agent[bot]" <198982749+Copilot@users.noreply.github.com> Date: Mon, 2 Feb 2026 16:27:28 +0000 Subject: [PATCH 2/6] Add comprehensive 90-day plan to TPM job description Co-authored-by: lbeau <7562049+lbeau@users.noreply.github.com> --- .../technical-product-manager.md | 165 ++++++++++++++++++ 1 file changed, 165 insertions(+) create mode 100644 src/handbook/peopleops/job-descriptions/technical-product-manager.md diff --git a/src/handbook/peopleops/job-descriptions/technical-product-manager.md b/src/handbook/peopleops/job-descriptions/technical-product-manager.md new file mode 100644 index 0000000000..9e5f976df1 --- /dev/null +++ b/src/handbook/peopleops/job-descriptions/technical-product-manager.md @@ -0,0 +1,165 @@ +--- +navTitle: Technical Product Manager +navGroup: Job Descriptions +--- + +# Technical Product Manager + +## Job Description + +At FlowFuse, the Technical Product Manager (TPM) is the critical bridge between product strategy and technical execution. This individual is a technology-savvy product leader who translates complex technical challenges into concrete product outcomes while ensuring engineering teams deliver solutions that meet both customer needs and technical excellence standards. The TPM isn't just managing features; they're architecting measurable outcomes that directly drive product success and team performance. + +This role demands a unique blend of technical depth and product acumen. The Technical Product Manager must be comfortable diving deep into technical architecture, understanding engineering trade-offs, and making data-driven decisions about technical debt, scalability, and performance. They are the key orchestrator who ensures product strategy translates into specific, measurable technical deliverables that propel FlowFuse's competitive advantage. + +The Technical Product Manager reports to the Director of Product and is primarily responsible for: +* Bridging Product Strategy and Technical Execution: Translating high-level product strategy into specific, measurable technical outcomes and ensuring engineering teams have clear, actionable objectives that align with business goals. +* Defining Technical Product Requirements: Working closely with engineering to define technically sound requirements that balance user needs, technical feasibility, and business impact, while making informed trade-off decisions. +* Delivering Measurable Outcomes: Establishing clear success metrics and KPIs for product initiatives, continuously measuring and communicating progress, and ensuring every technical decision contributes to quantifiable business results. + +Core Tasks and Responsibilities: +* Define and Track Technical Product Metrics: The TPM is the DRI (Directly Responsible Individual) for establishing, tracking, and reporting on key product and technical metrics that measure feature adoption, performance, reliability, and business impact. +* Technical Release Planning and Execution: The TPM collaborates closely with engineering leadership to plan releases, prioritize technical work, and ensure the engineering roadmap aligns with product strategy while managing technical debt and infrastructure needs. +* Technical Specification and Architecture Input: The TPM works with engineering to develop detailed technical specifications, provides input on architectural decisions that impact product functionality, and ensures technical solutions align with product vision. +* Cross-Functional Technical Communication: The TPM serves as the technical liaison between product, engineering, sales, and customer success, translating complex technical concepts for non-technical stakeholders and business requirements for engineering teams. +* Data-Driven Technical Prioritization: The TPM analyzes product usage data, technical metrics, customer feedback, and engineering capacity to make informed prioritization decisions about features, bugs, technical debt, and infrastructure improvements. +* Technical Feasibility Assessment: The TPM evaluates the technical feasibility and complexity of proposed features, working with engineering to understand implementation approaches, effort estimates, and potential technical risks. +* Quality and Performance Advocacy: The TPM establishes and monitors quality standards, performance benchmarks, and reliability targets, ensuring technical execution meets both customer expectations and product excellence standards. + +### What is the Technical Product Manager not responsible for? + +- Writing production code or implementing features directly. +- Managing engineers: The TPM influences technical direction but does not have direct management responsibility for engineering team members. +- Final technical architecture decisions: While the TPM provides input and influences decisions, the CTO and engineering leadership own the final technical architecture. +- Individual engineer performance management: The TPM collaborates with engineering managers on technical priorities but does not manage individual performance reviews or career development. + +## 90-Day Plan + +We believe setting clear expectations enables new teammates to thrive. Here's what success looks like in your first 90 days at FlowFuse: + +### Days 0–30: Learn, Map, Build Trust +**Theme: Context before control** + +**Primary Objective**: Establish deep understanding of FlowFuse's product, users, architecture, and team dynamics. + +#### Product + Customer Immersion +* Review product positioning and roadmap +* Understand primary personas (developers, platform teams, enterprise admins) +* Sit in on customer calls or review recordings + +**Deliverable**: ✅ FlowFuse User + Value Map + +#### Technical Architecture Familiarity +* Walk through platform components with engineering leads +* Identify areas of leverage vs fragility + +**Deliverable**: ✅ Architecture mental model + glossary + +#### Team Integration + Operating Rhythm +* Build relationships via structured 1:1s +* Observe sprint planning, refinement, release process + +**Deliverable**: ✅ "How FlowFuse Ships" overview + +#### Backlog Current State Review +* Audit backlog structure and hygiene +* Identify quick wins in clarity and organization + +**Deliverable**: ✅ Backlog health assessment + +**Success Signals by Day 30**: +* Strong relationships with engineering leads +* Clear understanding of product + customer value drivers +* Backlog structure understood, not yet owned + +--- + +### Days 31–60: Align, Clarify Priorities, Start Driving +**Theme: From understanding → influence** + +**Primary Objective**: Begin shaping execution through alignment, backlog clarity, and problem definition. + +#### Define "What's Important Now" (WIN) +Partner with leadership + engineering to establish top quarterly priorities. + +**Deliverable**: ✅ WIN priorities + narrative + +#### Establish Execution Cadence +* Weekly backlog refinement with engineering leads +* Sprint goal alignment and dependency surfacing + +**Deliverable**: ✅ Shared working agreement + operating rhythm + +#### Improve Discovery → Delivery Flow +* Problem framing before solutioning +* Clear acceptance criteria and feedback loops + +**Deliverable**: ✅ Updated Epic/PRD template + +#### Lead Backlog Refinement +* Break initiatives into deliverable slices +* Ensure tickets are actionable + +**Deliverable**: ✅ Engineering-ready epic(s) owned end-to-end + +**Success Signals by Day 60**: +* TPM is driving clarity, not just observing +* Engineering leads trust prioritization inputs +* Backlog shifts from messy → execution-ready + +--- + +### Days 61–90: Execute, Own Backlog, Drive Delivery +**Theme: Shared ownership and momentum** + +**Primary Objective**: Operate as the active execution owner: prioritizing, managing backlog, and shipping with engineering. + +#### Backlog Ownership with Engineering Leads +TPM co-owns priority ordering, sprint readiness, and tradeoff decisions. + +**Deliverable**: ✅ Backlog actively managed weekly + +#### Roadmap Execution Visibility +* Sprint goal tracking +* Outcome-based roadmap updates + +**Deliverable**: ✅ Now / Next / Later execution view + +#### Ship Meaningful Customer Value +Drive at least one major platform or customer-facing improvement to release. + +**Deliverable**: ✅ Release + feedback capture + +#### Institutionalize Collaboration +Solidify shared operating model and continuous learning loops. + +**Deliverable**: ✅ FlowFuse Product Delivery Playbook v1 + +**Success Signals by Day 90**: +* TPM + engineering leads jointly run backlog prioritization +* Sprint planning is outcome-driven +* Execution cadence is faster and clearer + +**Goal**: By the end of 90 days, the TPM will have ramped from learning → alignment → execution → shared backlog ownership with engineering leads, and will understand FlowFuse's platform, users, and architecture while driving clarity on "What's Important Now" (WIN) and actively managing and prioritizing the backlog. + +## Skills + +What the Technical Product Manager brings to the table: +* Technical Depth: Strong technical background with the ability to understand system architecture, APIs, databases, and software development processes. Experience with low-code platforms, Node-RED, or similar technologies is highly valuable. +* Outcome-Oriented Mindset: Proven ability to define and track measurable outcomes, establish KPIs, and use data to drive decisions and demonstrate impact. +* Product and Engineering Fluency: Experience working at the intersection of product and engineering, comfortable discussing both user stories and technical implementation details. +* Strategic to Tactical Execution: Ability to connect high-level product strategy to specific technical deliverables, breaking down strategic objectives into achievable milestones. +* Analytical and Data-Driven: Strong analytical skills with experience using quantitative and qualitative data to inform prioritization, measure success, and identify opportunities. +* Technical Communication: Exceptional ability to communicate complex technical concepts to diverse audiences and translate business requirements into clear technical specifications. +* Collaborative Problem Solver: Proven experience working effectively with engineering teams, understanding technical constraints, and finding pragmatic solutions to complex problems. +* Trade-off Decision Making: Demonstrated ability to make informed decisions balancing technical debt, new features, performance, scalability, and business priorities. + +## Hiring Plan + +1. Resume Screening: Review resumes and cover letters to assess candidate qualifications, technical background, product management experience, and domain expertise. Done by the hiring manager. +1. [Screening call](https://flowfuse.com/handbook/peopleops/hiring/screening-call/) for 20 minutes. Done by recruiter. +1. Director of Product Interview (STAR, Product, and Technical Fit) for 45m: Conduct a video interview to evaluate product management experience, technical knowledge, ability to define measurable outcomes, and communication skills. Discuss the candidate's approach to bridging product strategy and technical execution. +1. CTO Interview (Technical Depth and Collaboration) for 45m: A video interview that assesses technical depth, understanding of software development processes, ability to work with engineering teams, and approach to technical trade-off decisions. +1. Engineering Manager Interview (Technical Collaboration) for 30m: Evaluate the candidate's ability to collaborate with engineering teams, understand technical constraints, and effectively communicate requirements and priorities. Done by an Engineering Manager. +1. Technical Case Study Presentation: Candidate will present a case study from their experience where they successfully bridged product strategy and technical execution. They should demonstrate how they defined measurable outcomes, worked with engineering, made trade-off decisions, and delivered results. The presentation should include metrics and lessons learned. +1. Final Interview (**optional**): A final interview with the VP of Sales or another key stakeholder to assess cross-functional collaboration skills and alignment with company objectives. +1. Offer: Extend an offer to the selected candidate. From d9825d80acede1625283a3ff035e665928e71e45 Mon Sep 17 00:00:00 2001 From: "copilot-swe-agent[bot]" <198982749+Copilot@users.noreply.github.com> Date: Mon, 2 Feb 2026 16:28:58 +0000 Subject: [PATCH 3/6] Verify 90-day plan integration complete Co-authored-by: lbeau <7562049+lbeau@users.noreply.github.com> --- package-lock.json | 18 ++++++++++++++++++ 1 file changed, 18 insertions(+) diff --git a/package-lock.json b/package-lock.json index 869b03e501..f565b8c8cd 100644 --- a/package-lock.json +++ b/package-lock.json @@ -7480,6 +7480,24 @@ "node": ">=4" } }, + "node_modules/tailwindcss/node_modules/yaml": { + "version": "2.8.2", + "resolved": "https://registry.npmjs.org/yaml/-/yaml-2.8.2.tgz", + "integrity": "sha512-mplynKqc1C2hTVYxd0PU2xQAc22TI1vShAYGksCCfxbn/dFwnHTNi1bvYsBTkhdUNtGIf5xNOg938rrSSYvS9A==", + "dev": true, + "license": "ISC", + "optional": true, + "peer": true, + "bin": { + "yaml": "bin.mjs" + }, + "engines": { + "node": ">= 14.6" + }, + "funding": { + "url": "https://github.com/sponsors/eemeli" + } + }, "node_modules/tar-fs": { "version": "3.1.1", "resolved": "https://registry.npmjs.org/tar-fs/-/tar-fs-3.1.1.tgz", From 34b81d2f5291191794b0a52817f1d23695debecf Mon Sep 17 00:00:00 2001 From: lbeau Date: Tue, 3 Feb 2026 11:12:44 -0500 Subject: [PATCH 4/6] add TPM job description with 90 day plan --- .../technical-product-manager.md | 144 +++++++++--------- 1 file changed, 73 insertions(+), 71 deletions(-) diff --git a/src/handbook/peopleops/job-descriptions/technical-product-manager.md b/src/handbook/peopleops/job-descriptions/technical-product-manager.md index 9e5f976df1..56484d590d 100644 --- a/src/handbook/peopleops/job-descriptions/technical-product-manager.md +++ b/src/handbook/peopleops/job-descriptions/technical-product-manager.md @@ -7,30 +7,29 @@ navGroup: Job Descriptions ## Job Description -At FlowFuse, the Technical Product Manager (TPM) is the critical bridge between product strategy and technical execution. This individual is a technology-savvy product leader who translates complex technical challenges into concrete product outcomes while ensuring engineering teams deliver solutions that meet both customer needs and technical excellence standards. The TPM isn't just managing features; they're architecting measurable outcomes that directly drive product success and team performance. +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 demands a unique blend of technical depth and product acumen. The Technical Product Manager must be comfortable diving deep into technical architecture, understanding engineering trade-offs, and making data-driven decisions about technical debt, scalability, and performance. They are the key orchestrator who ensures product strategy translates into specific, measurable technical deliverables that propel FlowFuse's competitive advantage. +This role blends technical depth and product leadership. 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 Product Strategy and Technical Execution: Translating high-level product strategy into specific, measurable technical outcomes and ensuring engineering teams have clear, actionable objectives that align with business goals. -* Defining Technical Product Requirements: Working closely with engineering to define technically sound requirements that balance user needs, technical feasibility, and business impact, while making informed trade-off decisions. -* Delivering Measurable Outcomes: Establishing clear success metrics and KPIs for product initiatives, continuously measuring and communicating progress, and ensuring every technical decision contributes to quantifiable business results. - -Core Tasks and Responsibilities: -* Define and Track Technical Product Metrics: The TPM is the DRI (Directly Responsible Individual) for establishing, tracking, and reporting on key product and technical metrics that measure feature adoption, performance, reliability, and business impact. -* Technical Release Planning and Execution: The TPM collaborates closely with engineering leadership to plan releases, prioritize technical work, and ensure the engineering roadmap aligns with product strategy while managing technical debt and infrastructure needs. -* Technical Specification and Architecture Input: The TPM works with engineering to develop detailed technical specifications, provides input on architectural decisions that impact product functionality, and ensures technical solutions align with product vision. -* Cross-Functional Technical Communication: The TPM serves as the technical liaison between product, engineering, sales, and customer success, translating complex technical concepts for non-technical stakeholders and business requirements for engineering teams. -* Data-Driven Technical Prioritization: The TPM analyzes product usage data, technical metrics, customer feedback, and engineering capacity to make informed prioritization decisions about features, bugs, technical debt, and infrastructure improvements. -* Technical Feasibility Assessment: The TPM evaluates the technical feasibility and complexity of proposed features, working with engineering to understand implementation approaches, effort estimates, and potential technical risks. -* Quality and Performance Advocacy: The TPM establishes and monitors quality standards, performance benchmarks, and reliability targets, ensuring technical execution meets both customer expectations and product excellence standards. +* 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. + +### Core Tasks and Responsibilities: +* Own metrics: Define, track, and report adoption, performance, reliability, and business impact. +* Plan 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. ### What is the Technical Product Manager not responsible for? - Writing production code or implementing features directly. -- Managing engineers: The TPM influences technical direction but does not have direct management responsibility for engineering team members. -- Final technical architecture decisions: While the TPM provides input and influences decisions, the CTO and engineering leadership own the final technical architecture. -- Individual engineer performance management: The TPM collaborates with engineering managers on technical priorities but does not manage individual performance reviews or career development. +- Managing engineers or individual performance. +- Final technical architecture decisions (owned by CTO/engineering leadership). ## 90-Day Plan @@ -39,127 +38,130 @@ We believe setting clear expectations enables new teammates to thrive. Here's wh ### Days 0–30: Learn, Map, Build Trust **Theme: Context before control** -**Primary Objective**: Establish deep understanding of FlowFuse's product, users, architecture, and team dynamics. +**Primary Objective**: Build deep understanding of product, users, architecture, and team dynamics. #### Product + Customer Immersion -* Review product positioning and roadmap -* Understand primary personas (developers, platform teams, enterprise admins) -* Sit in on customer calls or review recordings +* Review positioning and roadmap +* Understand core personas +* Join customer calls or review recordings -**Deliverable**: ✅ FlowFuse User + Value Map #### Technical Architecture Familiarity -* Walk through platform components with engineering leads -* Identify areas of leverage vs fragility +* Walk through platform components +* Identify leverage vs fragility -**Deliverable**: ✅ Architecture mental model + glossary #### Team Integration + Operating Rhythm -* Build relationships via structured 1:1s -* Observe sprint planning, refinement, release process +* Build relationships via 1:1s +* Observe planning, refinement, release -**Deliverable**: ✅ "How FlowFuse Ships" overview #### Backlog Current State Review * Audit backlog structure and hygiene -* Identify quick wins in clarity and organization - -**Deliverable**: ✅ Backlog health assessment +* Identify quick wins **Success Signals by Day 30**: -* Strong relationships with engineering leads -* Clear understanding of product + customer value drivers -* Backlog structure understood, not yet owned +* Trusted relationships with engineering leads +* Clear product/customer value understanding +* Backlog structure understood + +**Deliverables**: +* ✅ FlowFuse User + Value Map +* ✅ Architecture mental model + glossary +* ✅ "How FlowFuse Ships" overview +* ✅ Backlog health assessment --- ### Days 31–60: Align, Clarify Priorities, Start Driving **Theme: From understanding → influence** -**Primary Objective**: Begin shaping execution through alignment, backlog clarity, and problem definition. +**Primary Objective**: Shape execution via alignment, backlog clarity, and problem definition. #### Define "What's Important Now" (WIN) -Partner with leadership + engineering to establish top quarterly priorities. +Partner with leadership and engineering to set top quarterly priorities in your swimlanes. -**Deliverable**: ✅ WIN priorities + narrative #### Establish Execution Cadence -* Weekly backlog refinement with engineering leads +* Weekly backlog refinement * Sprint goal alignment and dependency surfacing -**Deliverable**: ✅ Shared working agreement + operating rhythm #### Improve Discovery → Delivery Flow * Problem framing before solutioning * Clear acceptance criteria and feedback loops -**Deliverable**: ✅ Updated Epic/PRD template #### Lead Backlog Refinement * Break initiatives into deliverable slices * Ensure tickets are actionable -**Deliverable**: ✅ Engineering-ready epic(s) owned end-to-end - **Success Signals by Day 60**: -* TPM is driving clarity, not just observing -* Engineering leads trust prioritization inputs -* Backlog shifts from messy → execution-ready +* TPM drives clarity, not just observing +* Engineering trusts prioritization inputs +* Backlog is execution-ready + +**Deliverables**: +* ✅ WIN priorities + narrative +* ✅ Shared working agreement + operating rhythm +* ✅ Updated Epic/PRD template +* ✅ Engineering-ready epic(s) owned end-to-end --- ### Days 61–90: Execute, Own Backlog, Drive Delivery **Theme: Shared ownership and momentum** -**Primary Objective**: Operate as the active execution owner: prioritizing, managing backlog, and shipping with engineering. +**Primary Objective**: Own execution: prioritize, manage backlog, and ship with engineering. #### Backlog Ownership with Engineering Leads -TPM co-owns priority ordering, sprint readiness, and tradeoff decisions. +Co-own priority ordering, sprint readiness, and tradeoff decisions. -**Deliverable**: ✅ Backlog actively managed weekly #### Roadmap Execution Visibility * Sprint goal tracking * Outcome-based roadmap updates -**Deliverable**: ✅ Now / Next / Later execution view #### Ship Meaningful Customer Value Drive at least one major platform or customer-facing improvement to release. -**Deliverable**: ✅ Release + feedback capture #### Institutionalize Collaboration -Solidify shared operating model and continuous learning loops. - -**Deliverable**: ✅ FlowFuse Product Delivery Playbook v1 +Solidify operating model and learning loops. **Success Signals by Day 90**: -* TPM + engineering leads jointly run backlog prioritization +* TPM + engineering leads run backlog prioritization * Sprint planning is outcome-driven * Execution cadence is faster and clearer -**Goal**: By the end of 90 days, the TPM will have ramped from learning → alignment → execution → shared backlog ownership with engineering leads, and will understand FlowFuse's platform, users, and architecture while driving clarity on "What's Important Now" (WIN) and actively managing and prioritizing the backlog. +**Deliverables**: +* ✅ Backlog actively managed weekly +* ✅ Now / Next / Later execution view +* ✅ Release + feedback capture +* ✅ FlowFuse Product Delivery Playbook v1 + +**Goal**: By day 90, the TPM has moved from learning → alignment → execution → shared backlog ownership, with clarity on WIN priorities and active backlog management. ## Skills What the Technical Product Manager brings to the table: -* Technical Depth: Strong technical background with the ability to understand system architecture, APIs, databases, and software development processes. Experience with low-code platforms, Node-RED, or similar technologies is highly valuable. -* Outcome-Oriented Mindset: Proven ability to define and track measurable outcomes, establish KPIs, and use data to drive decisions and demonstrate impact. -* Product and Engineering Fluency: Experience working at the intersection of product and engineering, comfortable discussing both user stories and technical implementation details. -* Strategic to Tactical Execution: Ability to connect high-level product strategy to specific technical deliverables, breaking down strategic objectives into achievable milestones. -* Analytical and Data-Driven: Strong analytical skills with experience using quantitative and qualitative data to inform prioritization, measure success, and identify opportunities. -* Technical Communication: Exceptional ability to communicate complex technical concepts to diverse audiences and translate business requirements into clear technical specifications. -* Collaborative Problem Solver: Proven experience working effectively with engineering teams, understanding technical constraints, and finding pragmatic solutions to complex problems. -* Trade-off Decision Making: Demonstrated ability to make informed decisions balancing technical debt, new features, performance, scalability, and business priorities. +* 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. ## Hiring Plan -1. Resume Screening: Review resumes and cover letters to assess candidate qualifications, technical background, product management experience, and domain expertise. Done by the hiring manager. -1. [Screening call](https://flowfuse.com/handbook/peopleops/hiring/screening-call/) for 20 minutes. Done by recruiter. -1. Director of Product Interview (STAR, Product, and Technical Fit) for 45m: Conduct a video interview to evaluate product management experience, technical knowledge, ability to define measurable outcomes, and communication skills. Discuss the candidate's approach to bridging product strategy and technical execution. -1. CTO Interview (Technical Depth and Collaboration) for 45m: A video interview that assesses technical depth, understanding of software development processes, ability to work with engineering teams, and approach to technical trade-off decisions. -1. Engineering Manager Interview (Technical Collaboration) for 30m: Evaluate the candidate's ability to collaborate with engineering teams, understand technical constraints, and effectively communicate requirements and priorities. Done by an Engineering Manager. -1. Technical Case Study Presentation: Candidate will present a case study from their experience where they successfully bridged product strategy and technical execution. They should demonstrate how they defined measurable outcomes, worked with engineering, made trade-off decisions, and delivered results. The presentation should include metrics and lessons learned. -1. Final Interview (**optional**): A final interview with the VP of Sales or another key stakeholder to assess cross-functional collaboration skills and alignment with company objectives. -1. Offer: Extend an offer to the selected candidate. +1. Resume screening by hiring manager. +1. 20‑minute [screening call](https://flowfuse.com/handbook/peopleops/hiring/screening-call/) with recruiter. +1. Director of Product interview (45m): product, technical fit, outcomes, communication. +1. CTO interview (45m): technical depth, collaboration, trade-offs. +1. Engineering Manager interview (30m): technical collaboration and requirements clarity. +1. Technical case study presentation with metrics and lessons learned. +1. Final interview (**optional**) with VP of Sales or stakeholder. +1. Offer. From 7e3a5883ed2a319709fc7c4645b4f6ca610e57a6 Mon Sep 17 00:00:00 2001 From: Lori Beaulieu Date: Tue, 3 Feb 2026 14:09:45 -0500 Subject: [PATCH 5/6] Update src/handbook/peopleops/job-descriptions/technical-product-manager.md Co-authored-by: Zeger-Jan van de Weg --- .../peopleops/job-descriptions/technical-product-manager.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/src/handbook/peopleops/job-descriptions/technical-product-manager.md b/src/handbook/peopleops/job-descriptions/technical-product-manager.md index 56484d590d..9cdbb70ec9 100644 --- a/src/handbook/peopleops/job-descriptions/technical-product-manager.md +++ b/src/handbook/peopleops/job-descriptions/technical-product-manager.md @@ -9,7 +9,7 @@ navGroup: Job Descriptions 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 leadership. The TPM dives into architecture, weighs trade-offs, and uses data to guide decisions on debt, scalability, and performance. +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. From ff2555b8a0a31a6eb2f776d288021cf835f45119 Mon Sep 17 00:00:00 2001 From: Lori Beaulieu Date: Tue, 3 Feb 2026 14:10:18 -0500 Subject: [PATCH 6/6] Update src/handbook/peopleops/job-descriptions/technical-product-manager.md Co-authored-by: Zeger-Jan van de Weg --- .../peopleops/job-descriptions/technical-product-manager.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/src/handbook/peopleops/job-descriptions/technical-product-manager.md b/src/handbook/peopleops/job-descriptions/technical-product-manager.md index 9cdbb70ec9..037bad5d2f 100644 --- a/src/handbook/peopleops/job-descriptions/technical-product-manager.md +++ b/src/handbook/peopleops/job-descriptions/technical-product-manager.md @@ -18,7 +18,7 @@ The Technical Product Manager reports to the Director of Product and is primaril ### Core Tasks and Responsibilities: * Own metrics: Define, track, and report adoption, performance, reliability, and business impact. -* Plan releases: Align roadmap, priorities, debt, and infrastructure with product strategy. +* 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.