Technical Product Manager , Fight Friction

We need to output HTML fragment with sections: About the role? Actually the posting includes sections: "Why Protolabs?" (maybe About the role), "What You'll Do" (Responsibilities), "What It Takes" (Requirements/Qualifications), "Preferred Qualifications", "You Might Be a Great Fit If" (Skills), "What's In It For You!" (Benefits, Pay). Also schedule: "This is a fixed hybrid role (M/F remote; Tues-Thurs onsite) at HQ in Maple Plain, MN." That's schedule info. Pay: "$107,400 - $161,000 a year". Benefits: list of benefits. We must not repeat job title as heading. Use

for section headings: e.g., About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We need to include sections only when posting has real specific content. So we will have sections: About the role (maybe from "Why Protolabs?" and intro), Responsibilities (What You'll Do), Requirements (What It Takes), Qualifications (Preferred Qualifications?), Skills (You Might Be a Great Fit If), Benefits (What's In It For You! benefits list), Pay (salary range), Schedule (hybrid role). Also maybe include location? Not required. We must not include boilerplate like EEO, ITAR, physical demands, etc. Remove those. Also remove "Proto Labs maintains ITAR-compliant operations..." etc. Also remove "Physical Demands", "Work Environment". Also remove "We are an equal opportunity employer" etc. Also remove "Individuals with temporary visas..." etc. Also remove "Proto Labs, Inc. is an Equal Opportunity Employer". Also remove "We do not discriminate..." etc. Also remove "Be yourself at Protolabs Studies have shown..." Actually that's intro encouraging underrepresented groups; that's EEO boilerplate; we should remove that as it's equal opportunity boilerplate. Also remove "We strongly believe diversity..." etc. Also remove "Why Protolabs?" maybe we keep as About the role content. The "Why Protolabs?" paragraph is substantive about company culture; we can keep. We need to preserve all substantive information; not invent or summarize away detail. So we need to keep the details from each section. Let's extract content: Intro: "Be yourself at Protolabs Studies have shown that women and people of color are less likely to apply to jobs unless they meet every single qualification. We are an equal opportunity employer, and we are committed to building a diverse team that feels they are valued in the workplace. So do you feel you do not meet every single requirement but still intrigued? We encourage you to still apply! You can help make our company even better. We do not discriminate based on race, color, national origin, sexual orientation, gender, age, mental or physical ability, or any way you represent yourself. We strongly believe diversity makes for more successful teams." This is EEO boilerplate; remove. Next: "Why Protolabs? We are the leaders in digital manufacturing. We hire doers, makers, and creative thinkers who tackle our roles with an entrepreneurial spirit. Our culture is centered around meaningful work that brings new and innovative products to market at unprecedented speeds. We are a diverse team that comes from all walks of life and take pride in our team who is smart, genuine, humble, and passionate about what we do. It’s our people who fuel our creativity and make our culture feel like home." Keep as About the role. Next: "Join our team as a Technical Product Manager, Fight Friction! This is a fixed hybrid role (M/F remote; Tues-Thurs onsite) at HQ in Maple Plain, MN." This includes schedule and location. We'll extract schedule for Schedule section; location maybe not needed but could be part of About the role? Might keep location in About the role? But we have schedule separate. Next: "What You'll Do" bullet list (actually sentences). We'll convert each sentence to

under

