Events & Partnerships Coordinator

We need to output HTML fragment with sections: headings

for sections like About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. Only include sections where there is real content. We need to parse the posting. First, remove boilerplate: cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, application instructions. Also remove "Year Round WORK AND PLAY IN THE MOUNTAINS" maybe not needed? It's part of description but not a heading. Keep substantive info. We need sections: maybe "About the role" (job summary), "Responsibilities", "Requirements" (maybe Ideal Candidate Profile), "Qualifications" (maybe not separate), "Skills", "Benefits", "Pay", "Schedule". We need to see what content exists. Let's extract: - Job Title: Events & Partnerships Coordinator (but we don't repeat as heading) - Business Unit: Sales - Position Reports to: Events & Partnership Manager - Position Type: Full-Time Year Round - Reporting to this Role: None - Wage Range: $23-$25/ hour - Location: Crystal Mountain, WA Then "Resort Overview, Culture And Vision" paragraph. Then "Job Summary" paragraph. Then "Ideal Candidate Profile" bullet list (Detail-Oriented etc). That's requirements/qualifications/skills. Then "Primary Responsibilities" with subheadings: Event Planning & Execution, Grow, Partnership Coordination. That's responsibilities. Then "Performance Criteria" list (maybe part of requirements? but could be responsibilities? It's more like expectations.) Then "PHYSICAL DEMANDS AND WORKING CONDITIONS" (maybe schedule? Actually schedule info: working evenings, weekends, holidays; physical demands). Could be schedule. Then "Other Duties As Assigned" maybe not needed. Then "Benefits" list: many bullet points under "BIG PEAKS, BIGGER PERKS Employee Perks". That's benefits. We need to produce sections: About the role (maybe combine Resort Overview + Job Summary?), Responsibilities (Primary Responsibilities + maybe Performance Criteria?), Requirements (Ideal Candidate Profile + maybe Physical Demands?), Skills (maybe from Ideal Candidate Profile?), Benefits (list), Pay (Wage Range), Schedule (maybe from PHYSICAL DEMANDS AND WORKING CONDITIONS about working evenings, weekends, holidays). Also location maybe not needed. We must not invent sections with placeholder text. Ensure each section has content. Let's gather content. **About the role**: Could be "Resort Overview, Culture And Vision" + "Job Summary". We'll combine into a

maybe multiple paragraphs. **Responsibilities**: From "Primary Responsibilities" (Event Planning & Execution, Grow, Partnership Coordination). Also maybe "Performance Criteria" could be considered responsibilities but it's more about expectations. We'll include Performance Criteria under Responsibilities or maybe as separate? But we have limited sections; we can put Performance Criteria under Responsibilities as additional bullet points. **Requirements**: Ideal Candidate Profile bullet list. **Skills**: Could be extracted from Ideal Candidate Profile (Detail-Oriented, Clear Communicator, etc.) but that's overlapping with Requirements. Maybe we can treat Requirements as qualifications, Skills as specific abilities (like Technologically Proficient & Interpersonally Skilled, Resourceful & Dependable, Flexible Schedule). However we risk duplication. Better to follow instruction: Use sections only when posting has real specific content. The posting has "Ideal Candidate Profile" which includes traits; we could map that to Requirements or Skills. Since we have both Requirements and Skills sections possible, we need to decide. The posting does not have a separate "Skills" heading; but we can infer skills from the Ideal Candidate Profile. However we must not invent content; we can rephrase but must preserve all substantive information. We could put the Ideal Candidate Profile under Requirements (or Skills). To avoid thin sections, we can combine Requirements and Skills into one section? But instruction says prefer a few substantive sections over many thin ones. So we could have: About the role, Responsibilities, Requirements (which includes Ideal Candidate Profile and Physical Demands?), Benefits, Pay, Schedule. That's 5 sections. Let's see if we have content for each: - About the role: Resort Overview + Job Summary. - Responsibilities: Primary Responsibilities (Event Planning & Execution, Grow, Partnership Coordination) + Performance Criteria. - Requirements: Ideal Candidate Profile (list of traits) + maybe Physical Demands? Physical Demands is more about working conditions; could go under Schedule? Actually schedule is about working hours; physical demands about lifting etc. Could be under Requirements? Might be better under Schedule? But schedule section is for work schedule info; physical demands is not schedule. Could be under Requirements as "Working Conditions". However we have no explicit section for Working Conditions; we could put under Requirements or maybe under Responsibilities? I'd put under Requirements as "Working Conditions & Physical Demands". That seems okay. - Benefits: list under BIG PEAKS, BIGGER PERKS. - Pay: Wage Range $23-$25/ hour. - Schedule: info about working evenings, weekends, holidays; also maybe flexible schedule from Ideal Candidate Profile (Flexible Schedule). Also PHYSICAL DEMANDS AND WORKING CONDITIONS mentions working evenings, weekends, holidays. So schedule section can include that. Thus we have all sections. Now we need to format using

for each section heading. Use

