Software Engineer applicants have rated the interview process at Datadog with 3 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 49.1% positive. This is according to Glassdoor user ratings.
Candidates applying for Software Engineer roles take an average of 28 days to get hired, when considering 122 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 Software Engineer according to 122 Glassdoor interviews include:
Phone interview: 32%
One on one interview: 23%
Skills test: 13%
Presentation: 11%
Group panel interview: 6%
Background check: 5%
Other: 4%
Personality test: 3%
Drug test: 2%
IQ intelligence test: 2%
Here are the most commonly searched roles for interview reports -
I applied online. The process took 4 weeks. I interviewed at Datadog in May 2019
Interview
Applied online for a remote Software Engineer position.
First had a quick recruiter phone call.
Had a video chat coding exercise with an engineer. The exercise involved coding a simple statsd log parser to retrieve tags from the log lines. The interviewer left some time for questions and discussion about the team and the position.
Then had a video chat interview with the manager for the team. Discussed my experience and the position and team.
Following this was a take-home coding exercise to write a program that monitors a log file and performs parsing and aggregation of data and then displays summary of data and performs notifications based on metrics requirements, for example if errors are above a threshold and similar. This was a fun exercise.
After this got invited for a day of on-site interviews in NYC. Datadog arranged and paid for the travel. On-site visit consisted of:
- A different manager interview, where we talked about my experience and discussed the team. Also had to describe an architecture of a system I worked on and in detail elaborate on my contributions.
- Following this was a lunch with a couple of other engineers on the team at the office cafeteria. It was very nice to meet other people and just have some relaxing, social "off-time" in-between the interviews.
- Coding exercise interview again. Coincidentally this was the same problem I already did on a video call earlier in the process.
- System Design interview where I had to design and architect a YouTube-like application.
- Interview with VP of Engineering where we discussed my experience, the team, what I want to do, Datadog, etc... He was very open and available for any questions and any kind of discussion.
- Wrap up with the recruiter.
In the end they said I would probably get an offer if I was to relocate to NYC to work there, but a they weren't 100% sold on my for a remote for this specific position.
Throughout the interview numerous time the recruiter asked for feedback on the process and offered time for updates and check-ins and to answer any questions.
Overall a positive experience.
Interview questions [1]
Question 1
Write a simple program that parses log files and extracts specific tags out of it.
Describe a system you worked on and elaborate in detail on your contributions.
Design a YouTube-like application and describe architecture.
One knowledge interview and one technical interview afterwards. Knowledge was fine. During the tech one, the interviewer was not listening. The problem was a standard one. Got rejected after second round.
Interview questions [1]
Question 1
Knapsack problem with coins, solved via dynamic programming
Screening RH, qui mentor durant le process, puis deux rounds, le deuxième avec 4 test différents. Bon feedback tout du long. C'est fluide et le RH est là pour aider à préparer les sujets.
El proceso constó de tres fases principales. Primero, apliqué online a un puesto de trabajo disponible. Posteriormente, pasé a una entrevista técnica de aproximadamente una hora, enfocada principalmente en el desarrollo, integración y securización de APIs. También discutimos estrategias de despliegue, monitorización y gestión de recursos en la nube utilizando el ecosistema de Azure. Por último, realizamos un ejercicio conversacional sobre buenas prácticas de código y arquitectura. Fue un proceso fluido y el equipo fue muy profesional.