Data Scientist applicants have rated the interview process at Datadog with 3.4 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 48.8% positive. This is according to Glassdoor user ratings.
Candidates applying for Data Scientist roles take an average of 3 days to get hired, when considering 5 user submitted interviews for this role. To compare, the hiring process at Datadog overall takes an average of 26 days.
Common stages of the interview process at Datadog as a Data Scientist according to 5 Glassdoor interviews include:
Phone interview: 50%
Presentation: 25%
One on one interview: 25%
Here are the most commonly searched roles for interview reports -
Regular process with a first HR call to discuss the position and profile followed by a technical interview with a data scientist (leetcode easy/medium and basic stats questions), a rather long take-home assignment and finally a 3x1h round with a software engineer, data scientist and hiring manager.
Interview questions [1]
Question 1
algorithmic complexity, hypothesis of a linear regression
I applied through a recruiter. The process took 2 weeks. I interviewed at Datadog in Dec 2021
Interview
I was contacted by the recruiter on LinkedIn.
- A first technical interview with a data scientist (DS): coding test + knowledge test (regression algorithm)
- a homework, made of 2 exercises (time series analysis + software development)
The technical interviewer was very nice and the discussion sounded like a conversation between two DS (and not like a test given by a teacher to a student) so it gave me a good impression.
Unfortunately I was very disappointed by the way I was treated after returning the homework.
I was told there was no time limit and that there would be another interview with a DS to discuss more about the 1st exercise (time series analysis).
Instead, I did not have that chance and was rejected after having returned the homework for the main reason that the analysis was not "thorough enough" for the examiner.
Since it is supposed to be not limited in time, they could have simply asked me if I could "dig" a bit more... (I decided to return the homework when I considered I had answered the questions, knowing that I was not supposed to spend too much time on it.)
Anyway, considering that I spent several evenings to work on it (since I have a family and a job that keep me quite busy), I really think this is a lack of respect and consideration to not even let the candidate defend his work with the examiner.
In addition, the homework itself let me some bad impression of the company, notably regarding the 1st exercise (time series analysis):
- The questions were not clear at all (even the recruiter felt he had to explain them even before sending the homework).
- No effort was made obviously for the presentation (instructions given in a simple text file, without any formatting... It didn't look professional at all and you could wonder if they expect the same quality from you...).
- The exercise was quite scholar (with several oriented questions) and did not reflect the real daily work of a data scientist.
Interview questions [1]
Question 1
Server log analysis that contains mean response times and number of processed requests per second.
I applied online. The process took 6 weeks. I interviewed at Datadog in Feb 2022
Interview
As explained in previous posts, the interview process has 5 interviews and two take home tests.
- First step is a screening interview with the tech recruiter.
- The second interview is technical with some basic stats questions, LC easy/medium coding problem, and 10/15 minutes to present a technical project you did.
- Two take-home tests, one on data analysis and the other on coding.
- 3rd interview is more focused on data science. Just like the first technical, you start off by explaining a tech project you did. Then, you can expect general DS questions + some open-ended questions related to the take-home project (time series).
- 4th interview is a live coding problem.
- 5th interview is with the hiring manager. Don't be surprised if the discussion becomes technical at some point.
The interview process was very well organized and took about 6 weeks. The recruiter was highly available and gave me useful feedback after each interview.
Some tips:
- When presenting your project, don't hesitate to bring technical depth as it enables the interviewer to better gauge your level.
- Some questions are open-ended, so you are expected to show your reasoning around edge cases, potential problems etc.
- For the live coding problems, asking the right questions and communicating effectively with the interviewer is important. Present how you plan on solving the problem before diving into the code.
- For the take-home projects, I recommend asking the recruiter about the main points that will be evaluated. Unsurprisingly, you're expected to write clean and documented code.
- Prepare some questions for all the interviewers beforehand.