Benchling
Software Engineer, Full Stack (Document Canvas)
About this role
Benchling is hiring a Full Stack Software Engineer for the Document Canvas team to build a digital lab notebook that helps scientists plan, document, and share research. You'll own end-to-end projects across frontend and backend, collaborate with cross-functional teams, and help shape the technical vision for this widely-used product.
What you'll do
- Own large-scale projects from concept through user rollout, working across frontend and backend systems
- Design and implement backend models, APIs, and rich frontend components using modern frameworks
- Collaborate with product managers and designers to deliver user-focused solutions for scientific workflows
- Build new products and drive existing features toward completeness
- Mentor engineers and lead technical and architectural discussions across teams
- Shape long-term technical vision and roadmap for the product
What they're looking for
- Full-stack web development (frontend and backend)
- React or similar JavaScript-based frontend frameworks
- Backend API design and implementation
- Large-scale project ownership and execution
- Product-focused engineering mindset
- Technical leadership and mentorship
- Ability to work in mature codebases
- Quick iteration and shipping
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 large-scale project you owned end-to-end—how did you approach breaking it into iterative milestones?
- Walk us through your experience building both user-facing and backend systems. What's an example where frontend and backend work had to be tightly coordinated?