Intern, MEP

We need to output HTML fragment with headings

for sections: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. Only include sections that have real specific content. Must not repeat job title as heading. Must not include Job ID etc. Must preserve all substantive info, no invented or summarizing away detail. Remove boilerplate: cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, application instructions. Also remove "Please apply and upload a copy of your resume to be considered for all openings with Halff." That's application instruction; remove. Also remove "Halff is a drug-free workplace..." etc (EEO). Remove "All qualified applicants will receive consideration..." etc. Remove "This offer of employment is contingent upon..." etc. Remove "Interns are paid hourly and work full-time (40 hours/week), typically 8a-5p Monday through Friday." This appears twice; we need to keep schedule info maybe under Schedule section. Also "Halff does not pay for or provide housing for Internships." That's a detail maybe under Benefits? Actually it's a note about housing not provided; could be under Benefits? Might be better to include under Benefits as a note? But it's not a benefit; it's a limitation. Could be placed under About the role? Probably better to include under About the role or maybe under Schedule? The instruction: include a section ONLY when posting has real, specific content for it. So we need to extract schedule: "Interns are paid hourly and work full-time (40 hours/week), typically 8a-5p Monday through Friday." Also start and end dates: "The Internship will begin on June 7th, 2027, and conclude on August 13th, 2027." That's schedule info as well. So we can have a Schedule section with those details. Pay: "Interns are paid hourly" but no specific rate; "Salary is competitive and commensurate with experience." That's not specific; we should not create Pay section unless posting actually states them. The rule: never create Pay/Schedule/Benefits sections unless the posting actually states them. For Pay, we have "Interns are paid hourly" and "Salary is competitive and commensurate with experience." That's vague; but "Interns are paid hourly" is a statement about pay type, but not a specific amount. The rule says: 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. Since the posting does not give a specific pay rate or range, we should not create a Pay section. However we could include pay info under About the role? But the instruction says we should not create Pay section unless posting actually states them. It does state that interns are paid hourly, which is a statement about pay. But is that enough? The rule says "never create Pay/Schedule/Benefits sections unless the posting actually states them." It does state that interns are paid hourly, so we could include a Pay section with that info. However also we must avoid filler like "commensurate with experience". The posting also says "Salary is competitive and commensurate with experience." That's filler; we should not include that. So we could include Pay section with just "Interns are paid hourly." That is specific enough? Might be considered not filler. I'd lean to include Pay section with that line. Benefits: The posting lists benefits under "We Offer Excellent Benefits, Including But Not Limited To ..." then a list. That's specific content. So we should include Benefits section with that list. Schedule: we have start/end dates and hours. So include Schedule section. About the role: we have description: "MEP Intern Halff is actively seeking a Mechanical or Electrical Engineering Intern for our MEP team in San Antonio, TX. The Intern will assist in electrical engineering, designing, and producing of commercial, Industrial, and Institutional projects. The Intern will assist with work on HVAC and plumbing design projects." That's about the role. Also maybe include "What You Will Do" as Responsibilities. Responsibilities: list from "What You Will Do" bullet points. Requirements: maybe from "What You Will Need". That's requirements. Qualifications: maybe overlapping with requirements; but we can treat "What You Will Need" as Requirements/Qualifications. The instruction: use headings for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). We need to decide which to use. We have content for About the role, Responsibilities, Requirements, Qualifications (maybe same as Requirements), Skills (communication skills, relationship building, self-motivated, organization skills). Also we have "Experience or familiarity with Revit and AutoCAD is necessary" which could be under Requirements or Skills. We'll allocate. We must not repeat job title as heading. So no heading for "MEP Intern". Good. We must not include duplicated lines. Ensure we don't repeat same info. We must remove boilerplate: EEO lines, drug-free workplace, etc. Also remove "Click here for a more comprehensive list of Halff's benefits" maybe keep as part of benefits? It's a link; we can keep the list but maybe drop the link instruction. The instruction: remove application instructions, cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines. The "Click here for a more comprehensive list of Halff's benefits" is navigation/link; we should drop it. Also "Learn more about Halff’s MEP services, check out some of our projects, and meet our team" is promotional; maybe drop as boilerplate? It's not required substantive info; could be considered navigation. Safer to drop. Also "Company Overview" paragraphs about Halff history etc. That's not specific to the internship; could be considered boilerplate? The instruction: preserve ALL substantive information; do NOT invent or summarize away detail. The company overview is substantive about the company but not about the role. However it's not required to be kept? The instruction says remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. It does not explicitly say to remove company overview. But we might keep it under About the role? However the About the role section should be about the role, not company overview. Could we include a separate section like "About Halff"? Not in allowed headings. The allowed headings list does not include "Company Overview". So we should not create a heading for it. We could fold relevant details into About the role? But the company overview is not about the role. The instruction: "Prefer a few substantive sections over many thin ones." So we might omit the company overview entirely, as it's not required for the internship posting. However the instruction says preserve ALL substantive information; do NOT invent or summarize away detail. If we omit company overview, are we losing substantive information? It's about the company, not the internship. Might be considered not essential to the job posting. But the rule says preserve ALL substantive information; but maybe they mean substantive information about the job. The company overview is generic; could be considered boilerplate. I'd lean to omit it to keep focused. Similarly "Halff’s MEP Advantage" bullet points: "Our professionals aim to design buildings that use less energy, generate less waste and cost less to maintain. Our staff knows there isn’t one right answer to MEP challenges. We understand the demands of managing multiple projects under Indefinite Delivery/Indefinity Quantity contracts." That's somewhat about the company but could be considered relevant to the role. Could be included under About the role or maybe as a separate section? Not in allowed headings. Could be folded into About the role. We'll produce sections: About the role, Responsibilities, Requirements, Skills, Benefits, Pay, Schedule. Possibly Qualifications not needed if we merge with Requirements. But we have both Requirements and Qualifications allowed; we could use Requirements for education/experience, Qualifications for skills? But we also have Skills heading. Let's allocate: - About the role: brief description of internship, location, team, projects, start/end dates? Actually dates go to Schedule. So About the role: "MEP Intern Halff is actively seeking a Mechanical or Electrical Engineering Intern for our MEP team in San Antonio, TX. The Intern will assist in electrical engineering, designing, and producing of commercial, Industrial, and Institutional projects. The Intern will assist with work on HVAC and plumbing design projects." Also maybe include "Halff’s MEP Advantage" points? Could add as part of About the role: "Our professionals aim to design buildings that use less energy, generate less waste and cost less to maintain. Our staff knows there isn’t one right answer to MEP challenges. We understand the demands of managing multiple projects under Indefinite Delivery/Indefinity Quantity contracts." That's okay. - Responsibilities: list from "What You Will Do". We'll convert each sentence to

