Director of Event Operations, BETT USA
About the role
with. - Responsibilities: The bullet list after "As part of your job, you’ll:" includes many items. Also later "Work closely with the commercial team..." etc. Also "Manage commercial operations budget..." etc. So we need to gather all responsibilities. Let's list them: - Manage the planning and execution the event. This includes pre-event and on-site planning and execution. - Manage the onsite execution of our Meetups program - Manage event budgets and forecasts; develop and relationships with local and national vendors; conduct site visits and manage RFPs. - Manage event logistics such as floor plans, room sets, AV, F&B, décor, signage, collateral materials, staffing, security, etc. - Work with venues on F&B, AV, signage, and manage BEOs and MEOs - Manage contract negotiations, invoice payments, and insurance requirements - Plan and manage staffing for each event - this includes temp and contract staffing for on-site - Work on post-event reconciliation, including gathering feedback during debriefing meetings with vendors - Manage, grow, and lead a small team of 1-3 event coordinators/managers, this includes creating and reviewing processes for onboarding and objective setting - Work closely with the commercial team, marketing team, and where applicable content team to manage the delivery of commercial partnerships at the show - Develop and maintain processes and ways of working to ensure efficient and effective delivery of all BETT USA sponsorships. - Develop and manage the commercial inventory, working closely with the Event Director, to ensure the inventory matches budget requirements, provides the growth required, and is kept up to date with the wider commercial team - Manage commercial operations budget, and provide weekly updates to the finance team - Work closely with the Event Director & VP of Operations to update and manage the show floor throughout the show cycle - Manage the delivery of sponsored features and activations from the RFP tender process through to the onsite build Also earlier: "Developing and streamlining new processes and their strategic implementation will be a crucial success factor." That's more about role but could be responsibilities. We'll include responsibilities as a
- .
- Requirements: The "Here’s what we’re looking for from you:" list includes many bullet-like sentences. Let's extract:
- Strong background with proven experience in planning and implementing large-scale events, conferences and/or trade shows
- 5-7 years of event management experience, working in a large conference or tradeshow environment
- Exceptional interpersonal, communication and negotiation skills
- Must be super organized, and can work under pressure and make thoughtful decisions
- Must be extremely comfortable with technology platforms and technology management
- Have strong Excel skills or be willing to take courses/training necessary to achieve them
- Have experience developing young teams and a willingness to lead by example and help them to excel in their skills and careers
- Be extremely detail-oriented, be a take-charge problem-solver
- Take ownership of your work and can stay organized when facing multiple priorities
- Having high standards, and knowing that “good enough” is definitely not enough!
- Ability to negotiate large-scale contracts with vendors and venues
- At least ten years experience working on an event or conference
- Solid written and verbal communication skills
- Creative problem-solving and the ability to multitask is essential
- Must be willing to commute 2-3 days per week to NYC offices as needed
Note: Some overlap with skills. We'll put these under Requirements.
- Qualifications: Not explicitly separate; maybe "At least ten years experience" etc. Could be considered qualifications. But we can treat Requirements as qualifications. However we need separate sections only if content exists. The posting doesn't have a distinct "Qualifications" heading; we could combine Requirements and Qualifications? The instruction: Use headings for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). We should include only those with real content. If we don't have distinct Qualifications separate from Requirements, we could either omit Qualifications or merge into Requirements. Safer to omit Qualifications if no distinct content.
- Skills: Could extract specific skills: technology platforms, Excel, interpersonal, communication, negotiation, organization, detail-oriented, problem-solving, multitasking, etc. But many already in Requirements. Might be redundant. We could create Skills section for things like "Strong Excel skills", "technology platforms", "interpersonal, communication and negotiation skills", "detail-oriented", "problem-solving", "multitasking". However we risk duplication. The instruction: Prefer a few substantive sections over many thin ones. So maybe we combine Requirements and Skills into one? But they ask to use those headings if content exists. We could put Skills as a subsection under Requirements? But they want separate headings. Let's see if we can extract distinct skills not covered in Requirements: "Strong Excel skills or be willing to take courses/training necessary to achieve them" is a skill. "Must be extremely comfortable with technology platforms and technology management" is skill. "Exceptional interpersonal, communication and negotiation skills" is skill. "Must be super organized" is skill. "Be extremely detail-oriented" is skill. "Take-charge problem-solver" is skill. "Creative problem-solving and the ability to multitask is essential" is skill. So we could have Skills section listing those. Requirements could be more about experience: "Strong background with proven experience...", "5-7 years...", "At least ten years experience...", "Have experience developing young teams...". That seems like experience/requirements. So we can separate.
Thus:
- Requirements: experience-based items.
- Skills: skill-based items.
Let's list Requirements:
- Strong background with proven experience in planning and implementing large-scale events, conferences and/or trade shows
- 5-7 years of event management experience, working in a large conference or tradeshow environment
- At least ten years experience working on an event or conference (note: this conflicts with 5-7 years; but we keep both as posted)
- Have experience developing young teams and a willingness to lead by example and help them to excel in their skills and careers
Maybe also "Must be willing to commute 2-3 days per week to NYC offices as needed" could be requirement but it's more about location; could be Schedule? Actually schedule/commute. We'll treat under Schedule maybe.
But we have Schedule section: we could include commute requirement.
Pay: Salary band $120,000 - $140,000 based on experience, plus competitive bonus structure.
Benefits: Full medical, dental, vision; retirement plan with company match (401K); competitive vacation policy; hybrid work.
Schedule: Hybrid work, commute 2-3 days per week to NYC offices as needed. Also maybe travel to events (BETT UK, ASU+GSV Summit) but that's travel requirement not schedule.
We'll include Schedule: Hybrid work; must be willing to commute 2-3 days per week to NYC offices as needed.
Now we need to ensure we don't include boilerplate like "Think that sounds good? Wait until our talent acquisition team tells you about the culture." etc. Also remove "A bit about the division", "A bit about us", "A bit about you", "Our shared behaviours", etc. Those are boilerplate/culture; we should remove.
Also remove "Ready to make some great experiences? Your Hyve adventure begins with one click-Apply now!" (application instruction). Remove.
Now produce HTML.
Structure:
- ... ...
- ... ...
- ... ...
- ... ...
- ... ...
About the role
...
Responsibilities
Requirements
Skills
Benefits
Pay
...