Datadog Product Manager interview typically runs 0 rounds: recruiter scheduling only. Based on one candidate, the process took about a few weeks and was marked by repeated last-minute cancellations.
$195K
Avg. Base Comp
$363K
Avg. Total Comp
3 rounds
Typical Rounds
1-2 weeks
Process Length
Our candidates report that Datadog’s biggest signal often appears before any substantive interview begins: whether the company can keep its own process together. In the experience we saw, the recruiter repeatedly canceled at the last minute, which left the candidate with no chance to demonstrate product thinking at all. That kind of pattern matters because it suggests the early funnel can be operationally brittle, and candidates should pay close attention to how clearly the team communicates and whether commitments are honored.
What stands out is not a deep assessment of PM skills, but the absence of one. When a process breaks down this early, it becomes a proxy for how much the company values candidate experience and internal coordination. For a Product Manager role at a developer tools company like Datadog, we’d expect strong ownership, crisp follow-through, and respect for time to show up immediately. Instead, the recurring theme here is that reliability and communication may be part of the evaluation whether or not anyone says so explicitly.
Our read is that candidates should treat the earliest interactions as meaningful data, not just logistics. If the scheduling layer feels messy, that can be a warning sign about how much friction you may face later. In this case, the most important takeaway is simple: at Datadog, the process itself can reveal as much as the interview questions would have.
Synthetized from 1 candidates reports by our editorial team.
Had an interview recently?
Share your experience. Unlock the full guide.
Real interview reports from people who went through the Datadog process.
I didn’t get far enough to have a real interview, which was honestly the most frustrating part. A recruiter reached out to me for a Product Manager II role, and the process never got past scheduling because the calls kept getting canceled at the last minute. The recruiter flaked within about 30 minutes of each scheduled call on three separate occasions. On the final attempt, I even checked in a few hours beforehand to make sure the time still worked, and they still backed out literally at :59. There wasn’t any technical screen or behavioral conversation to judge, just a string of scheduling conflicts that made the whole thing feel pretty unprofessional.
I know things come up, but this went beyond a one-off reschedule and made it hard to take the process seriously. Since there were no actual interview questions, I can’t speak to the PM loop itself, but my takeaway was that communication and candidate respect were weak at the recruiter stage. If you’re interviewing here, I’d make sure you have firm confirmation before blocking time and be prepared for a process that may not be very organized.
Prep tip from this candidate
There wasn’t a substantive interview loop here, so the only practical prep is to confirm every recruiter call in writing right before the meeting and not assume the slot is locked until the recruiter actually joins.
Share your own interview experience to unlock all reports, or subscribe for full access.
Sourced from candidate reports and verified by our team.
Topics based on recent interview experiences.
Featured question at Datadog
How would you make a control group and test group to account for network effects
| Question | |
|---|---|
| Trial User Segmentation | |
| Production Rollout Challenges | |
| Docs Metrics | |
| Empty Neighborhoods | |
| 2nd Highest Salary | |
| Top Three Salaries | |
| Rolling Bank Transactions | |
| Customer Orders | |
| Comments Histogram | |
| Closest SAT Scores | |
| Manager Team Sizes | |
| Subscription Overlap | |
| Upsell Transactions | |
| Monthly Customer Report | |
| Download Facts | |
| Experiment Validity | |
| First Touch Attribution | |
| Google Maps Improvement | |
| Employee Salaries (ETL Error) | |
| Hurdles In Data Projects | |
| Random SQL Sample | |
| Lowest Paid | |
| Button AB Test | |
| Cyclic Detection | |
| Average Quantity | |
| Instagram TV Success | |
| Last Transaction | |
| Top 3 Users | |
| Project Budget Error |
Synthesized from candidate reports. Individual experiences may vary.
Use this first stage to prepare for resume context, role fit, motivation for Datadog, logistics, and a concise walkthrough of relevant projects. The available candidate evidence is sparse, so this stage is framed as a practical preparation bucket rather than a claim that every candidate saw a separate formal round. Evidence used for this guide includes: Recruiter Screen Scheduling: A recruiter reaches out to coordinate an initial conversation for the Product Manager II role. In this experience, the process did not progress into an actual interview because the recruiter repeatedly canceled at the last minute, so this stage appears to be the first contact and scheduling step.
A recruiter reaches out to coordinate an initial conversation for the Product Manager II role. In this experience, the process did not progress into an actual interview because the recruiter repeatedly canceled at the last minute, so this stage appears to be the first contact and scheduling step.
Close preparation with examples that show ownership, communication, and how you work with cross-functional partners or technical peers. The available candidate evidence is sparse, so this stage is framed as a practical preparation bucket rather than a claim that every candidate saw a separate formal round. Where the source evidence blended final steps together, this stage captures the final evaluation themes without adding unsupported company-specific claims.