Product Deployment Engineer, gTech Ads, Search

We need to output HTML fragment with sections only if content present. Need to extract sections: About the role? Actually there is "About The Job" heading. Also "Responsibilities". Also "Minimum qualifications" and "Preferred qualifications". Also "Pay" (Individual pay...). Also maybe "Location" note about locations? There's a note about location options. Should we include a "Location" section? The rules: use headings for section headings like About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. They didn't list Location as a standard heading, but we could include if content present? The instruction: "use

for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." It says e.g., not exclusive. But they say "Prefer a few substantive sections over many thin ones." Probably we should include sections that map to these headings: About the role (About The Job), Responsibilities, Qualifications (maybe combine Minimum and Preferred?), Pay. Benefits? There's a link "Learn more about benefits at Google." but no explicit benefits listed. So we should not create Benefits section unless posting actually states them. It only mentions link, not details. So skip Benefits. Schedule not present. Skills? Not explicit. Requirements? Could combine qualifications. But we have Minimum qualifications and Preferred qualifications. Could put under "Requirements" heading? The instruction: Use headings like Requirements, Qualifications. We could have a "Qualifications" section with both minimum and preferred. Or separate "Minimum qualifications" and "Preferred qualifications" as subheadings? But they said use

for section headings. Could have

Minimum qualifications

and

Preferred qualifications

. That's okay. They didn't forbid using those exact phrases. So we can include those. Also location note: "This role may also be located in our Playa Vista, CA campus." plus list of locations. Could be a "Location" section but not in list. Might be considered metadata; maybe we can fold into a short

under About the role? But they said do NOT put Job ID / requisition numbers as headings — fold minor metadata into a short

or drop it. Location is minor metadata? Might be okay to include as a short paragraph under About the role. However they said preserve ALL substantive information. Location is substantive. Could create a

Location

but not in the example list. Might be acceptable but they said prefer few substantive sections. Might be better to include location info in a paragraph under About the role or as a separate short

before sections. I'd include a

