Datadog · Primly Community

Datadog product manager interview questions, what they focus on (2026 loop)

pm_priya · 4 replies

Just finished my Datadog PM loop for a role on the platform product side. It's a B2B infrastructure monitoring company, so the PM interview has a different flavor than consumer or growth PM interviews. Sharing details because there's basically nothing specific out there for Datadog PM.

The process: Recruiter screen, then a take-home exercise, then a final round with 4-5 interviewers.

Take-home: They sent me a product brief about a fictional observability feature and asked me to present a PRD-like doc. Time limit was 72 hours but it doesn't need to be a dissertation. I did about 4-5 pages covering user problem, target persona, metrics for success, and a rough feature prioritization. They gave me 15 minutes to present this at the start of the final round, then 30 minutes of Q&A from the panel.

Panel questions I remember: How would you define the ICP for a new Datadog product targeting small engineering teams vs enterprise? Walk me through how you'd prioritize a backlog when two high-value customers are asking for contradictory things. Tell me about a time you shipped something and it didn't land. What did you do? How do you think about feature adoption metrics for a tool engineers use but don't consciously think about?

That last one is genuinely interesting for an observability product. If Datadog is working, you don't think about it. How do you measure value in absence?

Technical depth expected: More than most PM interviews. They're fine if you don't write code but you should know what APM is, why distributed tracing matters, what cardinality means in the context of metrics. Not deep, but not nothing.

Comp for PM roles I've seen in the community: mid-senior PM in NYC seems to be landing in the 180-240k total comp range depending on level, with equity making up a meaningful chunk. I can share more details if folks are curious.

4 replies

apm_aisha

The take-home PRD exercise is interesting. Did they give you a real product area to work on or something completely hypothetical? I'd be worried about spending 10+ hours on something that's just a screening filter.

pm_priya

Hypothetical product scenario, not a real one. They're not getting free consulting. And honestly 4-5 tight pages took me maybe 6 hours. Don't over-engineer it. They're looking for clear thinking, not a 30-page MRD.

jordan_pm

The 'feature adoption metrics for a tool engineers don't consciously think about' question is excellent. That's the kind of question that separates people who think about product strategically from people who just memorize frameworks. There's no formula answer.

growth_gabe

Interesting that it's so B2B-heavy. I have more consumer PM background. Did they seem interested in people with that background or was it clearly a liability?