. List items: - Own and maintain the product roadmap for the assigned ecosystem area, balancing new capability development against friction-reduction and quality-of-experience work - Translate business and customer needs into clear requirements, user stories, and acceptance criteria for the engineering team - Prioritize the backlog using a consistent framework, balancing engineering capacity, customer/business impact, and cross-functional input - Partner with engineering leads on release planning, scope trade-offs, and delivery timelines; coordinate launch and rollout activities - Define and track success metrics for shipped work, including adoption, quality, and friction-reduction indicators - Partner directly with Sales and Customer Success to systematically surface friction points across the ecosystem — including lost or stalled deals, recurring support escalations, churn signals, and workaround patterns — and translate them into a prioritized, actionable backlog - Act as the coordination point between engineering, Sales, and Customer Success so that friction-related fixes move through hand-offs cleanly rather than stalling between teams, despite having no direct authority over those teams - Establish and run a recurring intake and feedback loop (e.g., regular syncs, a shared submission process, or office hours) so Sales and Customer Success have a known, reliable channel for raising friction issues rather than relying on ad hoc escalation - Report on friction-reduction progress using concrete before/after metrics (e.g., ticket volume, time-to-resolution, deal-blocking issues resolved, repeat-escalation rate), and communicate that progress back to Sales, Customer Success, and engineering leadership - Facilitate trade-off conversations when friction-reduction priorities compete with other roadmap commitments, ensuring decisions and rationale are visible to all stakeholders - Represent the voice of the customer and front-line teams in engineering planning and prioritization discussions - Identify opportunities for continuous improvement in how the team identifies, triages, and resolves ecosystem friction. Next: "What It Takes" list: - A degree in Business, Computer Science, or a related field, or equivalent practical experience - 4+ years' experience in technical product management, ideally supporting a software engineering team - Experience working directly with Sales and/or Customer Success teams, ideally in a cross-functional, platform, or ecosystem-facing role - Experience coordinating delivery across multiple teams without direct authority over those teams Next: "Preferred Qualifications" list: - Prior experience in a platform, ecosystem, or internal-tools product role spanning multiple customer-facing teams - Experience building or running a formal intake/feedback process between product and go-to-market teams - Exposure to complex operational environments where technology, people and process all need to work together Next: "You Might Be a Great Fit If" with subheadings: Product & Analytical Skills, Collaboration & communication. We'll treat as Skills section; we can keep bullet points under each subheading? Could just list them as items. Under Product & Analytical Skills: - Comfortable working with funnels, experiments and cost/benefit framing to support decisions - Ability to define clear success metrics and measure product performance against business outcomes and KPIs - User-centric mindset with the ability to balance customer, business and operational considerations Under Collaboration & communication: - Strong written and verbal communication skills with technical and non-technical stakeholders - Able to create clarity in complex domains and build alignment without direct authority - Pragmatic, decisive and impact-oriented: you focus on outcomes over outputs Next: "What's In It For You!" includes benefits list and salary. Paragraph: "We offer a competitive salary and total rewards packageWe offer amazing benefits including but not limited to:" (note missing space). Then list: - Health Insurance: Traditional OR High Deductible plan - Flexible Spending Accounts - Health Savings Account (including employer contributions) - Dental and Vision - Basic and Supplemental Life Insurance - Short-Term and Long-Term Disability - Paid caregiver leave - You will receive at least 3 weeks of PTO + Wellness + Holiday Pay + Volunteer Hours - 401k with company match and immediate vest - Employee Stock Purchase Program at a discounted rate - Matching grants through Protolabs foundation - And More! Then salary: "$107,400 - $161,000 a year" We need Benefits section: list of benefits. Pay section: salary range. Schedule section: "This is a fixed hybrid role (M/F remote; Tues-Thurs onsite) at HQ in Maple Plain, MN." We'll put schedule info. We must not include location as heading; maybe include in About the role? But we can put location in Schedule or About the role. Since schedule section is for schedule, we can include hybrid details and location. Now produce HTML:

About the role

We are the leaders in digital manufacturing. We hire doers, makers, and creative thinkers who tackle our roles with an entrepreneurial spirit. Our culture is centered around meaningful work that brings new and innovative products to market at unprecedented speeds. We are a diverse team that comes from all walks of life and take pride in our team who is smart, genuine, humble, and passionate about what we do. It’s our people who fuel our creativity and make our culture feel like home.

Responsibilities

• Own and maintain the product roadmap for the assigned ecosystem area, balancing new capability development against friction-reduction and quality-of-experience work
• Translate business and customer needs into clear requirements, user stories, and acceptance criteria for the engineering team
• Prioritize the backlog using a consistent framework, balancing engineering capacity, customer/business impact, and cross-functional input
• Partner with engineering leads on release planning, scope trade-offs, and delivery timelines; coordinate launch and rollout activities
• Define and track success metrics for shipped work, including adoption, quality, and friction-reduction indicators
• Partner directly with Sales and Customer Success to systematically surface friction points across the ecosystem — including lost or stalled deals, recurring support escalations, churn signals, and workaround patterns — and translate them into a prioritized, actionable backlog
• Act as the coordination point between engineering, Sales, and Customer Success so that friction-related fixes move through hand-offs cleanly rather than stalling between teams, despite having no direct authority over those teams
• Establish and run a recurring intake and feedback loop (e.g., regular syncs, a shared submission process, or office hours) so Sales and Customer Success have a known, reliable channel for raising friction issues rather than relying on ad hoc escalation
• Report on friction-reduction progress using concrete before/after metrics (e.g., ticket volume, time-to-resolution, deal-blocking issues resolved, repeat-escalation rate), and communicate that progress back to Sales, Customer Success, and engineering leadership
• Facilitate trade-off conversations when friction-reduction priorities compete with other roadmap commitments, ensuring decisions and rationale are visible to all stakeholders
• Represent the voice of the customer and front-line teams in engineering planning and prioritization discussions
• Identify opportunities for continuous improvement in how the team identifies, triages, and resolves ecosystem friction.

Requirements

• A degree in Business, Computer Science, or a related field, or equivalent practical experience
• 4+ years' experience in technical product management, ideally supporting a software engineering team
• Experience working directly with Sales and/or Customer Success teams, ideally in a cross-functional, platform, or ecosystem-facing role
• Experience coordinating delivery across multiple teams without direct authority over those teams

Qualifications

• Prior experience in a platform, ecosystem, or internal-tools product role spanning multiple customer-facing teams
• Experience building or running a formal intake/feedback process between product and go-to-market teams
• Exposure to complex operational environments where technology, people and process all need to work together

Skills

• Comfortable working with funnels, experiments and cost/benefit