Guest Experience Supervisor

We need to output HTML fragment with headings

for sections: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. Only include sections that have real specific content. We must not repeat job title as heading. Remove boilerplate like EEO, etc. Also remove application instructions. Must preserve all substantive info. Let's parse the posting. Content: - Intro: "Join Dash In as a Guest Experience Manager La Plata, MD Be part of a Great Place to Work Certified™ company. At Dash In, we're more than a convenience store—we're building exceptional guest experiences while investing in the people who make it happen. As part of the Wills Group family, you'll have opportunities to grow your career while making a real impact every day." - "Why Join Dash In? Outstanding Benefits" then list benefits. - "About the Role" paragraph. - "What You'll Do" list of duties. - "Qualifications" with Required and Preferred. - "Grow Your Career With Us" paragraph. - Then EEO etc. We need sections: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We have: - About the role: we have a paragraph under "About the Role". Use that. - Responsibilities: we have "What You'll Do" list of duties. That can be Responsibilities. - Requirements: maybe combine Required qualifications? The posting has "Qualifications" with Required and Preferred. We could split: Requirements = Required qualifications; Qualifications = Preferred? But spec says we can have both Requirements and Qualifications sections. We need to decide. The spec says use headings for those categories if content exists. We have Required and Preferred. Could put Required under "Requirements" and Preferred under "Qualifications". Or we could combine all under Qualifications. But spec says prefer few substantive sections over many thin ones. However we have both Required and Preferred distinct. Could make Requirements = Required, Qualifications = Preferred. That seems reasonable. - Skills: maybe we can extract from Preferred: "Active ServSafe certification, Experience with POS systems, Strong coaching, communication, and organizational skills, Results-driven with excellent problem-solving abilities". Those are skills. Could put under Skills. - Benefits: we have list under "Why Join Dash In? Outstanding Benefits". That's Benefits. - Pay: not mentioned. No pay info. So we should NOT include Pay section. - Schedule: mention "Ability to work a flexible full-time schedule, including nights, weekends, and overnights". That's schedule info. Could be Schedule section. We also have "Grow Your Career With Us" paragraph. Could be part of About the role or maybe a separate section like "Career Development". Not in list; we could incorporate into About the role or maybe omit as not required heading. But we must preserve all substantive information. Could add a paragraph under About the role or maybe a separate section like "Career Growth". But spec only lists allowed headings; we can add other headings? It says use

for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). It doesn't forbid other headings, but says "Use

for section headings (e.g. ...)". Likely they expect only those headings. But we need to preserve all substantive info; we can incorporate "Grow Your Career With Us" into About the role or Qualifications. Probably incorporate into About the role as extra paragraph. Also "Why Join Dash In? Outstanding Benefits" includes benefits list. We'll put that under Benefits. We need to remove boilerplate: EEO, etc. Also remove "Apply today and discover why Dash In is a Great Place to Work Certified™ employer." That's application instruction? It's a call to apply; we should remove application instructions. Also remove "#DASHSOMD". Also remove "Be part of a Great Place to Work Certified™ company." maybe keep as part of intro? It's substantive? It's marketing but maybe keep. The instruction: "Preserve ALL substantive information; do NOT invent or summarize away detail." So we keep that sentence. We also need to remove duplicated lines. Not seeing duplicates. Now craft HTML. Structure:

About the role

... (intro + About the Role paragraph + Grow Your Career With Us)

Responsibilities

• Recruit, hire, train, and coach team members
• Lead daily Front of House operations
• Ensure outstanding guest service
• Maintain inventory and reduce product loss
• Drive sales while controlling labor and expenses
• Ensure compliance with company standards and safety procedures
• Prepare for and successfully complete third-party inspections
• Build a positive, engaging team culture
• Serve as the Store Manager when needed

Note: The "You'll also serve as the Store Manager when needed." is from earlier paragraph; include.

Requirements

• High school diploma or GED
• 3+ years of retail, food service, customer service, or operations experience
• 2+ years of leadership experience
• Ability to work a flexible full-time schedule, including nights, weekends, and overnights
• Must be at least 18 years old
• Ability to pass a background check and drug screening
• Authorized to work in the United States

