Coordinator of Orientation & Transition Programs

The user wants me to convert this job posting into clean semantic HTML. Let me analyze the content and structure it according to the rules. First, I need to identify the sections: - About the role / Who We Are (the "Who We Are" section) - Required Qualifications - Preferred Qualifications - Brief Description of Duties (this seems like an overview) - Then there are detailed duty sections: Onboarding New Students, Supervision, Transition Programs, Technology & Communication, Student Affairs & University Program Support, Purchasing And Inventory, Professional Development And Committee Involvement - Special Notes (includes salary, FLSA, essential position, visa sponsorship, etc.) - At the end there's metadata: Official Job Title, Job Field, Primary Location, Department/Hiring Area, Schedule, Posting Start Date, Posting End Date, Appointment Type, Salary Grade Rules: - Use

for section headings (About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule) - Use

• for lists - Use

  for prose - Do NOT repeat job title as heading (page already shows it) - Do NOT put Job ID / requisition numbers as headings — fold minor metadata into short

  or drop it - Preserve ALL substantive information - Remove boilerplate (cookie/navigation/legal/EEO/equal-opportunity/scam-warning, duplicated lines, application instructions) - Include section ONLY when posting has real, specific content for it — never emit heading followed by filler/placeholder text (e.g., "commensurate with experience", "not specified", "N/A", "varies", "TBD") - Never create Pay/Schedule/Benefits sections unless posting actually states them - Prefer few substantive sections over many thin ones - Output ONLY HTML fragment — no /, no markdown code fences Now, let's map the content. The "Who We Are" section is about the division, not the role specifically. Could be "About the division" or "About the organization". The rule says "About the role" as example heading. But this is "Who We Are" describing the Division of Student Affairs. I'll use "About the division" or "About the organization". Since the rule says "About the role" as example, but we can use appropriate heading. I'll use "About the division". Required Qualifications and Preferred Qualifications are clearly qualifications. Could combine under "Qualifications" with subsections? But rule says use

  for section headings like "Qualifications". Could have two

  headings: "Required qualifications" and "Preferred qualifications". That's fine. Brief Description of Duties is an overview. Then there are detailed duty sections. Those could be grouped under "Responsibilities" with sub-sections? But rule says use

  for section headings. Could make each detailed duty area a separate

  ? That would be many headings. The rule says prefer few substantive sections over many thin ones. But each of those sections has substantial content. However, they are all responsibilities. Could combine into one "Responsibilities" section with sub-lists? But the content is long and categorized. The rule says use

  for section headings like "Responsibilities". It doesn't forbid multiple

  for sub-sections. But the example headings include "Responsibilities" as a single heading. However, the posting has distinct functional areas. I think it's okay to have multiple

  headings for each major duty area, as they are substantive. But the rule says "Prefer a few substantive sections over many thin ones." These are not thin; each has multiple bullet points. But they are all part of responsibilities. Could structure as:

  Responsibilities

  Then for each area, maybe use

  ? But rule says use

  for section headings. It doesn't mention

  . Safer to use

  for each major area. However, the example headings list: "About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule". So "Responsibilities" is one heading. But the posting has multiple distinct responsibility categories. I'll create a "Responsibilities" heading and then use subheadings? But rule says only

  for section headings. Could use

  for each category. That would be many

  s. Let's see: Onboarding New Students, Supervision, Transition Programs, Technology & Communication, Student Affairs & University Program Support, Purchasing And Inventory, Professional Development And Committee Involvement. That's 7 headings. Might be too many. But they are all responsibilities. Could combine into one "Responsibilities" section with bullet points grouped by category using labels? But the rule says use

  • for any list of duties. Could make a single list with all duties, but that would be huge. Better to keep the categorization. I'll use

    for each major duty area, as they are distinct and substantive. The rule says "use

    for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." It doesn't say you cannot have multiple Responsibilities-like headings. But "Responsibilities" is a category. The posting has "Brief Description Of Duties" then detailed sections. I'll treat "Brief Description Of Duties" as an overview paragraph, then the detailed sections as separate responsibility areas. Special Notes includes salary, FLSA, essential position, visa sponsorship, application instructions (resume/cover letter), EEO statement, accommodation, crime statistics link, WHY WORK HERE link. Need to remove boilerplate: EEO/equal-opportunity, scam-warning, application instructions, accommodation instructions, crime statistics link, WHY WORK HERE link. Keep substantive: salary, FLSA status, essential position, visa sponsorship note. Also the metadata at the end: Official Job Title, Job Field, Primary Location, Department/Hiring Area, Schedule, Posting Start Date, Posting End Date, Appointment Type, Salary Grade. These are metadata. Rule: do NOT put Job ID / requisition numbers as headings — fold minor metadata into a short

    or drop it. So I'll create a "Position details" or "Job details" section with a paragraph summarizing key metadata: full-time, temporary, schedule, location, salary grade, posting dates. But the rule says never create Pay/Schedule/Benefits sections unless posting actually states them. The posting states salary in Special Notes. So we can have a "Pay" section. Schedule is mentioned: "Full-time" and "Evening and weekend work will be required at times." Also metadata says Schedule Full-time. So we can have a "Schedule" section. Benefits: not explicitly stated except maybe "total rewards" link but that's boilerplate. So no Benefits section. Let's structure: 1. About the division (from Who We Are) 2. Required qualifications 3. Preferred qualifications 4. Responsibilities (maybe with subsections? I'll make each duty area an

    but that might be too many. Alternatively, make one "Responsibilities" heading and then use

    ? But rule says only

    . I'll use

    for each duty area, but maybe combine some? The posting has clear headings: Onboarding New Students, Supervision, Transition Programs, Technology & Communication, Student Affairs & University Program Support, Purchasing And Inventory, Professional Development And Committee Involvement. I'll keep them as

    headings. That's 7 headings. Plus the overview "Brief Description Of Duties" could be a paragraph under a "Role overview" heading. But the rule says "Prefer a few substantive sections over many thin ones." These are not thin. However, they are all responsibilities. Could group under "Responsibilities" with each area as a lead-in to a list. But the rule says use

    • for any list of duties. It doesn't forbid multiple lists. I think it's acceptable to have multiple

      for each functional area. But the example headings list "Responsibilities" as a single heading. The user might expect a single Responsibilities section. However, the instruction: "use

      for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." This suggests those are the typical sections. But the posting has more granular sections. I'll follow the posting's structure but map to those standard headings where possible. Let's map: - "Who We Are" -> "About the division" (or "About the organization") - "Required Qualifications" -> "Requirements" or "Qualifications" - "Preferred Qualifications" -> "Preferred qualifications" (could be under same Qualifications heading) - "Brief Description Of Duties" -> "Role overview" or "About the role" - Then the detailed duties: these are all responsibilities. Could be under "Responsibilities" with sub-sections. But since we can only use

      , maybe we make each a

      but that deviates from the example. However, the rule says "use

      for section headings (e.g. ...)" meaning those are examples, not exhaustive. So we can have other headings. I'll create: -

      About the division

      -

      Required qualifications

      -

      Preferred qualifications

      -

      Role overview

      (for Brief Description Of Duties) -

      Onboarding new students

      -

      Supervision

      -

      Transition programs

      -

      Technology & communication

      -

      Student affairs & university program support

      -

      Purchasing & inventory

      -

      Professional development & committee involvement

      -

      Pay

      (from Special Notes salary) -

      Schedule

      (from Special Notes evening/weekend work and metadata) -

      Position details

      (for metadata like appointment type, location, posting dates, salary grade) But note: "Special Notes" also includes FLSA Non Exempt, essential position, visa sponsorship. Those could go in Position details or separate. I'll include in Position details. Also, the posting says "Evening and weekend work will be required at times." That's schedule. Now, need to remove boilerplate: The EEO statement, accommodation instructions, crime statistics link, WHY WORK HERE link, application instructions (resume/cover letter). Also the "Click here for more information" links. Remove those. Preserve all substantive information. Let's write HTML. First, "Who We Are" content: multiple paragraphs. I'll put them in

      tags. There are bullet points? Actually it's prose with some bullet-like lines but not marked as list. It says "We celebrate and take pride in the following:" then lines like "Named one of the “Most Promising Places to Work in Student Affairs” by Diverse Magazine." etc. Those are bullet points. I'll make a

      for those. Required Qualifications: list of items. Use
      • . Preferred Qualifications: list. Brief Description Of Duties: prose paragraphs. Onboarding New Students: multiple paragraphs, each seems like a duty. Could be list items. The text is a series of sentences each starting with a verb. I'll make each sentence a list item? But they are long. Better to keep as paragraphs? The rule says use
        • for any list of duties. The duties are listed as separate paragraphs. I'll convert each paragraph to a list item. However, some paragraphs are long with multiple sentences. I'll