Winter Trails Manager - Aspen Mountain - Winter 26-27

We need to produce HTML fragment with sections: About the role? The posting includes description paragraphs about company, but we need to follow rules: Use

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

• for any list of duties/requirements/benefits, and

  for prose. Do NOT repeat the job title as a heading. Do NOT put Job ID / requisition numbers as headings — fold minor metadata into a short

  or drop it. Preserve ALL substantive information; do NOT invent or summarize away detail. Remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. IMPORTANT: include a section ONLY when the posting has real, specific content for it — never emit a heading followed by filler/placeholder text (e.g. "commensurate with experience", "not specified", "N/A", "varies", "TBD") and never create Pay/Schedule/Benefits sections unless the posting actually states them. Prefer a few substantive sections over many thin ones. Output ONLY the HTML fragment — no /, no markdown code fences. We need to decide which sections to include based on content. We have: - Intro about company (maybe "About the role"? Actually "About the role" could be description of role. The intro about company could be considered "About the role"? Might be better to have "About the role" as a paragraph summarizing role description. The posting includes "Job Description The Trails Manager is responsible for the year-round oversight of all Summer and/or Winter Trails operations, ensuring safe, efficient, and high-quality grooming and trail preparation. This position leads budgeting, scheduling, and performance management for trail crews while supporting capital planning and environmental stewardship. This role directly reports to the Mountain Manager." That's role description. Then "The salary range for this position is $70,000 - $85,000. Actual pay will be dependent on budget and experience; all our salaried roles are eligible for bonus." That's Pay. Then "Job Posting Deadline: Applications for this position will be accepted until September 15th, 2026." That's maybe metadata but we can drop or put in short p. Then "Essential Job Function" list: many bullet-like sentences. Those are responsibilities/duties. So we can have a Responsibilities section with

  • each bullet. Then "Qualifications Education and Experience Requirements" list: bullet-like items. That's Requirements/Qualifications. Then "Knowledge, Skills, And Abilities" list: bullet-like items. That's Skills. Then "Additional Information Work Environment & Physical Demands": bullet-like items. Could be part of Requirements or separate? Might be considered "Work Environment" but not in allowed headings list. We could incorporate into Qualifications or Requirements? The allowed headings list includes About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. So we need to map content to those. We have Benefits: "Job 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 Programs Paid Leave Programs Employee Ski Pass and Dependent Ski Passes Other company perks". That's benefits. We have Pay: salary range. We have Schedule? Not explicitly given; maybe "seasonal full-time position". Could infer schedule but not explicit; we should not create Schedule section unless posting actually states them. It does not give schedule details like hours, shift. So we omit Schedule. We have About the role: could be the introductory paragraph about role and company? The intro about company may be considered "About the role"? Might be better to have About the role as a paragraph describing the role and its context. We'll include that. We need to avoid boilerplate: remove EEO, legal, etc. Also remove duplicated lines, navigation, cookie, etc. Also remove "Please note that all official communications..." etc. Also remove "Job Posting Deadline:" maybe we can keep as short p? It's minor metadata; we can fold into a short p or drop. The 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 p for Job Posting Deadline maybe. But we should avoid creating extra sections for it. We'll just include a

    maybe after About the role? Or we could incorporate into About the role? Better to keep as a short p separate but not a heading. We must not repeat the job title as heading. The job title is "Trails Manager". We won't use that as heading. We need to preserve all substantive information. So we need to include all bullet points from Essential Job Function, Qualifications, Knowledge Skills Abilities, Work Environment & Physical Demands, Benefits, Pay. We must not invent or summarize away detail. So we need to keep each bullet exactly as given (or close). We must not add extra info. We need to format as HTML fragment: use

    for section headings. Use

    • for any list of duties/requirements/benefits, and

      for prose. Thus: -

      About the role

      then

      containing the role description paragraph(s). Possibly also include company overview? The company overview is not about the role but could be considered part of About the role? The instruction: "use

      for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)". So About the role likely expects a description of the role and maybe the company. We'll include the company overview plus the role description? Might be too much but okay. Better: About the role: include the paragraph that starts "With roots dating back to 1946..." that's company overview. Then also the Job Description paragraph. Could combine into one

      or two

      s. Since we need to preserve all substantive information, we can include both as separate

      under About the role? But the rule says use

      for prose. So we can have multiple

      under the heading. Thus:

      About the role

      With roots dating back to 1946, Aspen Skiing Company, a division of Aspen One, owns and operates four mountains—Aspen Mountain, Snowmass, Aspen Highlands, and Buttermilk. Inspired by place, united by purpose, defined by you, 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 and Facebook.

      The Trails Manager is responsible for the year-round oversight of all Summer and/or Winter Trails operations, ensuring safe, efficient, and high-quality grooming and trail preparation. This position leads budgeting, scheduling, and performance management for trail crews while supporting capital planning and environmental stewardship. This role directly reports to the Mountain Manager.

      Then we might include a short p for Job Posting Deadline: maybe after About the role? But we could drop it. The instruction says we can fold minor metadata into a short

      or drop it. I'd include a short p:

      Job Posting Deadline: Applications for this position will be accepted until September 15th, 2026.

      Then Responsibilities:

      Responsibilities

      then
      with each Essential Job Function bullet. List them exactly: - Lead, schedule, train, and develop trail crew teams for both summer and winter operations - Prepare and manage department budgets, tracking labor and expenses throughout the season - Ensure compliance with safety standards, documenting and addressing any issues - Coordinate timely equipment repairs with Vehicle Maintenance staff - Oversee trail grooming and maintenance for special events and seasonal conditions - Manage hiring, performance reviews, disciplinary actions, and scheduling - Recommend capital purchases and contribute to long-term equipment planning - Oversee summer trail maintenance projects and erosion control efforts - Utilize Snowcat GPS data to optimize grooming efficiency and reduce idle time - Maintain compliance with National Forest Service and Storm Water Management Plan requirements - Collaborate cross-departmentally to maintain a positive and productive work environment - Other duties as assigned Make sure each is
      • . Then Requirements: maybe combine Education and Experience Requirements and Knowledge, Skills, And Abilities? But we have separate headings: Requirements, Qualifications, Skills. The instruction list includes Requirements, Qualifications, Skills. So we need to map. We have "Education and Experience Requirements" bullet list: that could go under Requirements. We have "Knowledge, Skills, And Abilities" bullet list: that could go under Skills. We also have "Qualifications" heading maybe for something else? The posting has "Qualifications Education and Experience Requirements" and "Knowledge, Skills, And Abilities". There's no separate "Qualifications" besides those. So we could treat "Qualifications" as a heading that includes both Education/Experience and Knowledge/Skills? But we already have Requirements and Skills headings. The instruction list includes Qualifications as a possible heading. We could decide to not use Qualifications if we already covered via Requirements and Skills. But we need to include all substantive information; we can put Education/Experience under Requirements, Knowledge/Skills under Skills, and maybe omit Qualifications heading (since no distinct content). That's acceptable: include a section only when posting has real, specific content for it. Since there is no separate "Qualifications" beyond those, we can omit Qualifications heading. Thus:

        Requirements

        • Valid, current unrestricted Driver’s License required
        • High school diploma or equivalent preferred
        • Must pass DMV check

        Skills

        • Knowledge of snow grooming operations, trail maintenance, and environmental best practices
        • Strong leadership and team management skills across seasonal teams
        • Ability to obtain ASC snowmobile license
        • Ability to manage budgets, track expenses, and prepare accurate reports
        • Skilled in coordinating equipment maintenance and understanding mechanical needs
        • Familiarity with snowcat GPS systems and operational data interpretation
        • Strong communication and interpersonal skills across departments and with direct reports
        • Ability to conduct performance management, including training and corrective action
        • Proficient in Microsoft Office and scheduling software
        • Comfortable working in varied mountain conditions and with ski/snowboard terrain
        • Committed to safety, environmental compliance, and guest experience excellence
        Then Benefits:

        Benefits

        then
        with benefits list. Benefits 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 Programs Paid Leave Programs Employee Ski Pass and Dependent Ski Passes Other company perks" We need to break into list items. The sentences: "Enrollment dates differ across the various programs." could be a note. "Paid Time Off Programs" "Paid Leave Programs"