Get more replies from employers
Send a job-specific resume in minutes.
Strativ Group in Cambridge, MA is seeking a Laboratory Informatics Lead to own Benchling-based data models, sample tracking, and automation integrations.
You will partner with scientists and data engineers to scale the lab's informatics backbone, ensure traceability across complex sample splits, and deliver robust, production-ready schemas and integrations with AWS. This is an on-site role.
Our lab processes hundreds of samples a week, from intake through to sequencing handoff, as part of a biosurveillance program that screens for novel pathogens.
We’re building out Benchling as our lab informatics platform, and we need someone to own it: the data models, sample tracking, automation integrations, and the day-to-day experience for the scientists who rely on it.
You’ll take a system that works today and turn it into the backbone of how our lab operates. That means designing schemas that can handle a single sample splitting into multiple paths without losing traceability, building integrations with lab instruments and AWS, and spending real time with bench scientists to understand where things get frustrating.
Sample tracking and data models — Design schemas that track every sample end to end, including splits into multiple aliquots that all trace back to one source. Build this alongside the computational team so metadata flows cleanly into their pipelines. Handle samples from 50+ external sources without the system breaking under the variation.
Benchling ownership — Own the platform: entity and registry schemas, inventory, templates, assay schemas. Favor the simple solution that holds up over the clever one that doesn’t. Ship in small, visible pieces rather than one long implementation project.
Automation and integration — Partner with the Automation Lead and lab operations on barcode and sample tracking systems. Build and maintain integrations across Benchling, lab instruments, and AWS.
User experience — Spend real time watching how scientists actually use the system day to day. Translate what lab scientists and computational engineers each need into one system that works for both.
Project management — Own your own roadmap, flag what’s at risk before it becomes a problem. Manage any vendors or consultants involved in the build.