Tech Lead, TPU AI Infrastructure

We need to output HTML fragment with sections: headings

for sections like About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. Only include sections that have real specific content. Remove boilerplate, duplicate lines, application instructions, EEO, etc. We need to parse the posting. Key info: - In most instances, this position requires in-person interviews as part of the hiring process. (Probably not needed as a section; maybe we can put in a short paragraph under something like "Hiring Process"? But we only have allowed headings; we could include in a paragraph under maybe "About the role" or similar. But we need to preserve all substantive info. Could embed in a

under "About the role" or a generic section? The instruction: Use

for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). So we can have sections like About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We need to decide which sections have content. Let's extract: About the role: The posting includes a paragraph: "About The Job Google's software engineers develop the next-generation technologies...". That's about the role. So we can put that under

About the role

with paragraphs. Responsibilities: There's a "Responsibilities" heading in the posting with bullet points: "Learn more about benefits at Google . Define the technical roadmap...". Actually the bullet list includes: "Learn more about benefits at Google ." (maybe a link). Then bullet points: Define the technical roadmap..., Own architectural..., Establish and maintain..., Foster a culture..., Coach and mentor... So we can put those as

• . Requirements: Minimum qualifications listed: Bachelor's degree or equivalent practical experience. 8 years of experience with software development in one or more programming languages (e.g., Python, C, C++, Java, JavaScript). 5 years of experience building and developing large-scale infrastructure, distributed systems or networks, or experience with compute technologies, storage, or hardware architecture. 5 years of experience testing, and launching software products. 3 years of experience with software design and architecture. Qualifications: Preferred qualifications: Experience with Temporal orchestration workflows or similar workflow engines. Expertise in Kubernetes, ArgoCD, and container orchestration. Familiarity with hardware/software integration, hardware lifecycle, or bare-metal provisioning (PXE). Excellent communication skills with the ability to manage stakeholder relationships and drive cross-functional alignment. Skills: Could be derived from preferred qualifications? But we already have Qualifications section; maybe we can combine? The instruction says we can have Skills section separate if there is content. The preferred qualifications could be considered Skills. But we already have Qualifications (maybe split into Minimum qualifications and Preferred qualifications). However the allowed headings include Requirements, Qualifications, Skills. We could put minimum qualifications under Requirements, and preferred qualifications under Qualifications or Skills. Let's decide: Use Requirements for minimum qualifications, Qualifications for preferred qualifications. Or we could put both under Requirements and Qualifications. We'll follow typical: Requirements = minimum qualifications, Qualifications = preferred qualifications. Skills: Could be extracted from preferred qualifications like "Excellent communication skills..." but that's more a skill. Could also include technical skills like Kubernetes etc. But we already have them under Qualifications. To avoid duplication, maybe we put technical skills under Skills and soft skills under Qualifications? But we need to preserve all info. Let's think: The posting has "Preferred qualifications: Experience with Temporal orchestration workflows or similar workflow engines. Expertise in Kubernetes, ArgoCD, and container orchestration. Familiarity with hardware/software integration, hardware lifecycle, or bare-metal provisioning (PXE). Excellent communication skills with the ability to manage stakeholder relationships and drive cross-functional alignment." We could treat that as Qualifications (preferred). Then Skills could be empty; we should not create empty sections. So we omit Skills. Benefits: The posting includes a benefits paragraph: "In accordance with Washington state law, we are highlighting our comprehensive benefits package, which is available to all eligible US based employees. Benefits for this role include: Health, dental, vision, life, disability insuranceRetirement Benefits: 401(k) with company matchPaid Time Off: 20 days of vacation per year, accruing at a rate of 6.15 hours per pay period for the first five years of employmentSick Time: 40 hours/year (increased to 69 hours/year for Seattle) including 5 discretionary sick days per instance Maternity Leave (Short-Term Disability + Baby Bonding): 28-30 weeksBaby Bonding Leave: 18 weeksHolidays: 13 paid days per year". Also note: "Note: By applying to this position you will have an opportunity to share your preferred working location from the following: Sunnyvale, CA, USA; Kirkland, WA, USA." That's location info, could be part of About the role or maybe a separate section? Not in allowed headings; we could embed in About the role paragraph. Pay: The posting includes: "Individual pay is determined by factors including job-related skills, experience, and relevant education or training. US: $207000 - $300000 (USD) + 20% bonus target + equity + benefits". So we have pay range and bonus target. So we can create a Pay section. Schedule: Not mentioned. So we omit Schedule. Also we have statement about in-person interviews: "In most instances, this position requires in-person interviews as part of the hiring process." Could be placed under About the role or maybe a separate section like "Hiring Process" but not allowed. We'll embed in About the role paragraph. We must remove boilerplate: EEO, accommodation, legal, etc. Also remove duplicated lines, navigation, cookie, etc. Also remove "Learn more about benefits at Google ." (maybe it's a link; but it's part of responsibilities bullet; we should keep it? It's a bullet point: "Learn more about benefits at Google ." That seems like a placeholder link; but it's part of responsibilities list. Should we keep? It's substantive? It's basically a link to benefits page; maybe we keep as is. It's not boilerplate. We'll keep. Also remove "Google is proud to be an equal opportunity workplace..." etc. Now produce HTML fragment. Structure:

  About the role

  ... paragraphs ...

  Responsibilities

  • Learn more about benefits at Google .
  • Define the technical roadmap and architecture for inventory and fleet management, focusing on Temporal orchestration, automated node re-bootstrapping, and self-service remediation.
  • Own architectural and design decisions for the platform, collaborating with leadership and cross-functional teams to prioritize efforts, resolve roadblocks, and manage technical debt.
  • Establish and maintain machine health Service Level Objectives (SLOs), driving continuous improvements in fleet-wide observability and environmental monitoring.
  • Foster a culture of engineering excellence by establishing shared responsibility models with tenant teams and enforcing robust system-level access guardrails.
  • Coach and mentor engineers on the team, guiding their technical development and helping them grow their impact.

  Requirements

  • Bachelor's degree or equivalent practical experience.
  • 8 years of experience with software development in one or more programming languages (e.g., Python, C, C++, Java, JavaScript).
  • 5 years of experience building and developing large-scale infrastructure, distributed systems or networks, or experience with compute technologies, storage, or hardware architecture.
  • 5 years of experience testing, and launching software products.
  • 3 years of experience with software design and architecture.

  Qualifications

  • Experience with Temporal orchestration workflows or similar workflow engines.
  • Expertise in Kubernetes, ArgoCD, and container orchestration.
  • Familiarity with hardware/software integration, hardware lifecycle, or bare-metal provisioning (PXE).
  • Excellent communication skills with the ability to manage stakeholder relationships and drive cross-functional alignment.

  Benefits

  • Health, dental, vision, life, disability insurance
  • Retirement Benefits: 401(k) with company match
  • Paid Time Off: 20 days of vacation per year, accruing at a rate of 6.15 hours per pay period for the first five years of employment
  • Sick Time: 40 hours/year (increased to 69 hours/year for Seattle) including 5 discretionary sick days per instance
  • Maternity Leave (Short-Term Disability + Baby Bonding): 28-30 weeks
  • Baby Bonding Leave: 18 weeks
  • Holidays: 13 paid days per year

  Note: By applying to this position you will have an opportunity to share your preferred working location from the following: Sunnyvale, CA, USA; Kirkland, WA, USA.

  Pay

  Individual pay is determined by factors including job-related skills, experience, and relevant education or training. US: $207000 - $300000 (USD) + 20% bonus target + equity + benefits.

  We also need to include the in-person interviews statement. Where to put? Could add a paragraph under About the role: "In most instances, this position requires in-person interviews as part of the hiring process." Let's incorporate. Thus About the role paragraph(s): First paragraph: "Google's software engineers develop the next-generation technologies that change how billions of users connect, explore, and interact with information and one another. Our products need to handle information at massive scale, and extend well beyond web search. We're looking for engineers who bring fresh ideas from all areas, including information retrieval, distributed computing, large-scale system design, networking and data storage, security, artificial intelligence, natural language processing, UI design and mobile; the list goes on and is growing every day. As a software engineer, you will work on a specific project critical to Google’s needs with opportunities to switch teams and projects as you and our fast-paced business grow and evolve. We need our engineers to be versatile, display leadership qualities and be enthusiastic to take on new problems across the full-stack as we continue to push technology forward. Our team is building the future of at-scale computing by delivering a groundbreaking, on-premises AI supercomputer—the next evolution of Google's AI accelerator hardware. This is a rare opportunity to join a specialized team creating novel solutions for customers with sophisticated security and data locality requirements. You will be at the heart of building the next generation of AI hardware and the critical software that brings it to life, making a Google-scale impact on the future of AI. We manage complex infrastructure, integrating with Kubernetes, Temporal, and custom orchestration tools to ensure our compute nodes meet rigorous health standards. We are evolving our infrastructure toward automated node repair, self-healing frameworks, and advanced fleet-wide observability to reduce manual operational overhead and build robust platform boundaries. Google Cloud accelerates every organization’s ability to digitally transform its business and industry. We deliver enterprise-grade solutions that leverage Google’s cutting-edge technology, and tools that help developers build more sustainably. Customers in more than 200 countries and territories turn to Google Cloud as their trusted partner to enable growth and solve their most critical business problems." Then second paragraph: "In most instances, this position requires in-person interviews as part of the hiring process." We could combine into one

  but better separate. Now ensure we didn't include any boilerplate like EEO, accommodation, etc. Also removed duplicated lines. Check for any leftover like "See also