Experienced Ski Lift Mechanic
for section headings like About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We must not repeat job title as heading. We must include sections only when posting has real specific content. We need to extract content: The posting includes a lot of fluff at top: "Create Your Experience of a Lifetime! ..." That's basically about the role? It's a description. Could be "About the role" or maybe "Job Summary". We have a "Job Summary" heading later. We'll treat that as About the role? The instruction: Use for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). So we can choose appropriate headings based on content. We have:
- Intro paragraph: "Create Your Experience of a Lifetime! ..." This is about the company and role. Could be "About the role" or "Job Summary". There's also a "Job Summary" later: "We are seeking a skilled and motivated Experienced Ski Lift Mechanic..." That's definitely a summary. So we can have an About the role
with the intro paragraphs (maybe combine). Or we could have Job Summary
but that's not in the list; but we can still use About the role.
- Responsibilities: There's "Job Responsibilities" list and "Additional Responsibilities (Advanced-Level Candidates)". So we can combine into Responsibilities section.
- Requirements: There's "Job Requirements" list and "Preferred For Advanced-Level Applicants". Also "Technical training preferred..." etc. So we can have Requirements section.
- Qualifications: Might overlap with Requirements; but we could treat Requirements as qualifications. However we need to decide sections: maybe we have Responsibilities, Requirements, Benefits, Pay. Also maybe Skills? There's a list of skills in Preferred For Advanced-Level Applicants (welding, rope splicing, NDT, controls troubleshooting, familiarity with software). Could be Skills section.
- Benefits: There's a big list: "Job Benefits Ski/Mountain Perks! ..." plus 401(k), Employee Assistance Program, etc. Also health insurance for full-time roles. So we have Benefits.
- Pay: There's "Starting Wage: $23.00/hr - $30.91/hr" and later "The expected pay range is $23.00/hr - $30.91/hr." So we have Pay.
- Schedule: There's "Employment Type: Year Round", "Shift Type: Full Time hours available", also mention early mornings, weekends, holidays, nights, overtime shifts may be required. So we have Schedule.
We must not include sections with placeholder text. All these have real content.
We must not include boilerplate like EEO, etc. Remove those lines.
We must not include Job ID/requisition numbers as headings; we can fold minor metadata into a short
About the role
with the intro paragraphs (maybe combine). Or we could haveJob Summary
but that's not in the list; but we can still use About the role. - Responsibilities: There's "Job Responsibilities" list and "Additional Responsibilities (Advanced-Level Candidates)". So we can combine into Responsibilities section. - Requirements: There's "Job Requirements" list and "Preferred For Advanced-Level Applicants". Also "Technical training preferred..." etc. So we can have Requirements section. - Qualifications: Might overlap with Requirements; but we could treat Requirements as qualifications. However we need to decide sections: maybe we have Responsibilities, Requirements, Benefits, Pay. Also maybe Skills? There's a list of skills in Preferred For Advanced-Level Applicants (welding, rope splicing, NDT, controls troubleshooting, familiarity with software). Could be Skills section. - Benefits: There's a big list: "Job Benefits Ski/Mountain Perks! ..." plus 401(k), Employee Assistance Program, etc. Also health insurance for full-time roles. So we have Benefits. - Pay: There's "Starting Wage: $23.00/hr - $30.91/hr" and later "The expected pay range is $23.00/hr - $30.91/hr." So we have Pay. - Schedule: There's "Employment Type: Year Round", "Shift Type: Full Time hours available", also mention early mornings, weekends, holidays, nights, overtime shifts may be required. So we have Schedule. We must not include sections with placeholder text. All these have real content. We must not include boilerplate like EEO, etc. Remove those lines. We must not include Job ID/requisition numbers as headings; we can fold minor metadata into a shortor drop it. So we can maybe include a
for Requisition ID etc at bottom? 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 at end with that info, but not as heading. However we might drop it entirely as it's minor. Safer to drop it. We must preserve ALL substantive information; do not invent or summarize away detail. So we need to keep all details from the posting, but we can reformat into HTML. We need to ensure we don't miss any details: The intro fluff includes many details: "With 40+ resorts across 3 continents, you can join our team for a season or stay to build a career. From day one, you'll receive some of the highest compensation rates in the industry, free Epic pass(es) along with free ski and snowboard lessons, 40% retail discounts, the chance to grow through Epic Service - our leading training and development experience, and wellness benefits to fuel your success. Candidates for year-round positions are reviewed on a rolling basis. Applications will be accepted up to 90 days after the posting date, or until the position is filled (whichever is first)." This is substantive; we should keep it. It could go under About the role. Then there is a "Job Benefits Ski/Mountain Perks!" list: "Free passes for employees, employee discounted lift tickets for friends and family AND free ski lessons MORE employee discounts on lodging, food, gear, and mountain shuttles 401(k) Retirement Plan Employee Assistance Program Excellent training and professional development Referral Program Full Time Roles Are Eligible For The Above, Plus Health Insurance; Medical Insurance, Dental Insurance, and Vision Insurance plans (for eligible seasonal employees after working 500 hours) Free ski passes for dependents Critical Illness and Accident plans". We need to preserve that as benefits. We also have "Job Summary" paragraph: "We are seeking a skilled and motivated Experienced Ski Lift Mechanic to join our Lift Maintenance team. The successful candidate will be hired into an Intermediate or Advanced role based on experience, technical proficiency, and leadership ability. This position plays a key role in ensuring the safe, reliable, and efficient operation of all aerial and surface lift systems across the resort." We have "Job Specifications": Starting Wage, Employment Type, Shift Type, Minimum Age, Housing Availability, Working Conditions. We have "Job Responsibilities" bullet list. We have "Additional Responsibilities (Advanced-Level Candidates)" bullet list. We have "Job Requirements" bullet list. We have "Preferred For Advanced-Level Applicants" bullet list. We have "The expected pay range is $23.00/hr - $30.91/hr." (duplicate of starting wage). We have legal statements about redaction, child labor, EEO, etc. We must remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate. So we should remove the EEO paragraph and the redaction statement, child labor statement, Vail Resorts is an equal opportunity employer, etc. Also remove "Reference Date: 04/09/2026 Job Code Function: Lift Maintenance" maybe minor metadata; we can drop or put in a short p. We must not include application instructions: "Applications will be accepted up to 90 days after the posting date, or until the position is filled (whichever is first)." That's not exactly application instructions but it's about acceptance period; it's substantive? It's about application timeline. Might be considered part of posting; but it's not a boilerplate. However it's about application process; but the instruction says remove application instructions. This line is about application acceptance period; could be considered application instruction. Safer to remove it? The instruction: "Remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions." So we should remove that line. Also "Candidates for year-round positions are reviewed on a rolling basis." That's also about application process; maybe remove as well. But it's also substantive about hiring process. However it's likely considered application instruction. I'd remove both to be safe. We must keep all other substantive info. Now we need to output only HTML fragment, no /, no markdown fences. We'll structure:
About the role
Intro paragraph(s) ...