• for any list of duties/requirements/benefits. Use

  for prose. We must not repeat job title as heading. Do not put Job ID etc. We must remove boilerplate: EEO statement, "Other Duties As Assigned", maybe "This position description is an overview..." etc. Also remove "AN EQUAL OPPORTUNITY EMPLOYER" etc. Also remove "This job description in no way states..." etc. Also remove "To perform this job successfully..." maybe keep? It's part of physical demands? Might be boilerplate. Safer to remove generic accommodation statement. But we need to preserve substantive information; the accommodation statement is legal boilerplate; we can remove. Also remove "This position description is an overview..." etc. Also remove "During these times of change..." maybe keep? It's about flexibility; could be part of responsibilities? Might be boilerplate but it's about accepting new responsibilities. Could keep as part of Responsibilities? Might be okay. We need to ensure we don't lose substantive info like "Willing to accept new and varied responsibilities". That's from Performance Criteria? Actually that's in Performance Criteria list. We'll keep. Now craft HTML. Structure:

  About the role

  Resort overview paragraph + Job summary paragraph.

  We need to combine two paragraphs into maybe two

  inside the section? The instruction: use

  for prose. Could have multiple

  under same section. That's fine. Thus:

  About the role

  Crystal Mountain is the Pacific Northwest's premier destination for skiers, snowboarders, and summer adventurers. We are part of Alterra Mountain Company which consists of some of the world's most aspirational brands. A career with Crystal Mountain is more than what you do today; it's being part of creating a community rooted in the spirit of the mountains, united by a passion for adventure, and celebrating the legendary adventures and enduring memories that mountains bring to everyone. Crystal Mountain delivers best in class service and adventures worthy of our extraordinary terrain and beauty. We are here to shape the future of mountain adventure. We Embrace Empowerment We Honor Authenticity We Cultivate Collaboration We Prioritize Purpose

  The Events and Partnerships Coordinator plays a vital role on the Events team, bringing a strong blend of organization, communication, and creativity to the table. This individual thrives in a fast-paced environment, demonstrates exceptional attention to detail, and excels at building and maintaining community connections.

  But note the original had "We Embrace Empowerment We Honor Authenticity We Cultivate Collaboration We Prioritize Purpose" without punctuation; we can keep as is. Now Responsibilities:

  Responsibilities

  • Event Planning & Execution
    • Plan Create and maintain comprehensive internal and external planning documents.
    • Coordinate pre-event logistics and communications with internal departments (F&B, Mountain Ops, Communications, Finance, Volunteers) and external stakeholders (musicians, brand partners, vendors, clients).
    • Identify potential challenges and help develop contingency plans.
    • Execute Support and lead the execution of on-brand events that reflect Crystal Mountain's identity-authentic, inclusive, adventurous, confident, and community-focused.
    • Manage on-site event setup and operations, ensuring events start on time, are properly staged, and run smoothly.
    • Lead and support event volunteers, providing clear direction and fostering a team-oriented environment.
    • Respond to day-of issues with professionalism and creativity, escalating as needed while collaborating with the larger Events team.
  • Grow
    • Support achievement of annual events revenue and profit targets by accurately tracking income and expenses.
    • Assist with post-event reporting, gathering feedback, summarizing outcomes, and identifying areas for improvement.
    • Maintain and nurture relationships with clients and vendors through timely follow-up and relationship-building efforts.
    • Contribute to developing new event concepts and experiences by participating in brainstorming sessions, proposal drafting, and project tracking.
  • Partnership Coordination
    • Coordinate sponsor fulfillment by ensuring promised benefits are delivered and expectations are met.
    • Support the maintenance of strong, ongoing relationships with brand and event partners.
    • Assist with drafting and distributing regular communications to keep stakeholders informed and aligned.
    • Collaborate with the Events and Partnerships Manager to meet obligations and reporting requirements.
    • Maintain accurate tracking of all partnership deliverables to ensure timely execution.
  • Performance Criteria
    • Willingness to learn and share feedback and other information with team and management
    • Uphold company and departmental policy at all times
    • Demonstrates support for company mission and values
    • Can work under stressful conditions without creating tension among fellow employees, vendors, and supervisors over long hours and sometimes challenging conditions.
    • Maintain workstation, event storage, and surrounding area cleanliness
    • Ability to communicate pleasantly and efficiently.
    • Ability to present company policy in a diplomatic way
    • Possesses and utilizes good verbal communication skills and phone etiquette
    • Knows policies and procedures, ensures team is aware and adequately utilizing them
    • Willing to accept new policies and procedures as changes occur.
    • Available for varied work shifts, including weekends and holidays, as agreed upon with management
    • Ability to complete projects and tasks according to collaborative due dates across all platforms
    • Efficiently organizes workload adhering to time constraints and often shifting priorities
    • Successfully follows event plans and cues while remaining flexible and collaborative as plans change
    • Ensures adherence by the team to lunch and break schedules to maximize coverage and provide quality guest service
    • Willing to accept new and varied responsibilities
  But note we have nested lists; the instruction says use
  • for any list of duties/requirements/benefits. It didn't forbid nested lists. Could be okay. However we might flatten to avoid complexity. Could just list all responsibilities as flat items. But we have headings inside responsibilities (Event Planning & Execution etc). Could treat each as a

    ? But we only allowed

    for section headings. Could use inside

    . Simpler: make each top-level bullet a duty heading, then sub-bullets