Datadog Interview Questions
& Process

Datadog's interview process is quite thorough, covering coding, design, delivery management, and people management. They offer extensive preparation materials and a general overview of each interview's focus, aiming to maximize your chances of success. While no single interview is excessively difficult, the sheer number and breadth of topics can be demanding. A unique aspect is their post-interview feedback: instead of a generic rejection, the recruiter calls to discuss high-level feedback from each interview, which is incredibly helpful for future opportunities. In my case, the feedback indicated a lack of depth in technical details. Datadog prefers candidates with deep expertise in certain areas, even if other areas are less developed, over those with moderate knowledge across the board. So, understanding this preference is key when going into their interviews.

I sent in my application online and then a recruiter from Singapore got in touch via email. They explained the steps: first, there's a Hackerrank assessment. After that, I'd interview with the hiring manager to discuss my background, projects, and tools, and to understand my motivation for this support engineering role. Then, I'd chat with some engineers on the team about scenarios, like managing multiple tickets and handling challenging customers. Following that, there's a live troubleshooting session where I'd need to role-play, asking questions about the problem presented, and I'd be given documentation. Finally, a conversation with a director about career aspirations and how Datadog fits in.

The interview process began with a first-round call with a recruiter based in Singapore. This interview was rescheduled twice, and one of those changes was communicated only about two hours before the original time. The interview was planned for 30 minutes but concluded in about 15. I was asked to share my questions at the start, and then we discussed my background, my interest in Datadog, and my reasons for pursuing Customer Success. The role itself is primarily focused on cross-sell and upsell opportunities, with renewals being handled separately. Overall, the conversation was brief and structured, and I didn't feel particularly engaged.

So the process started with a recruiter chat to see if I fit any of their roles. I mentioned I was in a bit of a rush with another interview process, so she really tried to speed things up for me. It included: 1. A coding interview about building a stream processing thing for logs and queries. 2. Another coding interview for a prefix tag search setup. 3. A system design round, kinda like designing r/place. 4. An interview digging into a past project of mine. 5. A values interview with questions about how I've dealt with people before. The recruiter was great throughout, keeping me updated and telling me what interviewers were looking for. I even met the team. Honestly, it was one of the best interview experiences I've had.