Software Product Strategy & Roadmap
• Own the software product roadmap for the assigned product line — defining the vision, prioritising features and releases, and sequencing development work against commercial opportunity and customer value
• Develop software product requirements: user stories, functional specifications, and acceptance criteria that R&D can act on — with clear priority rationale for each item
• Make evidence-based trade-off decisions about software feature scope, release timing, and technical debt — balancing commercial urgency with software quality and architectural sustainability
• Own the software product versioning and release strategy — coordinating release cadence with hardware product launches and sustaining release cycles
Customer & Market Requirements
• Conduct structured VOC for software: customer interviews, usability feedback sessions, and competitive software benchmarking — generating a minimum of 15 documented customer conversations per year specifically focused on software needs
• Monitor the competitive software landscape: competitor instrument software releases, third-party integration developments, and emerging customer expectations around connectivity, data management, and regulatory compliance
• Partner with Strategic Segment Managers to understand how regulatory requirements (21 CFR Part 11, GAAMP, OECD GLP) affect software product needs in priority end markets
• Translate hardware NPI requirements into software specification — ensuring instrument control software is developed in parallel with the hardware programme and available at launch
R&D Partnership & Delivery
• Serve as the primary product management interface to the software R&D team — attending sprint reviews, backlog grooming sessions, and software programme milestones
• Maintain a clearly prioritised software backlog — updated regularly, visible to stakeholders, and reflective of current commercial priorities
• Own software release acceptance: define and execute user acceptance testing criteria, certify that software releases meet the defined product requirements before commercial release
• Coordinate beta customer programmes for major software releases — managing site selection, structured feedback collection, and issue resolution before general availability
• Develop software-specific commercial enablement materials: feature release notes, upgrade guides, competitive software comparison sheets, and software-focused demo guides for the sales organisation
• Train the commercial team on major software releases — ensuring field teams can demonstrate, position, and sell software capabilities as a competitive differentiator
• Support the MarComm team with technically accurate software content for campaigns, product brochures, and digital channels