FACILITIES SUPERVISOR - 10202026-81811

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 (About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule) 2. Use

• for lists 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 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: - Job Information: State of Tennessee, Opening/Closing dates, Salary (Monthly/Annually), Job Type, City/State, Department, Location details - MVR screening, criminal background check - Qualifications: Education and Experience, Necessary Special Qualifications, Examination Method - Overview - Responsibilities (list of duties) - Competencies (KSA's): Competencies, Knowledge, Skills, Abilities, Tools & Equipment I need to structure this into appropriate sections. The job title is not given explicitly but appears to be a Facilities Supervisor or similar role. Since the page already shows the title, I won't include it as a heading. I'll create sections for: - Overview (prose) - Responsibilities (list) - Qualifications (with subsections for Education/Experience, Special Qualifications, Examination Method) - Competencies (KSA's) - could break into Knowledge, Skills, Abilities, Tools & Equipment - Pay (since salary is provided) - Schedule (job type is Full-Time, but maybe not enough for a schedule section? The posting says "Job Type Full-Time" - that could be schedule) - Maybe a section for "Additional Information" for the MVR screening, background check, location details But the rules say: never create Pay/Schedule/Benefits sections unless the posting actually states them. The posting states salary and job type (Full-Time). So I can include Pay and Schedule sections. Also, the opening/closing dates are metadata - I can fold into a short

  or drop. I'll include a brief "Job Details" paragraph with key metadata. Let me structure: 1.

  Overview

  with

  for the overview text. 2.

  Responsibilities

  with
  • for each bullet. 3.

    Qualifications

    with subsections? The rules say use

    for section headings. I could use

    for Qualifications and then

    and

    inside. But the qualifications have multiple parts: Education and Experience, Necessary Special Qualifications, Examination Method. I could make them sub-headings using

    ? The rules only mention

    for section headings. It doesn't forbid

    . But to keep it simple, I'll use

    for Qualifications and then list the details in

    and

    . 4.

    Competencies

    with subsections for Competencies, Knowledge, Skills, Abilities, Tools & Equipment. Could use

    or just list them as separate lists under Competencies. 5.

    Pay

    with salary details. 6.

    Schedule

    with job type Full-Time. 7. Maybe

    Additional Requirements

    for MVR screening, background check, license requirement. But the rules: "Prefer a few substantive sections over many thin ones." So I should combine where appropriate. Let me think: The posting has distinct sections: Overview, Responsibilities, Qualifications, Competencies (KSA's). Also Pay and Schedule are given. The metadata (dates, location, department) can be in a brief introductory paragraph. I'll create: - A brief introductory paragraph with key details: location, department, dates, salary, job type. - Overview - Responsibilities - Qualifications - Competencies - Pay - Schedule But the rules say: "Do NOT put Job ID / requisition numbers as headings — fold minor metadata into a short

    or drop it." So I'll fold the metadata into a short

    at the top. Now, for Qualifications: The posting has "Education and Experience", "Necessary Special Qualifications", "Examination Method". I'll include them as a list under Qualifications. For Competencies: The posting lists "Competencies", "Knowledge", "Skills", "Abilities", "Tools & Equipment". I'll include them as separate lists under Competencies. Now, I need to ensure I don't include any boilerplate. The posting seems clean. Let me write the HTML. First, a paragraph with metadata:

    Location: Tiptonville, TN | Department: Correction | Opening: 10/20/2026 | Closing: 11/02/2026 | Job Type: Full-Time | Salary: $5,151.00 - $6,437.00 monthly ($61,812.00 - $77,244.00 annually)

    But the salary is already in Pay section. Maybe include salary only in Pay section. I'll include location, department, dates, job type in the intro paragraph. Then sections. I'll use

    for each section. Let's draft:

    Overview

    Under general supervision, is responsible for supervisory facilities maintenance work of average difficulty; and performs related work as required. An employee in this class supervises a moderate-sized staff of building maintenance and skilled craft workers performing carpentry, electrical, plumbing, painting, boiler operation and related duties; and acts as the assistant to the facilities maintenance manager at a large facility or supervises a crew of workers performing roving maintenance at several facilities. This class differs from that of Facilities Manager 1 in that an incumbent of the latter is in charge of maintenance at a moderate-sized facility and may supervise Facilities Supervisors.

    Responsibilities

    • Ensures environmental, occupational, safety, and health compliance according to state, federal, and local guidelines.
    • Reads and interprets sketches, diagrams, schematics, and blueprints for facility maintenance, repairs, and utility location.
    • Oversees and performs various maintenance tasks, including plumbing, electrical, HVAC/R, appliances, structural, environmental, and landscape management.
    • Conducts facility inspections to assess maintenance and repair needs for systems like fire alarms, HVAC/R, electrical, plumbing, and structural components.
    • Trains and supervises maintenance staff, ensuring facility readiness and conducting performance evaluations to promote productivity.
    • Manages supply inventory, forecasts material needs, and prepares purchase requests for equipment, materials, and supplies.
    • Reports maintenance and repair issues to relevant personnel to maintain safe and efficient facility operations.
    • Monitors contractor performance to ensure security and proper execution of facility repairs.
    • Assigns and prioritizes daily work orders for the maintenance staff, ensuring efficient workflow and task completion.

    Qualifications

    Education and Experience: Education equivalent to graduation from a standard high school and experience equivalent to substantial (five or more years of) increasingly responsible and skilled full-time building maintenance or construction work in one or more of the following areas: carpentry, plumbing, electrical, painting, masonry, heating, ventilating, refrigeration, or other related area, including at least one year of lead or supervisory experience; qualifying full-time building maintenance or construction work may be substituted for the required education on a year-for-year basis, to a maximum of two years.

    Necessary Special Qualifications: A valid motor vehicle operator's license may be required for employment in some positions.

    Examination Method: Education and Experience, 100%, for Preferred Service positions.

    Competencies

    Competencies

    • Manages Ambiguity
    • Directs Work
    • Interpersonal Savvy
    • Business Insight
    • Decision Quality

    Knowledge

    • Building and Construction

    Skills

    • Reading Comprehension
    • Writing
    • Active Learning and Listening
    • Equipment Maintenance
    • Troubleshooting

    Abilities

    • Speech Clarity

    Tools & Equipment

    • Computer, Telephone
    • Hand/Power Tools and Landscaping Equipment
    • Vehicles
    • Radio
    • Scanner, Copy/Fax Machine, Printer

    Pay

    Monthly: $5,151.00 - $6,437.00

    Annually: $61,812.00 - $77,244.00

    Schedule

    Full-Time

    Additional Requirements

    • A Motor Vehicle Records (MVR) screening will be conducted prior to employment.
    • This position requires a criminal background check; you may be required to provide information about your criminal history in order to be considered for this position.
    But the rules say: "Use

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

    . However, using

    for subsections might be okay, but to be safe, I could keep all as

    and use

    for subheadings. But the competencies have multiple categories. I could make each category a separate

    ? That would create many thin sections. The rules say "Prefer a few substantive sections over many thin ones." So I should keep Competencies as one section with sub-lists. I'll use

    for Competencies and then use for subcategories within

    or just list them with labels. Alternatively, I can structure Competencies as a list of categories with sub-items. But HTML doesn't have a good way without subheadings. I'll use

    for subcategories; it's still semantic and not prohibited. The instruction only says "use

    for section headings" but doesn't forbid other heading levels. I think it's fine. But to be safe, I'll use

    for main sections only, and for subcategories I'll use

    Category

    followed by

    . Let me adjust. Also, the "Additional Requirements" section might be considered boilerplate? But it's specific to this posting: MVR screening and criminal background check. It's not generic EEO boilerplate. So I'll keep it. Now, the intro paragraph: I'll include location,