Highlands/Buttermilk Shuttle Driver - Winter 26-27

We need to output HTML fragment with sections: About the role? Actually the posting includes a description of company, then Job Description, then Responsibilities, Qualifications, Additional Information (physical demands), Job Benefits, etc. We need to use

for section headings: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We must not repeat job title as heading. We need to include sections only when posting has real specific content. No Pay or Schedule unless present. The posting does not mention Pay or Schedule explicitly. So we should not include Pay or Schedule sections. Benefits: there is a "Job Benefits" section with some text: "This position is classified as a seasonal full-time position eligible for the following benefits: Enrollment dates differ across the various programs. Paid Time Off ProgramsPaid Leave ProgramsEmployee Ski PassOther company perks". That's vague but mentions benefits. It's real content (though generic). We can include Benefits section with that content. Also we have "Additional Information" about work environment and physical demands. That could go under Requirements? Or maybe "Qualifications" includes Education & Experience Requirements, Knowledge, Skills & Abilities. The "Additional Information" about physical demands could be part of Requirements or maybe a separate section like "Requirements". The instruction: Use headings for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). So we can map: About the role: maybe the introductory paragraph about company and role? The posting includes a paragraph: "With roots dating back to 1946..." That's company overview. Then "Job Description The Driver supports operations..." That's about the role. So we can put that in About the role. Responsibilities: list of duties from "Essential Job Functions/Key Job Responsibilities". Use

