VP Revenue Operations

We need to output HTML fragment with sections: About Us? Actually "About Us" is a section heading? The instruction says use

for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). They gave examples but we can use other headings if content exists. The posting includes "About Us", "Summary", "Essential Duties & Responsibilities", "What Success Looks Like", "Education & Experience Required", "Preferred", "Travel Requirements", "What We Offer", "Diversity Commitment". We need to decide which sections to include based on real content. We should not repeat job title. We should not include boilerplate like EEO etc. Remove Diversity Commitment? It's EEO boilerplate; instruction says remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate. So we should omit Diversity Commitment. We need to include sections only when posting has real specific content. For each we need to decide. - About Us: contains description of company. That's substantive. Use

About Us

then

...

. - Summary: description of role. Use

Summary

then

...

. - Essential Duties & Responsibilities: list of duties. Use

Essential Duties & Responsibilities

then

• ...
...

. Need to preserve all bullet points. - What Success Looks Like: list of bullet points. Use heading. - Education & Experience Required: list of requirements. Use heading. - Preferred: list of preferred qualifications. Use heading. - Travel Requirements: mention travel up to 25%. Use heading. - What We Offer: list of benefits. Use heading. We should not include Pay or Schedule unless stated. There's mention: "It is eligible to work a hybrid schedule, generally requiring work in-office and/or show-site 2-3 days per week." That's schedule info. So we should include a Schedule section. Also there is no explicit Pay. So no Pay. We also have "Preferred locations for this role include the following; however, qualified candidates outside of these markets will also be considered." That's location info; maybe we could include under a Locations section but not required. Not in examples but we could include as part of Summary? Probably better to include a Locations section? The instruction only gave examples but didn't forbid other headings. It says use

for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). It implies those are typical but we can use others if needed. However they say "Prefer a few substantive sections over many thin ones." So maybe we incorporate location info into Summary or About Us? Probably better to add a Locations section if it's substantive. But they didn't list Locations as example; but we could still use

Locations

. However they said "use

for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." The e.g. suggests those are examples, not exclusive. So we can add Locations. But we need to avoid filler. Locations list is specific. We also have "Preferred locations for this role include the following; however, qualified candidates outside of these markets will also be considered. Philadelphia, PA Fort Wayne, IN Las Vegas, NV Royal Oak, MI Grand Prairie, TX". That's location list. We also have "Travel Requirements Travel up to 25%". That's a short line; we can include as a

under Travel Requirements heading. Now we need to strip boilerplate: Diversity Commitment, maybe also "#TFCSparks" at end (a hashtag). Remove. Also need to remove duplicated lines. Now construct HTML. We'll need to preserve all substantive info. Let's extract each section content. 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." We'll put that in

