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.

Our goal is to build a Google that looks like the world around us — and we want Googlers to stay and grow when they join us. As part of our efforts to build a Google for everyone, we build diversity, equity, and inclusion into our work and we aim to cultivate a sense of belonging throughout the company.

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.

• Coordinate and deliver program communications in collaboration with program stakeholders, including metrics progress, meeting notes, meeting AIs, decision/escalation logs, newsletters, and websites.
  
• Collect data relating to program progress from program stakeholders. Maintain project trackers and status reports in collaboration with program stakeholders.
  
• Author program charter that addresses scope and timeline of basic programs, specifies program objectives and key results (OKRs), and explains resource requirements/dependencies, in collaboration with program stakeholders.
  
• Author stakeholder map that specifies who is impacted by/who influences, program outcome in close collaboration with program stakeholders.
  
• Triage technical bugs and feature requests alongside engineering stakeholders for purposes of prioritization, resourcing, and tracking execution.