Support Specialist

We need to output only HTML fragment, no html/body tags. Use

for section headings: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We must include sections only when posting has real specific content. The posting includes: description (intro) maybe "About the role". It has responsibilities listed. It has requirements. It has "About Us" maybe not a required heading; but we could treat as "About the role"? Actually "About Us" is about the university, not role. The instruction: use headings for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). So we should map content to those headings if present. The posting includes: description of role (first paragraph). That could be "About the role". Then "Responsibilities:" section. Then "Requirements:" section. There's no explicit Qualifications, Skills, Benefits, Pay, Schedule. However there is mention of "Ability to work a flexible schedule that may include evenings and weekends." That's schedule info. So we could include a Schedule section with that detail. Also there is mention of "Proficient in Microsoft Office Suite..." which could be Skills. There's also "Customer or student information system experience preferred." That's also skill/experience. So we could create a Skills section. There's no explicit Benefits, Pay. So we should not create those sections. Also there is "About Us" which is not a standard heading but could be considered "About the role"? Probably not. The instruction says use those headings for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). It doesn't forbid other headings, but we should prefer those. We could include an "About the role" heading for the introductory paragraph. Then Responsibilities, Requirements, Skills, Schedule. Possibly also Qualifications? The requirements could be considered qualifications. But we already have Requirements heading; we could also have Qualifications if distinct. But we can combine. The instruction: "Prefer a few substantive sections over many thin ones." So we should not create many thin sections. We have Responsibilities, Requirements, Skills, Schedule, About the role. That's five sections. Could we merge Skills into Requirements? But they said prefer few substantive sections; we could keep Skills separate if substantive. The skills mentioned: Proficient in Microsoft Office Suite (Excel, PowerPoint, Word), Customer or student information system experience, ability to work independently and collaboratively, proven customer service, self-motivated, flexible, patient, solutions-oriented. Those are skills/qualities. Could be part of Requirements. But we already have Requirements heading for experience etc. Might be okay to put them under Requirements. However the instruction says use headings for those categories if content exists. Since we have content for skills, we could make a Skills section. But we must avoid thin sections. The skills list is substantive enough. Schedule: we have "Ability to work a flexible schedule that may include evenings and weekends." That's schedule info. Thus sections: About the role (intro paragraph), Responsibilities, Requirements, Skills, Schedule. We must not repeat job title as heading. No Job ID etc. We need to use

