Guest Experience Representative | Part-Time | Snapdragon Stadium
Oak View Group · San Diego, CA · 1 mo ago
OTHR$19.5/hrPart-time
We need to output only HTML fragment, no html/body tags, no markdown fences. Use for section headings: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We need to include sections only when posting has real specific content. Let's parse the posting.
Content:
- Oak View Group description (company overview) maybe not needed? It's not a section heading; we can include as prose maybe under "About the role"? Actually "About The Venue" is a section about venue. Could be considered "About the role"? Not exactly. The instruction: use
for section headings: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We need to include sections only when posting has real specific content. Let's parse the posting.
Content:
- Oak View Group description (company overview) maybe not needed? It's not a section heading; we can include as prose maybe under "About the role"? Actually "About The Venue" is a section about venue. Could be considered "About the role"? Not exactly. The instruction: use for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). So we can create headings for those if content exists.
We have:
- Position Summary: Guest Experience Representatives responsibilities, pay $19.50 hourly, benefits for part-time: 401(k) Savings Plan and 401(k) matching. Position open until Dec 25, 2026.
- About The Venue: description of Snapdragon Stadium.
- Responsibilities: list bullet points.
- Qualifications: list bullet points.
- Strengthened by our Differences... (diversity statement) maybe not needed as it's boilerplate? It's not EEO but it's a diversity statement; could be considered boilerplate? The instruction says remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate. The diversity statement might be considered EEO/equal-opportunity boilerplate. Likely remove.
- Equal Opportunity Employer section: remove.
Thus we keep: Position Summary (maybe as a short paragraph), About The Venue (maybe as "About the role"? Actually "About the venue" is not exactly "About the role". Could treat as "About the role" but it's about venue. Might be better to create a section "About the Venue" but not in allowed headings list. The instruction says use for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). It gives examples but not exclusive? It says use for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). Likely they expect only those headings. So we should map content to those headings.
We have:
- About the role: could include Position Summary and maybe About The Venue? But "About the role" is about the job, not venue. Could combine Position Summary and maybe some venue description as part of role context. But we must not invent headings. We'll create About the role
and put the position summary and maybe venue description as prose.
- Responsibilities: we have list.
- Requirements: we have qualifications (maybe treat as Requirements). Could also have Qualifications separate. The list includes both Requirements and Qualifications as possible headings. We have qualifications: high school diploma or equivalent required, previous experience preferred, must be comfortable standing..., excellent customer service skills required, must be able to display positive attitude, available to work nights..., strong interpersonal and communication skills.
We could split: Requirements: maybe the mandatory items (high school diploma, excellent customer service skills required, must be able to display positive attitude, available to work nights..., strong interpersonal and communication skills). Qualifications: preferred items (previous experience preferred, must be comfortable standing... maybe also required). But we can just put all under Qualifications heading. Since we have both headings possible, we can choose to use Qualifications only if we have content. The instruction: Prefer a few substantive sections over many thin ones. So we could combine Requirements and Qualifications into one section, maybe "Qualifications". But we need to follow the examples: they gave both as possible headings. We'll decide to use "Qualifications" heading and put all qualification-related content there. We'll omit "Requirements" heading to avoid thin section.
- Benefits: we have 401(k) Savings Plan and 401(k) matching for part-time roles.
- Pay: hourly rate $19.50.
- Schedule: not explicitly given; only mention "Available to work nights, weekends, holidays, and events as scheduled." That's about availability, not schedule details. The instruction: never create Pay/Schedule/Benefits sections unless the posting actually states them. Schedule: we don't have specific schedule (like shift times). So we should not create a Schedule section.
Thus sections: About the role, Responsibilities, Qualifications, Benefits, Pay.
We need to preserve all substantive information; do not invent or summarize away detail. So we need to include all details from posting within those sections.
Let's extract details:
Company overview: Oak View Group description (global leader...). Should we include? It's substantive but not under any heading. Could be placed in About the role as introductory prose. It's about the company, not role but okay.
Position Summary: Guest Experience Representatives responsibilities, pay hourly $19.50, benefits for part-time: 401(k) Savings Plan and 401(k) matching. Position open until Dec 25, 2026.
About The Venue: description of Snapdragon Stadium.
Responsibilities list:
- Provide excellent customer service for guests attending events at Snapdragon Stadium.
- Handle lost and found during events.
- Recognize potential hazards and observe appropriate precautions with guests.
- Scan and check for valid tickets at premium VIP entrances.
- Receive and quickly act upon requests or complaints from guests.
- Monitor all public areas to ensure they meet cleanliness standards.
- Be familiar with Snapdragon Stadium to answer stadium questions and provide accurate directions.
- Project a friendly, approachable, and professional attitude during your shift.
- Direct guests to their ticketed seat or appropriate seating sections.
- Keep aisles and stairs clear of guests.
- Monitor the seating area for guests who may not be in the correct area and ask to verify tickets.
- Provide location-specific direction for guests using elevators.
- Performs other duties as assigned by supervisor or manager.
Qualifications list:
- High school diploma or equivalent is required.
- Previous experience in a customer service role is preferred.
- Must be comfortable standing or remaining in a stationary position for extended periods of time.
- Excellent customer service skills are required.
- Must be able to display a positive and energetic attitude.
- Available to work nights, weekends, holidays, and events as scheduled.
- Strong interpersonal and communication skills.
Benefits: 401(k) Savings Plan and 401(k) matching (for part-time roles).
Pay: hourly rate $19.50.
Also note: "This position will remain open until December 25, 2026." That's a date; we should include somewhere, maybe in About the role or Pay section? Could be a note in About the role.
We must not include boilerplate like Equal Opportunity Employer, diversity statement.
Now produce HTML fragment:
About the role
for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). It gives examples but not exclusive? It says use for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). Likely they expect only those headings. So we should map content to those headings.
We have:
- About the role: could include Position Summary and maybe About The Venue? But "About the role" is about the job, not venue. Could combine Position Summary and maybe some venue description as part of role context. But we must not invent headings. We'll create About the role
and put the position summary and maybe venue description as prose.
- Responsibilities: we have list.
- Requirements: we have qualifications (maybe treat as Requirements). Could also have Qualifications separate. The list includes both Requirements and Qualifications as possible headings. We have qualifications: high school diploma or equivalent required, previous experience preferred, must be comfortable standing..., excellent customer service skills required, must be able to display positive attitude, available to work nights..., strong interpersonal and communication skills.
We could split: Requirements: maybe the mandatory items (high school diploma, excellent customer service skills required, must be able to display positive attitude, available to work nights..., strong interpersonal and communication skills). Qualifications: preferred items (previous experience preferred, must be comfortable standing... maybe also required). But we can just put all under Qualifications heading. Since we have both headings possible, we can choose to use Qualifications only if we have content. The instruction: Prefer a few substantive sections over many thin ones. So we could combine Requirements and Qualifications into one section, maybe "Qualifications". But we need to follow the examples: they gave both as possible headings. We'll decide to use "Qualifications" heading and put all qualification-related content there. We'll omit "Requirements" heading to avoid thin section.
- Benefits: we have 401(k) Savings Plan and 401(k) matching for part-time roles.
- Pay: hourly rate $19.50.
- Schedule: not explicitly given; only mention "Available to work nights, weekends, holidays, and events as scheduled." That's about availability, not schedule details. The instruction: never create Pay/Schedule/Benefits sections unless the posting actually states them. Schedule: we don't have specific schedule (like shift times). So we should not create a Schedule section.
Thus sections: About the role, Responsibilities, Qualifications, Benefits, Pay.
We need to preserve all substantive information; do not invent or summarize away detail. So we need to include all details from posting within those sections.
Let's extract details:
Company overview: Oak View Group description (global leader...). Should we include? It's substantive but not under any heading. Could be placed in About the role as introductory prose. It's about the company, not role but okay.
Position Summary: Guest Experience Representatives responsibilities, pay hourly $19.50, benefits for part-time: 401(k) Savings Plan and 401(k) matching. Position open until Dec 25, 2026.
About The Venue: description of Snapdragon Stadium.
Responsibilities list:
- Provide excellent customer service for guests attending events at Snapdragon Stadium.
- Handle lost and found during events.
- Recognize potential hazards and observe appropriate precautions with guests.
- Scan and check for valid tickets at premium VIP entrances.
- Receive and quickly act upon requests or complaints from guests.
- Monitor all public areas to ensure they meet cleanliness standards.
- Be familiar with Snapdragon Stadium to answer stadium questions and provide accurate directions.
- Project a friendly, approachable, and professional attitude during your shift.
- Direct guests to their ticketed seat or appropriate seating sections.
- Keep aisles and stairs clear of guests.
- Monitor the seating area for guests who may not be in the correct area and ask to verify tickets.
- Provide location-specific direction for guests using elevators.
- Performs other duties as assigned by supervisor or manager.
Qualifications list:
- High school diploma or equivalent is required.
- Previous experience in a customer service role is preferred.
- Must be comfortable standing or remaining in a stationary position for extended periods of time.
- Excellent customer service skills are required.
- Must be able to display a positive and energetic attitude.
- Available to work nights, weekends, holidays, and events as scheduled.
- Strong interpersonal and communication skills.
Benefits: 401(k) Savings Plan and 401(k) matching (for part-time roles).
Pay: hourly rate $19.50.
Also note: "This position will remain open until December 25, 2026." That's a date; we should include somewhere, maybe in About the role or Pay section? Could be a note in About the role.
We must not include boilerplate like Equal Opportunity Employer, diversity statement.
Now produce HTML fragment:
About the role
About the role
and put the position summary and maybe venue description as prose. - Responsibilities: we have list. - Requirements: we have qualifications (maybe treat as Requirements). Could also have Qualifications separate. The list includes both Requirements and Qualifications as possible headings. We have qualifications: high school diploma or equivalent required, previous experience preferred, must be comfortable standing..., excellent customer service skills required, must be able to display positive attitude, available to work nights..., strong interpersonal and communication skills. We could split: Requirements: maybe the mandatory items (high school diploma, excellent customer service skills required, must be able to display positive attitude, available to work nights..., strong interpersonal and communication skills). Qualifications: preferred items (previous experience preferred, must be comfortable standing... maybe also required). But we can just put all under Qualifications heading. Since we have both headings possible, we can choose to use Qualifications only if we have content. The instruction: Prefer a few substantive sections over many thin ones. So we could combine Requirements and Qualifications into one section, maybe "Qualifications". But we need to follow the examples: they gave both as possible headings. We'll decide to use "Qualifications" heading and put all qualification-related content there. We'll omit "Requirements" heading to avoid thin section. - Benefits: we have 401(k) Savings Plan and 401(k) matching for part-time roles. - Pay: hourly rate $19.50. - Schedule: not explicitly given; only mention "Available to work nights, weekends, holidays, and events as scheduled." That's about availability, not schedule details. The instruction: never create Pay/Schedule/Benefits sections unless the posting actually states them. Schedule: we don't have specific schedule (like shift times). So we should not create a Schedule section. Thus sections: About the role, Responsibilities, Qualifications, Benefits, Pay. We need to preserve all substantive information; do not invent or summarize away detail. So we need to include all details from posting within those sections. Let's extract details: Company overview: Oak View Group description (global leader...). Should we include? It's substantive but not under any heading. Could be placed in About the role as introductory prose. It's about the company, not role but okay. Position Summary: Guest Experience Representatives responsibilities, pay hourly $19.50, benefits for part-time: 401(k) Savings Plan and 401(k) matching. Position open until Dec 25, 2026. About The Venue: description of Snapdragon Stadium. Responsibilities list: - Provide excellent customer service for guests attending events at Snapdragon Stadium. - Handle lost and found during events. - Recognize potential hazards and observe appropriate precautions with guests. - Scan and check for valid tickets at premium VIP entrances. - Receive and quickly act upon requests or complaints from guests. - Monitor all public areas to ensure they meet cleanliness standards. - Be familiar with Snapdragon Stadium to answer stadium questions and provide accurate directions. - Project a friendly, approachable, and professional attitude during your shift. - Direct guests to their ticketed seat or appropriate seating sections. - Keep aisles and stairs clear of guests. - Monitor the seating area for guests who may not be in the correct area and ask to verify tickets. - Provide location-specific direction for guests using elevators. - Performs other duties as assigned by supervisor or manager. Qualifications list: - High school diploma or equivalent is required. - Previous experience in a customer service role is preferred. - Must be comfortable standing or remaining in a stationary position for extended periods of time. - Excellent customer service skills are required. - Must be able to display a positive and energetic attitude. - Available to work nights, weekends, holidays, and events as scheduled. - Strong interpersonal and communication skills. Benefits: 401(k) Savings Plan and 401(k) matching (for part-time roles). Pay: hourly rate $19.50. Also note: "This position will remain open until December 25, 2026." That's a date; we should include somewhere, maybe in About the role or Pay section? Could be a note in About the role. We must not include boilerplate like Equal Opportunity Employer, diversity statement. Now produce HTML fragment:About the role
Oak View Group (OVG) is the global leader in premium live entertainment infrastructure and services, with a platform spanning venue development and end-to-end capabilities across venue management, hospitality, and sponsorship sales. Founded in 2015, the company serves a collection of seven world-class owned venues and a client roster of the most iconic arenas, stadiums, convention centers, music festivals, performing arts centers, and cultural institutions, spanning four continents. Guest Experience Representatives are responsible for providing excellent customer service to Snapdragon Stadium’s guests. This role pays an hourly rate of $19.50. Benefits for part-time roles include a 401(k) Savings Plan and 401(k) matching. This position will remain open until December 25, 2026.
But we already have Benefits and Pay sections separate; we might want to avoid duplication. The instruction: Preserve ALL substantive information; do NOT invent or summarize away detail. If we put pay and benefits in About the role, then we also have separate Benefits and Pay sections, that would duplicate. Better to keep About the role focused on role description and company overview, and then have separate Benefits and Pay sections with the specifics. However we must not duplicate content. So we need to split: About the role includes company overview and role summary (maybe not pay/benefits). Then Benefits section includes the 401(k) details. Pay section includes hourly rate. The opening date could go in About the role or maybe a separate note; we can put in About the role. Thus: About the role: company overview + role summary (Guest Experience Representatives responsibilities? Actually responsibilities are separate section). So About the role could be: Oak View Group description + position summary (what the role does at high level). But we have responsibilities separate; we can keep About the role brief: Oak View Group description + that the role is Guest Experience Representative at Snapdragon Stadium, providing excellent customer service, etc. But we need to avoid repeating responsibilities details. We'll keep it high-level. Let's craft: About the role:Oak View Group (OVG) is the global leader in premium live entertainment infrastructure and services, with a platform spanning venue development and end-to-end capabilities across venue management, hospitality, and sponsorship sales. Founded in 2015, the company serves a collection of seven world-class owned venues and a client roster of the most iconic arenas, stadiums, convention centers, music festivals, performing arts centers, and cultural institutions, spanning four continents. The Guest Experience Representative role at Snapdragon Stadium focuses on delivering excellent customer service to guests attending events.
Responsibilities:- ... each bullet
- ... each bullet
- 401(k) Savings Plan
- 401(k) matching (for part‑time roles)
$19.50 per hour
We should not include Schedule section. Check for any other substantive info: "Position will remain open until December 25, 2026." Where to put? Could be in About the role as a note. Add a sentence: "This position will remain open until December 25, 2026." Add to About the role paragraph. Now ensure we didn't miss any responsibility: "Provide location-specific direction for guests using elevators." included. Check qualifications: "Must be comfortable standing or remaining in a stationary position for extended periods of time." included. "Excellent customer service skills are required." included. "Must be able to display a positive and energetic attitude." included. "Available to work nights, weekends, holidays, and events as scheduled." included. "Strong interpersonal and communication skills." included. "Previous experience in a customer service role is preferred." included. "High school diploma or equivalent is required." included. Now benefits: "401(k) Savings Plan and 401(k) matching." We'll split. Pay: "$19.50" hourly. Now ensure we didn't include any boilerplate: removed EEO, diversity statement. Now output HTML fragment only. Let's construct:About the role
Oak View Group (OVG) is the global leader in premium live entertainment infrastructure and services, with a platform spanning venue development and end-to-end capabilities across venue management, hospitality, and sponsorship sales. Founded in 2015, the company serves a collection of seven world-class owned venues and a client roster of the most iconic arenas, stadiums, convention centers, music festivals, performing arts centers, and cultural institutions, spanning four continents. The Guest Experience Representative role at Snapdragon Stadium focuses on delivering excellent customer service to guests attending events. This position will remain open until December 25, 2026.
Responsibilities
- Provide excellent customer service for guests attending events at Snapdragon Stadium.
- Handle lost and found during events.
- Recogn