Winter Lift Operations Lead
2. Essential Responsibilities - this has multiple subsections with lists 3. LEADERSHIP EXPECTATIONS - prose 4. Qualifications - list of requirements 5. Additional Duties And Operational Support - prose The rules say: - Use
for section headings (About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)
- Use - for lists
- Use
for prose
- Don't repeat job title as heading
- Don't put Job ID/requisition numbers as headings
- Preserve ALL substantive information
- Remove boilerplate (cookie/navigation/legal/EEO/scam-warning, duplicated lines, application instructions)
- Only include sections when there's real content
- No filler/placeholder text
- Output ONLY HTML fragment
Looking at the content:
- "Position Summary" - this is like "About the role"
- "Essential Responsibilities" with subsections: Zone & Operational Oversight, Crew Leadership & Accountability, Training & Employee Development, Lift & Emergency Operations, Mountain & Employee Support, Interdepartmental Coordination
- "LEADERSHIP EXPECTATIONS" - this could be part of responsibilities or separate
- "Qualifications" - list
- "Additional Duties And Operational Support" - prose
- "Job Posted by ApplicantPro" - this is boilerplate, should remove
I need to map the headings to the standard ones mentioned: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule.
The posting has:
- Position Summary → About the role
- Essential Responsibilities → Responsibilities
- LEADERSHIP EXPECTATIONS → could be part of Responsibilities or separate
- Qualifications → Qualifications (or Requirements)
- Additional Duties → could be part of Responsibilities
The rules say: "use
for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)". So I should use these standard headings where appropriate.
Let me structure:
About the role
Position Summary content...
Responsibilities
Then for each subsection under Essential Responsibilities, I could either make them sub-headings (but rules only mention h3 for main sections) or include as part of the list. The rules say "use - for any list of duties/requirements/benefits". The responsibilities are listed as bullet points under each subsection. I think I should create a list for each major responsibility area, or combine into one big list? The content has distinct categories with multiple bullet points each.
I could do:
Responsibilities
Zone & Operational Oversight
- but rules only mention h3 for section headings. It says "use for section headings". It doesn't forbid h4, but says "use for section headings (e.g. About the role, Responsibilities...)". Might be safer to keep only h3 for main sections and use lists for sub-items.
Alternatively, I could make each responsibility area a separate list with a heading in the list item? But that's not semantic.
Better: Use for main sections only. For subsections, perhaps use or just include as part of list items. But the content is structured with clear subsections.
Let me re-read: "use for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)". This suggests only those top-level sections get h3. Subsections should not get h3. So I'll use for the main sections, and within Responsibilities, I'll create lists for each area, perhaps with a leading bold text.
But the rules also say: "Preserve ALL substantive information; do NOT invent or summarize away detail." So I must keep all the bullet points.
I'll structure as:
About the role
...
Responsibilities
- Zone & Operational Oversight: Maintain Lift Operations AORs...
... but each bullet point is separate. Actually each subsection has multiple bullet points. I could make a list for each subsection, but that would be multiple under one . That's fine.
I'll do:
Responsibilities
Zone & Operational Oversight
- but no h4 allowed? The rules don't explicitly forbid h4, but they say "use for section headings". Might be okay to use h4 for subsections. However, to be safe, I'll use or just include the category in the list items.
Better: Use a definition list? But rules say - for lists.
I'll create separate
for each responsibility area, preceded by a Zone & Operational Oversight
or something. But that's not a heading.
Alternatively, I can make each responsibility area a list item with a nested list. Like:
- Zone & Operational Oversight
- Maintain Lift Operations AORs...
...
...
That preserves hierarchy and uses only ul/li. That seems good.
Similarly for Qualifications: it's a list of bullet points.
LEADERSHIP EXPECTATIONS: prose paragraphs.
Additional Duties: prose.
Now, the "Job Posted by ApplicantPro" is boilerplate, remove.
Also, there's no Pay, Schedule, Benefits sections mentioned, so don't create them.
Now, let's write the HTML.
First, About the role:
About the role
The Winter Lift Operations Lead is an on-mountain leadership position responsible for overseeing a rotating zone of lift operations. Leads support multiple lifts and crews within their assigned zone, ensuring employees, operational areas, and procedures consistently meet department and resort expectations. This position requires a high level of independence, initiative, and trust. Leads are expected to recognize operational needs, solve problems, develop employees, maintain their Area of Responsibility (AOR), and provide consistent leadership without requiring continuous direction from a Supervisor.
Responsibilities:
Responsibilities
- Zone & Operational Oversight
- Maintain Lift Operations AORs throughout the assigned zone, including lift stations, ramps, mazes, gantries, fencing, signage, barriers, shacks, and snow surfaces.
- Regularly inspect lifts and operational areas and independently identify and address needs.
- Maintain awareness of lift operations, conditions, documentation, and crew performance throughout the zone.
- Review lift logs and ensure required operational documentation is accurate and complete.
- Adjust staffing and rotations based on operational needs.
- Maintain station inventories, tools, supplies, and equipment.
- Crew Leadership & Accountability
- Maintain an active and professional leadership presence throughout the zone.
- Ensure employees consistently meet department expectations for safety, uniforms, punctuality, guest service, conduct, breaks, rotations, and job performance.
- Provide timely coaching, direction, corrective feedback, and verbal warnings when appropriate.
- Communicate performance concerns requiring further corrective action to Supervisors and management.
- Enforce department policies consistently and fairly.
- Promote a professional, respectful, and productive team environment.
- Training & Employee Development
- Provide hands-on training in lift operations, emergency procedures, opening and closing procedures, guest service, ramp maintenance, and department standards.
- Identify training needs and create opportunities for continued employee development.
- Assist with training documentation and logs.
- Maintain strong knowledge of resort operations and commonly asked guest questions.
- Lift & Emergency Operations
- Develop a strong working knowledge of lifts throughout the mountain, including normal operation, emergency procedures, and common operational concerns.
- Maintain proficiency in Lift Operations emergency procedures.
- Recognize and promptly communicate mechanical or operational concerns to Lift Maintenance and Supervisors.
- Coordinate with Lift Maintenance and assist with approved lift-related tasks when properly trained.
- Mountain & Employee Support
- Provide lift coverage and facilitate employee free runs when operational priorities allow.
- Ensure employees follow clock-out and department free-skiing procedures.
- Respond to guest and employee concerns escalated beyond the Level 2 operator.
- Support setup, tear-down, special projects, events, and changing mountain needs.
- Interdepartmental Coordination
- Work effectively with Lift Maintenance, Ski Patrol, Ski School, Arrowhead Ski Team, Ticket Office, Mountain Operations, and other resort departments.
- Assist with shared operational needs and identify opportunities to improve communication and efficiency.
- Represent Lift Operations professionally with guests, employees, resort leadership, and other departments.
Leadership Expectations: This is prose, could be a separate section or part of Responsibilities. The rules mention "Qualifications, Skills" as possible headings. Leadership Expectations could be under "Qualifications" or separate. Since it's about expectations of the lead, maybe include as a subsection under Responsibilities or as a separate Leadership Expectations
. But the rules say only use those example headings. However, they say "e.g." so not exhaustive. But they also say "include a section ONLY when the posting has real, specific content for it". Leadership Expectations has content. I'll include it as a separate section with Leadership Expectations
and prose.
But the example headings are "About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule". Leadership Expectations isn't listed. Could map to "Requirements" or "Qualifications". But it's more about behavioral expectations. I'll create a section Leadership Expectations
as it's a distinct section in the posting.
Qualifications: list.
Qualifications
- Minimum two years of demonstrated leadership experience.
- Advanced ski/snowboarding ability.
- Ability to work independently and recognize operational priorities.
- Ability to coach employees, provide direct feedback, and hold others accountable professionally and fairly.
- Strong understanding of lift operations or ability to quickly develop operational proficiency.
- Experienced skier or snowboarder capable of confidently navigating required mountain terrain while transporting work materials.
- Snowmobile experience and ability to complete Sundance snowmobile training.
- Proficiency with two-way
for prose - Don't repeat job title as heading - Don't put Job ID/requisition numbers as headings - Preserve ALL substantive information - Remove boilerplate (cookie/navigation/legal/EEO/scam-warning, duplicated lines, application instructions) - Only include sections when there's real content - No filler/placeholder text - Output ONLY HTML fragment Looking at the content: - "Position Summary" - this is like "About the role" - "Essential Responsibilities" with subsections: Zone & Operational Oversight, Crew Leadership & Accountability, Training & Employee Development, Lift & Emergency Operations, Mountain & Employee Support, Interdepartmental Coordination - "LEADERSHIP EXPECTATIONS" - this could be part of responsibilities or separate - "Qualifications" - list - "Additional Duties And Operational Support" - prose - "Job Posted by ApplicantPro" - this is boilerplate, should remove I need to map the headings to the standard ones mentioned: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. The posting has: - Position Summary → About the role - Essential Responsibilities → Responsibilities - LEADERSHIP EXPECTATIONS → could be part of Responsibilities or separate - Qualifications → Qualifications (or Requirements) - Additional Duties → could be part of Responsibilities The rules say: "use
for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)". So I should use these standard headings where appropriate.
Let me structure:
About the role
Position Summary content...
Responsibilities
Then for each subsection under Essential Responsibilities, I could either make them sub-headings (but rules only mention h3 for main sections) or include as part of the list. The rules say "use- for any list of duties/requirements/benefits". The responsibilities are listed as bullet points under each subsection. I think I should create a list for each major responsibility area, or combine into one big list? The content has distinct categories with multiple bullet points each.
I could do:
Responsibilities
Zone & Operational Oversight
- but rules only mention h3 for section headings. It says "usefor section headings". It doesn't forbid h4, but says "use
for section headings (e.g. About the role, Responsibilities...)". Might be safer to keep only h3 for main sections and use lists for sub-items. Alternatively, I could make each responsibility area a separate list with a heading in the list item? But that's not semantic. Better: Use
for main sections only. For subsections, perhaps use or just include as part of list items. But the content is structured with clear subsections. Let me re-read: "use
for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)". This suggests only those top-level sections get h3. Subsections should not get h3. So I'll use
for the main sections, and within Responsibilities, I'll create lists for each area, perhaps with a leading bold text. But the rules also say: "Preserve ALL substantive information; do NOT invent or summarize away detail." So I must keep all the bullet points. I'll structure as:
About the role
...
Responsibilities
- Zone & Operational Oversight: Maintain Lift Operations AORs... ... but each bullet point is separate. Actually each subsection has multiple bullet points. I could make a list for each subsection, but that would be multiple
- for lists.
I'll create separate
- for each responsibility area, preceded by a
- Zone & Operational Oversight
- Maintain Lift Operations AORs... ...
...
- Zone & Operational Oversight
- Maintain Lift Operations AORs throughout the assigned zone, including lift stations, ramps, mazes, gantries, fencing, signage, barriers, shacks, and snow surfaces.
- Regularly inspect lifts and operational areas and independently identify and address needs.
- Maintain awareness of lift operations, conditions, documentation, and crew performance throughout the zone.
- Review lift logs and ensure required operational documentation is accurate and complete.
- Adjust staffing and rotations based on operational needs.
- Maintain station inventories, tools, supplies, and equipment.
- Crew Leadership & Accountability
- Maintain an active and professional leadership presence throughout the zone.
- Ensure employees consistently meet department expectations for safety, uniforms, punctuality, guest service, conduct, breaks, rotations, and job performance.
- Provide timely coaching, direction, corrective feedback, and verbal warnings when appropriate.
- Communicate performance concerns requiring further corrective action to Supervisors and management.
- Enforce department policies consistently and fairly.
- Promote a professional, respectful, and productive team environment.
- Training & Employee Development
- Provide hands-on training in lift operations, emergency procedures, opening and closing procedures, guest service, ramp maintenance, and department standards.
- Identify training needs and create opportunities for continued employee development.
- Assist with training documentation and logs.
- Maintain strong knowledge of resort operations and commonly asked guest questions.
- Lift & Emergency Operations
- Develop a strong working knowledge of lifts throughout the mountain, including normal operation, emergency procedures, and common operational concerns.
- Maintain proficiency in Lift Operations emergency procedures.
- Recognize and promptly communicate mechanical or operational concerns to Lift Maintenance and Supervisors.
- Coordinate with Lift Maintenance and assist with approved lift-related tasks when properly trained.
- Mountain & Employee Support
- Provide lift coverage and facilitate employee free runs when operational priorities allow.
- Ensure employees follow clock-out and department free-skiing procedures.
- Respond to guest and employee concerns escalated beyond the Level 2 operator.
- Support setup, tear-down, special projects, events, and changing mountain needs.
- Interdepartmental Coordination
- Work effectively with Lift Maintenance, Ski Patrol, Ski School, Arrowhead Ski Team, Ticket Office, Mountain Operations, and other resort departments.
- Assist with shared operational needs and identify opportunities to improve communication and efficiency.
- Represent Lift Operations professionally with guests, employees, resort leadership, and other departments.
- Minimum two years of demonstrated leadership experience.
- Advanced ski/snowboarding ability.
- Ability to work independently and recognize operational priorities.
- Ability to coach employees, provide direct feedback, and hold others accountable professionally and fairly.
- Strong understanding of lift operations or ability to quickly develop operational proficiency.
- Experienced skier or snowboarder capable of confidently navigating required mountain terrain while transporting work materials.
- Snowmobile experience and ability to complete Sundance snowmobile training.
- Proficiency with two-way
Zone & Operational Oversight
or something. But that's not a heading. Alternatively, I can make each responsibility area a list item with a nested list. Like:About the role
The Winter Lift Operations Lead is an on-mountain leadership position responsible for overseeing a rotating zone of lift operations. Leads support multiple lifts and crews within their assigned zone, ensuring employees, operational areas, and procedures consistently meet department and resort expectations. This position requires a high level of independence, initiative, and trust. Leads are expected to recognize operational needs, solve problems, develop employees, maintain their Area of Responsibility (AOR), and provide consistent leadership without requiring continuous direction from a Supervisor.
Responsibilities:Responsibilities
Leadership Expectations
. But the rules say only use those example headings. However, they say "e.g." so not exhaustive. But they also say "include a section ONLY when the posting has real, specific content for it". Leadership Expectations has content. I'll include it as a separate section withLeadership Expectations
and prose. But the example headings are "About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule". Leadership Expectations isn't listed. Could map to "Requirements" or "Qualifications". But it's more about behavioral expectations. I'll create a sectionLeadership Expectations
as it's a distinct section in the posting. Qualifications: list.Qualifications
- Zone & Operational Oversight
- under one
. That's fine. I'll do:
Responsibilities
Zone & Operational Oversight
- but no h4 allowed? The rules don't explicitly forbid h4, but they say "usefor section headings". Might be okay to use h4 for subsections. However, to be safe, I'll use or just include the category in the list items. Better: Use a definition list? But rules say