Google Program / Project Manager Interview Questions

1.Tell me about a project where the requirements or success criteria kept shifting underneath you. How did you keep it moving?

2.You're asked to improve a key program metric by 30% over two quarters. Walk me through how you'd diagnose the problem and figure out where to focus first.

3.You're handed a program in a domain you know nothing about — new technology, new business unit, unfamiliar stakeholders. Walk me through exactly how you'd get up to speed and establish credibility in the first 30 days.

4.Walk me through the most complex program you've managed end-to-end. What was your actual tracking and risk management system, and where did it break down?

5.Tell me about a time you drove alignment across teams that didn't report to you, where at least one of them actively resisted what you were pushing for.

6.Describe a time you had to make a meaningful call with incomplete data and limited time. What did you decide, and what would have changed if you'd waited for more information?

7.Estimate how many active Google Workspace users there are globally, and what fraction of them are paying customers versus free tier. Walk me through your reasoning.

8.A metric you own — say, weekly active users of an internal Google Cloud ops tool — drops 20% in a single week. Nothing was released that week. How do you figure out what happened?

9.Google Maps is adding a new feature for local business owners to respond to reviews directly from the app. You're the PM. The feature is built and ready — how do you scope the launch rollout, and what's your sequencing logic?

10.You're running a program to migrate a large Google Cloud enterprise customer from an on-prem data warehouse to BigQuery. You're at 60% migration, the deadline is fixed, and the customer just told you they need to freeze all system changes for 30 days due to an internal audit. What do you do?

11.Estimate the annual cost to Google of storing all YouTube videos uploaded in a single day. Walk me through every assumption you make.

12.You're the PM for a multi-quarter program to roll out a new AI-assisted feature inside Google Search Console for webmasters. Six months in, usage data shows power users love it, but median adoption is near zero. You have one quarter left before the program formally closes. What do you do with it?

13.How do you build and maintain a program roadmap when you're managing dependencies across three or more teams? Walk me through the actual artifact and how you keep it current.

14.What's your approach to writing a program status update that actually gets read and acted on? What do you include, and what do you cut?

15.You're running a program with a fixed launch date that the business has already communicated publicly — say, a feature going live across Google Maps for a major market. Two weeks out, engineering tells you one component will be three weeks late. How do you handle it?

16.Walk me through how you would define and instrument success metrics for a new internal tooling program — say, a workflow tool rolled out to Google Cloud sales teams. How do you know if it's working six months in?

17.You're the PM for a cross-functional program where a partner team consistently misses their deliverables, and your escalation path is ambiguous — they're senior to you and not in your reporting chain. The delay is now on the critical path. What do you do?

18.You're asked to consolidate two programs that were run by different teams into one unified program — different charters, different stakeholders, overlapping but not identical scope, and one team feels like they're being absorbed. How do you structure the first 60 days?

19.You're running a program review meeting with six stakeholders and halfway through, two of them start debating a technical decision that's outside your agenda and outside your control. The meeting is burning time and you still have three critical items to cover. How do you handle it?

20.You've just been assigned to run a quarterly business review for a Google Cloud program that spans four teams. You have two weeks, no existing template, and the teams have never done a unified QBR together before. Walk me through how you structure the two weeks.

21.You're managing a program that's on track, but you notice a pattern: your weekly status report is consistently ignored by two of the three executives who need to act on it. What do you do?

22.You're the PM for a cross-org initiative and midway through, a key engineering team tells you they need to reprioritize to support a high-profile Google Search launch. Their work is on your critical path and no one above you has officially deprioritized your program. What's your move?

23.You're three months into a program when you discover that two separate teams have been building nearly identical tooling in parallel — neither knew the other existed. Stopping one team will upset them; letting both continue wastes six-figure engineering investment. You have no authority over either team. What do you do?

24.A Google Cloud enterprise customer is unhappy with the rollout of a feature your program delivered — their adoption is near zero and their account team is blaming poor onboarding, which falls under your program scope. You have no direct customer access and the account team is defensive. How do you get to the truth and fix it?

25.Think of a time you had to get a senior stakeholder excited about something they hadn't asked for — a process change, a new tool, a shift in how a program was structured. How did you sell it?

26.Describe a time you were the bridge between a technical team and a non-technical business stakeholder — both sides thought they were communicating clearly, but nothing was actually landing. How did you fix it?

27.Tell me about a time you had competing stakeholders who each thought their priority was the program's top priority — and they weren't wrong, both legitimately were. How did you make the call on sequencing?

28.You're running a program and you realize your executive sponsor has a fundamentally different understanding of what success looks like than you and the working teams do. It's month two, no one has flagged this, and the program is on track — but toward the wrong target. How do you handle it?

29.You've been asked to get sign-off on a program plan from five stakeholders across sales, engineering, finance, and legal — and you have one week. Two of them are responsive. The other three are not. Walk me through exactly what you do.

30.Tell me about a time a key stakeholder lost trust in you or your program mid-flight — not because of a catastrophic failure, but because of an accumulation of small things. How did you detect it, and what did you do to rebuild?