Ticket Sales Representative Intern, 2027 Season

We need to output HTML fragment with sections: About Us, What You'll Do, Your Responsibilities, What You Bring (maybe split into Required Experience & Skills, Education, Leadership, Flexibility & Travel, Physical Demands, Work Environment). Use

for headings. Use

• for any list of duties/requirements/benefits. Use

  for prose. We must not repeat job title as heading. No Job ID etc. Remove boilerplate like EEO, etc. Also remove navigation, cookie, legal, etc. The posting includes "EQUAL OPPORTUNITY" which we must remove. We need to preserve all substantive information. So we need to include sections where there is real content. Let's parse content: - About Us: paragraph about Penske Entertainment, description of brands. - What You'll Do: paragraph describing role. - Your Responsibilities: list of duties (Ticket Sales bullet points). Many bullet points. - What You Bring: includes "We’re looking for someone who’s ready to bring great effort every day and is committed to growing with us." Then sub-sections: Required Experience & Skills (list of attributes), Education, Leadership, FLEXIBILITY & TRAVEL, PHYSICAL DEMANDS, WORK ENVIRONMENT. We need to decide which headings to use. The instruction: use

  for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). But we can use other headings as appropriate? It says use

  for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). Likely they expect those standard headings, but we can also use other headings if needed? It says "use

  for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." It implies we should use those headings when applicable. However we can also use other headings if they match content? The examples are just examples; they didn't forbid other headings. But to be safe, we can map content to those headings: About Us -> About the role? Actually "About Us" could be "About the role" or "About the company". The instruction says use

  for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). So we should use those exact headings when we have content. Let's see: - About Us: could be "About the role" or maybe "About the company". But we have "About Us" describing company. Could map to "About the role"? Not exactly. But maybe we can use "About the role" as heading for the description of role and company. However we also have "What You'll Do" which could be "Responsibilities". Actually "What You'll Do" is similar to responsibilities. Then we have "Your Responsibilities" which is more detailed list. Could combine. We need to avoid thin sections. Perhaps we can have sections: About the role (combining About Us and What You'll Do), Responsibilities (the detailed list), Requirements (combining What You Bring: Required Experience & Skills, Education, Leadership, Flexibility & Travel, Physical Demands, Work Environment). Benefits, Pay, Schedule only if present. There is no explicit Pay or Benefits. There is mention of "FLSA Status Non-Exempt", "Employment Type Seasonal", "Duration December 2026 - July 2027". That's metadata; we could fold into a short

  maybe under About the role? But instruction: do NOT put Job ID / requisition numbers as headings — fold minor metadata into a short

  or drop it. So we can include a short paragraph with location, duration, FLSA status, employment type. We must not create Pay/Schedule/Benefits sections unless posting actually states them. There's no pay or benefits mentioned. So we omit those. We must not create sections with filler like "commensurate with experience". Not present. Thus output:

  About the role

  Location: Indianapolis, IN. FLSA Status: Non-Exempt. Employment Type: Seasonal. Duration: December 2026 – July 2027.

  At Penske Entertainment, we don’t just host world-class events—we create unforgettable moments. Our team fuels four iconic motorsports brands: Indianapolis Motor Speedway (IMS) – home of the world’s largest spectator sporting facility and annually hosts the world’s most prestigious auto race: the Indianapolis 500 presented by Gainbridge; INDYCAR - The Indianapolis-based governing body for North America's premier open-wheel auto racing series, the NTT INDYCAR SERIES, and its developmental series, INDY NXT by Firestone; IMS Productions - A multifaceted broadcast and multimedia division that helps bring INDYCAR and IMS events to life for global audiences; Motorsports Events Management (MEM) – Promotes major events featuring premier motorsports series throughout the United States. Whether on the track, behind the scenes, or on the screen, our people are at the heart of everything we do. If you’re ready for a career where excitement, purpose, and impact collide—we want to meet you.

  As a Ticket Sales Intern, you will play a key role in supporting the Indianapolis Motor Speedway by assisting with the sale of individual tickets for the INDYCAR Grand Prix, Indianapolis 500, Brickyard Weekend, and other ticket-related events. In this role, you'll be an important part of connecting fans with memorable experiences at the Racing Capital of the World. You'll engage directly with customers, build relationships with fans, and contribute to achieving ticket sales goals through outbound and inbound sales efforts. You’ll take ownership of key responsibilities, collaborate across departments, and bring energy and innovation within a fast-paced motorsports environment.

  Responsibilities

  • Make up to 400 calls a week.
  • Extensive telephone work including incoming, outgoing and follow-up calls to new potential leads and former ticket customers.
  • Generate revenue and drive attendance for IMS events including INDYCAR Grand Prix, Indianapolis 500, and Brickyard Weekend to reach individual sales goals and contribute to team goals.
  • Exhibit clear understanding and communication of IMS facility, events, products, and processes to both external and internal customers.
  • Compliance with proven telephone presentations and group sales approach.
  • Ability to be flexible.
  • Accurately operate IMS computer ticket system (SCORE) to process daily ticket orders and payments for packaging and fulfillment of all event tickets.
  • Ability to effectively operate IMS CRM software (Microsoft Dynamics) to manage and maintain customer lead data.
  • Handle cash, check, and credit card payments responsibly and accurately.
  • Accurately maintain confidential customer and business information.
  • Operate and maintain remote ticket locations during event times as assigned.
  • Other projects as assigned.

  Requirements

  We’re looking for someone who’s ready to bring great effort every day and is committed to growing with us.

  • Must be a self‑starter, professional, organized, creative, innovative, open‑minded, and self‑motivated.
  • Demonstrate teamwork, integrity, a GREAT attitude, and tremendous work ethic.
  • Strong knowledge of MS Office, with an emphasis on Excel and Word.
  • Must be creative, enthusiastic and possess excellent interpersonal skills.
  • Must be able to work overtime, evenings, weekends, and holidays.

  Education

  Currently pursuing an undergraduate or graduate degree from an accredited college or university. Any equivalent combination of experience and training which provides knowledge and abilities necessary to perform this position.

  Leadership

  This position does not have any supervisory responsibilities.

  Flexibility & Travel

  General office hours are Monday–Friday, 9 AM to 5 PM. Extended hours required during race weekends and key event periods (especially May and July). No travel. Our teams work together to create flexibility that supports life in and out of work.

  Physical Demands

  • Ability to lift up to 50 lbs.
  • Extended periods of sitting, standing, or walking (as needed).
  • Comfort working indoors/outdoors and around event noise.
  • Must be able to see and hear in the normal range with or without correction and communicate verbally and in written form with great facility and must be understood.
  • Must have the stamina to work long hours and must be willing to work an irregular schedule, which may include weekends or evenings.

  Work Environment

  Fast‑paced, collaborative office and event settings. Work is performed in an office environment with other workers. Incumbent shall be exposed to those conditions normally encountered in a business office environment. Staff will experience frequent interruptions and must be prepared to interact with others on a regular basis.

  We must ensure no boilerplate like EEO etc. We removed that. Check for any repeated content: We have "Ability to be flexible." as a bullet; also we have flexibility section. That's okay. Check for any placeholders like "commensurate with experience": none. Check for any mention of Pay/Benefits/Schedule: we have schedule info in Flexibility & Travel (general office hours, extended hours). That's okay; we used heading Flexibility & Travel, not Schedule. The instruction says use

  for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). It didn't forbid other headings, but we used Flexibility & Travel, Physical Demands, Work Environment, Education, Leadership. Those are not in the examples but likely acceptable. However they said "use

  for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." Could be interpreted that we should only use those headings. But they gave examples, not an exhaustive list. Usually they'd want those headings for typical sections. However we have many sub-sections like Education, Leadership, Flexibility & Travel, Physical Demands, Work Environment. Those could be considered under Requirements or Qualifications. Maybe we should combine them into a single Requirements section with sub-bullets. The instruction: "Prefer a few substantive sections over many thin ones." So we should avoid many thin sections. So better to combine Education, Leadership, Flexibility & Travel, Physical Demands, Work Environment into a single Requirements or Qualifications section. Thus we should have maybe three sections: About the role, Responsibilities, Requirements (or Qualifications). Let's do that. We need to include all substantive info. We'll put About the role (including About Us, What You'll Do, location/metadata). Responsibilities (the bullet list). Requirements (including What You Bring: Required Experience & Skills, Education, Leadership, Flexibility & Travel, Physical Demands, Work Environment). We'll not create Benefits, Pay, Schedule. We must use

  for section headings. So we will have:

  About the role

  ... location/metadata ...

  ... About Us paragraph ...

  ... What You'll Do paragraph ...

  Responsibilities

  ...

  Requirements

  We’re looking for someone who’s ready to bring great effort every day and is committed to growing with us.

  ... Required Experience & Skills bullets ...

  Education