Manager, Ticketing Analytics

We need to output HTML fragment with sections: About the role? The posting includes WHO WE ARE, OUR COMMITMENT TO INCLUSION, POSITION OVERVIEW, RESPONSIBILITIES..., QUALIFICATIONS, WORKING CONDITIONS, COMPENSATION AND BENEFITS. We need to use

for section headings (e.g., About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). We should map sections accordingly. We must not repeat job title as heading. No Job ID etc. Remove boilerplate: EEO etc. Also remove cookie/navigation/legal etc. The posting includes "We are an equal opportunity employer..." which is boilerplate; remove. We need to preserve all substantive information. So we need to include WHO WE ARE content? That's about company; maybe we can put under "About the role"? Actually "About the role" is typical heading for position overview. But we have separate sections: WHO WE ARE (company description) and OUR COMMITMENT TO INCLUSION (diversity statement). Might combine into "About the company" but headings list doesn't include that; but we can still use heading like "About the role"? The instruction: use

for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). It says e.g., meaning those are examples; we can use other headings if needed? Probably we should stick to those headings where applicable. But we have company overview and inclusion statement; maybe we can put them under "About the role"? Not ideal. Could create a section "About the company" but not in list; but instruction says use those headings for section headings (e.g...). It might be okay to use other headings if needed, but better to follow examples. However we need to include all substantive info; we could put WHO WE ARE and OUR COMMITMENT TO INCLUSION under a heading "About the role" or "About the company". The instruction says "do NOT repeat the job title as a heading (the page already shows it)". It doesn't forbid other headings. It says use

for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). So we can use those exact headings where appropriate. For company overview maybe "About the role" is not correct; but we could treat it as "About the role" includes position overview and company info? Might be okay. Alternatively we could create sections: "About the company" but that's not in examples; risk of being considered not following instruction. Safer to use given headings: we have Responsibilities, Qualifications, Benefits, Pay, Schedule. Also we could have "About the role" for position overview. For WHO WE ARE and OUR COMMITMENT TO INCLUSION maybe we can include under "About the role" as well. We also have WORKING CONDITIONS (travel, work environment, physical). That could be under "Schedule"? Not exactly. Could be under "Schedule" but schedule is about work hours; we have travel requirements and work environment. Could create a "Schedule" section for travel and work environment? Might be okay. We also have COMPENSATION AND BENEFITS: we need Pay and Benefits sections separately. So we will have

Pay

with pay range info.

Benefits

with benefits list. We need to remove boilerplate like "We are an equal opportunity employer..." etc. We need to preserve all substantive info: include details about responsibilities, qualifications, working conditions, compensation, benefits. Let's extract substantive content: WHO WE ARE: details about HBSE, portfolio, Prudential Center stats, etc. OUR COMMITMENT TO INCLUSION: statement about hiring best talent, supporting employees, inclusive environment. POSITION OVERVIEW: description of role, reporting to Senior Director of Pricing Analytics, tasks. RESPONSIBILITIES INCLUDE, BUT ARE NOT LIMITED TO THE BELOW: list bullet points. QUALIFICATIONS: list bullet points. WORKING CONDITIONS: Travel Requirements (About the role

WHO WE ARE content + OUR COMMITMENT TO INCLUSION + POSITION OVERVIEW combined? Might be too long but okay. Better: separate headings: maybe "About the company" and "Position overview". But not in list. However we could still use

for those; the instruction says use

for section headings (e.g. About the role, Responsibilities...). It doesn't forbid other headings, but says use

for section headings (e.g...). Likely they expect us to use those headings where applicable, but we can also add others if needed. Safer to stick to given headings. Thus we need to fit all content into those headings: About the role, Responsibilities, Qualifications, Benefits, Pay, Schedule. Possibly also Skills? Not needed. We can put WHO WE ARE and OUR COMMITMENT TO INCLUSION under About the role. Then POSITION OVERVIEW also under About the role (makes sense). Then Responsibilities under Responsibilities. Qualifications under Qualifications. Benefits under Benefits. Pay under Pay. Schedule under Schedule (travel, work environment, physical). That covers all. Now we need to ensure we don't include filler like "commensurate with experience". Not present. We need to use

