Google Technical Program Manager Interview Guide

The short answer: Google posts the role as Technical Program Manager, with numbered (II, III), Senior, Senior Leadership and Lead titles. Google publishes one hiring process for every role: an application, possible assessments, one or two recruiter calls, sometimes a small project, then a panel of interviews scored on the same rubric, with no brain teasers. Candidate guides add a hiring manager screen and describe a TPM loop of 4 to 6 interviews on program management, technical judgment, general cognitive ability and leadership. Candidate reports disagree on how technical that loop is: some describe one system design round and no coding, others describe coding rounds. Google says AI tools are not permitted during interviews. Last reviewed October 2026.

Google technical program manager interview: quick answers

The Google technical program manager role

What Google technical program managers work on, the skills its job postings ask for, and what a week can look like. Google posts the role as Technical Program Manager, Technical Program Manager II and III, Senior Technical Program Manager, Senior Leadership Technical Program Manager and Technical Program Manager Lead.

Google technical program manager levels and pay

Your level sets the bar you are interviewed against and the pay band of the offer.

Google's TPM postings do not state L numbers. They carry an experience badge (Mid or Advanced) and a minimum: 2 years of program management for TPM II, 8 years for Advanced and most Senior postings, and 10 years plus 7 in leadership for Senior Leadership TPM. TPM III appears in search results, but we did not open a TPM III posting.

Pay in Google's US job postings

Google's US TPM postings list one base salary range for the US. Each adds a bonus target (15% for Mid postings, 20% for Advanced and Senior, 25% for Senior Leadership), and several also name equity and benefits.

The location column is where the posting is based, since the range applies across the US. The GPS Tech Team posting requires an active TS/SCI clearance. Google says it shows ranges where local law requires. Ranges seen October 29, 2026.

Google technical program manager interview process

The steps follow Google's How we hire and interview tips pages, which cover every role. The hiring manager screen and the names of the loop rounds come from candidate guides and reports.

Based on Google's own pages and candidate reports.

Google says the process typically takes about 6 to 8 weeks once interviews start, that some roles have brought back in-person interviews after virtual first rounds, and that applicants who are not selected usually wait at least a year before reapplying for the same type of role. Because candidate reports disagree on coding, ask your recruiter whether your loop includes a coding round. Last reviewed October 2026.

What is different at Google

• The technical bar is real. Google's TPM postings ask TPMs to take part in architecture reviews and design discussions and give judgment on critical trade-offs. The Search Platforms posting asks for technical judgment equivalent to a practicing software engineer in the domain, and the Supply Chain posting asks the same for data platforms.
• Many US openings sit in infrastructure and AI. Current postings cover data center capacity and power, ML accelerator deployments, the TPU software stack across JAX and PyTorch, and Gemini post-training programs at Google DeepMind, alongside Pixel, Google Public Sector and Search.
• Titles are numbered and tiered. Google posts TPM II and III, Senior, Senior Leadership and Lead titles, and postings also shorten the role to TPgM. Program Manager titles without "Technical" are a separate job, and a candidate guide says those loops skip the technical judgment rounds.
• The amount of coding is disputed. One candidate guide says coding is usually not the focus of a TPM loop, but candidate reports describe whiteboard coding rounds, so confirm the format with your recruiter.
• Postings expect TPMs to use AI in the job. One posting asks TPMs to apply AI automation in program management, and a TPM II posting lists evaluating AI-generated code. In the interview itself, Google says AI tools are not permitted.

Google technical program manager interview questions

Questions from our bank, then practice prompts we wrote for this guide around Google's work.

1from typing import Dict, List, Tuple
2
3def critical_path(tasks: Dict[str, Tuple[int, List[str]]]) -> Tuple[int, List[str]]:
4    """Return (total duration, tasks on the critical path in order)."""
5    pass

1from collections import deque
2from typing import Dict, List, Tuple
3
4def critical_path(tasks: Dict[str, Tuple[int, List[str]]]) -> Tuple[int, List[str]]:
5    if not tasks:
6        return 0, []
7    indegree = {name: 0 for name in tasks}
8    children = {name: [] for name in tasks}
9    for name, (_, deps) in tasks.items():
10        for dep in deps:
11            if dep not in tasks:
12                raise ValueError(f"unknown dependency {dep}")
13            indegree[name] += 1
14            children[dep].append(name)
15
16    queue = deque(sorted(n for n, d in indegree.items() if d == 0))
17    finish, best_prev, done = {}, {}, 0
18    while queue:
19        name = queue.popleft()
20        done += 1
21        duration, deps = tasks[name]
22        start, prev = 0, None
23        for dep in sorted(deps):  # sorted so ties go to the first name
24            if finish[dep] > start:
25                start, prev = finish[dep], dep
26        finish[name], best_prev[name] = start + duration, prev
27        for child in children[name]:
28            indegree[child] -= 1
29            if indegree[child] == 0:
30                queue.append(child)
31    if done != len(tasks):
32        raise ValueError("plan has a cycle")
33
34    total = max(finish.values())
35    last = min(n for n, f in finish.items() if f == total)
36    path = []
37    while last is not None:
38        path.append(last)
39        last = best_prev[last]
40    return total, path[::-1]
41
42# Complexity: O(V log V + E log E) time for the sorts, O(V + E) space.

How to prepare

A plan for the Google loop, most important first:

1. Ask your recruiter which rounds your loop has and whether it includes coding, since candidate reports disagree.
2. Practice system design end to end on infrastructure and AI topics like the ones in current postings, such as capacity tracking or a staged rollout.
3. Build a library of 6 to 8 program stories (a launch, a slip, a conflict, an ambiguous start) with impact stated as X, as measured by Y, by doing Z.
4. Prepare one past program you can explain from architecture down to its riskiest dependency, for the hiring manager screen.
5. Practice "How would you approach" questions out loud, stating assumptions and whether you are going broad or deep.
6. Do two mock loops with no AI help, since Google does not permit AI tools in interviews.

Practice path

Courses that cover the rounds above:

• System Design
• Product Sense
• ML System Design
• Product Opportunity Sizing