Scientific Systems Product Manager

Location: Tarrytown, NY (3x per week onsite)

Duration: 1 year ongoing contract

Must-Haves

• 7 years of Product Management/Product Owner experience, including ownership of digital products from requirements through release and ongoing enhancement
• Strong experience owning and prioritizing product backlogs, defining epics/user stories, leading refinement, and partnering closely with engineering to ship features
• Proven ability to take ambiguous or loosely defined business needs and translate them into clear product requirements and actionable features
• Strong business process and systems thinking, including mapping current-state workflows, designing future-state processes, and understanding how systems/data connect
• Experience driving incremental product development and user adoption, gathering feedback after releases and determining what functionality should be built next
• Experience within biotech, pharma, life sciences, R&D, or scientific environments, with enough scientific fluency to understand terminology and workflows at a process level. Deep assay/scientific expertise is not required

Day to Day

This Product Manager will own the continued development of a product designed to give teams a shared view of antibody campaigns, priorities, work, scheduling, and capacity. The product connects work that is currently spread across separate tools and processes, helping teams better prioritize and plan work against real capacity. The Product Manager will own and prioritize the backlog, work closely with users and engineering to shape epics and user stories, lead refinement sessions, and drive features from concept through release. A major focus will be taking existing scientific and operational workflows and determining how the product should support and improve them. For example, a feature may involve building a scheduling board that allows teams performing assays to plan their work and capacity, rather than building the scientific assay itself. This person will continuously gather user feedback, build on initial releases, identify what functionality should come next, and drive adoption across teams. Scientific knowledge is important for understanding the environment and speaking the language, but this is primarily a product ownership and delivery role.