Manager, Event Operations & Venue Technology

We need to output HTML fragment with headings

for sections: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. Only include sections that have real specific content. The posting includes: - Intro paragraph about joining MetLife's Global Technology team: could be "About the role" maybe? Actually "When you join MetLife’s Global Technology team..." is description of role. Could be "About the role". We'll put that as

About the role

with

containing that paragraph. - Then "The Opportunity The Manager, Event Operations & Venue Technology is responsible for leading the operational strategy..." This is also role description; could be part of About the role. Could combine. - Then "Key Responsibilities" heading present: we should output

Responsibilities

with

• items. - Then "Required Qualifications" heading: we can map to

  Requirements

  (or Qualifications). The instruction says use headings like Requirements, Qualifications, Skills. We have both Required Qualifications and Preferred Qualifications. Could combine into Requirements (required) and maybe Skills (preferred). But we need to decide. We have "Required Qualifications" list: we can put under

  Requirements

  with
  . We have "Preferred Qualifications": could be under

  Preferred Qualifications

  but not in allowed list; allowed list includes Qualifications, Skills. Could treat Preferred Qualifications as

  Qualifications

  (maybe combine required and preferred?). But we already used Requirements for required. Could use Qualifications for preferred. Or we could put both under Requirements and note preferred? Better to follow instruction: Use headings for sections: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. So we need to map content accordingly. We have: - About the role: intro paragraphs. - Responsibilities: Key Responsibilities list. - Requirements: Required Qualifications list. - Qualifications: Preferred Qualifications list? Or maybe Skills: Preferred Qualifications? Actually "Skills" could be derived from preferred qualifications like certifications, specific tech knowledge. But we have both required and preferred qualifications; we could put required under Requirements, preferred under Qualifications. Skills maybe not needed if no explicit skills list separate. Could omit Skills if no specific content. - Benefits: we have benefits paragraph. - Pay: we have salary range: $121,200 - $161,600 plus short-term incentive mention. So we can include Pay section. - Schedule: not mentioned; omit. We must not include headings with filler text. So we will output sections: About the role, Responsibilities, Requirements, Qualifications, Benefits, Pay. We need to preserve all substantive information, not invent or summarize away detail. Must not repeat job title as heading. Must not put Job ID etc. We need to remove boilerplate: EEO, accommodation, drug-free workplace, Massachusetts lie detector law, posting duration, etc. Also remove navigation, cookie, legal, duplicated lines. Also remove "For more information regarding MetLife’s U.S. benefits, please click here." That's a link; we can drop that sentence? It's part of benefits but it's a referral; maybe we can keep benefits description but drop the link instruction. The instruction: remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. The "For more information regarding MetLife’s U.S. benefits, please click here." is like a link instruction; could be considered application instruction? It's not exactly application but it's a reference. Safer to remove that sentence. Also remove "About MetLife" section? That's company description; could be considered boilerplate? It's not EEO but it's generic company info. The instruction says remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. "About MetLife" is not explicitly listed; but it's generic company overview, could be considered boilerplate? Might be considered not substantive to the role. However the instruction says preserve ALL substantive information; does "About MetLife" count as substantive? It's about the company, not the role. Might be considered boilerplate but not explicitly prohibited. However typical job postings include company overview; but the instruction didn't forbid it. It only forbids cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. So we could keep About MetLife as a section? But we don't have a heading for it in allowed list; we could put it under About the role? Might be redundant. Safer to omit About MetLife as it's not required headings and could be considered filler. The instruction: "Prefer a few substantive sections over many thin ones." So we can omit About MetLife. Thus final HTML:

  About the role

  When you join MetLife’s Global Technology team, you’ll be part of a forward-thinking group dedicated to shaping the future of digital solutions for customers worldwide. You’ll develop, maintain and support technology applications and delivery, leveraging AI, automation, and contemporary ways of working to enhance experiences and drive business outcomes. Your work will simplify complex processes, improve tech resiliency, and ensure high-performing, seamless solutions that power life’s most important moments. In this dynamic environment, you’ll collaborate with talented peers across teams and functions, expanding your skills in impactful ways. Ready to push boundaries and set new industry standards? Join us and help drive the future of technology forward. The Opportunity The Manager, Event Operations & Venue Technology is responsible for leading the operational strategy, service delivery, and day-to-day support model for MetLife's premier event spaces across 200 Park Avenue, Warren, NJ, and Whippany, NJ. This role ensures MetLife leaders and business partners have reliable, high-quality events and production support for critical communications, executive meetings, hybrid events, and enterprise broadcasts. This is an exciting opportunity to lead a multi-site event operations team, standardize how high-visibility events are supported, strengthen venue readiness, and help shape the future of event technology across key MetLife locations.

  Responsibilities

  • Lead a team of event technology professionals supporting town halls, hybrid events, earnings calls, board meetings, and other high-visibility business communications.
  • Create a consistent, inclusive, collaborative, and customer-focused operating model that enables reliable event support across 200 Park Avenue, Warren, NJ, and Whippany, NJ.
  • Oversee operational readiness for event spaces, collaboration technology, production workflows, staffing coverage, escalation paths, and service quality across supported sites.
  • Oversee critical events, including planning, technical coordination, on-site execution, issue escalation, and post-event continuous improvement plans.
  • Develop standardized procedures, runbooks, training plans, metrics, and technology lifecycle recommendations that improve reliability, scalability, and team competency.
  • Coordinate with Multimedia Engineering, Networking, and Collaboration to ensure that all event technology is fit for purpose, cutting edge, and improving attendee experiences.

  Requirements

  • Demonstrated people leadership experience with the ability to coach, develop, prioritize, and guide technical teams in a high-visibility service environment.
  • Strong knowledge of corporate event operations, hybrid meeting production, venue technology support, and live event delivery for enterprise audiences.
  • Working knowledge of collaboration and production technologies such as Microsoft Teams Rooms, Teams Town Hall or similar live event platforms, video production switchers, digital audio systems, video conferencing codecs, and streaming workflows.
  • Ability to work under pressure, make sound decisions during live events, communicate clearly with senior stakeholders, and manage multiple priorities across multiple sites.
  • Strong stakeholder management, operational planning, documentation, and cross-functional coordination skills.

  Qualifications

  • 8+ years of experience in corporate live events, multimedia production, venue technology, broadcast operations, collaboration technology, or related enterprise technology support.
  • Experience managing event operations across multiple facilities, corporate campuses, or flagship event venues.
  • Experience supporting C-suite executives, board meetings, quarterly earnings calls, leadership broadcasts, or other highly visible enterprise communications.
  • CTS, CTS-D, CTS-I, PMP, ITIL, or equivalent industry certification.
  • Experience working with vendors, managed service providers, system integrators, workplace services, corporate communications, and technology engineering teams.
  • Familiarity with AV-over-IP, vMix, video codecs, production switchers, digital audio consoles, broadcast routing, streaming platforms, and enterprise collaboration environments.

  Benefits

  We offer a comprehensive health plan that includes medical/prescription drug and vision, dental insurance, and no-cost short- and long-term disability. We also provide company-paid life insurance and legal services, a retirement pension funded entirely by MetLife and 401(k) with employer matching, group discounts on voluntary insurance products including auto and home, pet, critical illness, hospital indemnity, and accident insurance, as well as Employee Assistance Program (EAP) and digital mental health programs, parental leave, paid time off, paid holidays, volunteer time off, tuition assistance and much more!

  Pay

  The expected salary range for this position is $121,200 - $161,600. This role may also be eligible for annual short-term incentive compensation.

  We need to ensure no extra whitespace at start? It's fine. Check that we didn't include any boilerplate like "All incentives and benefits are subject to the applicable plan terms." That's a sentence in benefits paragraph originally; we omitted it. Should we keep? It's substantive but maybe it's boilerplate? It's a statement about incentives and benefits being subject to plan terms. It's not EEO etc. Might be considered fine to keep. However we removed it to keep concise. The instruction: preserve ALL substantive information; do NOT invent or summarize away detail. Removing that sentence could be considered summarizing away detail. It's a detail about benefits eligibility. Better to include it. Let's add it to Benefits paragraph. Also we omitted "All incentives and benefits are subject to the applicable plan terms." Let's add after benefits description. Also we omitted "For more information regarding MetLife’s U.S. benefits, please click here." That's application instruction? It's a link; we can drop. Also we omitted "All incentives and benefits are subject to the applicable plan terms." We'll add. Also we omitted "This role may also be eligible for annual short-term incentive compensation." Already in Pay. Also we omitted "All incentives and benefits are subject to the applicable plan terms." Add to Benefits. Also we omitted "We offer a comprehensive health plan that includes medical/prescription drug and vision, dental insurance, and no-cost short- and long-term disability." Already there. Also we omitted "We also provide company-paid life insurance and legal services, a retirement pension funded entirely by MetLife and 401(k) with employer matching, group discounts on voluntary insurance products including auto and home, pet, critical illness, hospital indemnity, and accident insurance, as well as Employee Assistance Program (EAP) and digital mental health programs, parental leave, paid time off, paid holidays, volunteer time off, tuition assistance and much more!" Already there. Add the sentence about incentives and benefits subject to plan terms. Thus Benefits

  ... much more! All incentives and benefits are subject to the applicable plan terms.

  Check for any other substantive info: The posting also had "The expected salary range for this position is $121,200 - $161,600. This role may also be eligible for annual short-term incentive compensation. All incentives and benefits are subject to the