Research Facilities Manager

The user wants me to reformat a job posting into clean, well-structured semantic HTML. I need to follow the rules: 1. Use

for section headings (e.g., About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule) 2. Use

• for any list of duties/requirements/benefits, and

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

  or drop it 5. Preserve ALL substantive information; do NOT invent or summarize away detail 6. Remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions 7. 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") 8. Never create Pay/Schedule/Benefits sections unless the posting actually states them 9. Prefer a few substantive sections over many thin ones 10. Output ONLY the HTML fragment — no /, no markdown code fences Let me analyze the job posting: The posting has: - An introductory paragraph describing the role - Responsibilities section with subsections: Project Management, Safety, Facilities, Property Manager - Qualifications section with a list of requirements - Some metadata at the end: Standard Weekly Hours, Eligible for Overtime, Benefits Eligible, Probationary Period, Essential Services Personnel, Physical Capacity Exam Required, Valid Driver's License Required, Experience Level, Salary Range I need to structure this into semantic HTML. The job title is "Research Facilities Manager" but I should not repeat it as a heading. I'll create sections for: - About the role (the introductory paragraph) - Responsibilities (with subsections as lists) - Qualifications (the list of qualifications) - Pay (since salary range is given: $105,000 to $115,000) - Schedule (since Standard Weekly Hours 36.25, Eligible for Overtime No) - Benefits (since Benefits Eligible Yes, and there's mention of comprehensive benefit program) But note: The rules say "never create Pay/Schedule/Benefits sections unless the posting actually states them." The posting does state salary range, weekly hours, overtime eligibility, benefits eligibility. So I can include them. However, the metadata includes many items: Probationary Period, Essential Services Personnel, Physical Capacity Exam Required, Valid Driver's License Required, Experience Level. These are minor metadata. I should fold them into a short

  or drop them. The rule says "fold minor metadata into a short

  or drop it." I'll include them in a "Details" or "Additional Information" section? But the rule says prefer a few substantive sections over many thin ones. Maybe I can include them in a "Position Details" section as a list. But the user said: "Do NOT put Job ID / requisition numbers as headings — fold minor metadata into a short

  or drop it." So I should not create a heading for each metadata item. I can create a single "Position Details" section with a list of these metadata items. Alternatively, I can include them in a paragraph. But they are distinct facts. I'll create a "Position Details" section with a

  of these items. Now, the EEO statement and the paragraph about salary range factors and benefits link are boilerplate. I should remove them. The posting includes: "Princeton University is an Equal Opportunity Employer..." and "The University considers factors such as... Please see this link for more information." That's boilerplate. Remove. Also, the "Standard Weekly Hours 36.25 Eligible for Overtime No Benefits Eligible Yes Probationary Period 180 days Essential Services Personnel (see Policy For Detail) No Physical Capacity Exam Required Yes Valid Driver’s License Required Yes - Car Experience Level Mid-Senior Level Salary Range $105,000 to $115,000" are specific details. I'll keep them. Now, structure: -

  About the role

  ...intro paragraph...

  -

  Responsibilities

  Then for each subsection (Project Management, Safety, Facilities, Property Manager), I could use

  ? But the rule says use

  for section headings. It doesn't mention subheadings. I could use

  for subsections, but the rule only specifies

  for section headings. To be safe, I'll use

  for main sections only, and for subsections I'll use or just include them as list items with bold labels. However, the responsibilities are grouped into categories. I can make each category a list with a heading-like label. Since the rule says "use

  for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)", it implies only those top-level sections. So I'll keep Responsibilities as one section, and within it, use

  with
  • that have bold category names. But the responsibilities are quite detailed. I'll create a list for each category, maybe with a label. Alternatively, I can use

    for subsections. The rule doesn't forbid it, but it says "use

    for section headings". It doesn't say not to use other heading levels. However, to be safe, I'll use

    only for the main sections, and for subsections I'll use

    Project Management: ...

    but that would be prose. Better to use nested lists. I'll structure Responsibilities as:

    Responsibilities

    • Project Management: Serve as coordinator/liaison for all construction and renovation projects. Coordinate with OCP, EHS, Facilities, and outside vendors and contractors. Serve as the representative for the department and faculty at meetings related to construction projects. Ensure that the impact of construction projects on building residents is minimized as much as possible. Manage and coordinate all building maintenance, renovations, moves, transfers, furniture and repair projects.
    • Safety: Oversee the department's safety and compliance program. Serve as primary liaison with EHS to maximize GEO compliance with all applicable regulations. Create new compliance strategies with PIs, researchers, students and lab staff as regulations change and oversees implementation. Review laboratory information in SHIELD and ensure all records are current. Coordinate with the Laboratory Safety Program, the Radiation Safety Program, Institutional Bio-safety Committee, Laboratory Animal Resources (LAR) and the Hopewell Research Facility, to ensure GEO compliance with University, local, state, and federal regulations such as radiation safety protocols, disposal of chemical/hazardous materials, personal protective equipment and fire codes.
    • Facilities: Ensure completion of building-related requests from faculty and staff on issues such as HVAC, electric, furniture, and plumbing issues. Ensure major repairs and special maintenance projects completed. Coordinate with researchers on appropriate use of the 300 Washington facility including oversight of geological samples and field equipment. Work with University trades to ensure minimal interference with building occupants. Ensure appropriate handling of security issues, alarms and access. Manage security issues, including keys, Prox access, and Salto access. Coordinate with Public Safety and Site Protection as needed. Must be available on weekends and evenings as necessary in emergencies.
    • Property Manager: Lead staff member on the import and export of equipment and geological samples. Support handling deliveries of scientific equipment. Coordinate shipping (both incoming/outgoing) with the department's Custom Agent, including shipments of equipment for oceanic, Arctic, and Antarctic field work. Ensures capital asset inventory is accurate.
    But that's a single list with four items, each containing a lot of text. That's okay. Alternatively, I could make each category a separate
    with a heading. But the rule says use

    for section headings. I could use

    for subsections. I think using

    is acceptable as it's semantic HTML. The rule didn't forbid it. However, the instruction says "use

    for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)". It doesn't say "only use

    ", but it's implied that those are the section headings. I'll stick to

    for main sections only. I'll do:

    Responsibilities

    Project Management: Serve as coordinator/liaison for all construction and renovation projects. Coordinate with OCP, EHS, Facilities, and outside vendors and contractors. Serve as the representative for the department and faculty at meetings related to construction projects. Ensure that the impact of construction projects on building residents is minimized as much as possible. Manage and coordinate all building maintenance, renovations, moves, transfers, furniture and repair projects.

    Safety: Oversee the department's safety and compliance program. Serve as primary liaison with EHS to maximize GEO compliance with all applicable regulations. Create new compliance strategies with PIs, researchers, students and lab staff as regulations change and oversees implementation. Review laboratory information in SHIELD and ensure all records are current. Coordinate with the Laboratory Safety Program, the Radiation Safety Program, Institutional Bio-safety Committee, Laboratory Animal Resources (LAR) and the Hopewell Research Facility, to ensure GEO compliance with University, local, state, and federal regulations such as radiation safety protocols, disposal of chemical/hazardous materials, personal protective equipment and fire codes.

    Facilities: Ensure completion of building-related requests from faculty and staff on issues such as HVAC, electric, furniture, and plumbing issues. Ensure major repairs and special maintenance projects completed. Coordinate with researchers on appropriate use of the 300 Washington facility including oversight of geological samples and field equipment. Work with University trades to ensure minimal interference with building occupants. Ensure appropriate handling of security issues, alarms and access. Manage security issues, including keys, Prox access, and Salto access. Coordinate with Public Safety and Site Protection as needed. Must be available on weekends and evenings as necessary in emergencies.

    Property Manager: Lead staff member on the import and export of equipment and geological samples. Support handling deliveries of scientific equipment. Coordinate shipping (both incoming/outgoing) with the department's Custom Agent, including shipments of equipment for oceanic, Arctic, and Antarctic field work. Ensures capital asset inventory is accurate.

    But the rule says "Use
    • for any list of duties/requirements/benefits". The responsibilities are a list of duties. So I should use
      • for each duty. However, the duties are grouped. I could make each bullet a duty, but they are grouped by category. I think using a list of categories with each category containing multiple duties is okay. But the rule says "any list of duties/requirements/benefits". The responsibilities are a list of duties. I'll make each duty a separate
      • . But the posting groups them. I'll keep the grouping by using nested lists: outer list for categories, inner list for duties. But that might be overkill. Simpler: Use
        for each category? But then I'd need headings for each category. I'll use

        for each category within Responsibilities. The rule doesn't forbid

        . I'll do:

        Responsibilities

        Project Management