Special Events Manager

We need to output HTML fragment with sections: About the role? Actually the posting includes "About FIU" description, then "Job Summary", then responsibilities, then Minimum Qualifications, Departmental Requirements, Desired Qualifications, Job Category, Advertised Salary, Work Schedule, Working Condition(s), Pre-Employment Requirements, Other Information, How To Apply (both current employee and prospective employee), Disclosures (Clery Notice, Pay Transparency, Notice of Non-Discrimination, Reasonable Accommodation Statement). We need to remove boilerplate: cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. Also remove "How To Apply" sections? The instruction says: Remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. So we should remove the "How To Apply" sections entirely (both current employee and prospective employee). Also remove disclosures like Clery Notice, Pay Transparency, Notice of Non-Discrimination, Reasonable Accommodation Statement (these are legal/EEO). Also remove "Other Information"? Might be considered not boilerplate but includes travel etc. It's substantive? It says "Other Information Must attend meetings off campus and occasionally attend functions on weekends and evening Ability to travel locally and nationally. Ability to work flexible hours as needed. Ability to work occasional evenings, weekends and at locations outside of the University". That seems like job requirements, maybe keep as part of responsibilities or a separate section? Could be considered "Other Information". The instruction: include a section ONLY when the posting has real, specific content for it — never emit a heading followed by filler/placeholder text. So we can include a section like "Other Information" if it has content. But we need to decide headings: allowed headings: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. Also we can use other headings? The instruction says use

for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). It implies we should use those headings where appropriate, but we can also have other headings? It says "use

for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." That suggests those are the allowed headings; we should map content to those. So we need to map the posting content into those sections. We have: - About FIU: description of university. Could be "About the role"? Actually "About the role" is about the job, not the university. But we could treat the university description as "About the role"? Might be better to put under "About the role" a brief description of the role? The posting includes "Job Summary". That could be "About the role". So we can put the Job Summary under About the role. - Responsibilities: list of duties (Supports the planning..., etc). So we can put those under Responsibilities as

