Product Manager

The Product Manager II owns the roadmap, requirements, and delivery for an assigned product area or market segment of the STARLIMS portfolio, working within the strategy set by the business. The role turns customer needs and usage data into prioritized, well-defined work for Engineering, runs the backlog and releases with discipline, and is accountable for adoption and customer satisfaction in the area it owns, not only for on-time delivery. The Product Manager II works with moderate guidance.

Responsibilities

The Product Manager II is responsible for the following for an assigned product area within the STARLIMS portfolio:

• Roadmap: Maintain the roadmap for the assigned area within the strategy set by the business, and propose priorities supported by customer, usage, and competitive data.
• Requirements and backlog: Write clear requirements, user stories, and acceptance criteria; keep the backlog groomed and current; and prioritize using the team's standard method.
• Delivery: Work with an Agile engineering team through each sprint and release, make scope trade-offs, keep dates and commitments, report status and risks weekly, and prepare for and take part in PI Planning.
• Customer and market insight: Hold regular customer conversations and feedback sessions, turn what is learned into backlog items, and track competitors in the assigned area.
• Release and launch readiness: Coordinate release content, documentation, and launch materials with QA, Quality, Support, Services, Marketing, and Sales, and support product demonstrations and customer adoption.

Additional Responsibilities

• Outcomes and metrics: Define success metrics before features ship, review adoption, usage, and customer satisfaction afterward, and act on what the data shows.
• Planning input: Contribute customer, usage, and competitive inputs for the assigned area to annual planning and the long-range plan.
• Cross-functional communication: Keep Engineering, Sales, Support, Services, and Quality informed about roadmap, release content, and known issues for the assigned area.
• Beta and pilot programs: Run beta and pilot programs for new features, and collect and act on the feedback before general release.
• Quality and regulated environment: Follow the company's quality and release processes, and understand how customer regulatory requirements (for example, FDA, ISO, and GxP) affect requirements for the assigned area.

Qualifications

Education: Bachelor’s Degree in Business, Life Sciences, Engineering, or a related field, or an equivalent combination of education and work experience.

Experience: Minimum 2 years

• Experience in software product management or product ownership, with at least one release taken from requirements through launch.
• Working knowledge of Agile delivery and backlog management; experience writing requirements, user stories, and acceptance criteria.
• Experience participating in PI Planning in a scaled Agile environment, including preparing features and priorities for the planning event and committing to the resulting plan.
• SaaS, and preferably legacy software systems experience.
• Ability to use customer feedback and usage data to prioritize work and define success metrics.
• Experience with laboratory information management systems (LIMS) or other software in a highly regulated industry (for example, pharmaceutical, clinical, or forensics) is a plus.
• Ability to influence cross-functional teams (Engineering, Sales, Support, Services, Quality) without formal authority.
• Clear written and verbal communication, including presenting to customers and internal stakeholders.
• Comfort using AI tools to draft specifications, synthesize feedback, and automate routine product work.

Licenses and Certifications: None required. Product management or product ownership certification (for example, CSPO) is a plus.

Product Culture and Expectations

1. Structured thinking. Reasons from first principles, sees patterns instead of treating everything as bespoke, speaks plainly without jargon, and holds grounded opinions that don’t flip the moment someone pushes back.

1. Motor. Finds the critical path and attacks it. Ships, measures, iterates. Defaults to action and demos, not to more questions and more decks.

1. Win as a team. Sits at the center of an extended team (eng, design, sales, CS, marketing, renewals) and acts as connective tissue, never the bottleneck. In lock-step with GTM; owns outcomes jointly with the BU.

1. Product as a growth lever. Traces the work to revenue and customer outcomes (retention, expansion, activation, and time-to-value) and understands how the assigned area contributes to the group's growth goal.

1. Repeatable prioritization + editor’s judgment. Runs a consistent process with named information sources (customer feedback, funnel data, win/loss, competitive). Most ideas improve users’ lives; the PM’s job is to find the handful that move the business and say no to the rest.

1. Funnels and weekly cadence. Defines the funnel (incl. product-market-fit funnel with observable stages), instruments it, and runs a weekly loop: funnel, feedback/demo, backlog. Nothing ships without a hypothesis (GROW: gap → re-engineer → operationalize → weekly) so every release teaches us something.

1. Lives with the customer. Weekly customer/CAB feedback feeding directly into the backlog. Starts from the user’s jobs-to-be-done, breaks them into tasks, walks in the user’s shoes.

1. AI-native builder. Writes specs that agents execute, prototypes with AI tools, and treats their own PDLC as something to automate (build-the-builder applies to PMs too). Thinks in multiples of output, not percentages. Understands GOATs: agents that use the product like users, not just AI features bolted on.

1. Core craft and accountability. Backlog management, grooming, and MVP and launch-spec definition. Owns dates and commitments for the assigned area, reports weekly, and acknowledges reality when the numbers say it isn't working.

1. Taste and storytelling. Produces work that’s easy to understand, tells a compelling story, and is proven with examples. Focuses on “what you can now do” (capability), not on features or safety caveats.
   
   STARLIMS is an Equal Opportunity Employer. All qualified applicants will receive consideration for employment without regard to race, creed, religion, color, national or ethnic origin, citizenship, sex, sexual orientation, gender identity and expression, genetic information, veteran status, age or disability status.