• . Requirements: maybe Education & Experience Requirements? But we also have Qualifications section includes Education & Experience Requirements, Knowledge, Skills & Abilities. The instruction says we can have Requirements and Qualifications separate. We could put Education & Experience Requirements under Requirements, and Knowledge, Skills & Abilities under Skills. Or combine. Let's follow typical: Requirements = Education & Experience Requirements. Skills = Knowledge, Skills & Abilities. Qualifications maybe not needed? But we have both Requirements and Qualifications as possible headings. The posting includes "Education & Experience Requirements" and "Knowledge, Skills & Abilities". So we can map Education & Experience Requirements to Requirements heading, and Knowledge, Skills & Abilities to Skills heading. Qualifications maybe not needed; we could omit Qualifications section if no distinct content. However we have "Qualifications" heading in the posting? Actually the posting says "Qualifications Education & Experience Requirements". It uses "Qualifications" as a heading then subheadings. So we could treat "Qualifications" as a section containing both Education & Experience Requirements and Knowledge, Skills & Abilities. But the instruction says we can use headings like Requirements, Qualifications, Skills. To avoid duplication, we could have Qualifications section with Education & Experience Requirements and Knowledge, Skills & Abilities inside. But then we would also have Requirements and Skills sections maybe redundant. Better to follow the posting: Use Qualifications as a section, with subparts Education & Experience Requirements and Knowledge, Skills & Abilities. However the instruction says use headings for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). It doesn't forbid using both Requirements and Qualifications; but we should not create thin sections. We have substantive content for both Education & Experience Requirements and Knowledge, Skills & Abilities. Could split into Requirements (Education & Experience) and Skills (Knowledge, Skills & Abilities). That seems reasonable. Then we don't need a separate Qualifications heading. But the instruction includes Qualifications as an example; we can omit if not needed. Let's decide: We'll include About the role, Responsibilities, Requirements (Education & Experience), Skills (Knowledge, Skills & Abilities), Benefits, and maybe Additional Information (physical demands) could be part of Requirements? Could be a separate section like "Requirements" includes physical demands? But physical demands are not exactly requirements; they are work environment. Could be part of "Requirements" or maybe a separate section like "Additional Information". Since we have no specific heading for that, we could incorporate into Requirements as a bullet list? But the instruction says use
  • for any list of duties/requirements/benefits. Physical demands are a list of requirements. So we could add them under Requirements as well. However we already have Education & Experience Requirements; we could combine all requirements under Requirements heading: education, experience, physical demands. Then Skills heading for knowledge, skills, abilities. That seems clean. Thus sections: - About the role: includes company overview and job description paragraph. - Responsibilities: list of essential job functions. - Requirements: includes Education & Experience Requirements (high school diploma required, college degree preferred; valid Colorado driver’s license) plus physical demands (ability to reach, crouch, kneel, stand, bend, be on feet; work in wet/cold/hot conditions; lift up to 50 lbs). Could also include any other requirements like maybe none. - Skills: Knowledge, Skills & Abilities list. - Benefits: the Job Benefits paragraph. We must not include Pay or Schedule. We must remove boilerplate: cookie/navigation/legal/EEO/equal-opportunity/scam-warning, duplicated lines, application instructions. Remove the "Job Posting Deadline" line? That's not boilerplate but maybe considered metadata; but instruction says do NOT put Job ID / requisition numbers as headings — fold minor metadata into a short

    or drop it. The deadline is minor metadata; we could fold into a short p or drop. Probably drop it as not essential? But it's substantive? It's a date; could be considered metadata. The instruction says fold minor metadata into a short

    or drop it. We could include a short p with the deadline. However they said "do NOT put Job ID / requisition numbers as headings — fold minor metadata into a short

    or drop it." The deadline is minor metadata, so we could include a short p. But we also have "Please note that all official communications..." that's boilerplate; remove. Also "For more information, visit..." that's maybe boilerplate; remove. Also "Aspen Snowmass encompasses 5,680 acres..." that's company info; could be part of About the role. Keep. We need to preserve all substantive information; not invent or summarize away detail. So we need to keep the company overview, job description, responsibilities list, qualifications, skills, benefits, physical demands. Let's extract text. Company overview paragraph: "With roots dating back to 1946, and a division of Aspen One, Aspen Skiing Company owns and operates four mountains—Aspen Mountain, Snowmass, Aspen Highlands, and Buttermilk. Aspen Skiing Company takes pride in the coexistence of resort, community, and the environment, which exemplifies its values of living fully, honoring people and place, taking the long view, and pursuing excellence in everything it does. Aspen Skiing Company is where guests from around the world come to renew the mind, body, and spirit through unforgettable experiences at the confluence of nature, culture, and recreation. Aspen Skiing Company also owns and operates the award-winning Aspen Snowmass Ski & Snowboard School, Four Mountain Sports rental and retail shops, and a collection of sustainably sourced on-mountain food and beverage outlets. Aspen Snowmass encompasses 5,680 acres of skiable terrain across four mountains, more than 40 ski lifts, and more than 410 trails. For more information, visit www.aspensnowmass.com or follow @aspensnowmass on Instagram, Facebook, and X." We may keep the "For more information..." as part of About the role? It's not essential but could be considered boilerplate? It's a link; maybe we can keep as it's part of company overview. The instruction says remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. This is not those. So keep. Job Description paragraph: "The Driver supports operations by providing safe, timely, and professional transportation services for guests, team members, and materials. Responsibilities include transporting guests to local destinations, completing scheduled pick-ups and drop-offs, assisting with luggage and deliveries, and maintaining the cleanliness and functionality of company vehicles. This role plays an important part in delivering a smooth and welcoming experience while also supporting internal logistical needs. The position reports directly to (insert hiring manager)." We keep that. Responsibilities list (Essential Job Functions/Key Job Responsibilities): - Transport guests to and from designated local locations as scheduled by the Concierge Desk - Coordinate transportation requests and updates with the Concierge and other relevant departments - Provide information about hotel amenities, local attractions, and events during transport when appropriate - Assist with loading and unloading luggage, following established procedures for tagging and tracking - Maintain a clean, safe, and presentable vehicle at all times; wash exterior and clean interior as needed - Complete routine vehicle inspections and maintenance checklists; monitor fluid levels and tire pressure - Report any mechanical issues, damage, or incidents promptly to the Guest Services Manager - Support hotel operations by transporting supplies, equipment, and interdepartmental packages as requested - Assist in coordinating and executing staff transportation needs for shifts, events, or off-site training - Work collaboratively with other departments to fulfill operational transport needs in a timely and efficient manner - Other duties as assigned for all roles We'll put each as

  • . Requirements: Education & Experience Requirements: - High school diploma required, college degree preferred - A valid Colorado driver’s license Physical demands (from Additional Information): - Ability to reach, crouch, kneel, stand, bend or be on your feet for extended periods of time - Regularly work in wet, cold, hot conditions requiring the use of protective apparel/equipment to prevent exposure to the elements and may be required to walk on slippery and uneven surfaces - Must be able to frequency lift, push or pull up to 50 lbs. individually or with assistance Note: "frequency" likely typo for "frequently". Keep as is. We'll combine these under Requirements. Skills (Knowledge, Skills & Abilities): - Knowledge of local area including roads, traffic patterns, airports, and key points of interest - Familiarity with vehicle maintenance procedures to perform basic safety checks and report issues promptly - Strong communication skills to interact professionally with guests, coworkers, and management - Excellent time management to follow schedules and respond to last-minute transportation needs efficiently - Ability to operate a variety of vehicles safely and responsibly, including vans and shuttles - Customer service orientation with a friendly, helpful attitude and a focus on creating a positive experience - Situational awareness and sound judgment for making safe decisions in changing traffic or weather conditions - Basic computer or mobile device skills for logging mileage, completing checklists, or using dispatch systems - Dependability and punctuality with a strong work ethic and attention to detail - Flexibility and teamwork with the ability to support other departments and adapt to shifting priorities Benefits: "This position is classified as a seasonal full-time position eligible for the following benefits: Enrollment dates differ across the various programs. Paid Time Off ProgramsPaid Leave ProgramsEmployee Ski PassOther company perks" Note there is missing spaces: "Paid Time Off ProgramsPaid Leave Programs". We'll keep as is. We should not include the boilerplate about reasonable accommodation, equal opportunity, etc. Remove. Also remove "Job Posting Deadline Applications for this position will be accepted until October 15th, 2026 for the 2026-2027 Winter Season." That's metadata; we could drop or fold into short p. I'd drop as not essential? It's substantive but maybe considered minor metadata. The instruction says fold minor metadata into a short

    or drop it. I'd drop it to keep sections focused