Product Manager, Benchling

• 3-5+ years of product management or equivalent experience
• A diverse career history. You've worked across 2-3+ meaningfully different domains or product types. This is the single strongest signal we're looking for. It tells us you're a systems thinker who adapts, not someone who relies on one playbook
• Product taste. You have a track record of building and improving products. You can translate a user requirement into a feature worth building, and you can look at any product and articulate what's broken and why. You understand that shipping software isn't just about delivering requirements. It's about getting a user to change their behavior, form a new habit, and make it stick
• Architectural fluency. You have experience guiding the architectural decisions of a product. You can reason about data models, state machines, or schema design. You don't write code, but you can spot when a technical decision will create a bad user experience, limit the extensibility of a product, or lead to something that's difficult to revert
• Technical tool competency. You're resourceful. You use tools to help yourself and your team get work done, whether that's writing SQL queries to make data-driven decisions, using design tools to create prototypes, or using something like Cursor to ship product improvements directly
• Clear communication. You can lead an engaging professional conversation and keep a room's attention. You know how to adapt your communication style based on your audience and can read and respond to the individuals in the conversation. As a PM, this matters almost more than anything else
• Track record of outcomes. You've stayed long enough at key roles to ship, learn, and speak to what worked and what didn't. We're looking for evidence of impact
• Intellectual range. You're genuinely curious, and that curiosity shows up in how you learn and think about problems. Product management is a means to an end. It's how you apply the learnings from the curiosity that has driven you. What you and your team decide to build is an inevitable conclusion of that curiosity
• You do not need a life sciences background. We're looking for a systems thinker with product taste who can walk into an unfamiliar domain, find the structural patterns, and be effective quickly
• The best PMs we've seen for this kind of work have diverse backgrounds
• They've built products across meaningfully different problem spaces and bring transferable instincts rather than a single industry playbook

Desirable

• Benchling's platform helps the world's largest biotech and pharma companies develop therapies faster
• As a Product Manager on the Scientific Development Solutions team, you'll work on products such as Recipes, Assays, and Workflows that scientists use to do their jobs
• These products are fundamental to how scientific processes get configured, run, and tracked across different phases of a drug's development cycle
• We launched Bioprocess in 2024 to help process development teams design, execute, and analyze the experiments that turn a molecule into a manufacturable drug
• In 2025, we announced a partnership with Merck (press release) to help their teams develop and test vaccines faster by bringing their analytical workflows onto a single platform
• Today, we're implementing the largest pharma companies in the world on Bioprocess, making the core product better every quarter, and expanding into Analytical Sciences and downstream QC
• Our vision is to become the software that helps biopharmas bring therapies to patients twice as fast
• This is a systems design problem disguised as a life sciences product
• You'll be working at the intersection of complex configuration, workflow orchestration, and behavior change
• You'll figure out how to make powerful software feel intuitive to the scientists who depend on it every day
• You are responsible for Recipes, Assays, and Workflows. That means you and your team decide what gets built, why, and in what order. You're accountable for the roadmap and the outcomes your roadmap produces
• To inform what you build, you will spend time with customers and GTM teams to understand how scientists actually work, and how to turn what they ask for into what they need. It's your responsibility to bring that context back to the team and turn it into product direction
• You'll work alongside design, engineering, GTM, and our customers to build and ship products. That means guiding product decisions with design and engineering, validating ideas early with customers, enabling customer experience teams on what you ship, and partnering with GTM to bring it to market
• Use tools at your disposal (SQL, AI, developer environment) to be more effective. That can mean pulling your own data to answer a question, building a prototype to clarify direction, or finding a way to find and summarize customer discovery notes. The point isn't the specific tool. It's the drive to find what you need and move fast rather than wait for someone else