Student Activities and Engagement Program Manager

We need to output HTML fragment with headings

for sections present: About the role? Actually the posting includes "Who We Are", "Summary", "Essential Functions", "Benefits at a Glance", "Salary/Pay Range", "Schedule" maybe. Also "Tentative Search Timeline" maybe not needed? The instruction: 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. Thus we need to decide which sections to include: About the role? The posting has "Who We Are" (description of UCCS). Could map to "About the role"? Might be better to use "About the role" heading for description of role? But we have "Summary" which describes responsibilities. Could treat "Summary" as About the role? Actually "Summary" is a paragraph describing the role. Could use

  About the role

  then

  with that summary text. Then we have "Essential Functions" which includes percentages and bullet-like sentences. Could treat as Responsibilities heading. Use

  Responsibilities

  then
  • each duty. We have "Benefits at a Glance" which lists benefits. Use

    Benefits

    then
    • . We have Salary/Pay Range: "$ 47,351- 60,000 annually. Compensation will be commensurate upon experience and qualifications." This is pay info. Should we include Pay section? The instruction: never create Pay/Schedule/Benefits sections unless the posting actually states them. It does state salary range, so we can include Pay section. However we must avoid filler like "commensurate with experience" which is placeholder? It says "Compensation will be commensurate upon experience and qualifications." That is somewhat generic but still part of posting. Should we include it? The instruction says never emit a heading followed by filler/placeholder text (e.g. "commensurate with experience", "not specified", "N/A", "varies", "TBD") . That suggests we should not include a Pay section if the only content is filler like "commensurate with experience". But we also have actual range "$ 47,351- 60,000 annually." That's specific. So we can include Pay section with that range and maybe note that compensation is commensurate with experience (but that's filler). Could we include both? Might be okay to include the range and then note that compensation is commensurate with experience (though it's filler). The instruction says never emit a heading followed by filler/placeholder text. It doesn't say we cannot include filler within a section if there is also substantive content. So we can include Pay section with the range and the commensurate sentence. Schedule: The posting mentions "Frequent evening and weekend work is required." Also "Schedule Full-time" near the bottom. So we have schedule info: Full-time, frequent evening and weekend work. So we can include Schedule section. We also have "Tentative Search Timeline" with dates. That's not in the list of headings but could be considered metadata; maybe we can drop as minor metadata? The instruction says do NOT put Job ID / requisition numbers as headings — fold minor metadata into a short

      or drop it. The timeline could be considered minor metadata; we could drop it or include in a short p under maybe "Application Process"? But we are to remove application instructions. The timeline is part of hiring process; maybe we can drop as not essential. Safer to drop. We also have "Required training" etc. That's boilerplate legal/EEO; remove. We have "University Staff Special Instructions to Applicants" etc. Remove. We have "Job Category Student Services Department C0001 -- Colorado Springs Campus Schedule Full-time Posting Date Sep 17, 2026 Unposting Date Ongoing Posting Contact Name Christopher LaLone Posting Contact Email clalone@uccs.edu Position Number 00002774". This is metadata; we can drop or fold into short p. Probably drop. We need to preserve ALL substantive information; not invent or summarize away detail. So we need to keep the essential functions details, benefits details, salary range, schedule info, who we are description, summary. We must not repeat the job title as a heading. The job title is "Student Activities and Engagement Program Manager". We must not use that as heading. We need to output only HTML fragment, no /, no markdown. Thus produce something like:

      About the role

      ... (Who We Are + maybe summary? Actually Who We Are is about UCCS, not role. Could treat as About the role? Might be better to have two sections: About UCCS and Summary? But only allowed headings from list; we could use About the role for the summary of responsibilities, and maybe include Who We Are as a paragraph under About the role? Or we could create a section "About the university"? Not in list. The instruction says use

      for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). It gives examples but not exclusive; we could use other headings? It says use

      for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). Likely they expect us to use those headings only. So we need to map content to those headings. Thus: - About the role: could include the "Who We Are" description of UCCS and maybe the summary? But "Who We Are" is about the institution, not role. However it's still substantive info about the employer. Could fit under About the role? Might be okay. - Responsibilities: essential functions. - Requirements: maybe the qualifications: bachelor's degree required, experience planning programs required, etc. Also preferred qualifications: master's degree, higher ed experience, supervising student employees. - Skills: maybe not explicitly listed; we could omit if no specific skills. - Benefits: benefits at a glance. - Pay: salary range. - Schedule: full-time, frequent evening and weekend work. We must not create sections with filler. Ensure each heading has substantive content. Let's extract content. Who We Are paragraph: "The University of Colorado Colorado Springs (UCCS) is a premier educational institution that prides itself on academic excellence, research, and community engagement and is actively seeking a Student Activities and Engagement Program Manager to join our team! UCCS is committed to academic excellence, professional development, and fostering an environment that supports innovation and student success. At the base of the Rocky Mountains, Colorado Springs is captivated by its stunning landscapes, making it a paradise for nature lovers. This city is more than its scenery—a mosaic of history, arts, and a vibrant tech scene. We invite you to join a community that cherishes outdoor adventure as much as forward-thinking growth, an exceptional setting for both career and lifestyle." We can put that in

      under About the role. Summary paragraph: "The Program Manager, Student Activities and Engagement will lead long-term and short-term strategic visioning and planning for student engagement and advocate for departmental needs and resources to support student engagement. The Program Manager, Student Activities and Engagement is responsible for planning, implementing, promoting, and assessing a comprehensive portfolio of student engagement opportunities that foster involvement, belonging, retention, persistence, and student success. Reporting to the Director of Student Engagement, this position coordinates campus traditions, educational programs, entertainment events, and community-building initiatives that serve residential, commuter, and nontraditional students. The position develops collaborative partnerships across the university, leads marketing and outreach efforts, supervises student employees, and utilizes assessment data to continuously improve programs and services. Frequent evening and weekend work is required." That could also go under About the role or Responsibilities. But we already have Responsibilities for essential functions. The summary is more overview; we could include it under About the role as well. But to avoid duplication, maybe we put summary under About the role and essential functions under Responsibilities. Now Responsibilities: essential functions broken down by percentages and bullet-like sentences. We need to turn each sentence into

      . The essential functions section includes: 45% Student Activities and Campus Programming - Coordinate and assess student engagement programs and campus traditions. - Direct and manage a full calendar of large-scale, traditional events on campus, including, but not limited to, Clyde’s Kickoff, Disorientation Week, Homecoming Weekend, Winter Welcome Week, Commuter Appreciation Weeks, and other related co-sponsored events. - Develops and facilitates ongoing weekly programs and events that engage a broad cross-section of the student body. - Emphasis will be placed on hosting events in a wide variety of campus locations and beyond - Lead collaborative and inclusive campus programing efforts with students, administrators, faculty, staff, and the community. - Manage logistics, contracts, vendors, staffing, and evaluations. - Coordinate commuter student engagement initiatives. - In partnership with Residence Life and Housing staff, expand active and engaging student programming within the residential villages. 25% Marketing, Communications, and Student Outreach - Develop marketing and promotional strategies. - Maintain engagement platforms, calendars, social media, websites, and digital signage. - Ensure alignment with university branding standards. - Oversee the capture of high-resolution photos and videos at student events and develops promotional strategies that showcase these experiences through Student Life & Leadership and UCCS communication channels, including social media, websites, digital signage, print publications, and other outreach platforms. 15% Assessment and Program Evaluation - Track participation and attendance data. - Administer evaluations and surveys. - Incorporate program and learning outcomes into a robust calendar of programs and events. - Prepare reports and recommendations for continuous improvement. - Actively serve on the campus programming committee 15% Supervision and Departmental Support - Recruit, train, supervise, and evaluate student employees. - Provide active supervision, leadership development, and mentoring. - Participate in departmental initiatives and perform related duties We need to preserve all substantive information. The percentages are part of content; we could keep them as part of the

      text or maybe as a heading? But we can just include them in the

      . Eg "

      45% Student Activities and Campus Programming: Coordinate and assess student engagement programs and campus traditions.

      " but that would duplicate. Better to keep the percentage as a separate

      heading? But we only have

      • for list; we could have a
      • that includes the percentage and then a sublist? Not allowed to nest? Could just include the percentage as part of the first item. However we need to preserve all detail; we could keep the percentage as a separate
      • line like "
      • 45% Student Activities and Campus Programming
      " then subsequent items as sub-items? But that would change structure. The instruction: Use
      • for any list of duties/requirements/benefits. It doesn't forbid nested lists, but safer to keep flat list and include the percentage within each relevant item. We could break into sections with

        ? Not allowed; only