Command Center & Loss Prevention Supervisor - Winter 26-27

We need to output HTML fragment with sections: About the role? Actually the posting includes a description paragraph before "Job Description". We need to reformat into clean semantic HTML using

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: - Company description (intro) about Aspen Skiing Company. Could be "About the role"? Actually "About the role" is typical heading for role description. But we have a paragraph describing the company and then "Job Description". The role description is after "Job Description". So we could have an "About the role" section containing the job description paragraph (the first paragraph after "Job Description"). - Then "Essential Job Functions / Key Job Responsibilities" list: we can put under a heading "Responsibilities". Use

  • . - Then "Qualifications" section includes "Education & Experience Requirements" and "Knowledge, Skills & Abilities". Could combine into "Qualifications" and "Skills"? The instructions list possible headings: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We need to decide which to use. We have Education & Experience Requirements (qualifications). Then Knowledge, Skills & Abilities (skills). Could separate into Qualifications and Skills sections. We also have "Additional Information" includes Work Environment & Physical Demands, benefits info (Paid Time Off Programs, Paid Leave Programs, Employee Ski Pass and Dependent Ski Passes, Other company perks). Also mentions "This position is classified as a seasonal full-time position eligible for the following benefits:" then list. So we have benefits info. Also schedule? Not explicitly given; it's seasonal full-time but no schedule details. We should not create Schedule section unless posting actually states them. It says "seasonal full-time position". That's a schedule type but not specific hours. Might be considered schedule info? The instruction: never create Pay/Schedule/Benefits sections unless the posting actually states them. It does state benefits (list). So we can include Benefits section. Pay: they gave salary range: $60,416 - $70,416. That's pay info. So we should include Pay section. Schedule: they mention seasonal full-time but not specific schedule; maybe we could include Schedule section with that info? The posting says "This position is classified as a seasonal full-time position". That's schedule info. It's specific enough? It states the position classification. I'd consider that schedule info. However the instruction says never create Schedule section unless posting actually states them. It does state it's seasonal full-time. So we could include Schedule section with that sentence. But we need to avoid filler like "commensurate with experience". The pay range is specific. Good. We also have "Applications for this position will be considered on a rolling basis." That's application instruction; we should remove. We have "Essential Job Functions / Key Job Responsibilities" list; we will put under Responsibilities. We have "Qualifications" heading originally; we can split into Qualifications (Education & Experience Requirements) and Skills (Knowledge, Skills & Abilities). Or we could combine into Qualifications and Skills sections as per allowed headings. We also have "Additional Information" includes Work Environment & Physical Demands; maybe we could put under a heading like "Working Conditions" but not in allowed list. Since not in allowed list, we might omit or incorporate into Responsibilities? Probably better to omit as not required heading. But we need to preserve ALL substantive information; we cannot drop substantive info. However we can incorporate into a

    under maybe "Responsibilities" or a generic section? The instruction says use headings only from the list; but we can still have

    paragraphs without headings? It says "Use

    for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." It doesn't forbid other headings, but says to use those for section headings. Likely we should stick to those headings only. However we need to preserve all substantive info; we could put the work environment info under a

    after the Skills section without a heading, or under a heading like "Requirements"? Not appropriate. Maybe we can incorporate into "Qualifications" as part of requirements? It's not qualification but work environment. Could be under "Requirements"? Not ideal. Alternatively, we could create a section "Requirements" for work environment? But the heading "Requirements" is allowed. Could place physical demands there. However "Requirements" usually refers to job requirements like education/experience. But we already have Qualifications and Skills. Could shift: Qualifications for education/experience, Skills for knowledge/skills, Requirements for physical demands/work environment. That seems plausible. Thus we can have sections: - About the role (intro paragraph describing role) - Responsibilities (list of essential job functions) - Qualifications (education & experience requirements) - Skills (knowledge, skills & abilities) - Requirements (work environment & physical demands) - Benefits (list of benefits) - Pay (salary range) - Schedule (seasonal full-time) We need to ensure we don't create empty sections. All have content. Now we need to strip boilerplate: remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. We need to remove lines like "For more information about Aspen Snowmass, visit www.aspensnowmass.com." That's not boilerplate? It's informational but maybe not essential? It's about company; could be considered part of About the role? Might be okay to keep as part of intro? But it's not directly about the role. The instruction: Preserve ALL substantive information; do NOT invent or summarize away detail. That line is substantive info about company. Could keep. But we also need to remove duplicated lines. There's some duplication: "Ability to be on your feet, kneel and bend for extended periods of time" appears in Work Environment & Physical Demands. Also later "The physical demands described here are representative..." That's boilerplate legal. We'll remove that. Also remove "By accepting a position with Aspen One, Aspen Snowmass, Aspen Ventures or Aspen Hospitality you acknowledge that you are able to perform the essential functions of the job with or without reasonable accommodation." etc. That's legal boilerplate; remove. Also remove "Reasonable accommodations may be made..." etc. Also remove "This job description is designed to indicate the general nature and level of work..." etc. Also remove "Aspen One is an equal opportunity employer..." etc. Also remove "Aspen One participates in E-Verify. E-Verify & Right to Work Poster". Also remove "#ASPENHP2627" maybe it's a tag; could be considered metadata; we can drop. Also remove "Applications for this position will be considered on a rolling basis." (application instruction). Also remove "Enrollment dates differ across the various programs." maybe part of benefits but it's vague; we can keep as part of benefits? It's not specific benefit; maybe we can keep as part of benefits paragraph. Now let's extract substantive content. Intro paragraph before "Job Description": "Established in 1946, Aspen Skiing Company, also known as Aspen Snowmass, owns and operates four mountains—Snowmass, Aspen Mountain, Aspen Highlands and Buttermilk—creating premium, sustainable and transformative experiences in recreation, culture, and nature. In addition, the company runs the award-winning Aspen Snowmass Ski & Snowboard School, Four Mountain Sports rental and retail shops, and a collection of sustainably-sourced on-mountain food & beverage outlets. Aspen Skiing Company also owns Aspen Hospitality, which is comprised of The Little Nell and Limelight Hotel brands and ASPENX, a contemporary retail and experience brand. Across all divisions, Aspen Skiing Company works to drive positive social change through climate, community, and minority group advocacy and investment. For more information about Aspen Snowmass, visit www.aspensnowmass.com." That's company overview. Could be placed under About the role? Actually About the role should describe the role, not company. But we could include a brief company overview as 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. The company overview is not role-specific but could be considered part of About the role? Might be okay to include as a paragraph under About the role before describing the role. However we also have a specific job description paragraph after "Job Description". That is the role description. So we could have About the role containing both company overview and role description? Might be redundant but okay. Alternatively, we could treat the company overview as a separate section not in allowed headings; but we must stick to allowed headings. Could we omit it? That would lose substantive info (company overview). The instruction says preserve ALL substantive information. So we need to keep it somewhere. We could put it under About the role as a preamble. Thus About the role section will contain the company overview paragraph plus the role description paragraph (the one after "Job Description"). Now role description paragraph: "The Command Center & Loss Prevention Supervisor partners with the Mountain Sales & Schools management team to safeguard revenue and system integrity across Mountain Sales operations. This role monitors real-time gate scan activity, investigates irregular scan behavior and potential pass fraud, and coordinates with Lift Operations, IT, and frontline teams to resolve access issues. The Supervisor supports and coaches’ staff while serving as the central point of contact for incident intake, escalation, and reporting. This position reports to the Mountain Sales Director of Operations with dual reporting to the Senior Manager of Sales & Reservations. The budgeted salary range for this position is $60,416 - $70,416 . Actual pay will be dependent on budget and experience, all our salaried roles are eligible for bonus." Note: salary range is mentioned here; we will also have Pay section later; we should not duplicate. Better to keep salary info only in Pay section, not in About the role. So we should remove salary sentence from the role description paragraph when moving to About the role. But we need to preserve all substantive info; we will move it to Pay section. So we will omit that sentence from About the role. Thus About the role paragraph: company overview + role description without salary sentence. Now Responsibilities: list from "Essential Job Functions / Key Job Responsibilities". We'll extract each bullet. List items: - Provide supervision and support to agents within the Mountain Sales & Schools team to ensure consistent delivery of exceptional guest service and achievement of goals - Model and uphold exemplary customer service standards to foster a guest-focused and sales-driven team culture - Manage employee workflow and create effective team schedules that optimize guest service coverage and sales opportunities - Develop and maintain reporting processes, dashboards, and documentation to support operational visibility and risk mitigation - Gain working knowledge of all Mountain Sales systems including access gates, self-service kiosks,