for each section heading. Use

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

  for prose. We need to preserve all substantive information; do not invent or summarize away detail. Remove boilerplate etc. The posting includes a lot of detail in responsibilities broken down by percentages and bullet-like sentences. We need to convert to

  • items preserving details. The responsibilities section includes percentages and sub-bullets. We'll need to capture each duty as list items. Could keep the percentages as part of the item text. We must not include duplicated lines, cookie/navigation/legal/EEO etc. The posting includes an EEO statement at the end: "It is the policy of Rasmussen University to afford equal opportunity..." That's boilerplate; we should remove it. Also the "About Us" paragraph is not boilerplate; it's substantive about the university. Should we keep it? It's about the university, not role. The instruction says remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. The About Us paragraph is not boilerplate; it's descriptive of the university. Might be considered part of job posting but not required headings. Could we include it under About the role? Or maybe we could create an "About the university" section but not in allowed headings. Safer to incorporate relevant info into About the role? But the About the role heading is for role description, not university. However we could still include the About Us paragraph as a

    under About the role heading? Might be okay but could be considered off-topic. The instruction: "Use

    for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." It doesn't forbid other headings, but we should prefer those. The About Us could be considered "About the role"? Not exactly. But we could treat the introductory paragraph as About the role, and the About Us paragraph could be omitted? The instruction says preserve ALL substantive information; do NOT invent or summarize away detail. So we must keep the About Us paragraph somewhere. If we don't have a heading for it, we could just put it as a

    before any headings? But we need to use headings for sections; we could have a heading like "About Rasmussen University" but that's not in the list. However the instruction says use those headings for section headings (e.g. ...). It doesn't say we cannot use other headings, but we should prefer those. However to preserve all substantive info, we need to include it. Perhaps we can include it under a heading "About the role" but that would be mixing. Better to create a heading "About Rasmussen University" as

    and put the paragraph there. The instruction says "Use

    for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." The "e.g." suggests examples, not exclusive list. So we can use other headings as needed, but we should prefer those examples. However we must not create sections with filler. The About Us paragraph is substantive, so we can create a heading for it. Let's use

    About Rasmussen University

    . Now we need to ensure we don't include boilerplate like EEO statement. Remove that. Also remove duplicated lines: there may be duplicated content like "Assist with..." repeated? We'll just keep unique. Now craft HTML. Structure:

    About the role

    The Support Specialist works in a team environment to support the campus in operating efficiently and effectively while serving students, the team and our community. In this capacity, the Support Specialist will leverage his/her experience in an operations/administrative capacity to support all programs on campus, with a focus on nursing programs. The Support Specialist also serves as a resource for the central departments when support and information is requested. The Support Specialist will follow the policies and procedures adopted by the University in performing the duties of the position, including adhering to the Family Educational Rights and Privacy Act (FERPA) in handling student information.

    Responsibilities

    • Records – 55%: Responsible for the overall maintenance of all electronic and paper student records generated or stored at the campus. To include, but not limited to; background check process, immunizations, NCLEX scores, drug screening and other clinical preparation to ensure compliance with accreditation, state, federal and University standards.
    • Serve as liaison to the Office of Student Records and Operations to receive, authenticate and file official transcripts, pull reports then validate and distribute student information.
    • Lead or assist with tracking student immunization compliance for students.
    • Run reports and/or gather data for day-to-day operations.
    • Track and update student background checks, drug screening, NCLEX scores and nursing orientation.
    • Track team member community hours.
    • Assist with student outreach for schedule confirmation, immunizations, etc.
    • Build Residential Term schedules in Campus Nexus.
    • Monitor student attendance.
    • Activities/Events – 20%: Update student portal and social media outlets.
    • Lead or assist with organizing commencement ceremony, and/or honors awards, and/or campus pinning ceremony.
    • Assist with organizing advisory committee meetings.
    • Assist with refreshing campus bulletin boards, campus PowerPoint slideshow, and other pertinent campus information.
    • Assist with facilities related issues, and other maintenance concerns. To include, but not limited to; inventory and order campus supplies, confirm monthly dialing of 911 is operational, inform leaders when a facility issue arises, then request work through facilities team, provide liaison support for team with IT issues.
    • In support of the collaborative team environment, share responsibility to assist with campus and community activities and/or events both on campus and off-site, student orientations, career fairs, etc.
    • Administrative/Front Desk – 20%: Assist with accreditation visit preparation.
    • Assist with processing any invoices and submitting to accounts payable.
    • Assist with opening and closing the campus, serve as a campus point person.
    • Manage the community calendar(s) for the campus, make room reservations for courses and guests.
    • Process, reconcile and prepare incoming and outgoing mail and packages.
    • Assist with the oversight of front desk activities to include, but not limited to: Provide general guidance and direction to Student Ambassadors; Escalate any concerns including work schedules and front desk coverage; Answer and refer incoming calls and concerns to the appropriate department; Assist with the overall maintenance and appearance of the front desk/welcome area; Assist with onboarding of new hires, as necessary.
    • Exam Proctoring and Other Duties – 5%: Will also perform other duties as requested.

    Requirements

    • Minimum of two years’ experience working in a fast paced, service-focused setting.
    • Experience in an institution of higher learning preferred.
    • Ability to work a flexible schedule that may include evenings and weekends.
    • Strong organizational skills with the ability to manage interruptions while delivering within tight deadlines.
    • Excellent written and verbal communication skills.
    • Proficient in Microsoft Office Suite, in particular, proficiency in MS Excel, Power Point and Word.
    • Customer or student information system experience preferred.
    • Ability to work independently and collaboratively as a member of a team and with other departments both in person and virtually.
    • Proven customer service in a professional environment.
    • Must be self-motivated, flexible, patient and solutions-oriented.

    Skills

    • Proficient in Microsoft Office Suite (Excel, PowerPoint, Word).
    • Customer or student information system experience.
    • Strong organizational skills.
    • Excellent written and verbal communication.
    • Ability to work independently and collaboratively.
    • Proven customer service.
    • Self‑motivated, flexible, patient, solutions‑oriented.

    Schedule

    Ability to work a flexible schedule that may include evenings and weekends.

    About Rasmussen University

    Rasmussen University, a university accredited by the Higher Learning Commission, an institutional accreditation agency recognized by the U.S. Department of Education (www.hlcommission.org), is dedicated to changing lives and the communities it serves through innovative educational programs. As a pioneer in career-focused education since 1900, the