Datadog Program / Project Manager Interview Questions

1.Walk me through a project where you had no visibility into whether things were actually on track until something broke. What did you put in place afterward?

2.Give me an example of a program where you set up the status reporting and health tracking from scratch. What did you track and how did you decide what mattered?

3.Tell me about a time you had to coordinate a program across several engineering teams, all moving at different speeds. How did you keep the whole thing from stalling?

4.Describe a time you had to translate a complex technical problem — say, a performance issue or an infrastructure constraint — into a program decision for a non-technical audience. What did you leave out and why?

5.Tell me about a time a program you owned went sideways in production — a missed release, a bad rollout, something that affected real users. What broke down and what changed afterward?

6.Tell me about a time you were running a large, fast-moving program and realized the process you set up couldn't keep up with the scale. What did you change and how fast could you move?

7.Estimate how many engineering hours Datadog would need to invest to add a new cloud provider integration — say, Oracle Cloud — to Infrastructure Monitoring. Walk me through your assumptions.

8.You're a program manager for a team building a new Datadog dashboard feature. Halfway through the quarter, usage data shows only 15% of target users have adopted it. What's your diagnostic process?

9.Datadog's APM product is growing fast in enterprise accounts, but your team's quarterly planning data shows that enterprise onboarding programs are taking 30% longer than SMB ones. How would you figure out whether that's a problem worth solving, and where would you start?

10.You're program managing a migration of 500 Datadog enterprise customers from a legacy log pipeline to a new one. The migration has been running for three months and you're at 60% complete — but the remaining 40% are disproportionately the largest and most complex accounts. How do you restructure your plan to finish?

11.You're leading the program for a new Datadog security feature that needs sign-off from legal, security, engineering, product, and GTM before it can launch. Every team says they're aligned in writing, but you've seen two of these launches fail post-alignment because something wasn't actually resolved. How do you structure the final alignment process to actually de-risk the launch?

12.Datadog is planning to launch a new product tier aimed at mid-market customers — between self-serve and enterprise. You've been asked to estimate the program investment needed to support this launch across product, sales, and customer success. Where do you start and what does your estimate look like?

13.How do you decide what goes on a program roadmap versus what gets tracked as a dependency or a risk? Walk me through how you'd structure that for a new product launch.

14.You're running a program with five engineering teams and the project plan has drifted — some tasks are two weeks late, others finished early. How do you rebaseline the plan, and what do you tell leadership?

15.Imagine you're the PM for a feature that's shipping across Datadog's APM and Infrastructure Monitoring products at the same time. The APM team is ready, but the Infrastructure team is four weeks behind. How do you handle the launch decision?

16.You've been asked to improve on-time delivery for a team that's consistently missing sprint commitments by 20–30%. Where do you start, and what would you measure to know if anything is actually improving?

17.You're managing a program where three teams have conflicting priorities — each team lead says their work is the critical path, but you can see from the dependency map that only one of them is right. How do you resolve it and get alignment?

18.You're responsible for the program plan for a major Datadog product release, and two weeks before launch your security review surfaces a vulnerability that will take an unknown amount of time to fix. How do you manage the next 48 hours?

19.You're running a cross-functional program and a key stakeholder starts skipping your syncs and going directly to engineering leads to reprioritize work. How do you handle it?

20.A customer-facing release is scheduled for next Monday, and you find out on Thursday that one of the three teams contributing to it has a 40% engineer absence due to a sudden illness outbreak. What do you do?

21.You're PM on a program where engineering estimates have consistently come in 2x longer than planned for the past three sprints. Leadership is asking you why the dates keep slipping. What's your diagnosis process and what do you tell them?

22.You're leading a program to roll out a new internal tooling platform to 200 engineers across six product teams. Two weeks in, adoption is stalling — only one team is actually using it. What's your next move?

23.You're the program lead for a new enterprise feature that's six weeks from GA. A mid-sized customer on the design partner program has just escalated that the feature doesn't support a use case they were promised it would cover — and your sales team is citing it as a $1.5M renewal risk. Engineering says adding support for that use case is a 4-week effort. What do you do?

24.You've just been handed ownership of a program that's been running for four months without a PM. There's no documented plan, engineers are working off Slack threads, and there's a hard external deadline in ten weeks tied to a customer contract. How do you take control without blowing up what's already in motion?

25.Tell me about a time you had to get a sales or go-to-market team aligned on a timeline they weren't happy with. How did you bring them along?

26.Walk me through a time you had to onboard a skeptical stakeholder — someone who didn't see the value of the program you were running. What was their objection and how did you handle it?

27.Describe a time you had to present bad news — a slip, a scope cut, a missed milestone — directly to an executive or VP. How did you prepare and how did it land?

28.Tell me about a time two senior stakeholders had fundamentally different views on what success looked like for a program you owned. How did you resolve it?

29.You're managing a cross-functional program and a Finance or Legal stakeholder is blocking progress — their review is on the critical path but they're treating it as low priority. You have no authority over them. What do you do?

30.Tell me about a time you were managing a program where a key engineering partner consistently said everything was fine in standups but you suspected it wasn't. What did you do, and what did you find?