Heat and Vent Mechanic

We need to output HTML fragment with sections for headings: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. Only include sections that have real specific content. We need to parse the posting. Posting Description: "HEAT AND VENT MECHANIC, Repair and Maintenance , is responsible for repairing and maintaining heating, ventilation, air-conditioning and refrigeration for the Institute’s buildings and equipment. Inspects and test heating, ventilation, and air conditioning systems to ensure proper functioning. Operates and maintains steam heating systems, HVAC controls, gas and oil fired heating systems and boilers, water treatment, and refrigeration systems. Trouble-shoots, repairs and install pneumatic electronic temperature control systems. Maintains repairs and rebuilds pumps, ice machines, air compressors and other building systems equipment. Receives work order assignments, orders materials and completes tasks accurately with detailed written comments provided on work orders upon completion. Completes time entry and returns work orders to supervisor on a daily basis with comments. Performs duties in accordance with MSDA’s, signage and general instructions. Performs scheduled preventative maintenance on building equipment, including but not limited to: lubricating components, changing filters, repacking valves, adjusting and replacing belts. Cleans work areas and maintains tools and equipment. Provides customers with information about the progress of work." That's responsibilities. Job Requirements: REQUIRED: Driver’s License; EPA Universal Recovery Certificate/License; five years of work experience in applicable trade/field, or formal controls training in mechanical operations and maintenance; High School Diploma or equivalent; and be able to move up to 50 pounds. PREFERRED: MA Oil Burner License and Certification; Sheet Metal License; MA Universal Refrigerant Recovery Certificate; MA Refrigeration Technician Certification; general understanding of building automation systems; knowledge of environmental rooms such as Harris Environmental; ability to read ladder diagrams, blue prints and schematics; or experience working in labs. Working Conditions: includes ascending/descending stairs, traversing the campus, moving about the jobsite and machinery to access equipment, and/or remaining stationary for extended periods of time. Work from ladders, scaffolds and other above ground locations such as roofs. Personal Protective Equipment must be worn as required by the specific assignment. Required to wear MIT provided ARC flash rated clothing. Environment contains dust, odors, and fumes, high levels of noise and temperature extremes. Work performed near steam and moving machinery and in tight areas and confined spaces such as manholes and crawl spaces. Work performed with and around chemicals and solvents. Some work performed in research labs and animal facilities. Some work performed outdoors in inclement weather. Employees who are assigned to an irregular shift are considered essential personnel in accordance with the MIT Policy on Emergency Closing or Early Release. During emergencies, these employees are excused from their regularly scheduled work only with the specific authorization of their supervisor, regardless of any public announcement that the Institute is closed. Must work all Institute holidays and closings. 9/28/2026 We need to decide sections: About the role (maybe a brief description). Responsibilities (list). Requirements (maybe combine required and preferred). Qualifications (maybe same as requirements). Skills (maybe list of skills). Benefits, Pay, Schedule: none given. So we should not include those sections. We need to avoid repeating job title as heading. Use

