BenchSci logo

BenchSci Interview Questions
& Process

Real candidates share what happened, how many rounds they had,
and how the experience turned out.

Based on 115 interview experiences · FREE TO READ

2.9 Rounds average
Average Typical difficulty
51.3% Positive experience

Which role are you interviewing for?

30 roles · 115 reports

Candidate interview experiences

First-hand accounts from people who interviewed at BenchSci.

Showing 4 of 115
BenchSci logo
BenchSci

Machine Learning Engineer

Engineering · nearly a year ago

Senior Easy Negative experience No offer 2 rounds
Interview process
Recruiter call Technical screen Offer
Interview formats
Technical Behavioral

I applied for a UK-based Senior ML Engineer role. Started with HR screening, then a technical call. The technical interview felt off, with the interviewer mentioning 'vibe coding' and trying to make it very conversational, agreeing with me a lot. He assured me I'd pass and discussed the next steps. Then I got a rejection email saying they wanted someone more senior, which didn't align with the earlier chats. It felt like a performance rather than a real evaluation, lacked transparency, and showed poor company culture.

Confirmed questions1 question
  • Can you describe a past machine learning project you were involved in?
BenchSci logo
BenchSci

Team Lead

Engineering · nearly a year ago

Lead Average Positive experience Accept offer 3 rounds
Interview process
Recruiter call Phone screen Presentation
Interview formats
Case Presentation Behavioral

You start with a zoom screening with the Recruiter, and if that goes well, the hiring manager will talk to you. If the hiring manager thinks you might be a good fit, you'll get case studies to work on. These case studies usually have a week to prepare and you present them to a group of 3-4 people from the current team or from other teams.

Confirmed questions1 question
  • What makes you want to work at BenchSci?
BenchSci logo
BenchSci

Product Designer

Design · a year ago

Entry Average Negative experience No offer 2 rounds
Interview process
Recruiter call Technical screen Onsite
Interview formats
Behavioral Technical

The HR round was great. The first technical interview seemed like the interviewer wasn't really engaged and lacked experience. They just had a basic list of questions. It was a 45-minute video call to discuss my work history and experience, behavioral and situational questions, and my personal values. This felt impossible to cover in the time given, especially since 15 minutes were spent explaining the company and teams, leaving only 30 minutes for the actual interview. Some design questions were confusing as they didn't have clear answers and it wasn't a conversation at all. It was very formal, with me answering and the hiring manager just saying "thank you for that" after each response. They didn't seem interested in my examples, even saying it was okay not to use them.

Confirmed questions1 question
  • What would you do if a developer said they couldn't build your design?
BenchSci logo
BenchSci

Senior Software Engineer

Engineering · a year ago

Senior Average Negative experience No offer 2 rounds
Interview process
Recruiter call Technical screen Technical screen
Interview formats
Coding System Design

I applied online. A recruiter reached out to me and scheduled the first two interviews: Python Refactoring and System Design. I got an email from the interviewer a few minutes before the interview with a zip file which needed refactoring (they assume you have an environment set up on your machine without communicating this to you in advance). During the interview, he asked to open the project in an IDE and start refactoring. It is a very unstructured and open ended interview. I came out of it thinking I did very well given the unclear instructions and the fact that you can't finish it all within 45 minutes. The system design interview was also conducted in an unstructured way. The interviewer came to the meeting unprepared and took them a while to set up a whiteboard where he could explain the problem. The problem is very specific to BenchSci domain. I got a rejection email a few days after saying that they could provide more feedback on my performance if I ask for it and they will provide it to me within max 2-3 days. I asked for feedback and did not hear back for a week despite following up. After a couple of weeks, the recruiter responded with some poorly written feedback that did not make sense. They only shared the 'areas for improvement' with a few vague bullet points which out of 5, I actually had done 4 of them during the interview (unjust and lousy feedback!). This tells me the interviewers can get away with anything as the process is not regulated. They can let in their buddies and block people they have biases against. I'm glad this didn't work out for me as I wouldn't have wanted to work with these people.

Confirmed questions2 questions
  • Refactor this Python code.
  • Design a system to analyze scientific papers.

BenchSci Interview Questions

Quoted word for word from BenchSci interview reports.

What controls would you include in a western blot to validate an antibody?

Read reports

What strategies or techniques, such as using the React.memo hook, can be employed to optimize for heavy data usage in a React app?

Read reports

Can you explain the API and query needed to get records from a many-to-many relationship?

Read reports

What is state in a frontend framework? How would you manage users authentication and authorization in the system?

Read reports

What exactly is state in a frontend framework, and how would you handle user authentication and authorization within the system?

Read report

What specific endpoints would you suggest using for this type of system?

Read report

In the context of a React application using MaterialUI, which hooks do you think would be most beneficial?

Read report

What business insights or value can be derived from the data package provided?

Read report

Can you describe the frontend components necessary to complete the provided wireframe?

Read report

Formats, difficulty and experience

Across all 115 BenchSci interview reports.

Interview formats

Behavioral 38%
Technical 26.7%
Presentation 11.4%
Coding 9.4%
Case 5.9%

Interview difficulty

Easy 17.4%
Average 63.5%
Difficult 19.1%

Candidate experience

Negative 33%
Positive 51.3%
Neutral 15.7%

Reports by job function

Engineering 47
Research 24
Operations 10
Sales 9
Analytics 7
Other 6