Demo Solutions and Experience Lead

We need to output HTML fragment with sections: headings

for sections like About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We must only include sections that have real specific content. We must not repeat job title. Must not include Job ID etc. Must preserve all substantive info. Remove boilerplate: EEO, accommodation, legal, etc. Also remove "Learn more about benefits at Google ." maybe keep? It's a link but it's boilerplate? It's about benefits but not specific benefit details. The instruction: include a section ONLY when posting has real, specific content for it — never emit a heading followed by filler/placeholder text (e.g., "commensurate with experience", "not specified", "N/A", "varies", "TBD") and never create Pay/Schedule/Benefits sections unless the posting actually states them. The posting includes pay: "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". That's specific pay range and bonus target, equity, benefits. So we can include Pay section with that info. Benefits: they mention "+ benefits" but not specific benefits. The instruction says never create Benefits section unless posting actually states them. It only says "+ benefits" generic, not specific. So we should not create a Benefits section. Schedule: not mentioned, so omit. We have Minimum qualifications and Preferred qualifications. Those can go under Requirements or Qualifications. We need to decide sections. Could have "Requirements" for minimum qualifications, and "Preferred Qualifications" maybe as a subsection? But we only have headings for Requirements, Qualifications, Skills. Could combine. Perhaps use "Requirements" for minimum qualifications, and "Preferred Qualifications" as a subheading? But only allowed headings are those listed; we cannot create custom headings like "Preferred Qualifications". Could put both under "Qualifications". Or we could have "Requirements" for minimum, and "Qualifications" for preferred. That seems acceptable: Requirements = minimum qualifications; Qualifications = preferred qualifications. Also we have skills: maybe we can extract skills from responsibilities? But we have a Skills section optional if we have specific skill statements. The posting includes abilities like "Ability to operate autonomously across matrixed organizations..." etc. Those could be skills. Could put them under Skills. Responsibilities: we have bullet list. About the job: we have paragraph about role. That's "About the role" heading. Thus sections: About the role, Responsibilities, Requirements, Qualifications, Skills, Pay. We must not include Schedule or Benefits. We need to use

for each section heading. Use