. Summary: "The Vice President, Revenue Operations is a strategic and analytical leader responsible for unifying and optimizing the processes, systems, and data that drive revenue across the commercial growth organization. Reporting to senior growth leadership, this role owns the revenue operating system—the definitions, reporting, and operating rhythm that give leadership a single, trusted view of performance and the confidence to steer growth. It is a senior, function-building role requiring you to set the architecture, direct delivery, grow the team, and turn complex data into clear, executive-ready insight. This is a rare chance to build a revenue operations function from the ground up: Build and lead a new function, setting how revenue is planned, measured, and managed. Shape the systems, data, and cadence behind every revenue decision. Join at a pivotal moment of growth, with strong executive sponsorship and visibility across leadership. This position will support our Growth team. It is eligible to work a hybrid schedule, generally requiring work in-office and/or show-site 2-3 days per week." We could split schedule into separate Schedule section later, but we can keep schedule info in Summary and also have Schedule section. To avoid duplication, maybe we move schedule info to Schedule section and keep Summary without that sentence. But we must preserve all info; we can keep it in Summary and also have Schedule section referencing it? That would duplicate. Better to extract schedule sentence to Schedule section and remove from Summary. Let's do that. So Summary without schedule sentence: "The Vice President, Revenue Operations is a strategic and analytical leader responsible for unifying and optimizing the processes, systems, and data that drive revenue across the commercial growth organization. Reporting to senior growth leadership, this role owns the revenue operating system—the definitions, reporting, and operating rhythm that give leadership a single, trusted view of performance and the confidence to steer growth. It is a senior, function-building role requiring you to set the architecture, direct delivery, grow the team, and turn complex data into clear, executive-ready insight. This is a rare chance to build a revenue operations function from the ground up: Build and lead a new function, setting how revenue is planned, measured, and managed. Shape the systems, data, and cadence behind every revenue decision. Join at a pivotal moment of growth, with strong executive sponsorship and visibility across leadership. This position will support our Growth team." Now Schedule section: "It is eligible to work a hybrid schedule, generally requiring work in-office and/or show-site 2-3 days per week." Now Essential Duties & Responsibilities: list bullet points. We need to capture each bullet: - Revenue Strategy & Planning: Lead annual and quarterly revenue planning, forecasting, and target-setting with senior growth leadership. - Own forecasting across bookings and delivered revenue, with pipeline coverage and attainment analysis leadership can act on. - Shape quota setting, territory and coverage design, capacity planning, and go-to-market segmentation. - Identify revenue leakage and inefficiencies across the client lifecycle, and drive the fixes. - Revenue Definitions, Data & Reporting - Establish and govern the single source of truth for revenue: the definitions, solution taxonomy, and metrics used across Events, Exhibits, and EMEA. - Lead executive reporting, from dashboards to weekly, monthly, and quarterly business reviews, with insight leadership can act on. - Partner with the central finance and reporting team to align revenue pacing and reporting standards across the wider organization. - Set the standard for data quality, pipeline hygiene, and reporting discipline. - Systems & Technology - Own the commercial technology stack and its integration with finance systems, on shared definitions. - Lead the evaluation, selection, and implementation of new revenue-enabling technology. - Build scalable, automated workflows that reduce manual effort and speed up revenue. - Growth, Retention & Account Health - Build the operating view of the existing client base: expansion, retention, and account health, with the reporting and cadence to manage them. - Establish at-risk and renewal reporting, and the process to act on it. - Surface and quantify expansion opportunities across key accounts, with the account and growth teams. - Cross-Functional Leadership & Team - Build, lead, and develop the revenue operations function and its analytics and reporting capability. - Partner closely with Sales Operations, with clear ownership between strategic revenue operations and day-to-day deal support. - Connect client-facing and marketing operations so every team works from the same definitions, data, and cadence. - Partner with Finance on planning, budget, and revenue recognition, and translate strategy into operational initiatives with clear ownership. We need to preserve all. We'll output as

• ... each bullet as separate
• . For sub-bullets we could keep as part of same
• with semicolons? But better to keep each bullet as separate
• . The original had headings within the duties; we could keep those headings as part of
• text. Eg "
• Revenue Strategy & Planning: Lead annual and quarterly revenue planning..." but we shouldn't add extra tags not in original? The instruction didn't forbid adding but better to keep plain text. We'll keep the heading as part of the sentence. Thus each
• will contain the heading and description. Now What Success Looks Like: bullet points: - A single, agreed set of revenue definitions and a solution taxonomy in use across the business. - Forecasting and reporting that leadership trusts, delivered on a predictable cadence. - A revenue operations function and team established and running. - A shared operating rhythm across growth, finance, and the business segments. Now Education & Experience Required: bullet points: - Proven track record of building or scaling a revenue operations function, not only running an established one. - 10+ years in Revenue Operations, Sales Operations, or commercial operations, including team leadership. - Experience in an agency, marketing services, brand experience, or other project-based business. Strongly preferred. - Advanced proficiency with CRM platforms, with Salesforce required, and experience integrating commercial and finance systems. - Strong analytical skills and the ability to direct BI and reporting delivery (Power BI, Tableau, Looker, or equivalent). - A track record of turning complex data into executive-ready narratives and leading cross-functional initiatives end to end. Now Preferred: bullet points: - Master’s degree preferred, Bachelor's degree from a 4 year accredited institution with relevant experience required - Experience operating across multiple brands or business units, and within a larger parent company. - Experience working with or alongside a Sales Operations team. - Prior experience supporting or reporting to a CGO, CRO, President, or EVP. - Familiarity with complex CPQ, revenue intelligence, and reporting tooling. Now Travel Requirements: "Travel up to 25%". We'll put as

  . Now What We Offer: bullet list: - Medical, Dental, Vision Insurance - Tuition Reimbursement - Paid Parental Leave - Life, Accident and Disability - Retirement with Company Match - Paid Time Off We should preserve as list. Now Locations: bullet list of preferred locations: - Philadelphia, PA - Fort Wayne, IN - Las Vegas, NV - Royal Oak, MI - Grand Prairie, TX We could also note that qualified candidates outside these markets will also be considered. Include that sentence. Now we need to output only HTML fragment, no markdown fences. Let's construct. We'll start with

  About Us

  ...

  Then

  Summary

  ...

  Then

  Locations

  • ...
  ...
  plus note. Then

  Essential