Director, Trust and Safety, Trusted Experiences, Google DeepMind

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 content. We need to parse the posting. First, remove boilerplate: The first paragraph about San Francisco Fair Chance Ordinance etc. That's legal boilerplate; remove. Also "In accordance with Washington state law, we are highlighting our comprehensive benefits package..." That's about benefits but we will extract benefits later. However that sentence is a bit generic but we can keep benefits details. We need to preserve all substantive info. Let's extract sections: - About The Job: there is a paragraph starting "About The Job Trust & Safety team members...". That is about the role. So we can have

About the role

with that prose. - Responsibilities: there is a "Responsibilities" heading in the text. After that, bullet list? Actually after "Responsibilities" there is a line: "Learn more about benefits at Google . Work closely with a global team..." It seems the responsibilities are a list of bullet-like sentences. We'll treat them as

• items. - Minimum qualifications: list of qualifications. That's qualifications section. - Preferred qualifications: also qualifications. - Skills: maybe we can extract from preferred qualifications: ability to apply systems thinking, exceptional executive communication skills, etc. Could be under Skills. - Benefits: we have a benefits list: Health, dental, vision, life, disability insurance; Retirement Benefits: 401(k) with company match; Paid Time Off: 20 days 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. Also note: "In accordance with Washington state law, we are highlighting our comprehensive benefits package, which is available to all eligible US based employees." That's just intro. - Pay: "Individual pay is determined by factors including job-related skills, experience, and relevant education or training. US: $264000 - $366000 (USD) + 30% bonus target + equity + benefits". So we have pay range. - Schedule: Not mentioned. No schedule info. So we should not create Schedule section. - Location: Not needed as heading; we can drop location list. - Also there is a line: "Note: By applying to this position you will have an opportunity to share your preferred working location from the following: Sunnyvale, CA, USA; Atlanta, GA, USA; Austin, TX, USA; New York, NY, USA; Seattle, WA, USA; San Francisco, CA, USA; Washington D.C., DC, USA." That's location info but not a heading; we can drop as per instruction: do not put Job ID/requisition numbers as headings — fold minor metadata into a short

  or drop it. This is location metadata; we could include as a short

  maybe but not required. Probably drop. - Also there is EEO boilerplate at end: remove. - Also "Learn more about benefits at Google ." that's a link; we can keep as part of responsibilities? It's a sentence after Responsibilities heading. Might be considered part of responsibilities but it's a link; we can keep as a

