Sr. Product Owner

Work Schedule Standard (Mon-Fri) Environmental Conditions Office Job Description JOB DESCRIPTION: Sr Business Analyst - Product Owner At Thermo Fisher Scientific, we develop innovative software solutions that enable our customers to advance science and improve human health. It is a close-knit, collaborative, cross-functional environment where Product Management, Software Engineering, Software Verification & Validation, Quality, and other functions work together to deliver high-quality products. The software team is tasked with applying industry best practices to the definition, design, development, verification, validation, and delivery of world-class software products for clinical and research settings. We are seeking an experienced and highly motivated Sr Business Analyst - Product Owner who will serve as the primary liaison between the Product Management team and the Software Engineering and Software V&V teams. This individual will translate product and customer needs into clear, complete, testable, and implementation-ready requirements and user stories so that Development and V&V teams have a common understanding of intended product behavior. The Product Owner will act as the single point of contact for functional understanding of the product and will own the quality and completeness of requirements throughout the software development lifecycle. You are excited and passionate about participating in an Agile/SCRUM setting to meet customer expectations and continuously drive quality and delivery improvements. You are comfortable working with technical and business stakeholders, facilitating decisions, identifying gaps, and constructively challenging assumptions. You do not stop at identifying problems; you develop practical proposals, build cross-functional alignment, drive actions to closure, and use meaningful metrics to demonstrate measurable improvement in requirement quality, defect prevention, and product delivery. Essential Functions: Serve as the primary liaison between Product Management, Software Engineering, and Software V&V, ensuring a common understanding of product requirements, workflows, priorities, and expected system behavior. Translate product requirements, customer needs, business objectives, scientific workflows, and regulatory considerations into clear Epics, Features, User Stories, and Acceptance Criteria that can be independently understood and executed by Software Development and V&V teams. Own the functional quality and completeness of software requirements throughout the product development lifecycle and ensure requirements are clear, consistent, testable, traceable, and sufficiently detailed before implementation begins. Ensure user stories capture the business and user objective, functional behavior, user workflows and use cases, business rules, acceptance criteria, positive and negative scenarios, boundary and exception conditions, dependencies, assumptions, data and integration considerations, and expected behavior required for verification and validation. Establish and drive effective requirements review and backlog refinement mechanisms so that Product Management, Engineering, V&V, and other relevant stakeholders have a shared understanding of scope and expected behavior before development begins. Drive adoption and continuous improvement of Definition of Ready, requirement quality standards, story templates, review checklists, traceability practices, and other mechanisms that improve requirement completeness and reduce downstream ambiguity and rework. Act as the single point of contact for functional interpretation and clarification of product requirements for Software Engineering and V&V teams. Maintain an end-to-end understanding of product workflows and proactively identify gaps, inconsistencies, dependencies, and unintended interactions across features. Ensure key product decisions, requirement clarifications, assumptions, changes, and impact assessments are documented and communicated to affected stakeholders, including impacts to existing functionality, development, V&V, documentation, timelines, and related product components. Drive processes and preventive actions that reduce defects whose root cause is attributed to Requirement Miss, incomplete or ambiguous requirements, inadequate acceptance criteria, or inconsistent functional interpretation. Play a leadership role in software defect triage, partnering with Product Management, Engineering, and V&V to establish expected system behavior and distinguish among software implementation defects, requirement misses or ambiguities, test coverage gaps, change requests or enhancements, and expected product behavior. Ensure defect triage results in clear decisions, owners, actions, and closure criteria, and drive timely resolution of product and functional questions that could otherwise block Software Development or V&V execution. Analyze requirement-related defects and defect trends to identify systemic patterns and recurring gaps. Partner with Engineering, V&V, and Product Management leaders to define corrective and preventive actions and drive those actions through completion. Establish and monitor meaningful quality and delivery metrics, including Requirement Miss defects, requirement-related defect escape rate, user-story rework after development begins, story readiness, acceptance-criteria completeness, requirement churn, defect recurrence, triage aging, corrective-action completion, and reduction in Development and V&V rework. Use metrics not only for reporting but to identify systemic issues, prioritize improvement opportunities, demonstrate the effectiveness of corrective actions, and show measurable improvement across releases or program increments. Work effectively with senior leadership and cross-functional teams, influence without direct authority, facilitate difficult discussions, create alignment among stakeholders with different priorities, and drive decisions and actions to closure. Demonstrate a strong ownership mindset, team spirit, and proactive approach to process and delivery improvement. Raise gaps early and pair identified issu