• for any list of duties/requirements/benefits. So responsibilities list, qualifications list, benefits list. We need to use

  for prose. Let's craft. First, About the role section: combine WHO WE ARE, OUR COMMITMENT TO INCLUSION, POSITION OVERVIEW into paragraphs. We'll write:

  About the role

  Founded by Josh Harris and David Blitzer, Harris Blitzer Sports & Entertainment (HBSE) includes in its portfolio the Philadelphia 76ers, the New Jersey Devils, Prudential Center in Newark, N.J., the Delaware Blue Coats, the Utica Comets and a variety of other sports and entertainment properties. Led by some of the best and brightest minds in the industry, HBSE positions itself as a pioneering and innovative global sports and entertainment business enterprise. We also strive to positively impact the local communities in which we operate through the powerful platform of sports. HBSE offers an energetic work environment built on collaboration, growth and a quest to excel in everything we do. As part of its portfolio, Prudential Center in downtown Newark, N.J. annually hosts more than 200 games, concerts, family shows and special events and is a top-5 ranked sports and entertainment venue in the U.S. by Pollstar and Billboard. It is home to the New Jersey Devils, a renowned NHL franchise with three Stanley Cup championships and a proud, passionate fan base. HBSE also owns the NBA’s Philadelphia 76ers, one of the most storied franchises in American sports, having won three championships led by some of the most iconic athletes in NBA history.

  At HBSE, we are dedicated to hiring the best talent from the communities where we live, work and play - across all groups and levels; supporting and developing every employee to reach their potential; and creating an inclusive environment that allows team members to bring their true authentic selves to work.

  HBSE is looking for a full-time Manager, Ticketing Analytics to join the Strategy & Analytics team and take on advanced, high-ownership work building out and executing pricing capabilities across the New Jersey Devils, Philadelphia 76ers, and more in the HBSE portfolio. Reporting directly to the Senior Director of Pricing Analytics, the manager will help run, design, and scale the pricing and inventory management systems that will power pricing and revenue management across all ticket products - all in a fast-paced, entrepreneurial, high-performing work environment. This role calls for an experienced individual who can take on advanced, ambiguous projects that require judgment and prior experience to execute well. You will help build and refine ticketing pricing strategies and inventory management approaches, working hands-on with data that directly shapes how our pricing capabilities scale and mature over time. In addition, you will be responsible for harnessing the power of ticketing and fan data to perform quantitative and qualitative analyses related to dynamic pricing, inventory management, and product mix, while translating that analysis into pricing strategy and business recommendations. The role requires end-to-end ownership, from querying and modeling data to making strategic business decisions, to communicating and defending recommendations to stakeholders across the organization.

  Now Responsibilities:

  Responsibilities

  • Set and adjust ticket pricing across HBSE properties based on market health, demand signals, and internal sales strategies.
  • Partner with the Senior Director to design, test, and refine pricing and inventory management strategies across single-game and multi-game ticket products.
  • Build and maintain analytical models supporting demand forecasting, price elasticity, inventory/product valuation, and revenue optimization that directly inform pricing decisions.
  • Lead experimentation on new pricing and inventory management approaches, applying findings to live pricing decisions and scaling results to future seasons.
  • Own ad-hoc and ongoing reporting and dashboards that inform business decisions, including querying, cleaning, and analyzing complex data sets.
  • Maintain clear documentation of system design and logic to support team scalability and continuity.
  • Create and monitor relevant KPIs to track performance against revenue and sell-through goals and surface actionable business insights.
  • Communicate analysis, recommendations, and pricing strategy clearly to audiences ranging from Strategy + Analytics peers to senior executives.
  Qualifications:

  Qualifications

  • 2-4 years of experience in pricing/revenue management or data science/analytics, ideally with exposure to both a hands-on technical function and a pricing or commercial strategy function.
  • Experience setting or directly informing pricing decisions within a revenue management, dynamic pricing, or similar commercial function.
  • Strong experience querying and working with structured data using SQL.
  • Proficiency in Python or R for data science and analytical work preferred.
  • Demonstrated experience building predictive models (forecasting, regression, or similar) and applying them to real pricing or business decisions.
  • Experience with experimental or causal analysis methods (A/B testing, causal inference, quasi-experimental design, or similar)
  • Experience using Databricks/Snowflake for querying and predictive modeling on large datasets preferred.
  • Experience with a data visualization tool (Tableau, Power BI, etc.) and building reporting for non-technical audiences.
  • Demonstrated ability to communicate data-driven insights and pricing recommendations to a range of audiences, including senior stakeholders.
  • Must be a strategic and critical thinker who is comfortable operating with ambiguity and open-ended projects.
  • Must possess outstanding problem-solving capabilities and be willing to approach undefined projects with proactiveness, tenacity, and rigor.
  • Ability to move quickly learning a new data and ticketing environment to making pricing and inventory decisions within it.
  • Sports and entertainment industry experience, particularly in ticketing, live events, or venue operations, preferred.
  • Comfort using AI-assisted tools to accelerate coding, analysis, or documentation workflows a plus.
  Benefits:

  Benefits

  • Medical/Dental/Vision/Flexible Spending Accounts
  • Pretax Transportation Benefit
  • Generous Parental Leave policies
  • 40