• maybe. We need to preserve all substantive info; do not invent or summarize away detail. Thus we need to output HTML with sections:

  About the role

  ... (the About The Job paragraph)

  Responsibilities

  • Learn more about benefits at Google .
  • Work closely with a global team to drive the responsible launch of GenAI models and products in partnership with internal and external stakeholders, defining metrics, strategic planning, and development for the team.
  • Drive strategic abuse prevention solutions and scaled enforcement through automation and innovation, enabling ML technologies to scale, building analyst teams, partnering with senior executive stakeholders and information advocacy during challenging times.
  • Manage abuse prevention, risk assessment, mitigation and enforcement on policies and guidelines for GDM products.
  • Drive organizational-wide impact and be committed to the mission of enhancing trust with our users and protecting them from abuse.
  • Lead and influence decision-making for organizational strategies across a senior stakeholder team.
  • Foster an innovative culture for a global team, drive execution, attract and develop existing leaders toward their career goals.

  Requirements

  maybe we combine Minimum qualifications as Requirements. The instruction says use headings like Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We have Minimum qualifications and Preferred qualifications. Could put both under

  Qualifications

  with sub-sections? But we cannot create nested headings besides h3? We could just put all qualifications in a
  under

  Qualifications

  . That would include both minimum and preferred. But we need to preserve distinction? The instruction says preserve ALL substantive information; we can keep both as separate lists maybe under same heading with headings? But we cannot use other headings besides h3? The instruction says use

  for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). It doesn't forbid other headings, but says use

  for section headings (list). It might be okay to use

  for sub-sections? Safer to stick to only h3 sections. We could have separate sections:

  Minimum qualifications

  and

  Preferred qualifications

  . Those are not in the list but they are specific headings from the posting. The instruction says use

  for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). It gives examples but not exclusive list. It likely expects we use those headings when applicable. Minimum qualifications and Preferred qualifications could be considered under Qualifications. But we could also make a Qualifications section and inside have two

  paragraphs labeling Minimum and Preferred. That preserves info. Let's do:

  Qualifications

  Minimum qualifications:

  ...

  Preferred qualifications:

  ...
  That uses only h3 for Qualifications. Similarly Skills: we could extract skills from preferred qualifications: Ability to apply systems thinking..., Exceptional executive communication skills..., Ability to synthesize information..., etc. Could put under

  Skills

  as a list. But we might be duplicating content. The instruction says prefer a few substantive sections over many thin ones. So maybe we combine qualifications and skills into one Qualifications section. However we have to include Skills heading only if there is real specific content for it. There is content about skills (systems thinking, communication, etc.) So we could make a Skills section. But we also have Qualifications (education, experience). Could make both. Let's decide: We'll have sections: About the role, Responsibilities, Qualifications, Skills, Benefits, Pay. We'll not have Requirements separate. Now extract content: About the role paragraph: "About The Job Trust & Safety team members are tasked with identifying and taking on the biggest problems that challenge the safety and integrity of our products. They use technical know-how, excellent problem-solving skills, user insights, and proactive communication to protect users and our partners from abuse across Google products like Search, Maps, Gmail, and Google Ads. On this team, you're a big-picture thinker and strategic team-player with a passion for doing what’s right. You work globally and cross-functionally with Google engineers and product managers to identify and fight abuse and fraud cases at Google speed - with urgency. And you take pride in knowing that every day you are working hard to promote trust in Google and ensuring the highest levels of user safety. At Google we work hard to earn our users’ trust every day. Trust & Safety is Google’s team of abuse fighting and user trust experts working daily to make the internet a safer place. We partner with teams across Google to deliver bold solutions in abuse areas such as malware, spam and account hijacking. A team of Analysts, Policy Specialists, Engineers, and Program Managers, we work to reduce risk and fight abuse across all of Google’s products, protecting our users, advertisers, and publishers across the globe in over 40 languages." We need to ensure we keep all that. Now Responsibilities: we already enumerated. Now Qualifications: Minimum qualifications: "Bachelor’s degree or equivalent practical experience. 15 years of experience working in the tech industry or a research, policy, legal, or operations field. Experience leading global teams, working across multiple regions." Preferred qualifications: "Advanced degree (e.g., Master's, PhD, MBA) in a related field (e.g., Analytical, Technical, Legal, Operations Management). Experience leading cross-functionally with multiple senior stakeholders and an ability to influence at all levels of the organization. Ability to apply systems thinking to analyze complex problems, identify interdependencies, and develop holistic solutions with high business impact. Exceptional executive communication skills and judgment to partner effectively with senior leaders, functions and influence end-to-end design, launch, and enforcement outcomes. Ability to synthesize information to bring clear recommendations to drive decision-making and impact inline with T&S business goals." We could split: some of those are skills. But we will keep them under Qualifications. Now Skills: maybe we extract the skill-specific items: Ability to apply systems thinking..., Exceptional executive communication skills..., Ability to synthesize information..., etc. Also maybe "Experience leading cross-functionally with multiple senior stakeholders and an ability to influence at all levels of the organization." That's also a skill. But to avoid duplication, we could put skills as a separate list derived from preferred qualifications that are skill-oriented. However the instruction says preserve ALL substantive information; if we put them only under Skills and not under Qualifications, we would lose the context that they are preferred qualifications. But we could keep them under both? That would duplicate. Better to keep them under Qualifications only, and not create a separate Skills section unless we have additional skill content not already covered. Since the preferred qualifications already contain skill statements, we could treat Qualifications as encompassing both education/experience and skills. Then we don't need a separate Skills section. The instruction says prefer a few substantive sections over many thin ones. So we can omit Skills. Thus sections: About the role, Responsibilities, Qualifications, Benefits, Pay. Now Benefits: we need to list as
  • items. Benefits list: - 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 Also note: "In accordance with Washington state law, we are highlighting our comprehensive benefits package, which is available to all eligible US based employees." That's just a preamble; we could include as a

    before the list. Now Pay: "Individual pay is determined by factors including job-related skills, experience, and relevant education or training. US: $264000 - $366000 (USD) +