Bioinformatics Engineer applicants have rated the interview process at Zymergen with 3 out of 5 (where 5 is the highest level of difficulty) and assessed their interview experience as 100% positive. To compare, the company-average is 41% positive. This is according to Glassdoor user ratings.
Candidates applying for Bioinformatics Engineer roles take an average of 36 days to get hired, when considering 3 user submitted interviews for this role. To compare, the hiring process at Zymergen overall takes an average of 30 days.
Common stages of the interview process at Zymergen as a Bioinformatics Engineer according to 3 Glassdoor interviews include:
One on one interview: 20%
Presentation: 20%
Group panel interview: 20%
Phone interview: 20%
Drug test: 10%
Background check: 10%
Here are the most commonly searched roles for interview reports -
I applied online. The process took 4 weeks. I interviewed at Zymergen (San Francisco, CA) in Aug 2018
Interview
Pretty standard seeming for this type of job: Multiple rounds of phone interviews then on-site. Phone interviews went from personality match w/ recruiter, discussion w/ hiring manager, tech screen w/ coding portion, and then all-day onsite. People seemed interested in my work and I enjoyed the process.
Interview questions [1]
Question 1
Go through a mock requirements design process with an end-user and come up with a prototype.
I had in total of 4 round interviews
One round phone screen
One round HR call
One round paired coding
On site: one hour presentation(seminar) and whole day back to back 1:1s
The whole process took me more than a month
I applied online. The process took 6 weeks. I interviewed at Zymergen (Emeryville, CA) in Sep 2018
Interview
First step was a phone screen with a recruiter. Second step, about one week later, was a phone interview with the hiring manager. One week later, did a pair programming session over the phone. About two weeks after that (due to vacations, etc) we set up an in-person interview. The interview consisted of a presentation, lunch, and a series of 1x1 interviews including a roleplay about interacting with scientists and gauging needs.
Interview questions [1]
Question 1
What do you like about your favorite programming language?
What challenges have you had interacting with non-programming scientists?
Let's go over a pretend request a scientist might have, how would you flesh this out?