• for any list of duties/requirements/benefits. Use

  for prose. We must preserve all substantive information. Must not invent or summarize away detail. Must not repeat job title. Must not include boilerplate like EEO, accommodation, legal, etc. Also remove duplicated lines. Let's extract content. Original text: "Minimum qualifications: Bachelor’s degree or equivalent practical experience.8 years of experience in a technical project management or a customer-facing role." Note missing space after period? It's "experience.8 years". We'll keep as is but maybe add space? We should preserve exactly? Probably keep as is but we can add a space for readability? The instruction: preserve ALL substantive information; do not invent or summarize away detail. Adding a space is not changing meaning, but could be considered altering. Safer to keep as is: "Bachelor’s degree or equivalent practical experience.8 years of experience in a technical project management or a customer-facing role." Might look odd but it's what they wrote. "Preferred qualifications: Experience developing scripts, presentation playbooks, training guides, and narrative frameworks to scale demo adoption.Experience gathering client feedback and turning it into practical recommendations for demo and product improvements.Experience presenting complex technical topics and AI/Cloud solutions to senior leadership and audiences of 20+ executives in person.Conversational depth of subject-matter expertise across Google Cloud, machine learning, and enterprise AI solutions (e.g., Gemini ecosystem).Ability to operate autonomously across matrixed organizations, collaborating with Sales, CorpEng, Facilities, and product teams." "About the jobAs the Demo Solutions and Experience Lead, you are the frontline storyteller bringing Google’s most advanced technology to life inside our Experience Centers. You will partner with sales leadership to activate our spaces as strategic growth engines—delivering unforgettable, high-touch demonstrations that inspire C-level executives, build trust, and accelerate agreement momentum across Global Business Organization (GBO).Google creates products and services that make the world a better place, and gTech’s role is to help bring them to life. Our teams of trusted advisors support customers globally. Our solutions are rooted in our technical skill, product expertise, and a thorough understanding of our customers’ complex needs. Whether the answer is a bespoke solution to solve a unique problem, or a new tool that can scale across Google, everything we do aims to ensure our customers benefit from the full potential of Google products. To learn more about gTech, check out our video ." "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" Responsibilities list: "Lead live, interactive demonstrations (e.g., Gemini ecosystem) for C-level executives, translating complex engineering into compelling business value. Collaborate with Engagement Managers to integrate demos into briefing schedules, adjust timing, flag risks, and keep live sessions on schedule. Serve as on-site subject matter expert for interactive exhibits, partnering with central gForce to deploy new experiences and ensure briefing-ready reliability.Author standardized demo scripts, talking points, and self-service guides to help account teams present Google innovations confidently without deep technical support.Capture executive feedback during briefings to identify top-performing demos versus portfolio gaps, relaying demand signals to product teams for future refreshes." Note some missing spaces after periods; we keep as is. Now we need to format. Section About the role: use prose

  containing the About the job paragraph. Section Responsibilities:

  • each bullet. Section Requirements: minimum qualifications: maybe two items: Bachelor’s degree or equivalent practical experience; 8 years of experience in a technical project management or a customer-facing role. Could be list. Section Qualifications: preferred qualifications: list each bullet. Section Skills: maybe extract abilities: "Ability to operate autonomously across matrixed organizations, collaborating with Sales, CorpEng, Facilities, and product teams." Also maybe "Conversational depth of subject-matter expertise across Google Cloud, machine learning, and enterprise AI solutions (e.g., Gemini ecosystem)." Also "Experience presenting complex technical topics and AI/Cloud solutions to senior leadership and audiences of 20+ executives in person." etc. But those are already in preferred qualifications. Might be redundant. Perhaps better to put skills separate: we could list abilities like "Ability to operate autonomously across matrixed organizations..." etc. However the preferred qualifications already include many skill-like statements. To avoid duplication, we could still include them under Skills if they are distinct. But instruction: preserve ALL substantive information; we can duplicate? It didn't forbid duplication but better not to repeat same content. However we could keep them under Qualifications and not have Skills section. But we need to decide if we want Skills section. The posting does not have explicit "Skills" heading; but we can infer skill statements. The instruction: Prefer a few substantive sections over many thin ones. So maybe we skip Skills section and put ability statements under Qualifications. That would keep fewer sections. Thus sections: About the role, Responsibilities, Requirements, Qualifications, Pay. Now Pay section: we need to include the pay info as prose

    . Could also list bullet? It's prose. Now ensure we don't include boilerplate: remove EEO, accommodation, legal, "Learn more about benefits at Google .", "Individual pay is determined by factors including job-related skills, experience, and relevant education or training." Actually that is part of pay info; we keep it. The phrase "Individual pay is determined by factors including job-related skills, experience, and relevant education or training." is part of pay description; we keep. Now also need to remove duplicated lines: there may be duplicate sentences? Not seeing. Now produce HTML. We must not include or . Just fragment. Let's craft:

    About the role

    As the Demo Solutions and Experience Lead, you are the frontline storyteller bringing Google’s most advanced technology to life inside our Experience Centers. You will partner with sales leadership to activate our spaces as strategic growth engines—delivering unforgettable, high-touch demonstrations that inspire C-level executives, build trust, and accelerate agreement momentum across Global Business Organization (GBO).Google creates products and services that make the world a better place, and gTech’s role is to help bring them to life. Our teams of trusted advisors support customers globally. Our solutions are rooted in our technical skill, product expertise, and a thorough understanding of our customers’ complex needs. Whether the answer is a bespoke solution to solve a unique problem, or a new tool that can scale across Google, everything we do aims to ensure our customers benefit from the full potential of Google products. To learn more about gTech, check out our video .

    Responsibilities

    • Lead live, interactive demonstrations (e.g., Gemini ecosystem) for C-level executives, translating complex engineering into compelling business value.
    • Collaborate with Engagement Managers to integrate demos into briefing schedules, adjust timing, flag risks, and keep live sessions on schedule.
    • Serve as on-site subject matter expert for interactive exhibits, partnering with central gForce to deploy new experiences and ensure briefing-ready reliability.Author standardized demo scripts, talking points, and self-service guides to help account teams present Google innovations confidently without deep technical support.Capture executive feedback during briefings to identify top-performing demos versus portfolio gaps, relaying demand signals to product teams for future refreshes.
    Note the third bullet has missing spaces; we keep as is.

    Requirements

    • Bachelor’s degree or equivalent practical experience.8 years of experience in a technical project management or a customer-facing role.
    But that's two items combined into one li due to missing space. Better to split: we could separate into two lis: "Bachelor’s degree or equivalent practical experience." and "8 years of experience in a technical project management or a customer-facing role." However the original text had no space between the period and 8, but we can still split logically. The instruction: preserve ALL substantive information; splitting does not lose info, just adds readability. Might be okay. But to be safe, we could keep as one li with the exact string. However that looks weird. I'd split into two lis, preserving the content. The content is exactly those two sentences; we just add a line break. That's not inventing or summarizing. It's just formatting. I'll split. Thus:

    Requirements

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

    Qualifications

    • Experience developing scripts, presentation playbooks, training guides, and narrative frameworks to scale demo adoption.
    • Experience gathering client feedback and turning it into practical recommendations for demo and product improvements.
    • Experience presenting complex technical topics and AI/Cloud solutions to senior leadership and audiences of 20+ executives in person.
    • Conversational depth of subject-matter expertise across Google Cloud, machine learning, and enterprise AI solutions (e.g., Gemini ecosystem).
    • Ability to operate autonomously across matrixed organizations, collaborating with Sales, CorpEng, Facilities, and product teams.