about location after the About the job section maybe. We must remove boilerplate: EEO, accommodation, etc. Also remove duplicated lines. Also remove application instructions (like "Learn more about benefits at Google ." maybe part of benefits but we removed). Also remove "Google is proud to be an equal opportunity workplace..." etc. We need to preserve all substantive info: role description, responsibilities, qualifications, pay, location note, etc. Let's extract: Location note: - This role may also be located in our Playa Vista, CA campus. - Applicants in the County of Los Angeles: Qualified applications with arrest or conviction records will be considered for employment in accordance with the Los Angeles County Fair Chance Ordinance for Employers and the California Fair Chance Act. - 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: New York, NY, USA; Atlanta, GA, USA; Chicago, IL, USA; Los Angeles, CA, USA; San Francisco, CA, USA; Sunnyvale, CA, USA. But the Fair Chance Ordinance statements are legal boilerplate? Might be considered EEO/legal. The instruction: Remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate. Those statements about arrest or conviction records are likely legal boilerplate (Fair Chance). So we should remove them. Also the note about sharing preferred working location is substantive location info. Keep that. Thus location paragraph: "This role may also be located in our Playa Vista, CA campus. By applying to this position you will have an opportunity to share your preferred working location from the following: New York, NY, USA; Atlanta, GA, USA; Chicago, IL, USA; Los Angeles, CA, USA; San Francisco, CA, USA; Sunnyvale, CA, USA." Now About The Job: The paragraph(s) after "About The Job". Need to capture all descriptive text until "Responsibilities". Let's extract: "gTech Ads is responsible for all support and media and technical services for customers big and small across our entire Ad products stack. We help our customers get the most out of our Ad and Publisher products and guide them when they need help. We provide a range of services from enabling better self help and in-product support, to providing better support through interactions, setting up accounts and implementing ad campaigns, and providing media solutions for customers business and marketing needs and providing complex technical and measurement solutions along with consultative support for our large customers. These solutions range from bespoke and customized ones for our customers to scalable support for millions of customers worldwide. Based on the evolving needs of our ads customers, we partner with Sales, Product and Engineering teams within Google to develop better solutions, tools, and services to improve our products and enhance our client experience. As a cross-functional and global team, we ensure our customers get the best return on investment with Google and we remain a trusted partner. The Product Deployment Engineering (PDE) Team for Search+, gTech Ads AMER LCS, provides complex search consulting and implementation for Google’s top enterprise advertising clients. The core objective of the team is to unlock Search+ revenue by helping customers get the most out of their data across Google Ads, SA360, and Shopping. This most commonly looks like integrating customer data for the purposes of value-based bidding, inventory bidding, or third party attribution, as well prototyping and last-mile deployment of technical solutions that deliver insights, automation, etc. 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 ." We should remove the video link placeholder maybe but keep sentence. Now Responsibilities: list after "Responsibilities". It starts with "Learn more about benefits at Google ." Actually that line is before responsibilities? The text: "Individual pay is determined by factors including job-related skills, experience, and relevant education or training. US: $152000 - $221000 (USD) + 15% bonus target + equity + benefits Responsibilities Learn more about benefits at Google . Partner with regional product leads, Sales, and gTech Engagement Managers to assess customer marketing objectives, technical maturity, infrastructure, and first-party data management strategies. Lead deep-dive technical consultations and martech diagnostic sessions to uncover opportunities for custom solutions, ensuring designs respect industry-specific data constraints and business cycles.Translate complex customer requirements into clear system architectures and technical specifications that prioritize scalability, reusability, and media activation. Lead technical hand-overs to the engineering team by authoring high-quality, prototype-grounded Business/Product Requirement Documents aligned with the product roadmap. Serve as the strategic entry gatekeeper to the Engineering CoE.Act as a trusted advisor providing technical-product oversight during implementation, ensuring the engineering build aligns with customer strategy while deferring base-code decisions to Engineering.Partner with gTech teams and customer technical teams to drive last-mile delivery, enablement, and seamless deployment outcomes." We need to separate Pay section before Responsibilities. The pay line: "Individual pay is determined by factors including job-related skills, experience, and relevant education or training. US: $152000 - $221000 (USD) + 15% bonus target + equity + benefits". That's pay info. We'll make a Pay section. After that, "Responsibilities" heading then the list. We need to remove "Learn more about benefits at Google ." as it's a link to benefits but not actual benefits detail. It's likely boilerplate; we should remove it. Thus responsibilities list items: - Partner with regional product leads, Sales, and gTech Engagement Managers to assess customer marketing objectives, technical maturity, infrastructure, and first-party data management strategies. - Lead deep-dive technical consultations and martech diagnostic sessions to uncover opportunities for custom solutions, ensuring designs respect industry-specific data constraints and business cycles. - Translate complex customer requirements into clear system architectures and technical specifications that prioritize scalability, reusability, and media activation. - Lead technical hand-overs to the engineering team by authoring high-quality, prototype-grounded Business/Product Requirement Documents aligned with the product roadmap. - Serve as the strategic entry gatekeeper to the Engineering CoE. - Act as a trusted advisor providing technical-product oversight during implementation, ensuring the engineering build aligns with customer strategy while deferring base-code decisions to Engineering. - Partner with gTech teams and customer technical teams to drive last-mile delivery, enablement, and seamless deployment outcomes. Now Qualifications: Minimum qualifications and Preferred qualifications. Minimum qualifications: - Bachelor’s degree or equivalent practical experience. - 5 years of experience troubleshooting technical issues for internal/external partners or customers. - Experience in either system design or reading code (e.g., Java, C++, Python). Preferred qualifications: - Master’s degree in Business, Statistics, Mathematics, Economics, Engineering or Applied Science, or a related field. - Experience in an online advertising/customer growth role and familiarity with the ad serving industry and internet technologies. - Experience working with Google Ads, Google Marketing Platform products (e.g., SA360, DV360, GA4), or Google Cloud services. - Expertise in Search+ - Demonstrated coding ability with Java or Python, and database knowledge with the ability to construct complex SQL queries. Note: "Expertise in Search+" maybe a heading? It's a line. We'll output as

• . Now we need to decide sections: About the role (

  About the role

  ) with the About The Job paragraph(s). Responsibilities (

  Responsibilities

  ) with
  . Minimum qualifications (

  Minimum qualifications

  ) with
  . Preferred qualifications (

  Preferred qualifications

  ) with
  . Pay (

  Pay

  ) with

  maybe. Location note: Could be a short

  before sections or after About the role. I'll put a

  for location after About the role maybe as its own

  Location

  but not in list. Might be okay but risk of being considered thin. However location info is substantive. I'd include a

  Location

  with

  . But the instruction says use headings e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. It didn't forbid other headings but says "use

  for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." That implies those are examples; we can use others if needed. But they also say "Prefer a few substantive sections over many thin ones." Adding Location adds another section; maybe we can fold location into About the role paragraph as a short sentence. That would keep fewer sections. Thus we will include location sentence within About the role paragraph. Now we need to ensure we don't repeat job title as heading. Not needed. We must output only HTML fragment