Sr Producer
for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). Use - for any list of duties/requirements/benefits, and
for prose. Do NOT repeat the job title as a heading (the page already shows it) and do NOT put Job ID / requisition numbers as headings — fold minor metadata into a short
or drop it. Preserve ALL substantive information; do NOT invent or summarize away detail. Remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. IMPORTANT: include a section ONLY when the posting has real, specific content for it — never emit a heading followed by filler/placeholder text (e.g. "commensurate with experience", "not specified", "N/A", "varies", "TBD") and never create Pay/Schedule/Benefits sections unless the posting actually states them. Prefer a few substantive sections over many thin ones. Output ONLY the HTML fragment — no /, no markdown code fences.
Thus we need to extract sections: About Us (company description) maybe "About Us". Summary (role summary). Essential Duties & Responsibilities (list). Team Management & Development (list). Client & Vendor Relationship Management (list). Project Strategy & Innovation (list). Education & Experience (list). Travel Requirements (maybe schedule? Actually travel). What We Offer (benefits). Diversity Commitment (maybe not needed? It's EEO boilerplate; we should remove EEO boilerplate. The Diversity Commitment is basically EEO statement; we should remove it. Also "#TFCSparks" maybe a tag; remove.
We need to avoid repeating job title. Not present.
We need to include sections only when there is real specific content. So we can have sections: About Us, Summary, Responsibilities (maybe combine duties?), Requirements (Education & Experience), Benefits (What We Offer), Travel (maybe schedule? Actually travel requirement). The instructions list possible headings: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We can map: About Us could be "About the role"? But they said use
for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). So we should use those exact headings? Probably we should use those headings when appropriate. "About Us" is not exactly "About the role". But we could use "About the role" for the summary? Actually "About Us" is company description. Might be better to use "About the role" for the summary of role. But we also have company description; maybe we can include as a paragraph before headings? The instruction: "use for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." It doesn't forbid other headings, but suggests using those. Safer to use those headings for sections we have.
Thus we could have:
About the role
(contains summary + maybe about us? Actually "About the role" could include summary of role and maybe company description? But they said do NOT repeat the job title as a heading (the page already shows it). So "About the role" is fine.
We need to preserve all substantive information. So we need to include company description somewhere. Could be in a
before the first heading or within About the role section.
Let's structure:
About Us: Sparks is a leading global brand experience agency...
Then About the role
with summary paragraph.
Then Responsibilities
with - for each duty bullet. The duties are grouped under headings: Event Leadership & Delivery, Team Management & Development, Client & Vendor Relationship Management, Project Strategy & Innovation. We could combine all duties into one list, but maybe better to keep subheadings? The instruction says use
for section headings; we could have subheadings as ? Not specified. Safer to just make a single Responsibilities section with all duties as list items.
Then Requirements
(or Qualifications) for Education & Experience. We'll list bullet points.
Then Benefits
for What We Offer (list benefits).
Then Schedule
maybe for hybrid work schedule and travel requirements? The posting mentions: "This position will support our Events & Experiences team and is eligible for a hybrid work schedule, generally requiring work in the office and/or at show site 2-3 days a week." Also "Preferred locations for this role include the following; however, qualified candidates outside of these markets will also be considered." Then list of locations. Also "Travel Requirements Travel 25% to 50%". So schedule could include hybrid work schedule and travel. We'll put that in Schedule section.
We must not include Pay section because not specified.
We must not include filler.
We must remove EEO boilerplate (Diversity Commitment). Also remove "#TFCSparks". Also remove "Preferred locations for this role include the following; however, qualified candidates outside of these markets will also be considered." That's substantive (locations). We should keep that as part of Schedule or maybe a separate section? Could be part of Schedule or maybe a separate "Location" but not in allowed headings. Could include in Schedule as note.
We need to preserve all substantive information: list of locations: Philadelphia, PA; Fort Wayne, IN; Las Vegas, NV; Royal Oak, MI; Grand Prairie, TX; New York, NY; Chicago, IL; Los Angeles, CA; San Francisco, CA.
We need to keep travel requirement.
Now produce HTML.
Let's craft:
About Us: 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.
About the role
The Senior Producer is a key leader within the Events & Experiences team, responsible for guiding the strategic vision and flawless execution of complex event programs. Working closely with Operations, Growth, Strategy, Creative Technology and Creative leadership, this role ensures that every project delivers meaningful client results while meeting financial and operational goals. The Senior Producer drives alignment across internal teams, external partners, and clients, bringing effective communication, leadership, and project‑management expertise to every engagement. This position will support our Events & Experiences team and is eligible for a hybrid work schedule, generally requiring work in the office and/or at show site 2-3 days a week.
Responsibilities
- Lead cross‑functional teams, including growth, strategy, creative, creative technology, operations, production, and technical production, to deliver a wide range of event experiences such as proprietary events, conferences, brand activations, virtual events and large‑scale experiential programs (both B-to-B and B-to-C).
- Oversee programs from RFP through post‑event wrap‑up, ensuring all deliverables meet client expectations and internal quality standards.
- Manage all aspects of project execution including venue logistics, technical production, staffing, décor, signage, food & beverage, health & safety, security, transportation, permitting and on‑site operations.
- Monitor project budgets, track expenses and vendor invoices, and drive profit margins through thoughtful financial management.
- Facilitate internal and client meetings, lead kickoff sessions, maintain consistent communication, and provide timely documentation and action‑item reporting.
- Supervise and support producers, event managers, and coordinators, assigning workloads and coaching team members to grow their expertise.
- Conduct regular employee reviews and contribute to ongoing team training and development initiatives.
- Mentor junior production staff and help build a positive, strong, collaborative, and high‑performing department culture.
- Serve as the primary point of contact for clients in collaboration with the growth lead and Executive Sponsor, setting program goals, managing communication, managing the budget and nurturing long‑term relationships that support business growth.
- Work with Growth Leads to define program success metrics and ensure all teams are aligned.
- Develop strong relationships with third‑party vendors, freelance staff, and production partners; negotiate and manage their contracts to ensure the highest level of service and execution quality.
- Support RFP development as needed.
- Translate client goals into actionable production plans and timelines, including production schedules, budgets, communication plans, show flows, and run‑of‑show documents.
- Collaborate with growth, strategy and creative teams to support concept development, content, and audience engagement strategies.
- Identify opportunities for improvement, propose innovative production solutions, and support continuous evolution of event delivery methodologies.
Requirements
- Bachelor’s degree or equivalent practical experience.
- 10+ years of conference operations and management experience within an agency, communications firm, or production company.
- Demonstrated experience producing diverse events, including conferences, concerts/evening events, hospitality programs, and consumer activations.
- Proven ability to manage budgets of $2M+ and oversee multiple large‑scale programs simultaneously.
- Experience managing programs with 5,000+ attendees.
- Motivated, positive attitude, and results‑oriented mindset.
- Champion culture and embrace culture.
- Strong communication, leadership, project management, and client‑service skills, with exceptional attention to detail.
- Mastery of G Suite (Slides, Sheets, Docs), Microsoft Office, Airtable, and all relevant internal and client tools.
Benefits
- Medical, Dental, Vision Insurance
- Tuition Reimbursement
- Paid Parental Leave
- Life, Accident and Disability
- Retirement with Company Match
- Paid Time Off
Schedule
Hybrid work schedule: generally requiring work in the office and/or at show site 2-3 days a week. Preferred locations: Philadelphia, PA; Fort Wayne, IN; Las Vegas, NV; Royal Oak, MI; Grand Prairie, TX; New York, NY; Chicago, IL; Los Angeles, CA; San Francisco, CA. Travel requirement: 25% to 50%.
We must ensure no boilerplate. We removed EEO. Also removed "#TFCSparks". Also removed "Diversity Commitment". Also removed "What We Offer The Freeman Company provides benefits that aim to empower our people and their families to thrive mentally, physically, and financially. These are a handful of the types of programs and benefits our full-time people may be eligible for. There may be some variances in specific benefits across regions." We kept the list but removed that introductory fluff? We kept just list. That's okay; we preserved substantive info (the benefits). The introductory sentence is somewhat generic; we could keep it as a before list, but it's not required. The instruction: preserve ALL substantive information; do NOT invent or summarize away detail. The introductory sentence is somewhat generic but still part of the posting. It's not
for prose. Do NOT repeat the job title as a heading (the page already shows it) and do NOT put Job ID / requisition numbers as headings — fold minor metadata into a short
or drop it. Preserve ALL substantive information; do NOT invent or summarize away detail. Remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. IMPORTANT: include a section ONLY when the posting has real, specific content for it — never emit a heading followed by filler/placeholder text (e.g. "commensurate with experience", "not specified", "N/A", "varies", "TBD") and never create Pay/Schedule/Benefits sections unless the posting actually states them. Prefer a few substantive sections over many thin ones. Output ONLY the HTML fragment — no /, no markdown code fences. Thus we need to extract sections: About Us (company description) maybe "About Us". Summary (role summary). Essential Duties & Responsibilities (list). Team Management & Development (list). Client & Vendor Relationship Management (list). Project Strategy & Innovation (list). Education & Experience (list). Travel Requirements (maybe schedule? Actually travel). What We Offer (benefits). Diversity Commitment (maybe not needed? It's EEO boilerplate; we should remove EEO boilerplate. The Diversity Commitment is basically EEO statement; we should remove it. Also "#TFCSparks" maybe a tag; remove. We need to avoid repeating job title. Not present. We need to include sections only when there is real specific content. So we can have sections: About Us, Summary, Responsibilities (maybe combine duties?), Requirements (Education & Experience), Benefits (What We Offer), Travel (maybe schedule? Actually travel requirement). The instructions list possible headings: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We can map: About Us could be "About the role"? But they said use
for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). So we should use those exact headings? Probably we should use those headings when appropriate. "About Us" is not exactly "About the role". But we could use "About the role" for the summary? Actually "About Us" is company description. Might be better to use "About the role" for the summary of role. But we also have company description; maybe we can include as a paragraph before headings? The instruction: "use for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." It doesn't forbid other headings, but suggests using those. Safer to use those headings for sections we have.
Thus we could have:
About the role
(contains summary + maybe about us? Actually "About the role" could include summary of role and maybe company description? But they said do NOT repeat the job title as a heading (the page already shows it). So "About the role" is fine.
We need to preserve all substantive information. So we need to include company description somewhere. Could be in a
About the role
(contains summary + maybe about us? Actually "About the role" could include summary of role and maybe company description? But they said do NOT repeat the job title as a heading (the page already shows it). So "About the role" is fine. We need to preserve all substantive information. So we need to include company description somewhere. Could be in abefore the first heading or within About the role section. Let's structure:
About Us: Sparks is a leading global brand experience agency...
ThenAbout the role
with summary paragraph. ThenResponsibilities
with- for each duty bullet. The duties are grouped under headings: Event Leadership & Delivery, Team Management & Development, Client & Vendor Relationship Management, Project Strategy & Innovation. We could combine all duties into one list, but maybe better to keep subheadings? The instruction says use
for section headings; we could have subheadings as
? Not specified. Safer to just make a single Responsibilities section with all duties as list items. Then
Requirements
(or Qualifications) for Education & Experience. We'll list bullet points. ThenBenefits
for What We Offer (list benefits). ThenSchedule
maybe for hybrid work schedule and travel requirements? The posting mentions: "This position will support our Events & Experiences team and is eligible for a hybrid work schedule, generally requiring work in the office and/or at show site 2-3 days a week." Also "Preferred locations for this role include the following; however, qualified candidates outside of these markets will also be considered." Then list of locations. Also "Travel Requirements Travel 25% to 50%". So schedule could include hybrid work schedule and travel. We'll put that in Schedule section. We must not include Pay section because not specified. We must not include filler. We must remove EEO boilerplate (Diversity Commitment). Also remove "#TFCSparks". Also remove "Preferred locations for this role include the following; however, qualified candidates outside of these markets will also be considered." That's substantive (locations). We should keep that as part of Schedule or maybe a separate section? Could be part of Schedule or maybe a separate "Location" but not in allowed headings. Could include in Schedule as note. We need to preserve all substantive information: list of locations: Philadelphia, PA; Fort Wayne, IN; Las Vegas, NV; Royal Oak, MI; Grand Prairie, TX; New York, NY; Chicago, IL; Los Angeles, CA; San Francisco, CA. We need to keep travel requirement. Now produce HTML. Let's craft:About Us: 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.
About the role
The Senior Producer is a key leader within the Events & Experiences team, responsible for guiding the strategic vision and flawless execution of complex event programs. Working closely with Operations, Growth, Strategy, Creative Technology and Creative leadership, this role ensures that every project delivers meaningful client results while meeting financial and operational goals. The Senior Producer drives alignment across internal teams, external partners, and clients, bringing effective communication, leadership, and project‑management expertise to every engagement. This position will support our Events & Experiences team and is eligible for a hybrid work schedule, generally requiring work in the office and/or at show site 2-3 days a week.
Responsibilities
- Lead cross‑functional teams, including growth, strategy, creative, creative technology, operations, production, and technical production, to deliver a wide range of event experiences such as proprietary events, conferences, brand activations, virtual events and large‑scale experiential programs (both B-to-B and B-to-C).
- Oversee programs from RFP through post‑event wrap‑up, ensuring all deliverables meet client expectations and internal quality standards.
- Manage all aspects of project execution including venue logistics, technical production, staffing, décor, signage, food & beverage, health & safety, security, transportation, permitting and on‑site operations.
- Monitor project budgets, track expenses and vendor invoices, and drive profit margins through thoughtful financial management.
- Facilitate internal and client meetings, lead kickoff sessions, maintain consistent communication, and provide timely documentation and action‑item reporting.
- Supervise and support producers, event managers, and coordinators, assigning workloads and coaching team members to grow their expertise.
- Conduct regular employee reviews and contribute to ongoing team training and development initiatives.
- Mentor junior production staff and help build a positive, strong, collaborative, and high‑performing department culture.
- Serve as the primary point of contact for clients in collaboration with the growth lead and Executive Sponsor, setting program goals, managing communication, managing the budget and nurturing long‑term relationships that support business growth.
- Work with Growth Leads to define program success metrics and ensure all teams are aligned.
- Develop strong relationships with third‑party vendors, freelance staff, and production partners; negotiate and manage their contracts to ensure the highest level of service and execution quality.
- Support RFP development as needed.
- Translate client goals into actionable production plans and timelines, including production schedules, budgets, communication plans, show flows, and run‑of‑show documents.
- Collaborate with growth, strategy and creative teams to support concept development, content, and audience engagement strategies.
- Identify opportunities for improvement, propose innovative production solutions, and support continuous evolution of event delivery methodologies.
Requirements
- Bachelor’s degree or equivalent practical experience.
- 10+ years of conference operations and management experience within an agency, communications firm, or production company.
- Demonstrated experience producing diverse events, including conferences, concerts/evening events, hospitality programs, and consumer activations.
- Proven ability to manage budgets of $2M+ and oversee multiple large‑scale programs simultaneously.
- Experience managing programs with 5,000+ attendees.
- Motivated, positive attitude, and results‑oriented mindset.
- Champion culture and embrace culture.
- Strong communication, leadership, project management, and client‑service skills, with exceptional attention to detail.
- Mastery of G Suite (Slides, Sheets, Docs), Microsoft Office, Airtable, and all relevant internal and client tools.
Benefits
- Medical, Dental, Vision Insurance
- Tuition Reimbursement
- Paid Parental Leave
- Life, Accident and Disability
- Retirement with Company Match
- Paid Time Off
Schedule
Hybrid work schedule: generally requiring work in the office and/or at show site 2-3 days a week. Preferred locations: Philadelphia, PA; Fort Wayne, IN; Las Vegas, NV; Royal Oak, MI; Grand Prairie, TX; New York, NY; Chicago, IL; Los Angeles, CA; San Francisco, CA. Travel requirement: 25% to 50%.
We must ensure no boilerplate. We removed EEO. Also removed "#TFCSparks". Also removed "Diversity Commitment". Also removed "What We Offer The Freeman Company provides benefits that aim to empower our people and their families to thrive mentally, physically, and financially. These are a handful of the types of programs and benefits our full-time people may be eligible for. There may be some variances in specific benefits across regions." We kept the list but removed that introductory fluff? We kept just list. That's okay; we preserved substantive info (the benefits). The introductory sentence is somewhat generic; we could keep it as abefore list, but it's not required. The instruction: preserve ALL substantive information; do NOT invent or summarize away detail. The introductory sentence is somewhat generic but still part of the posting. It's not