But note schedule ability also appears; we might move schedule to Schedule section. However we have schedule info also in Requirements. Could keep schedule in Requirements but also have Schedule section. To avoid duplication, we could put schedule ability in Schedule section and not duplicate. The spec says preserve ALL substantive information; we can mention schedule in Schedule section and not duplicate in Requirements. But we need to keep the requirement about schedule; we can move it to Schedule section and not list under Requirements. However the requirement list includes schedule as a requirement; we could keep it there and also have Schedule section maybe redundant. Better to have Schedule section separate and not duplicate. Let's see: The posting says "Ability to work a flexible full-time schedule, including nights, weekends, and overnights" under Required. That's schedule requirement. So we can put that under Schedule section. Then we can remove from Requirements. Thus Requirements list excludes schedule. Now Qualifications (Preferred):

Qualifications

• Associate's or Bachelor's degree
• Active ServSafe certification
• Experience with POS systems
• Strong coaching, communication, and organizational skills
• Results-driven with excellent problem-solving abilities

Skills: maybe we could combine some of these into Skills. But we already have Qualifications covering preferred. Could also have Skills section for "Strong coaching, communication, and organizational skills" etc. But that would be thin. Better to not create Skills section if content is thin. However we have skills like "Strong coaching, communication, and organizational skills" and "Results-driven with excellent problem-solving abilities". Could put under Skills. But we already have Qualifications for preferred; maybe we treat Qualifications as both required and preferred? But we already split. The spec says we can have Skills section; we could put those skill items there. However we would then have Qualifications (maybe only degree and certification) and Skills (soft skills). Let's decide. We have Preferred items: degree, ServSafe, POS experience, coaching/communication/organizational skills, results-driven problem-solving. Could split: Qualifications = degree, ServSafe, POS experience (more formal qualifications). Skills = coaching/communication/organizational skills, results-driven problem-solving. That seems reasonable. Thus:

Qualifications

• Associate's or Bachelor's degree
• Active ServSafe certification
• Experience with POS systems

Skills

• Strong coaching, communication, and organizational skills
• Results-driven with excellent problem-solving abilities

Benefits: list.

Benefits

• Up to 5 weeks of paid time off
• 3 weeks vacation
• 6 sick days
• 4 personal days
• 8 paid holidays
• 2 paid volunteer days each year
• 100% tuition reimbursement
• Medical, dental & vision insurance
• Health Savings Account (HSA)
• Paid parental leave
• Pet insurance
• Company-paid life insurance & short-term disability
• 401(k) with up to 7% company match
• Career advancement opportunities throughout the Mid-Atlantic
• Leadership development and management training
• Employee discounts on food, beverages, and car washes

Schedule: we have ability to work flexible full-time schedule including nights, weekends, overnights.

Schedule

Ability to work a flexible full-time schedule, including nights, weekends, and overnights.

Now About the role section: combine intro paragraph and About the Role paragraph and Grow Your Career With Us. Intro: "Join Dash In as a Guest Experience Manager La Plata, MD Be part of a Great Place to Work Certified™ company. At Dash In, we're more than a convenience store—we're building exceptional guest experiences while investing in the people who make it happen. As part of the Wills Group family, you'll have opportunities to grow your career while making a real impact every day." But we should not repeat job title as heading; but we can keep it in paragraph. Then About the Role paragraph: "As a Guest Experience Manager, you'll lead our Front of House team and partner with the Store Manager to create an exceptional guest experience while driving operational excellence. You'll help build a high-performing team focused on: Outstanding customer service Sales growth Team development Brand standards Inventory and labor management Safe, efficient 24/7 operations You'll also serve as the Store Manager when needed." We need to preserve the colon list; we can keep as prose or break into list? The spec says use

• for any list of duties/requirements/benefits. This is a list of focus areas under "You'll help build a high-performing team focused on:" which is a list. So we should make that a list. However the spec says use
  • for any list of duties/requirements/benefits. This is a list of focus areas (not duties but similar). Safer to make it a list. Thus we can restructure About the role section: a paragraph for intro, then a paragraph for the role description, then a list for the focus areas, then maybe a paragraph for Grow Your Career With Us. But we must not create extra headings. We'll keep under About the role heading. Let's craft:

    About the role

    Join Dash In as a Guest Experience Manager La Plata, MD. Be part of a Great Place to Work Certified™ company. At Dash In, we're more than a convenience store—we're building exceptional guest experiences while investing in the people who make it happen. As part of the Wills Group family, you'll have opportunities to grow your career while making a real impact every day.

    As a Guest Experience Manager, you'll lead our Front of House team and partner with the Store Manager to create an exceptional guest experience while driving operational excellence. You'll also serve as the Store Manager when needed.

    You'll help build a high-performing team focused on:

    • Outstanding customer service
    • Sales growth
    • Team development
    • Brand standards
    • Inventory and labor management
    • Safe, efficient 24/