• . - Requirements: Minimum Qualifications, Departmental Requirements, maybe also Desired Qualifications? Could be under Requirements or Qualifications. The instruction includes Requirements and Qualifications as separate possible headings. We need to decide. Minimum Qualifications and Departmental Requirements are requirements. Desired Qualifications could be under Qualifications. Or we could combine. - Skills: maybe list of skills like communication, project management, etc. Could be under Skills. - Benefits: not mentioned except maybe none. No benefits described. So we should not create Benefits section. - Pay: Advertised Salary $50,000-$55,000. So we need a Pay section with that. - Schedule: Work Schedule (Begin time: 8:30 AM End time: 5:00 PM) plus maybe other schedule info (flexible hours, evenings, weekends). So we can put under Schedule. - Working Condition(s) maybe could be under Requirements? Or maybe under Responsibilities? But we have no specific heading for Working Condition. Could be part of Requirements or maybe under Responsibilities? Probably we can include under Requirements as a bullet. - Pre-Employment Requirements (Criminal Background Check, Driver's License Check) maybe under Requirements. - Other Information (travel, flexible hours) maybe under Schedule or Requirements. We must not include boilerplate like disclosures, How To Apply, etc. We must preserve all substantive information. So we need to include all the content from the posting except the removed parts. Let's extract substantive content: About FIU paragraph: "About FIU Florida International University is a Top 50, preeminent public research university with 55,000 students from all 50 states and more than 140 countries, as well as an alumni network of more than 340,000. Located in the global city of Miami, the university offers more than 200 degree programs at the undergraduate, graduate and professional levels, including medicine and law. FIU faculty are leaders in their fields and include National Academy members, Fulbright Scholars and MacArthur Genius Fellows. A Carnegie R1 institution, FIU drives impactful research in environmental resilience, health and technology and innovation. Home to the Wall of Wind and Institute of Environment, FIU stands at the forefront of discovery and innovation. With a focus on student success, economic mobility and community engagement, FIU is redefining what it means to be a public research university." Job Summary: "The Special Events Manager supports the planning, coordination, and execution of a wide range of university events that advance institutional goals, strengthen community engagement, and enhance the student, alumni, donor, faculty, staff, and visitor experience. Working collaboratively with campus partners, university leadership, vendors, and external stakeholders, the Special Events Manager assists with event logistics from concept through completion, ensuring events are delivered professionally, efficiently, on budget, and in alignment with university standards. The ideal candidate is an organized, detail-oriented, collaborative, and solutions-oriented professional with strong communication and project management skills and a passion for creating memorable, high-quality experiences in a higher education environment." Then a list of responsibilities (starting with "Supports the planning, coordination, and execution of assigned events within the Department of University Protocol, Ceremonies, and Events portfolio." and many bullet-like sentences). We'll treat each sentence as a bullet. Minimum Qualifications: "Bachelor's degree and two (2) years of related experience; OR six (6) years of related experience; OR an equivalent combination of relevant education and/or experience." Departmental Requirements: "Experience with event planning." Desired Qualifications: "Experience working in higher education, nonprofit, or institutional event planning.Ability to perform duties that involve frequent walking, standing for extended periods during events, and occasionally lifting and transporting event materials, with or without reasonable accommodation.Knowledge of event planning, production, logistics, and project coordination principles and practices." Job Category: "Administrative" Advertised Salary: "$50,000-$55,000" Work Schedule: "Begin time: 8:30 AM End time: 5:00 PM" Working Condition(s): "Operating University Vehicles (all types)" Pre-Employment Requirements: "Criminal Background CheckDriver's License Check" Other Information: "Must attend meetings off campus and occasionally attend functions on weekends and eveningAbility to travel locally and nationally.Ability to work flexible hours as needed.Ability to work occasional evenings, weekends and at locations outside of the University" We need to format as HTML with

  headings and

  • for lists,

    for prose. We need to avoid repeating job title as heading (the page already shows it). So we don't add a heading for the job title. We need to not put Job ID/requisition numbers as headings (none present). We need to remove duplicated lines: there may be duplicated sentences? Not obvious. We need to remove application instructions (How To Apply sections) and disclosures. Now decide sections: - About the role: could combine About FIU and Job Summary? But About the role likely about the job, not the university. However we have no separate "About the university" heading allowed. Could we put About FIU under About the role? Might be odd but permissible? The instruction 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 "use

    for section headings (e.g ...)". It implies we should use those headings for sections. Probably we should map content to those headings. So we need to decide which content goes under which heading. We have: - About the role: maybe the Job Summary (description of role). The About FIU could be considered background but not strictly about the role. Could we omit it? The instruction says preserve ALL substantive information; do NOT invent or summarize away detail. So we must keep the About FIU paragraph. Where to put it? Could be under About the role as well, but that might misrepresent. However we have no other heading for "About the university". Could we create a heading like "About FIU"? Not in the list but maybe allowed as it's not prohibited. The instruction says use

    for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). The "e.g." suggests those are examples, not an exhaustive list. So we could use other headings as needed, but we should prefer those. However to be safe, we could use "About FIU" as a heading. But the instruction says "use

    for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." It doesn't forbid other headings. So we can use About FIU as a heading. But we also need to avoid creating sections with filler text. About FIU has real content, so okay. Thus we can have:

    About FIU

    ...

    Then

    About the role

    with Job Summary. Then

    Responsibilities

    with
    • each responsibility sentence. Then

      Requirements

      with Minimum Qualifications and Departmental Requirements maybe as
      • . Then

        Qualifications

        with Desired Qualifications (maybe split into bullet points). Then

        Skills

        maybe we can extract skills from Desired Qualifications: strong communication and project management skills, etc. But we already have Qualifications. Could combine. But we need to avoid thin sections. Perhaps we can merge Qualifications and Skills into one section called Qualifications, containing both desired qualifications and skills. However the instruction allows both headings; we can choose to use only those with real content. We have Pay and Schedule sections definitely. We also have Working Condition(s) and Pre-Employment Requirements and Other Information. Where to put them? Could be under Requirements as additional bullets. Thus Requirements section could include: Minimum Qualifications, Departmental Requirements, Pre-Employment Requirements, Working Condition(s), Other Information. But we need to keep them distinct? Not required; just preserve all info. We'll create

        Requirements

        with a
        • list containing each item. We'll need to parse the sentences. Let's list all responsibility sentences: 1. Supports the planning, coordination, and execution of assigned events within the Department of University Protocol, Ceremonies, and Events portfolio. 2. Supports major university events, including commencement, convocations, ceremonies, institutional celebrations, and other high-profile events. 3. Communicates professionally and effectively with university leadership, faculty, staff, students, alumni, donors, community members, vendors, and other event stakeholders. 4. Assists with event logistics from initial planning through event completion, including venue reservations, registration, RSVP and guest management systems, audiovisual and technical requirements, setup, stage and seating arrangements, catering, signage, parking,