ROLE OVERVIEWCustomer Engineering owns two connected mandates: building custom integrations that connect biopharma and biotech customers' scientific and IT workflows directly to Benchling, and building the internal engineering products - desktop applications, Connect adapters, Tenant Operations tooling, and public MCP servers - that make that integration work scale across our whole customer base. See an example of our customer integration work on our website, which describes how we automated DNA assembly to improve efficiency and reduce cost.
RESPONSIBILITIES- Collaborate directly with customers to understand complex scientific workflows and implement product integrations.
- Own projects end-to-end, from initial design to production rollout, whether the "customer" is an external biopharma partner or Benchling's own engineering org.
- Strengthen Benchling's APIs and developer platform by leveraging the latest features and acting as the voice of the customer - or the team you're building for - to other groups within engineering.
- Contribute to continuous improvement of the Customer Engineering team's tooling and best practices, including being hands-on with our testing frameworks and CI/CD systems.
- Help scale our product and team. As a member of the engineering team, you'll be an integral part of how we mature our engineering processes and hiring.
Check out our blog for some examples of what we work on at Benchling. Here are some other examples of Customer Engineering projects:
- Tools to assist with DNA assembly - scientists need to plan which DNA entities should be combined to express a particular protein. They want to automate searching for the possible components of this assembly given desired ratios and what materials are available in inventory.
- Robot and instrument integration - scientists are increasingly using automated hardware in the lab to perform measurements. By integrating Benchling with machines like liquid handlers, we are working towards a world where a scientist can perform a physical experiment entirely using software.
- Tenant Operations - provisioning and configuring a customer's Benchling tenant used to mean manual, one-off engineering work for every request. We're building the internal tools and standardized workflows that let anyone on the team run these operations quickly and consistently, without relying on tribal knowledge.
- Public MCP servers - we build and maintain the servers that expose trusted scientific data sources, like ClinicalTrials.gov, bioRxiv, and ChEMBL, through the Model Context Protocol (MCP), so AI agents and tools can pull structured data directly into a researcher's workflow.
QUALIFICATIONS- 2+ years of experience in software engineering
- A customer-first approach to building software
- Familiarity with Python and AWS
- Strong abilities in problem solving and iterating on feedback
- Desire to own projects and interest in the real world impact of your code
- Curiosity in learning more about life science (prior knowledge is not required; desire to learn is a must)
HOW WE WORKWe offer a flexible hybrid work arrangement that prioritizes in-office collaboration. Employees are expected to be on-site 3 days per week (Monday, Tuesday, and Thursday).
#LI-Hybrid
#BI-Hybrid
#LI-KW1
