Context Technical Program Manager, Core
for sections like About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. Only include sections that have real specific content. We must preserve all substantive info, remove boilerplate: cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, application instructions. Also remove lines like "Learn more about benefits at Google ." maybe part of responsibilities? Actually that line is separate; it's a link to benefits; but we can keep as part of responsibilities? It's a sentence: "Learn more about benefits at Google ." Might be considered boilerplate? It's a link to benefits; but it's not substantive. Probably remove. We need to include sections: About the role (the paragraph after "About The Job") maybe we treat as About the role. Responsibilities: list of responsibilities bullet points. Requirements/Qualifications: we have Minimum qualifications and Preferred qualifications. Could combine into Requirements or Qualifications. Skills: maybe not explicit separate. Benefits: we have mention of benefits but not detailed; only "Individual pay is determined by factors..." and then pay range and bonus etc. Benefits not detailed. So we should not create Benefits section unless posting actually states them. It mentions "+ equity + benefits" but not detail. So we should not create Benefits section because no specific benefits listed. Pay: we have pay range and bonus target etc. So include Pay section. Schedule: not mentioned, so omit. We also have location note: "Applicants in San Francisco: Qualified applications with arrest or conviction records will be considered for employment in accordance with the San Francisco Fair Chance Ordinance for Employers and the California Fair Chance Act. Note: By applying to this position you will have an opportunity to share your preferred working location from the following: San Jose, CA, USA; San Francisco, CA, USA." This is location info; could be part of About the role? Might be considered metadata; we could put in a short
maybe under About the role or as a separate note. The instruction: do NOT put Job ID / requisition numbers as headings — fold minor metadata into a short
or drop it. So we can include a short paragraph about location and fair chance. We must remove EEO boilerplate lines: "Google is proud to be an equal opportunity workplace..." etc. Also "We also consider qualified applicants regardless of criminal histories, consistent with legal requirements." That's actually relevant to fair chance but maybe duplicate; we already have fair chance statement. Might keep but it's EEO boilerplate; remove. Also remove "See also Google's EEO Policy and EEO is the Law." etc. Remove accommodation line. Now structure:
About the role
... include the fair chance note and location note plus the descriptive paragraph about the job? The "About The Job" section starts after "About The Job". We'll combine. We need to preserve all substantive information: The paragraph after "About The Job": "A problem isn’t truly solved until it’s solved for all...." etc. Also the description of Core team etc. Also the individual pay line? That belongs to Pay section. Responsibilities: list bullet points after "Responsibilities". We need to capture each bullet. Let's extract responsibilities: From text: "Responsibilities Learn more about benefits at Google . Be a highly credible thought leader within Google and industry on the subject matter domain of the respective organization. Establish a reliable and visible cadence for portfolio reviews, decision making, prioritization, and resource management, whereby improvements are measurable and the impact can be felt organization wide. Drive measurable program performance gains correlated to execution velocity. Be a change advocate responsible for initiating and leading multiple organizations through pivots needed to address shifts in business trends and priorities.Lead strategic planning framework for a complex program portfolio including direct influence over resourcing decisions, planning cadence, and planning stakeholders." We need to split into bullet points. Each sentence seems a responsibility. Also there is "Learn more about benefits at Google ." which we should drop. Thus responsibilities: - Be a highly credible thought leader within Google and industry on the subject matter domain of the respective organization. - Establish a reliable and visible cadence for portfolio reviews, decision making, prioritization, and resource management, whereby improvements are measurable and the impact can be felt organization wide. - Drive measurable program performance gains correlated to execution velocity. - Be a change advocate responsible for initiating and leading multiple organizations through pivots needed to address shifts in business trends and priorities. - Lead strategic planning framework for a complex program portfolio including direct influence over resourcing decisions, planning cadence, and planning stakeholders. Now Minimum qualifications: - Bachelor's degree in a technical field, or equivalent practical experience. - 10 years of experience in program management. Preferred qualifications: - 10 years of experience managing complex cross-functional or cross-team projects. - Experience working closely with executive engineering leads. - Experience delivering technical innovation involving complex system issues. - Experience with solving complex system issues with technical innovation and ability to quickly learn/pick up new concepts (e.g., Generative AI, Large Language Model (LLM) space). We could combine Minimum and Preferred into Requirements/Qualifications sections. The instruction: use headings like Requirements, Qualifications, Skills. We could have a Requirements section for minimum, and Qualifications for preferred, or combine. Prefer few substantive sections. Could have a single "Requirements" section containing both minimum and preferred, maybe split into sub-bullets? But we need to preserve all info. Could do:
Requirements
- Minimum qualifications:
- Be a highly credible thought leader within Google and industry on the subject matter domain of the respective organization.
- Establish a reliable and visible cadence for portfolio reviews, decision making, prioritization, and resource management, whereby improvements are measurable and the impact can be felt organization wide.
- Drive measurable program performance gains correlated to execution velocity.
- Be a change advocate responsible for initiating and leading multiple organizations through pivots needed to address shifts in business trends and priorities.
- Lead strategic planning framework for a complex program portfolio including direct influence over resourcing decisions, planning cadence, and planning stakeholders.
- Bachelor's degree in a technical field, or equivalent practical experience.
- ... but nested lists maybe not needed. Simpler: list all qualifications with indication.
We could do two subheadings? Not allowed; only h3 for section headings. Could embed text like "Minimum qualifications: ..." within
then list. Better:
Requirements
Minimum qualifications:
- ...
Preferred qualifications:
- ...
About the role
A problem isn’t truly solved until it’s solved for all. That’s why Googlers build products that help create opportunities for everyone, whether down the street or across the globe. As a Technical Program Manager at Google, you’ll use your technical expertise to lead complex, multi-disciplinary projects from start to finish. You’ll work with stakeholders to plan requirements, identify risks, manage project schedules, and communicate clearly with cross-functional partners across the company. You're equally comfortable explaining your team's analyses and recommendations to executives as you are discussing the technical tradeoffs in product development with engineers. As a Staff Technical Program Manager, you will drive strategic cross-organizational AI initiatives focused on Retrieval-Augmented Generation (RAG) and next-generation search offerings. In this role, you will lead high-impact programs end-to-end, including Gemini Embeddings Service and agentic retrieval systems, balancing research, technical execution, and product adoption. You will partner closely with senior engineering leaders, Product Managers, and SRE teams to deliver scalable, low-cost retrieval infrastructure capable of handling complex workloads. Managing multi-product area dependencies and navigating ambiguity, you will define execution roadmaps, optimize program delivery through AI tooling, and pilot solutions for key client applications. Additionally, you will serve as a key liaison to executive leadership and partner teams across Search and DeepMind. You will establish program dashboards, maintain transparent stakeholder communication, and ensure organizational alignment to achieve critical business outcomes. The Core team builds the technical foundation behind Google’s flagship products. We are owners and advocates for the underlying design elements, developer platforms, product components, and infrastructure at Google. These are the essential building blocks for excellent, safe, and coherent experiences for our users and drive the pace of innovation for every developer. We look across Google’s products to build central solutions, break down technical barriers and strengthen existing systems. As the Core team, we have a mandate and a unique opportunity to impact important technical decisions across the company.
Applicants in San Francisco: Qualified applications with arrest or conviction records will be considered for employment in accordance with the San Francisco Fair Chance Ordinance for Employers and the California Fair Chance Act. Note: By applying to this position you will have an opportunity to share your preferred working location from the following: San Jose, CA, USA; San Francisco, CA, USA.
Responsibilities
Requirements
Minimum qualifications: