Product Support Manager

We need to output HTML fragment with sections: headings

for sections like About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We must include only sections with real content. The posting includes: - Application window date (but that's metadata; we can put in a short

maybe) - Minimum qualifications: Bachelor’s degree or equivalent practical experience. 8 years of experience in a technical project management or a customer-facing role. - Preferred qualifications: MBA or advanced degree in a Management, Business, a related field or equivalent practical experience. Experience in product support management, launch program management, or technical account management within the consumer electronics industry. Experienced in customer support, support operations and delivering excellent experiences for end consumers. Proven Track record of identifying and driving change improvement programs across policies, processes, procedures and tooling in complex consumer based businesses. Strong problem-solving skills with the ability to turn complex data into clear, actionable insights for executive leadership. Excellent communication skills, with a ability to influence cross-functional stakeholders across product, engineering, and support. - About The Job (description) – we can put under About the role? The instruction: use

for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). So we need to map content accordingly. We have: - About the role: The description about gTech Users and Products, mission, etc. That's the "About The Job" paragraph(s). So we can put that under

About the role

with

content. - Responsibilities: list of bullet points after "Responsibilities". The posting includes: "Serve as the regional subject matter expert and primary point of contact for the end-to-end support journey. Leverage deep expertise in local regulations, market nuances, and internal operations to drive customer experiences. Actively manage day-to-day escalations, legal cases, and launch readiness, while serving as the vital connector. Be curious and data-led to understand the customer journey, metrics and user voice feedback to identify what’s going well, and what needs improvement. Drive process improvements and changes, identify opportunities, shape ideas for improvement, win hearts and minds with amazing storytelling and data analysis. Partner cross-functionally with engineering, product, legal, PR, and support delivery to advocate for users and drive operational excellence." We can format as

• each sentence. - Requirements: Minimum qualifications? Could be Requirements section. The instruction says we can use Requirements heading. So we can put Minimum qualifications under Requirements. - Qualifications: Preferred qualifications could go under Qualifications (or maybe Skills). But we have both Requirements and Qualifications. We'll put Minimum qualifications under

  Requirements

  . Preferred qualifications under

  Qualifications

  . - Skills: maybe we can extract skills like problem-solving, communication, influencing, etc. But those are already in preferred qualifications. Could combine. However we should avoid thin sections. Perhaps we can merge preferred qualifications into Qualifications and not create separate Skills unless there is explicit skill list. The posting includes "Strong problem-solving skills..." etc. Those are skills. Could put them under Skills. But we already have Qualifications covering similar content. To avoid duplication, we could put the skill-based sentences under Skills and keep Qualifications for education/degree etc. Let's examine: Preferred qualifications list includes: - MBA or advanced degree in a Management, Business, a related field or equivalent practical experience. - Experience in product support management, launch program management, or technical account management within the consumer electronics industry. - Experienced in customer support, support operations and delivering excellent experiences for end consumers. - Proven Track record of identifying and driving change improvement programs across policies, processes, procedures and tooling in complex consumer based businesses. - Strong problem-solving skills with the ability to turn complex data into clear, actionable insights for executive leadership. - Excellent communication skills, with a ability to influence cross-functional stakeholders across product, engineering, and support. We could split: education/experience under Qualifications, and skills under Skills. But the instruction says prefer a few substantive sections over many thin ones. Having both Qualifications and Skills may be okay if each has substantive content. Let's decide: - Requirements: Minimum qualifications (Bachelor's degree or equivalent practical experience; 8 years experience in technical project management or customer-facing role). - Qualifications: Preferred qualifications (MBA/advanced degree; experience in product support management, launch program management, technical account management within consumer electronics; experience in customer support, support operations delivering excellent experiences; proven track record of identifying and driving change improvement programs across policies, processes, procedures and tooling in complex consumer based businesses). - Skills: Strong problem-solving skills; ability to turn complex data into clear actionable insights; excellent communication skills; ability to influence cross-functional stakeholders. That seems reasonable. - Benefits: The posting mentions "Individual pay is determined by factors including job-related skills, experience, and relevant education or training. US: $140000 - $204000 (USD) + 15% bonus target + equity + benefits". Also there is a link "Learn more about benefits at Google ." So we have pay and benefits info. We need to include Pay and Benefits sections only if posting actually states them. It does state pay range and bonus target + equity + benefits. So we can create

  Pay

  with

  containing the salary range and bonus target + equity. And

  Benefits

  with

  referencing "Learn more about benefits at Google" maybe summarizing that benefits are available per Google. But we must not invent details; we can say "Benefits include those offered by Google (see Google benefits page)". However the posting only says "Learn more about benefits at Google ." So we can put that as a

  with that sentence. - Schedule: Not mentioned. So we should not create Schedule section. - About the role: we have description. - Responsibilities: we have list. Now also we have application window date and location options. That's metadata; we can put in a short

  at top maybe. We must not repeat job title as heading. Not include Job ID etc. We must remove boilerplate: EEO, equal opportunity, accommodation, etc. Also remove "Google is proud to be an equal opportunity workplace..." etc. Also remove "Learn more about benefits at Google ." maybe we keep as part of Benefits? Actually that sentence is about benefits; we can keep it. We must also remove duplicated lines, cookie/navigation/legal/EEO etc. Now produce HTML fragment. Structure:

  Application window open until at least September 29, 2026. Preferred working locations: Atlanta, GA, USA; Boulder, CO, USA.

  About the role

  ... (the about job paragraph(s))...

  Responsibilities

  • Serve as the regional subject matter expert and primary point of contact for the end-to-end support journey.
  • Leverage deep expertise in local regulations, market nuances, and internal operations to drive customer experiences.
  • Actively manage day-to-day escalations, legal cases, and launch readiness, while serving as the vital connector.
  • Be curious and data-led to understand the customer journey, metrics and user voice feedback to identify what’s going well, and what needs improvement.
  • Drive process improvements and changes, identify opportunities, shape ideas for improvement, win hearts and minds with amazing storytelling and data analysis.
  • Partner cross-functionally with engineering, product, legal, PR, and support delivery to advocate for users and drive operational excellence.

  Requirements

  • Bachelor’s degree or equivalent practical experience.
  • 8 years of experience in a technical project management or a customer‑facing role.

  Qualifications

  • MBA or advanced degree in Management, Business, a related field or equivalent practical experience.
  • Experience in product support management, launch program management, or technical account management within the consumer electronics industry.
  • Experienced in customer support, support operations and delivering excellent experiences for end consumers.
  • Proven track record of identifying and driving change improvement programs across policies, processes, procedures and tooling in complex consumer‑based businesses.

  Skills

  • Strong problem‑solving skills with the ability to turn complex data into clear, actionable insights for executive leadership.
  • Excellent communication skills, with the ability to influence cross‑functional stakeholders across product, engineering, and support.

  Pay

  US: $140,000 – $204,000 (USD) + 15% bonus target + equity.

  Benefits

  Learn more about benefits at Google.

  Make sure to use proper HTML. No extra whitespace issues. Ensure no markdown fences. Check for any leftover boilerplate: we removed EEO etc. Also removed "Individual pay is determined by factors including job-related skills, experience, and relevant education or training." Actually we kept that? We omitted that sentence; we only included pay range. The instruction says preserve ALL substantive information; do NOT invent or summarize away detail. The sentence about how pay is determined is substantive. Should we include it? It is about pay determination. We could include it in Pay section as a

  before the range. Let's include it. Thus Pay section:

  Individual pay is determined by factors including job-related skills, experience, and relevant education or training.

  US: $140,000 – $204,000 (USD) + 15% bonus target + equity.

  Similarly Benefits: we have "Learn more about benefits at Google ." That's the only substantive benefit info. Keep. Now check for any other substantive info: The posting also includes "Note: By applying to this position you will have an opportunity to share your preferred working location from the following: Atlanta, GA, USA; Boulder, CO, USA." We included that in the initial p. Also "The application window will be open until at least September 29, 2026. This opportunity will remain online based on business needs which may be before or after the specified date." We included first sentence but omitted second sentence about remain online based on business needs. That is substantive; we should include it. So adjust initial p: include both sentences. Thus initial p: "The application window will be open until at least September 29, 2026. This opportunity will remain online based on business needs which may be before or after the specified date. Note: By applying to this position you will have an opportunity to share your preferred working location from the following: Atlanta, GA, USA; Boulder, CO, USA." Now check for any other substantive content: The "About The Job" includes multiple paragraphs. We need to preserve all. Let's capture them: Paragraph 1: "In gTech Users and Products (gUP), our mission is to advocate for Google’s users by creating helpful and trusted experiences across the product ecosystem. We represent the Google's users and partners, sharing insights to enable exceptional customer and product experiences." Paragraph 2: "Within the gUP Platforms and Devices (P&D) team, we focus specifically on growing loyal Pixel users through seamless support and collaborative product improvements." Paragraph 3: "The Pixel Support Experience team combines a deep knowledge of our products and services, alongside expertise on support policies, process, procedures and tooling. We leverage data-driven insights to identify opportunities to define and create outstanding support experiences, shaping how we work today and visioning for the future." Paragraph 4: "As the Product Support Manager (PSM) for North America, you will lead the end-to-end support strategy for Google's Pixel ecosystem in the region. You will be responsible for helping shape and deliver changes which unlock amazing support experiences for our users.