Software Engineer Interview Experience - United States
Process
The interview process was explained as:
- Call with recruiter
- Technical interview with an engineer
- Follow-up with recruiter
- Virtual onsite, behavioral + system design interview
I progressed as far as the technical interview. It was to last an hour. The engineer was not engaged and stopped me from continuing to code after I found the brute-force solution, despite my having explained I wanted to spend time improving the efficiency. I had never had an interviewer stop me from using the time I had been told I could use.
Questions
Describe one project you're particularly proud of.
Was this helpful?
Interview Statistics
The following metrics were computed from 39 interview experiences for the Benchling Software Engineer role in United States.
Success Rate
Benchling's interview process for their Software Engineer roles in the United States is extremely selective, failing the vast majority of engineers.
Experience Rating
Candidates reported having very good feelings for Benchling's Software Engineer interview process in United States.
Benchling Work Experiences
- 4.0Good people, ok outlookSoftware Engineer • Current EmployeeSan Francisco, California, United StatesJuly 25, 2025Pros: Friendly crew, team-dependent experience.Cons: Messy codebase and bad tech debt
- 4.0Kind People, Low PaySoftware Engineer • Current EmployeeSan Francisco, California, United StatesJune 1, 2025Pros: Some of the kindest, most capable, and humblest people I've ever worked with.Cons: Somewhat low drive and low pay relative to "elite" tech companies.
- 4.0Cool product, sound business, but easy days are overSoftware Engineer • Current EmployeeSan Francisco, California, United StatesMarch 18, 2025Pros: The eng team has become much more collaborative in the face of business challenges. Cool mission.Cons: Revenue flagging since ZIRP ended. New plans to improve revenue will take a while to pay off. Let's see how things are going next year.