. - Requirements: education: "Pursuing Bachelor’s or Master’s Degree in Mechanical or Electrical Engineering or ABET accredited equivalent Engineering degree". Also "Experience or familiarity with Revit and AutoCAD is necessary". Could also include "Great communication skills" etc but those are skills. - Qualifications: maybe we could treat as same as Requirements; but to avoid thin sections, we could omit Qualifications and put those under Requirements or Skills. Since we have Skills heading, we can put communication, relationship building, self-motivated, organization skills under Skills. - Skills: list those. - Benefits: list from "We Offer Excellent Benefits, Including But Not Limited To ..." then the list items. We'll include each as

. We'll exclude the "Click here for a more comprehensive list..." line. - Pay: "Interns are paid hourly." - Schedule: include start date June 7th, 2027, end date August 13th, 2027, and work hours: full-time (40 hours/week), typically 8a-5p Monday through Friday. We must not repeat duplicated lines: The sentence about interns paid hourly appears twice; we will include only once in Pay section. We must not include application instructions: "Please apply and upload a copy of your resume to be considered for all openings with Halff." Remove. We must not include EEO lines etc. Now produce HTML fragment. Use

for each section heading. Use

• for lists. Use

  for prose. We must not include or . Just the fragment. Let's craft. About the role: maybe two paragraphs: first about seeking intern, second about MEP Advantage. Responsibilities: list items. Requirements: list items (education, Revit/AutoCAD). Skills: list items (communication skills, relationship and team building skills, self-motivated, strong organization skills). Benefits: list items. Pay:

  Interns are paid hourly.

  Schedule:

  Internship runs from June 7th, 2027 to August 13th, 2027. Interns work full-time (40 hours/week), typically 8a-5p Monday through Friday.

  Check for any leftover boilerplate: "Halff does not pay for or provide housing for Internships." This is a detail about housing not provided. Where to put? Could be under Benefits as a note? But it's not a benefit; it's a limitation. Could be under About the role or Schedule? Perhaps add a sentence in Schedule or About the role: "Halff does not pay for or provide housing for Internships." We'll include it as a separate

  under About the role or maybe under Benefits as a note? I'd add a short paragraph under About the role after the advantage points: "Note: Halff does not pay for or provide housing for Internships." Make sure not to duplicate. Now ensure we didn't include any filler like