Executive Producer - Events and Experiences

We need to output HTML fragment only, with headings

for sections: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. Use only sections that have real specific content. Remove boilerplate, navigation, EEO, etc. Also remove duplicated lines. Preserve all substantive info. We need to parse the posting. Let's extract sections: - About The Role: paragraph(s) after "About The Role". It includes description: "As an Executive Producer for Google.Monks Events & Experience, you’ll oversee high-profile experiential projects from pitch through delivery, ensuring exceptional creative output, operational excellence, and client satisfaction. You’ll serve as a senior point of accountability - guiding producers, PMs, and cross-functional leads to deliver seamless work that meets both creative ambitions and commercial goals. This role blends strategic oversight and production leadership with an understanding of business growth and client partnership. You’ll help shape opportunities within the Google.Monks ecosystem while ensuring every project is delivered on time, on budget, and with the quality and innovation that define Monks work." We can keep that as

under

About the role

. - Responsibilities: There's a list with headings: Project and Delivery Oversight, Team Leadership, Client Partnership, Business & Growth, Subject Matter Expertise. Each has bullet points (some sentences). We need to output a

• list for any list of duties/requirements/benefits. The instructions: Use
  • for any list of duties/requirements/benefits, and

    for prose. So we need to decide: Should we treat each responsibility heading as a list item? Probably we can combine all responsibilities into a

    with each bullet as
    • . The headings themselves could be part of the
    • text. We'll need to preserve all substantive info. Let's extract each responsibility bullet: Project and Delivery Oversight: - Oversee $2–8M USD in active project revenue, ensuring financial health, delivery excellence, and client satisfaction. - Manage multiple large-scale experiential and digital projects simultaneously, balancing priorities and ensuring alignment across creative, strategy, tech, and production. - Maintain clear oversight of scope, timeline, resourcing, and margin driving accountability through each phase of delivery. - Partner closely with Producers and PMs to ensure workflows, deliverables, and communication remain proactive and solution-oriented. Team Leadership: - Lead, coach, and motivate teams - including senior producers, producers, and project managers - to operate efficiently, think strategically, and maintain commercial awareness. - Foster a culture of ownership, calm under pressure, and cross-functional collaboration. - Serve as an escalation point for both internal teams and clients, maintaining a solutions-first mindset. Client Partnership: - Act as the senior production lead for key Google initiatives, ensuring client confidence through clear communication, thoughtful planning, and delivery excellence. - Cultivate trusted relationships with senior stakeholders, helping clients navigate challenges while identifying opportunities for future collaboration. - Represent the Monks experience capability internally and externally, championing best-in-class creative production. Business & Growth: - Partner with client and growth teams to execute against new business opportunities, shape proposals, and lead high-quality pitches. - Manage and maintain visibility into your opportunity pipeline across Salesforce, Monday.com, and other tools. - Support long-term growth through smart resourcing, forecasting, and identification of new experiential opportunities. - Remain accountable for the vision and estimates set during pitch through execution, ensuring alignment between creative ambition and financial stewardship. Subject Matter Expertise: - Pursue and apply expertise across one or more core areas of the practice: AI, immersive web, experiential/events, live production, or interactive storytelling. - Champion innovation within the team, helping shape how we bring emerging technologies and creative formats to life for Google and other partners. We'll output these as
    • items. - Requirements / Qualifications / Skills: The posting includes "About You" section with essentials: communication, listening, 6+ years experience, portfolio, curious about popular culture, etc. Also maybe "Subject Matter Expertise" is more about expertise but could be considered skills. However we have separate sections for Requirements, Qualifications, Skills. We need to decide which content goes where. The instruction: Use headings only when posting has real specific content for it. We have content about essentials: communication, listening, 6+ years experience, portfolio, curious about popular culture. That could be considered Requirements or Qualifications. There's also "Subject Matter Expertise" which could be Skills. But we already used Subject Matter Expertise as a responsibility heading? Actually it's under Responsibilities as a heading. But we could treat it as a skill area. However the posting already has a "Subject Matter Expertise" heading under Responsibilities. We need to decide whether to keep it as part of Responsibilities or separate Skills section. The instruction: Use headings for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). So we should map the content to those headings if they exist. The posting has "About The Role", "Responsibilities", "About You". It does not have explicit Requirements, Qualifications, Skills headings. However we can create them if the posting has real specific content for them. Does it have content that fits Requirements? Yes, the "About You" includes essentials: communication, listening, 6+ years experience, portfolio, curious about popular culture. That could be considered Requirements or Qualifications. We could put them under Requirements (or Qualifications). Since we have both Requirements and Qualifications headings available, we need to avoid thin sections. Better to combine into one section, maybe Requirements, and omit Qualifications and Skills if not enough distinct content. But we also have "Subject Matter Expertise" which could be Skills. However it's already under Responsibilities; but we could still extract it as Skills. However the instruction: "Prefer a few substantive sections over many thin ones." So we should avoid creating many sections with little content. We have substantive content for About the role, Responsibilities, About You (which could be Requirements), Benefits, Pay (salary range), Schedule (RTO policy). Let's see if we have Pay: Yes, salary range $175,000—$200,000 USD. Also note about compensation range disclaimer. That's specific content for Pay. Schedule: The posting mentions Return to Office (RTO) policy: "If you reside within a commutable distance of one of our office locations, you will be expected to work from the office a set number of days per week. The specific details, including the number of required office days, will be in accordance with the company’s then-current RTO policy, which is subject to change from time to time." That's schedule info. So we can include Schedule section. Benefits: There's a Benefits section with bullet points: "Excellent, full coverage medical, dental, and vision insurance - more about our coverage here!Generous PTO and 15 company-wide holidays401k with company contributionPaid parental leaveWork-life balance with an emphasis on personal well-beingCareer growth in a disruptor space & entrepreneurial opportunities within the Monks network A globally diverse & inclusive culture with employee resource groups such as S4 Melanin, Pride.Monks, Cultura.Monks, and more!Authentic commitment to DEI efforts and sustainable growth. (Why Sir Martin Sorrell signed The Climate Pledge here!)". This is a run-on paragraph but we can split into list items. We need to remove boilerplate: The initial warning about payment, fraudulent job postings, etc. Also the repeated RTO policy appears twice; we should keep only once. Also the EEO statement at end about equal-opportunity employer etc. Should be removed as boilerplate. Also the "About Monks" paragraph describing the company; that's likely boilerplate? It's substantive about the company but maybe considered boilerplate? The instruction: Remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. The "About Monks" is not exactly boilerplate but could be considered company description; but it's not a section heading we have. It might be considered extra info not needed for job posting? The instruction says preserve ALL substantive information; do NOT invent or summarize away detail. The "About Monks" is substantive about the company, but is it required? It's not a standard heading but could be considered part of "About the role"? Probably not; it's general company info. However the instruction says remove duplicated lines and boilerplate; "About Monks" might be considered boilerplate but it's not legal/EEO. It's describing the company; could be considered substantive but not required for the job. However the instruction says preserve ALL substantive information; do NOT invent or summarize away detail. So we should keep it unless it's clearly boilerplate like EEO. I'd lean to keep it as a paragraph maybe under a section like "About Monks" but we don't have a heading for that. We could incorporate it into "About the role" or maybe as a separate

      after responsibilities? But the instruction says use headings only for those specific section headings. It doesn't forbid other headings, but says use

      for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). It doesn't say we cannot have other headings, but we should follow the pattern. Safer to not add extra headings. We could put the About Monks paragraph as a

      after the sections, but that might be considered extra content not under a heading. The instruction: Output ONLY the HTML fragment — no /, no markdown code fences. It didn't say we cannot have stray

      elements. So we could include it as a

      after the sections. However the instruction about sections: "Use

      for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." It implies we should use those headings for sections, but we can still have other content not under headings? Probably better to keep all content under those headings if possible. The About Monks could be considered part of "About the role" or maybe "About Monks" is not needed. I think we can omit it because it's not directly about the role; it's company description. The instruction says preserve ALL substantive information; but maybe company description is considered substantive but not required for the job posting? However it's part of the posting; removing it could be considered summarizing away detail. But the instruction also says remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. It does not explicitly say to remove company description. So we should keep it. We could add a section "About the company" but not in allowed headings. But we could just put it as a

      after the sections without a heading. That might be acceptable. But to be safe, we could treat it as part of "About the role" by appending after the role description. However that would mix company info with role description; but still preserves info. Let's decide: We'll include a

      about Monks after the sections, without a heading. It's not a heading, but it's just a paragraph. The instruction didn't forbid stray paragraphs. It said use

      for section headings (list). It didn't say you cannot have other elements. So okay. Now we need to ensure we don't repeat duplicated lines: The RTO policy appears twice; we will include only once under Schedule. Also the benefits paragraph appears duplicated? It appears once; we will output as list. Now we need to format Benefits as

      • . The benefits paragraph is a run-on sentence; we can split by commas or periods. Let's extract each benefit: - Excellent, full coverage medical, dental, and vision insurance - more about our coverage here! - Generous PTO and 15 company-wide holidays - 401k with company contribution