Benchling
Software Engineer, Registry and Inventory
About this role
Join Benchling as a Software Engineer to build registry and inventory systems that power biotech R&D workflows used by 200,000+ scientists globally. You'll own full-stack projects (React + Python), shape technical architecture, and mentor engineers while working on mission-critical data integrity tools.
What you'll do
- Lead end-to-end design and implementation of high-impact features across the full stack (React + Python)
- Make foundational architecture decisions that improve system performance, reliability, and scalability
- Collaborate cross-functionally with product, design, and customer success teams to align on goals
- Proactively identify and address technical debt through refactoring and strategic platform improvements
- Mentor and support other engineers through guidance, code reviews, and knowledge sharing
- Design performant systems capable of handling complex, large-scale life sciences workflows
What they're looking for
- Full-stack development (React, Python)
- System design and scalability optimization
- Code quality and testing practices
- Cross-functional collaboration and communication
- Technical mentorship and leadership
- Performance optimization and reliability engineering
- Version control and engineering workflow best practices
- Rapid learning in ambiguous, domain-complex environments
Opens the application — the Jobs AI extension fills it for you. Set up autofill
Opens the official application on the employer’s site. No login required.
Benchling
Benchling builds an AI-powered platform for biotech R&D that integrates scientific workflows and data processes to accelerate research breakthroughs. The company is hiring software engineers across full-stack, customer engineering, agentic AI, and security roles to enhance developer productivity, build production AI systems, and protect sensitive research data.
- Website
- benchling.com
Likely interview questions
- Tell us about a complex, end-to-end project you led across the stack—what were the key technical decisions and tradeoffs you made?
- Describe your approach to designing systems that need to scale—how do you balance flexibility with validation and data integrity?