Memorial Sloan Kettering Cancer Center interviews FAQs
Bioinformatics Engineer applicants have rated the interview process at Memorial Sloan Kettering Cancer Center with 3.3 out of 5 (where 5 is the highest level of difficulty) and assessed their interview experience as 50% positive. To compare, the company-average is 67.6% positive. This is according to Glassdoor user ratings.
Candidates applying for Bioinformatics Engineer roles take an average of 60 days to get hired, when considering 4 user submitted interviews for this role. To compare, the hiring process at Memorial Sloan Kettering Cancer Center overall takes an average of 29 days.
Common stages of the interview process at Memorial Sloan Kettering Cancer Center as a Bioinformatics Engineer according to 4 Glassdoor interviews include:
Phone interview: 30%
Group panel interview: 20%
One on one interview: 20%
Presentation: 20%
Skills test: 10%
Here are the most commonly searched roles for interview reports -
I applied online. The process took 4 weeks. I interviewed at Memorial Sloan Kettering Cancer Center (New York, NY) in Oct 2021
Interview
Phone call; no coding test; On-site interview
During the whole day of the on-site interview, I got to meet with the whole team and the department head. Basically just went over my resume. Asked me any challenge I ever faced and how I solved it.
I applied online. I interviewed at Memorial Sloan Kettering Cancer Center
Interview
OA, recruiter phone, 1-on-1 with engineer, panel interview (didn't get to this point though). Every step was very messy and lacked coordination. I was asked various frontend (React, Typescript, etc) questions on a Google Doc for a Bioinformatics Engineer position... I wish I was joking.
Interview questions [1]
Question 1
React & Typescript questions. I don't even remember the specifics because the whole time during the interview I was bewildered I would even be asked these questions.
I applied online. I interviewed at Memorial Sloan Kettering Cancer Center in Apr 2021
Interview
Easy and very long Interview process included one coding test with 3 Leetcode Medium questions. Then 3 weeks later, a get-to-know-each-other interview then 3 weeks later, an HR interview then 3 weeks later an interview with head of department. Then a take home quiz.
For the take home quiz, they assigned a frontend based task and said dont spend more than 4 hours. They did not describe how they want the code returned and when the deliverable was done and doing as expected, the interview rejected 2 weeks later with some of following excuses:
1. File name could have been different.
2. Code could have had test cases.
3. Code could have been on Github.
4. Variable name could be different.
5. More instructions should have been there.
6. Delivery method could have been different.
Who puts company quiz on Github ? Wouldnt it have been unprofessional? My code was named script.py. What name did he want ? Variables had meaningful names and comments too. If they had asked, i could have sent on Github, docker or anything. Apparently, a zip file with readme and requirements.txt to install all libraries werent enough.
All in all, a total unprofessional team who wouldn't specifically tell what they want and would expect a production quality output. Process seemed biased as they didnt ask a single technical question at all. Just wasted my time on take-home quiz and took 3 months in interview process, only to make silly excuses in take home quiz.
Interview questions [1]
Question 1
Just about past experience and a take home quiz and Algo monster difficult coding challenge