Datadog Product Manager Interview Questions
& Process

Had a recruiter call which was easy, just talked about my interest in the company and my background, also logistics. Then a technical interview with someone from the product management team. They asked about the same stuff but also including a project I've worked on, a B2B tool I like, explanation of its software architecture and more PM related questions.

So, I had this initial HM screen thing, then went into four structured rounds: one with engineering on how we'd collab, another was a deep dive on analytics, a technical round, and then a case study. Most of it felt pretty good and relevant to the PM role, but it really felt like the final call depended way too much on just one of those rounds, not the whole picture. It's kinda weird because Datadog is doing cool stuff in observability and cloud infrastructure, and the interview setup looked good on paper with clear steps and good case studies. Talking to most of the team, especially on the technical and analytical sides, was actually pretty engaging. But yeah, the main bummer was how much weight one person's opinion seemed to have, even though I did well in the other parts. Then the feedback was super vague and confusing – they said I didn't need to improve anything but still no offer. One interviewer was totally checked out and dismissive, which felt more like they were just trying to block me than actually assess me. And the recruiter's vibe was way too casual, almost unprofessional at times, which just added to the frustration when they gave me a 2-minute call after I spent two weeks working hard to say they weren't moving forward, with zero actual feedback. Honestly, they should really rethink how they weigh everything, make sure feedback is actually useful, and remember candidates put in effort too.

Got contacted by a recruiter. The process was pretty standard but also kinda weird - started with a recruiter screen, then a 1-hour Hiring Manager interview. After that, it was an 'onsite' which was actually 6 separate 1-hour interviews: one with Engineering, one Technical, one Analytical, and one Case Study. So yeah, spent about 6 hours just interviewing, plus another 5-6 hours prepping. I even read their latest financial reports. It's a huge time commitment, especially when you're already working full-time. I was pretty bummed at the end because they said I aced all the PM parts but failed the Technical Interview. They asked me to design the Netflix homepage from a backend infra perspective and thought I wasn't technical enough on recommendation engines. I mean, I'm not an engineer. I get they want folks to understand the tech, which is fine. I was an engineer for 4 years before becoming a PM and can definitely talk shop with my team, they love that. But I've never had to build the system architecture myself in my PM career. Ultimately, I think it wasn't the right fit for me and DD. Honestly, I'm glad it worked out this way because I want a company that judges me on my PM skills, not expects me to invent backend architecture. So, heads up if you're interviewing: make sure you actually want a role where technical understanding is super important before you dump 10-12 hours into it.