Guest Account Coordinator - Winter 2026 - 27

The user wants me to reformat a job posting into clean semantic HTML. Let me analyze the content and structure it according to the rules. First, I need to identify the sections: - About the role / Purpose of Position - Responsibilities (multiple subsections) - Qualifications - Dates of Employment - Pay Rate - Benefits (there's a list of perks at the beginning) The posting starts with a description of Deer Valley Resort and staff perks. That's essentially "About the company" and "Benefits". Then there's "PURPOSE OF POSITION" which is the role summary. Then "Responsibilities" broken into subcategories. Then "Qualifications". Then "Dates Of Employment" and "Pay Rate". Also EEO statement at the end which should be removed. Rules: - Use

for section headings (About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule) - Use

• for lists,

  for prose - Do NOT repeat job title as heading (page already shows it) - Do NOT put Job ID/requisition numbers as headings - Preserve ALL substantive information - Remove boilerplate (EEO, etc.) - Include section ONLY when real specific content exists - Never emit heading followed by filler/placeholder text - Never create Pay/Schedule/Benefits sections unless posting actually states them - Output ONLY HTML fragment, no html/body, no markdown fences Let me structure: 1. About the role (from PURPOSE OF POSITION) - prose 2. Responsibilities - this has multiple subsections. Should I keep subsections as subheadings? The rules say use

  for section headings. The subsections (Project & Operational Support, Systems & Technical Proficiency, etc.) are part of Responsibilities. Could make them

  but rules only mention

  . Probably keep as

  for each major responsibility area? But the rule says "use

  for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)". So maybe "Responsibilities" is one

  and then the sub-items as list items? However the subsections are distinct categories with multiple bullet points each. Could make each a

  but that might be too many. The rule says "Prefer a few substantive sections over many thin ones." So maybe keep "Responsibilities" as one

  and then use nested lists? But the subsections are distinct. I think it's okay to have multiple

  for each responsibility category, as they are substantive. The example includes "Responsibilities" as a heading, but the posting has multiple responsibility categories. I'll treat each category as a separate

  with a descriptive title, but the rule says use

  for section headings like "Responsibilities". Hmm. Better: Use

  for "Responsibilities" and then within that, use

  for subcategories? But the rule only mentions

  . It doesn't forbid

  . However the instruction: "use

  for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)". It doesn't say you cannot use other headings. But to be safe, I'll use

  for each major section: "About the role", "Responsibilities", "Qualifications", "Benefits", "Pay", "Schedule". The subcategories under Responsibilities can be presented as a list of bullet points with bold labels? Or as separate

  ? The rule says "Prefer a few substantive sections over many thin ones." So maybe combine all responsibilities under one "Responsibilities" heading with a list of bullet points that include the subcategory labels. But the subcategories have multiple bullet points each. Could do:

  Responsibilities

  • Project & Operational Support
    • Support divisional projects...
    ...
  ...
  But that's nested lists. That's acceptable HTML. However the rule says "Use
  • for any list of duties/requirements/benefits". Nested lists are okay. Alternatively, make each subcategory a separate

    like "Project & Operational Support", "Systems & Technical Proficiency", etc. That would be many headings. The rule says "include a section ONLY when the posting has real, specific content for it". Each subcategory has real content. But they are sub-sections of Responsibilities. I think using

    for each is okay, but the example list includes "Responsibilities" as a heading, not sub-responsibilities. I'll follow the example: use

    for "Responsibilities" and then list all duties as bullet points, perhaps grouping with bold labels. Let me decide: I'll create sections: - About the role (from PURPOSE OF POSITION) - Responsibilities (with sub-bullets) - Qualifications - Benefits (from the perks list at top) - Pay (from Pay Rate) - Schedule (from Dates Of Employment and flexible availability) The posting mentions "Dates Of Employment Early November through mid-April" and "Flexible availability, including weekends - typically will be scheduled 4-5 days per week, 8-10 hours per day." That's schedule info. Also "Pay Rate $22.00 per hour" -> Pay section. Benefits: the list at the beginning: Ski perks, friends/family discounts, subsidized meals, subsidized housing, discounts in Park City, healthcare options, 401k plan. That's substantive. Now, the "PURPOSE OF POSITION" is a paragraph. I'll put under "About the role". Qualifications list: bullet points. Now, remove EEO statement. Also note: "Seasonal Classic, consistent quality from a winning team!" is like a tagline, maybe part of About the role or company description. I'll include in About the role as intro paragraph. Let's craft HTML. Structure:

    About the role

    Seasonal Classic, consistent quality from a winning team! Deer Valley Resort is nestled in the Wasatch Mountains of Utah, in the historic mining town of Park City which has evolved into an exciting and diverse mountain ski town. Our staff consists of locals, transplants, seasonal workers from all 50 states and international students from around the globe. We are a diverse workforce where everyone feels welcome, appreciated, and valued. No matter if you are 14 or 84 years, there is a place for you in the Deer Valley family! (Last year over 1,100 staff members celebrated their fifth season or more at Deer Valley).

    The Guest Account Coordinator is responsible for assisting management with accounting, quality assurance, and client services tasks to support the Skier Services division. They will track and report issues, address client account needs, perform POS tasks, assist with daily web reconciliation reporting, provide technical application support, and organize training sessions with various departments in addition to assisting with daily operations as needed.

    Responsibilities

    • Project & Operational Support
      • Support divisional projects by monitoring timelines, tracking deliverables, and maintaining clear communication with leadership regarding progress and deadlines.
      • Collaborate across multiple systems to support project execution, while actively pursuing opportunities for skill development and process improvement.
      • Demonstrate a strong understanding of divisional products and services, supporting operations across various departments and applications.
      • Provide backup support for daily operations, including front-line and phone agent responsibilities, and other roles as needed.
      • Perform additional duties as assigned to support departmental needs and ensure operational efficiency.
    • Systems & Technical Proficiency
      • Exhibit technical proficiency in DVSS, RTP, Inntopia, flaik, credit card processing systems, reporting tools, and other relevant platforms.
      • Assist in identifying and resolving discrepancies between online bookings and source-system records to ensure data consistency and accuracy.
      • Investigate and provide resolution for out-of-balance DVSS accounts.
      • Assist with Lift Ticket GUID disconnected records.
    • Guest Service & Sales Fulfillment
      • Deliver professional and friendly guest service by fulfilling online sales orders and providing product guidance via telephone based on availability and guest needs.
    • Financial & Payroll Support
      • Assist with accounts payable and receivable processes (DVSS, Inntopia, etc.), including manual updates to financial tracking documents.
      • Support manual updates to Ski Instructor payroll and timekeeping records using DVSS and Workday systems.
      • Address divisional accounting inquiries and resolve disputes directly with guests or through internal channels.
    • Data Management & Accuracy
      • Maintain and update client database records, promptly identifying and reporting any discrepancies to ensure data integrity.
      • Conduct research related to unauthorized ski instruction.
    • Issue Resolution & Prioritization
      • Prioritize and manage multiple incoming issues, including sensitive or confidential matters, determining appropriate responses and actions.

    Qualifications

    • Must be at least 18 years of age.
    • Strong communication skills and a commitment to delivering exceptional guest service.
    • Flexible availability, including weekends - typically will be scheduled 4-5 days per week, 8-10 hours per day.
    • Proficient in computer use, including typing at a minimum of 35 WPM and working with Microsoft 365 applications.
    • Demonstrated ability to make sound decisions, solve problems, multitask effectively, and maintain attention to detail and follow-through.
    • Highly organized, self-motivated, and able to maintain a positive attitude and composure in high-pressure situations.

    Benefits

    • Ski perks (vary based on employment status) may include Deer Valley season pass, free skiing or riding at other Alterra Resorts and select local Utah resorts.
    • Friends and family ski discounts, free staff ski lessons and discounted rentals (winter staff only).
    • Subsidized meals at Employee Dining Rooms offered for staff while on shift.
    • Subsidized housing options available for seasonal full-time staff.
    • Discounts for staff members at restaurants, shops, and service providers in Park City.
    • Healthcare options are available for staff members.
    • 401k plan with company match.

    Pay

    $22.00 per hour.

    Schedule

    Seasonal employment from early November through mid-April. Typically scheduled 4-5 days per week, 8-10 hours per day, including weekends.

    That's it. No EEO. No job title heading. No Job ID. Check rules: "Do NOT repeat the job title as a heading (the page already shows it)" - good. "Do NOT put Job ID / requisition numbers as headings" - none. "Preserve ALL substantive information" - yes. "Remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions." - removed EEO. "include a section ONLY when the posting has real, specific content for it" - each section has content. "never emit a heading