Benchling
Software Engineer, Full Stack (Enterprise Lifecycle) (High Seniority)
About this role
Benchling seeks a senior full-stack engineer to lead the design and development of regulatory compliance and audit systems for biotech enterprises. You'll architect horizontally impactful solutions that enable FDA submissions and GxP-regulated workflows while mentoring engineers and exploring AI applications in compliance workflows.
What you'll do
- Design and develop innovative compliance and regulatory systems serving enterprise biotech customers
- Independently architect solutions for audit coverage, export systems, document lifecycle management, and regulatory workflows
- Lead multi-quarter initiatives, breaking down ambiguous requirements into technical plans and delivery milestones
- Write well-documented, well-tested code and establish quality standards at the team level
- Provide technical leadership through code reviews, architecture guidance, and mentorship
- Partner with product, design, and cross-functional teams to translate customer needs into technical solutions
What they're looking for
- Backend systems and APIs for cloud-based applications
- Full-stack development (backend-primary with frontend capability)
- Software architecture and scalable system design
- Technical leadership and mentorship
- Regulatory/compliance domain knowledge
- AI and LLM integration
- Code quality and documentation practices
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 time you architected and owned a large, multi-quarter initiative that spanned multiple systems or teams. How did you break down ambiguous requirements and ensure successful delivery?
- Describe your experience building backend systems and APIs for scale and reliability. What patterns or architectural decisions have you found most important when designing for growing enterprise demand?