for section headings. We need to use

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

  for prose. We need to preserve all substantive information, not invent or summarize away detail. Remove boilerplate etc. There's no cookie/navigation etc. We need to include sections only when posting has real specific content. Thus we can have:

  About the role

  Heat and Vent Mechanic, Repair and Maintenance, responsible for repairing and maintaining heating, ventilation, air-conditioning and refrigeration for the Institute’s buildings and equipment.

  Then Responsibilities: list items. We need to extract each duty as bullet. From description: - repairing and maintaining heating, ventilation, air-conditioning and refrigeration for the Institute’s buildings and equipment. - Inspects and test heating, ventilation, and air conditioning systems to ensure proper functioning. - Operates and maintains steam heating systems, HVAC controls, gas and oil fired heating systems and boilers, water treatment, and refrigeration systems. - Trouble-shoots, repairs and install pneumatic electronic temperature control systems. - Maintains repairs and rebuilds pumps, ice machines, air compressors and other building systems equipment. - Receives work order assignments, orders materials and completes tasks accurately with detailed written comments provided on work orders upon completion. - Completes time entry and returns work orders to supervisor on a daily basis with comments. - Performs duties in accordance with MSDA’s, signage and general instructions. - Performs scheduled preventative maintenance on building equipment, including but not limited to: lubricating components, changing filters, repacking valves, adjusting and replacing belts. - Cleans work areas and maintains tools and equipment. - Provides customers with information about the progress of work. We can list these as
  • ... etc. Then Requirements: maybe separate Required and Preferred? Could combine into one Requirements section with subheadings? But we only have h3 headings allowed; we could have a single Requirements section with paragraphs for required and preferred. Or we could split into Requirements and Qualifications? The instruction says use headings for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). So we can have both Requirements and Qualifications if content exists. But we need to avoid filler. We have required qualifications: Driver’s License; EPA Universal Recovery Certificate/License; five years of work experience in applicable trade/field, or formal controls training in mechanical operations and maintenance; High School Diploma or equivalent; and be able to move up to 50 pounds. Preferred: MA Oil Burner License and Certification; Sheet Metal License; MA Universal Refrigerant Recovery Certificate; MA Refrigeration Technician Certification; general understanding of building automation systems; knowledge of environmental rooms such as Harris Environmental; ability to read ladder diagrams, blue prints and schematics; or experience working in labs. We could put Required under Requirements heading, Preferred under Qualifications heading (or Skills). But Qualifications could be for preferred qualifications. Skills could be for abilities like reading ladder diagrams etc. However we need to avoid thin sections. Perhaps combine required and preferred into Requirements, and then Skills for abilities like reading ladder diagrams, blueprints, schematics, understanding building automation, knowledge of environmental rooms, experience in labs. But we need to preserve all info. Better: Have Requirements section with required items as list, and then a paragraph for preferred items. Or have Requirements and Qualifications both. Given the instruction: "Prefer a few substantive sections over many thin ones." So maybe we combine required and preferred into one Requirements section, and maybe Skills for abilities like reading ladder diagrams etc. But we already have many abilities in preferred. Let's think: The posting includes both required and preferred qualifications. We could have:

    Requirements

    Required: ...

    Preferred: ...

    That's substantive. Then we might not need Qualifications or Skills separately. But we need to follow the instruction: "use

    for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." It doesn't forbid using other headings, but suggests those are typical. We can use only those we need. Thus we can have About the role, Responsibilities, Requirements. We need to ensure we don't repeat job title as heading. Already not. We need to not put Job ID/requisition numbers as headings - none. We need to output only HTML fragment. Let's craft. About the role: maybe a short paragraph summarizing role. Responsibilities: list. Requirements: list required and preferred. We need to preserve all substantive information: include details like "MSDA’s" (maybe MSDS?), but we keep as is. Also include working conditions? The posting includes Working Conditions section with details. Should we include that? The instruction says include a section only when posting has real specific content for it. Working conditions is specific content. Should we create a section for Working Conditions? The allowed headings list does not include Working Conditions, but we could still use

    for a custom heading? The instruction says use

    for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). It gives examples but not exclusive list. It says "use

    for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." This implies we should use those headings for those sections if they exist. For other sections like Working Conditions, we could still use

    but maybe not recommended. However we need to preserve all substantive information; we could incorporate working conditions into Responsibilities or Requirements? But it's distinct. Better to add a section for Working Conditions using

    Working Conditions

    . The instruction didn't forbid other headings; it just gave examples. It says "use

    for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." So we can use

    for any section heading, but we should follow the pattern. So we can add Working Conditions. Similarly, we could add a section for "Working Conditions". That would preserve info. Thus sections: About the role, Responsibilities, Requirements, Working Conditions. We need to avoid thin sections: Working Conditions has substantive content. Now we need to format. Let's extract Working Conditions details: "Working conditions include ascending/descending stairs, traversing the campus, moving about the jobsite and machinery to access equipment, and/or remaining stationary for extended periods of time. Work from ladders, scaffolds and other above ground locations such as roofs. Personal Protective Equipment must be worn as required by the specific assignment. Required to wear MIT provided ARC flash rated clothing. Environment contains dust, odors, and fumes, high levels of noise and temperature extremes. Work performed near steam and moving machinery and in tight areas and confined spaces such as manholes and crawl spaces. Work performed with and around chemicals and solvents. Some work performed in research labs and animal facilities. Some work performed outdoors in inclement weather. Employees who are assigned to an irregular shift are considered essential personnel in accordance with the MIT Policy on Emergency Closing or Early Release. During emergencies, these employees are excused from their regularly scheduled work only with the specific authorization of their supervisor, regardless of any public announcement that the Institute is closed. Must work all Institute holidays and closings. 9/28/2026" We need to preserve all that. The date at end maybe metadata; we could include as part of working conditions paragraph or drop? It's not boilerplate; it's a date maybe posting date. Could be considered metadata; but instruction says do NOT put Job ID/requisition numbers as headings — fold minor metadata into a short

    or drop it. The date could be considered minor metadata; we could fold into a short p or drop. Probably we can include it as part of the working conditions paragraph. Now we need to avoid repeating content. Let's craft HTML. We'll have:

    About the role

    Heat and Vent Mechanic, Repair and Maintenance, responsible for repairing and maintaining heating, ventilation, air‑conditioning and refrigeration for the Institute’s buildings and equipment.

    Responsibilities

    • Repairing and maintaining heating, ventilation, air‑conditioning and refrigeration for the Institute’s buildings and equipment.
    • Inspecting and testing heating, ventilation, and air conditioning systems to ensure proper functioning.
    • Operating and maintaining steam heating systems, HVAC controls, gas and oil fired heating systems and boilers, water