Datadog PM candidates describe a recruiter screen, a hiring manager conversation, and case, analytical, technical and cross-functional rounds. Technical fluency with engineers is a recurring theme, though depth varies by report.
$194K
Avg. Base Comp
$270K
Avg. Total Comp
2-6 rounds
Typical Rounds
Not reported
Process Length
Datadog Product Manager candidates describe a process that blends product judgment with real technical conversation. Most accounts start with a recruiter or HR screen and a hiring manager discussion, then move to several focused interviews. Reported rounds include a case study, an analytical exercise (one Senior PM candidate was asked to design a CEO dashboard), an engineering or cross-functional conversation, a presentation and a technical interview.
The technical round is where reports diverge most. One candidate called it easier than expected and walked through a past technical project and the architecture of a B2B tool they admired. A Senior PM candidate was asked to design a Netflix-style recommendation engine from a backend infrastructure angle and was rejected on technical architecture despite strong feedback on the PM rounds. Another candidate with an offer said the hiring manager probed how closely they worked with engineering, QA testing, code review and the tech stack, with emphasis on DevOps and cloud infrastructure. Prepare to reason about infrastructure trade-offs aloud, and be honest about how hands-on you are.
Business thinking also appears. One candidate with an offer worked through why monthly active users could grow while subscription revenue stayed flat, covering churn, downgrades and customer mix. Another was asked about pricing when a customer demands a discount. A third presented a data-heavy product they had designed and how they measured its success, so bring metrics and decisions as well as a narrative.
Experiences vary in tone. Several candidates praised recruiter communication and clear expectations, while one reported repeated last-minute cancellations before any interview took place. Confirm scheduling in writing, and prepare examples of measuring success and resolving disagreements with engineering.
Synthesized from 11 candidate 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.
The question that really made me think was straightforward on the surface but had a ton of depth: you've got a subscription service where monthly active users are growing steadily, but revenue stays flat. What could be causing that? I spent a good chunk of the second round working through different scenarios—churn patterns, downgrades, customer composition shifts, pricing strategy misalignment. The interviewer was clearly interested in seeing how I'd think through a revenue problem that doesn't have an obvious answer, and how I'd approach bringing functions together to diagnose and solve it.
I had two rounds overall. The recruiter screen was basic—just questions about my background and experience, nothing that required advance prep. Then the second round with a senior PM is where the actual assessment happened. They were really focused on B2B product thinking, specifically around subscription services and revenue models. That's clearly core to Datadog's business, so it made sense. Beyond the scenario questions, there were behavioral questions woven in, though the round was mostly centered on working through ambiguous product and business problems.
The whole process felt well-designed and purposeful. Not overly long, clearly structured. Ended up getting the offer.
Prep tip from this candidate
Prepare for B2B subscription revenue scenarios where user growth doesn't match revenue growth. Be ready to work through drivers like churn, downgrades, and customer composition shifts, and discuss how you'd collaborate with finance and product teams to diagnose the issue.
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 | |
|---|---|
| Hurdles In Data Projects | |
| Trial User Segmentation | |
| Client Solution Pushback | |
| Production Rollout Challenges | |
| Data Cleaning Experiences | |
| Docs Metrics | |
| Newsfeed Model | |
| Empty Neighborhoods | |
| 2nd Highest Salary | |
| Experiment Validity | |
| Button AB Test | |
| Top Three Salaries | |
| Rolling Bank Transactions | |
| Customer Orders | |
| Top 3 Users | |
| Comments Histogram | |
| Closest SAT Scores | |
| Find the First Non-Repeating Character in a String | |
| Manager Team Sizes | |
| Subscription Overlap | |
| Monthly Customer Report | |
| Upsell Transactions | |
| Download Facts | |
| Google Maps Improvement | |
| First Touch Attribution | |
| Losing Users | |
| Employee Salaries (ETL Error) | |
| Size of Joins | |
| Random SQL Sample |
Synthesized from candidate reports. Individual experiences may vary.
Candidates report an opening call with a recruiter or HR covering background, interest in Datadog and logistics. Questions such as why Datadog were mentioned. Several describe recruiters who set clear expectations for later rounds, though one candidate reported repeated last-minute cancellations before any interview took place.
Several candidates describe a hiring manager round that digs into past work and ownership. One was asked about a product's value proposition, how closely they work with engineering, and QA, code review and the tech stack. Expect this round to test credibility on both product and engineering topics.
Reports include a case study tied to one of Datadog's products and an analytical exercise to design a CEO dashboard. One candidate worked through flat revenue despite growing users, and another discussed pricing a customer discount request. Candidates describe these as open-ended, so show your reasoning and trade-offs.
Candidates report engineering and technical interviews that vary in depth. One found the technical round easier than expected. A Senior PM candidate was asked to design a Netflix recommendation engine from a backend infrastructure angle and was rejected on technical architecture. Prepare to explain trade-offs concretely.
Later stages differ by candidate. One described a whiteboarding round and a cross-functional round on handling disagreements with product and engineering stakeholders. Two describe a presentation round, including a case study portfolio presentation. Another met a director as the final step. Outcomes were mixed across these reports.
