Conference Producer

We need to output HTML fragment with sections: About Us? Actually the posting includes "About Us" paragraph, then "Summary", then "Essential Duties & Responsibilities", then "Budget & Financial Management", then "Client & Team Communication", then "Education & Experience", then "Travel Requirements", then "What We Offer". Also there is "Diversity Commitment" but that's boilerplate EEO, we should remove. Also "About Us" is a section heading? The instruction: use

for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). They gave examples but we can use any appropriate heading. We should not repeat job title as heading. The posting includes "About Us" which is about company; we can keep as a section heading maybe "About Us". It's not in the list but it's okay. Use

for each section heading. We need to use

• for any list of duties/requirements/benefits. So for duties we need list items. For responsibilities we have many bullet-like sentences; we can turn each into
• . For Education & Experience we have list of qualifications; we can turn into
• . For What We Offer we have list of benefits; turn into
• . Travel Requirements maybe just a sentence; we can put in

  . Also we need to include hybrid schedule info: "This position will support our Event & Experience team. It is eligible to work a hybrid schedule, generally requiring work in-office and/or show-site 3 days per week. The ideal candidate will be based out of any of the following locations: Philadelphia, PAFort Wayne, INRoyal Oak, MIGrand Prairie, TXLas Vegas, NV". That's location info; we can put in a

  maybe under a section like "Location & Schedule"? But we should only include sections when posting has real specific content. There's no explicit Pay or Benefits besides What We Offer. So we can have sections: About Us, Summary, Responsibilities (maybe combine Essential Duties & Responsibilities, Budget & Financial Management, Client & Team Communication into one Responsibilities section? But they are separate headings in posting; we could keep them as separate sections if they have substantive content. The instruction: Prefer a few substantive sections over many thin ones. But we can still keep them if they are substantive. However we could combine duties into one "Responsibilities" section. But we need to follow the heading examples: they gave "Responsibilities" as an example. So we could make a single

  Responsibilities

  and put all duty-related content inside
  • . That would be concise. Similarly "Education & Experience" could be "Qualifications". Use

    Qualifications

    . "What We Offer" could be "Benefits". Use

    Benefits

    . Travel Requirements maybe part of "Schedule"? Actually they gave Schedule as an example heading. Travel up to 25% is travel requirement, not schedule. Could be placed under a

    maybe within Responsibilities or a separate "Travel" section but we might avoid thin section. Could include in Responsibilities as a bullet? It's not a duty but a requirement. Could be placed under Qualifications as a bullet? Might be okay to add a

    after Qualifications: "Travel up to 25% required." Or we could add a

    Travel

    but that might be thin. Better to incorporate into Qualifications as a list item. Location info: "The ideal candidate will be based out of any of the following locations: Philadelphia, PAFort Wayne, INRoyal Oak, MIGrand Prairie, TXLas Vegas, NV". That's location requirement; could be part of Qualifications as a bullet. Hybrid schedule: "It is eligible to work a hybrid schedule, generally requiring work in-office and/or show-site 3 days per week." Could be part of Qualifications or a separate Schedule section. Since they gave Schedule as example heading, we could make a

    Schedule

    with that sentence. That's substantive. Thus sections: About Us (maybe not required but we can keep), Summary, Responsibilities, Qualifications, Benefits, Schedule. We need to remove boilerplate: Diversity Commitment, EEO, etc. Also remove "About Us" maybe? It's not boilerplate; it's company description. Keep. We need to preserve all substantive information. Let's extract. About Us paragraph: "Sparks is a leading global brand experience agency, specializing in the design and execution of award-winning experiences that forge deep connections between brands and audiences. Recognized by Adweek as Experiential Agency of the Year, we bring a unique blend of strategic insight and execution excellence to every brand activation, corporate event, trade show exhibit, and immersive experience. Our commitment to creativity, innovation, and flawless execution drives us to craft impactful experiential marketing solutions that deepen relationships, inspire action, and build trust—all around the world." Summary paragraph: "The Conference Producer is responsible for leading the planning, execution, and delivery of a wide range of corporate and consumer events, managing cross-functional teams, vendors, budgets, and project schedules to ensure flawless event execution. Serving as the main point of contact, for an event or for a workstream, the Producer leads all internal, client, and vendor meetings, coordinates resources within their assigned scope, and ensures projects are on time and within budget. Additionally, the Producer provides event reporting and analytics, negotiates contracts, and mentors junior staff to support successful project outcomes. This position will support our Event & Experience team. It is eligible to work a hybrid schedule, generally requiring work in-office and/or show-site 3 days per week. The ideal candidate will be based out of any of the following locations: Philadelphia, PAFort Wayne, INRoyal Oak, MIGrand Prairie, TXLas Vegas, NV" Note: The hybrid schedule and location appear in Summary; we might want to move them to Schedule and Qualifications respectively to avoid duplication. But we must preserve all info; we can keep them in Summary but also later sections? The instruction: preserve ALL substantive information; do NOT invent or summarize away detail. If we move them, we still preserve. It's okay to rephrase? We should not invent or summarize away detail, but we can reorganize as long as we keep the info. It's safer to keep them in Summary and also maybe not duplicate elsewhere. But we need a Schedule section; we could extract the hybrid schedule sentence and put it there, but then we would be removing it from Summary unless we keep it also. To avoid duplication, we could keep it only in Schedule and remove from Summary. However that would be removing content from Summary (the sentence). That would be summarizing away detail? Actually we would be moving it, not removing; the info still appears somewhere else. The instruction: "Preserve ALL substantive information; do NOT invent or summarize away detail." Moving is okay as long as it's still present. So we can extract hybrid schedule to Schedule section and location to Qualifications (or a separate Location section). But we need to ensure we don't lose any other details. Let's parse Summary sentences: 1. The Conference Producer is responsible for leading the planning, execution, and delivery of a wide range of corporate and consumer events, managing cross-functional teams, vendors, budgets, and project schedules to ensure flawless event execution. 2. Serving as the main point of contact, for an event or for a workstream, the Producer leads all internal, client, and vendor meetings, coordinates resources within their assigned scope, and ensures projects are on time and within budget. 3. Additionally, the Producer provides event reporting and analytics, negotiates contracts, and mentors junior staff to support successful project outcomes. 4. This position will support our Event & Experience team. 5. It is eligible to work a hybrid schedule, generally requiring work in-office and/or show-site 3 days per week. 6. The ideal candidate will be based out of any of the following locations: Philadelphia, PAFort Wayne, INRoyal Oak, MIGrand Prairie, TXLas Vegas, NV. We can keep 1-4 in Summary. 5 goes to Schedule. 6 goes to Qualifications (or Location). We'll keep them. Now Essential Duties & Responsibilities: many bullet-like sentences. We'll turn each into
  • . Let's list them: - Lead the delivery of various-scale events from kick-off through reconciliation - Lead workstream(s) of large projects under the direction of the Project Lead and/or the Account Lead - Set goals and objectives for projects and team - Provide best practices and future event recommendations based on experience - Collaborate closely with Technical Directors as needed - Collaborate closely with the creative team to ensure production and creative teams are aligned - Lead smaller programs entirely or Lead one or more logistics workstreams end to end — e.g., space/floor planning, F&B, transportation and shuttles, security, signage/graphics, attendee/people movement, etc. - Work with technical teams to develop floor plans, capacities, flow, and space allocations in coordination with venues and the creative team - Manage room blocks, housing, and travel logistics for attendees, staff, VIPs, and/or talent as scoped - Own health, safety, security, and emergency/contingency planning for assigned areas, in coordination with venue and security partners - Manage load-in, load-out, and on-site operational schedules across assigned workstreams - Coordinate permits, licensing, insurance/COIs, and venue and municipal compliance requirements - Oversee accessibility (ADA) and sustainability requirements within assigned scope - Serve as on-site operational lead for assigned workstreams through setup, event days, and strike - Run daily readiness checks, issue tracking, and real-time problem resolution on site That's a lot; we keep all. Budget & Financial Management: - Budget development and management; track costs throughout the course of a project and communicate scope changes that impact budget - Develop, manage and communicate project timelines - Negotiate contracts/agreements with third-party vendors - Manage and develop strong relationships with vendors and freelancers on assigned projects - Support RFP development as needed Client & Team Communication: - Serve as primary owner of client communication, alongside Account and Project Lead, for assigned project or area - Organize and manage team communications - Lead all internal, vendor, and client meetings for assigned scope - Serve as workstream escalation point for the project's internal and client teams - Help to create a positive, collaborative workplace We could combine all these under Responsibilities section as a single list. That would be long but okay. Education & Experience (Qualifications): List items: - Bachelor’s degree or equivalent practical experience - 6-9 years of event experience - Strong project management skills including budgeting, scheduling, and client relations - Strong written and verbal communication skills - Leadership skills to lead a project team and client - Development of positive working relationships with clients - Ability and desire to manage and mentor junior team members - Foster a positive working environment - Motivated, positive attitude, and results-oriented mindset - Mastery of G Suite (Slides, Sheets, Docs), Microsoft Office, Airtable, and all relevant internal and client tools - Strong knowledge of Procim/Sheets, Tools & Templates, PO and Accounts Receivables, Concur, Coupa and G Suite - Demonstrated experience leading event logistics and operations workstreams (e.g., space planning, F&B, transportation, security, registration, people movement) - Working knowledge of venue operations, safety/security protocols, permitting, and risk/contingency planning - Experience managing large-scale attendee flow, capacities, and crowd management - Comfort managing multiple concurrent workstreams and vendors under tight timelines - Travel up to 25% (maybe as separate bullet) - The ideal candidate will be based out of any of the following locations: Philadelphia, PAFort Wayne, INRoyal Oak, MIGrand Prairie, TXLas Vegas, NV We need to ensure we don't duplicate location; we already have location bullet. Travel up to 25% is a requirement; we can include as bullet