Facilities Maintenance I-1245

The user wants me to convert this job posting into clean semantic HTML following specific rules. Let me analyze the content and structure it appropriately. First, I need to identify the sections: 1. Job Summary - this is prose, should be

2. Job Responsibilities - this is a list of duties, should be

• 3. Core Skills/Competency Requirements - this is a list, should be
  • 4. Education - "Preferred High School Diploma/GED" - this is a requirement 5. Experience - "Preferred 1-3 Years" - this is a requirement 6. Physical Demands - this is a table-like structure with checkboxes I need to use

    for section headings. The rules say: use

    for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). I should not repeat the job title as a heading. The page already shows it. I should not put Job ID / requisition numbers as headings — fold minor metadata into a short

    or drop it. There's no Job ID here. Preserve ALL substantive information; do NOT invent or summarize away detail. Remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. There's none of that here. IMPORTANT: 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") and never create Pay/Schedule/Benefits sections unless the posting actually states them. Prefer a few substantive sections over many thin ones. Output ONLY the HTML fragment — no /, no markdown code fences. Now, let me structure the sections: - About the role (or Job Summary) - prose - Responsibilities - list - Requirements (or Qualifications) - could combine Education, Experience, and Core Skills - Physical Demands - this is specific content, should include The posting has "Core Skills/Competency Requirements" as a list, "EDUCATION Preferred High School Diploma/GED", "Experience Preferred 1-3 Years", and "PHYSICAL DEMANDS" with a table. I should create sections for: 1. About the role (Job Summary) 2. Responsibilities 3. Requirements (or Qualifications) - including Core Skills, Education, Experience 4. Physical Demands But the rules say: use

    for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). So I can use "Requirements" or "Qualifications". Since there are multiple sub-parts, maybe "Requirements" as a heading, then sub-lists? But the rules say use

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

      for prose. It doesn't say to nest headings. I think I should have separate sections for each distinct category if they have content. However, "Prefer a few substantive sections over many thin ones." So maybe combine Core Skills, Education, Experience under "Requirements" or "Qualifications". But they are distinct: Core Skills is a list, Education is a single line, Experience is a single line. Could make a "Requirements" section with a list that includes all? But the Education and Experience are not bullet points in the original; they are separate lines. I could present them as a list. Alternatively, create separate sections: "Skills", "Education", "Experience". But that might be too many thin sections. The rules say "never emit a heading followed by filler/placeholder text". Each has real content. Let's see: Core Skills/Competency Requirements has 6 bullet points. Education has one line. Experience has one line. Physical Demands has a table. I think I'll do: - About the role - Responsibilities - Requirements (with sub-lists? But HTML doesn't have sub-headings in fragment. I could use

      for each? But the rule says use

      for section headings. Could have multiple

      sections. Better to have:

      About the role

      ...

      Responsibilities

      ...

      Requirements

      ... core skills ...

      Education: High School Diploma/GED preferred

      Experience: 1-3 years preferred

      Physical Demands

      ... how to represent the table? The original has a table with columns: Never, Occasionally, Frequently, Continuously, and rows with X marks. I need to represent this in HTML. Could use a but the rules didn't mention tables. It says use
      • for any list, and

        for prose. But a table is not a list. However, the physical demands are a list of activities with frequency. Could represent as a list of items with frequency. For example: "Bending: Frequently", "Sitting: Never", etc. But the original has checkboxes. I think a table is appropriate semantic HTML for tabular data. The rules didn't forbid tables. They only specified

        ,

        • ,

          . But they didn't say "only use these tags". They said "use

          for section headings... Use

          • for any list... and

            for prose." It doesn't say you cannot use other tags. However, to be safe, maybe represent as a list. But the data is tabular. I'll use a simple table with , , , , , . That's semantic. But the instruction: "Output ONLY the HTML fragment — no /, no markdown code fences." So I can include a table. Let's craft the HTML. First, Job Summary: "The Facilities Maintenance Technician I provides general maintenance support to ensure a clean, safe, and functional workplace. This entry-level role involves routine inspections, basic repairs, and support for a wide range of facility-related tasks. Working under close supervision, the Technician I performs hands-on work related to lighting, HVAC filters, minor plumbing, carpentry, and general upkeep of shared and exterior areas. It is an ideal starting point for individuals seeking to develop technical maintenance skills while contributing to daily facility operations." That's one paragraph? Actually it's multiple sentences. Could be one

            or multiple. I'll keep as one

            . Responsibilities: list of 11 items. Each bullet. Core Skills/Competency Requirements: list of 6 items. Education: "Preferred High School Diploma/GED" - I'll include as a paragraph or list item under Requirements. Experience: "Preferred 1-3 Years" - same. Physical Demands: table with headers: Activity, Never, Occasionally, Frequently, Continuously. Rows: Bending, Sitting, Standing, Walking, Lifting/Carrying, Reaching, Pushing/Pulling. With X in appropriate columns. From the text: "PHYSICAL DEMANDS (check applicable box with “X”) Never Occasionally Frequently Continuously Bending X Sitting X Standing X Walking X Lifting/Carrying X Reaching X Pushing/Pulling X" It seems the columns are Never, Occasionally, Frequently, Continuously. And each row has an X in one column. For Bending: X under Frequently? Actually the line "Bending X" - but there are four columns. The formatting is messy. Let's parse: The line "Never Occasionally Frequently Continuously" are column headers. Then each row: "Bending X" - but where is the X? Probably under Frequently? The text: "Bending X Sitting X Standing X Walking X Lifting/Carrying X Reaching X Pushing/Pulling X". It might be that each activity has an X in one of the columns, but the column alignment is lost. In the original, it's likely a table with checkboxes. Since we can't know exactly which column, but the X appears after the activity name. Could be that all are "Frequently"? But "Sitting X" maybe Never? Actually typical physical demands: Bending frequently, Sitting occasionally, Standing frequently, Walking frequently, Lifting/Carrying frequently, Reaching frequently, Pushing/Pulling frequently. But we don't know. The safest is to replicate the data as presented: list each activity with the note "X" but we don't know frequency. However, the posting includes the column headers. I think we should present as a table with the columns and put "X" in the appropriate cell based on the order? But the text doesn't indicate which column. The line "Bending X" might mean there is an X in the first column? But there are four columns. The text is likely a copy-paste from a table where each row has four cells, one with X. Since we can't reconstruct, maybe we should just list the activities and note that frequency is indicated in the original table. But the rule: "Preserve ALL substantive information". So we must include the physical demands data. I'll create a table with the headers and rows, and put "X" in the cell that corresponds to the column where the X appears in the source? But we don't have that info. Looking at the raw text: "PHYSICAL DEMANDS (check applicable box with “X”) Never Occasionally Frequently Continuously Bending X Sitting X Standing X Walking X Lifting/Carrying X Reaching X Pushing/Pulling X" It might be that the X is under "Frequently" for all? But "Sitting X" could be "Occasionally". Without the original formatting, it's ambiguous. However, the user expects us to output the HTML fragment based on the given text. We have to work with what's given. Perhaps we can represent as a list: "Bending: X", "Sitting: X", etc. But that loses the column headers. Alternatively, we can create a table with two columns: Activity and Frequency, and put "X" as frequency? Not good. Maybe the original table has the X in the "Frequently" column for all? Let's assume the X is under "Frequently" because the text "Bending X" appears after "Continuously"? Actually the headers are "Never Occasionally Frequently Continuously". Then the rows: "Bending X" - if the X is under Frequently, then there would be spaces. But the text is linear. Given the ambiguity, I'll represent it as a table with the headers and for each activity, put "X" in the "Frequently" column as a guess? But that's inventing data. The rule: "do NOT invent or summarize away detail." So I must not guess. Better to present the data as a list of activities with a note that the frequency is marked with X in the original table. But that's summarizing. Perhaps the intended representation is to keep the table structure as closely as possible. Since the input is plain text, maybe the user expects us to create a table with the columns and rows, and put "X" in the cell that corresponds to the position? But we don't have positions. Wait, the text: "Never Occasionally Frequently Continuously Bending X Sitting X Standing X Walking X Lifting/Carrying X Reaching X Pushing/Pulling X". This could be interpreted as: The first row after headers is "Bending" and then "X" under "Never"? But there are four columns, so each row should have four entries. The text only shows one "X" per row. Maybe the X is in the first column? But "Bending X" - if X is under Never, that would mean bending never? That seems wrong. Usually bending is frequently. Maybe the X is under "Frequently"? The order of