The interview process included:
The phone screen was very easy, with two super simple questions.
Next, I received the take-home coding challenge. It wasn't particularly difficult, but it did take me 8-10 hours to complete. I believe it's unfair to expect candidates to invest this much time, as it definitely excludes individuals who may not have that availability (e.g., parents).
Finally, I had the onsite interviews. These consisted of 1 traditional coding interview, 1 traditional systems interview, and one focused on my past experience. While I understand the theoretical value of a third interview, the questions my interviewer asked felt strange.
Specifically, I was asked very detailed questions (e.g., how many hosts were running in each cluster) about a 4-month internship I completed 5 months prior. At that point, I had been away from the job longer than I had actually worked there. I performed poorly because I hadn't retained that specific information.
Overall, while everyone was very pleasant, there were two significant dissatisfactions with the process. The only reason I wouldn't categorize this as a "negative" experience was the incredibly helpful recruiters. They even shared the specific feedback I received from the interviews, which will help me improve.
Build an HTTP monitor.
The following metrics were computed from 38 interview experiences for the Datadog Software Engineer role in New York, New York.
Datadog's interview process for their Software Engineer roles in New York, New York is very selective, failing most engineers who go through it.
Candidates reported having very good feelings for Datadog's Software Engineer interview process in New York, New York.