Benchling
Software Engineer, Platform (Developer Experience)
About this role
Benchling seeks a Software Engineer to lead developer experience initiatives within the Platform team, focusing on building release tooling and frameworks that enable rapid, efficient code deployment to production. You'll partner with engineering teams to streamline workflows, gather feedback, and champion best practices across the organization.
What you'll do
- Design and implement release tooling enabling code changes to production within 10 minutes
- Build development, testing, and packaging tools that reduce friction in engineering workflows
- Gather and iterate on developer experience improvements using qualitative and quantitative data
- Integrate quality assurance and feedback mechanisms into software development processes
- Champion engineering best practices and operational patterns across the Engineering organization
- Collaborate cross-functionally with product, design, and engineering to enhance developer productivity
What they're looking for
- Software engineering (4+ years experience)
- Web framework expertise (Node.js or Python preferred)
- Release engineering and CI/CD tooling
- Problem-solving and iterative feedback integration
- Product-first mindset and rapid shipping mentality
- Cross-functional communication
- Empathy for end-user challenges
- Willingness to learn life science domain knowledge
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
- Describe a time you built developer tooling or infrastructure—what problem did it solve and how did you measure its impact?
- How would you approach reducing deployment time from current state to 10 minutes, and what metrics would you track?