Customer Facing Data Scientist applicants have rated the interview process at DataRobot with 3.1 out of 5 (where 5 is the highest level of difficulty) and assessed their interview experience as 40% positive. To compare, the company-average is 43.6% positive. This is according to Glassdoor user ratings.
Candidates applying for Customer Facing Data Scientist roles take an average of 55 days to get hired, when considering 15 user submitted interviews for this role. To compare, the hiring process at DataRobot overall takes an average of 32 days.
Common stages of the interview process at DataRobot as a Customer Facing Data Scientist according to 15 Glassdoor interviews include:
Phone interview: 35%
One on one interview: 18%
Presentation: 15%
Group panel interview: 12%
Skills test: 12%
Background check: 3%
Other: 3%
Personality test: 3%
Here are the most commonly searched roles for interview reports -
I applied online. The process took 1 week. I interviewed at DataRobot (Washington, DC) in Apr 2021
Interview
5 stage interview process:
Stage 1 involved talking with the recruiter and checking off some basic eligibility criteria. I had a little bit of time with the recruiter to talk through some basic questions.
Stage 2 involved talking with a senior data scientist on the team and answering a handful of technical questions related to data science and machine learning. Nothing too taxing in this round if you know your stuff. Again I had some time to ask some questions about the team.
Stage 3 involved a 1-hour live programming task, where I analyzed a dataset with my language of choice with the hiring manager and 2 other team members watching live. The task went from data ingestion to posing a problem and then implementing it as a ML problem. For this stage, you'll want to make sure that you're plenty familiar with your data science ecosystem -- although they do allow you to use Google and documentation.
Stage 4 involved the same group in Stage 3 and we talked through a business problem and how I would approach it from conception to implementation. This stage is meant to test how effectively you think as a data scientist and can take nebulous problems and turn them into data science problems.
Stage 5 involved a talk with just the hiring manager to answer any remaining questions I had about the role.
The recruiter and hiring manager were quite responsive during the whole interview process, and they made an outstanding and competitive offer at the end of the interview process. DataRobot is recruiting aggressively right now and it shows through their streamlined process.
Overall it was a quick interview process (about 1 week) and I felt that the interviewers were quite respectful of my time. The interviewers even asked for feedback on how to improve the interview process, which speaks to their focus on respecting their interviewers' time and streamlining the interview process.
I applied through a recruiter. The process took 5 months. I interviewed at DataRobot (Dubai)
Interview
5 rounds some technical questions mostly questions about prior experience and asked to deliver a presentation about previously delivered project
No coding take home assignment, no leetcode, no real hard DS grilling questions more trying to gauge your ability to explain technical concepts both to technical and non technical audience members
Interview questions [1]
Question 1
Could you present to us something you've previously worked on
The process included several rounds of talking with first a recruiter, then members of the team I was joining. It culminated with a presentation interview to two current employees posing as customers
I applied through a recruiter. The process took 3 weeks. I interviewed at DataRobot (Washington, DC) in Nov 2021
Interview
Approximately 5 technical (virtual) interviews and 1 behavioral. The technical interviews were highly repetitive in asking about the same supervised machine learning algorithms, pros/cons, and troubleshooting steps. Felt like there was no continuity between interviewers. Technical interviewers were adequate (but not excellent) technical communicators, but they were looking for very specific answers. Once I hit some arbitrary threshold of answering a question correctly, they'd interrupt and fire off the next question.
Interview questions [1]
Question 1
Name common preprocessing (cleaning) steps for a supervised machine learning model.
How would you deal with severe class imbalance while developing an ensemble model?