Mechanical Project Engineer

We need to output HTML fragment with sections: About the role? Actually the posting includes description about role. We need headings: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. Only include sections that have real specific content. We need to parse content: - About the role: The paragraph after "As a Project Engineer, you’ll be the operational hub..." That's description. Could be "About the role". We'll include that. - Responsibilities: The bullet list under "What You’ll Do". That's responsibilities. - Requirements: The bullet list under "What You’ll Bring". That's requirements/qualifications. Could split into Requirements and Qualifications? The instruction says we can have sections like Requirements, Qualifications, Skills. We need to decide based on content. The "What You’ll Bring" includes background, industry exposure, tools, strengths. Could treat as Requirements (background, experience) and Qualifications (tools, strengths) or Skills (tools). But we need to avoid thin sections. Perhaps combine into one "Requirements" section covering background, experience, tools, strengths. Or we could split: Requirements (background, experience), Qualifications (tools, strengths). But we need to avoid filler. Let's see content: Background: Construction Management or Mechanical Engineering degree and 3–5 years in commercial construction or 10+ years relevant mechanical construction experience in lieu of degree. Industry exposure: HVAC/Plumbing mechanical contractor experience on mid-to-large commercial projects (preferred). Tools: Bluebeam, MS Project, Excel/Word; familiarity with BIM/CADD workflows (Revit/Navis/AutoCAD a plus). Strengths: Organized, detail-driven, great follow-through; clear written/verbal communication; collaborative with GC/owner and trade partners. Nice-to-Haves (Preferred): Experience with submittal workflows, procurement, and vendor negotiations. Exposure to estimating/takeoffs and preconstruction reviews. Understanding of safety programs and quality systems in a self-perform environment. Thus we have Requirements (background, industry exposure), Qualifications (tools, strengths), Skills maybe tools? But we can combine. Benefits: There's a "Benefits Overview" with Health & Welfare, Time Off Benefits, Financial Benefits. So we have benefits content. Pay: There's a "Pay Disclosure & Considerations" section but no actual pay range. It says "Where pay ranges are indicated, please note that a successful candidate’s exact pay will be determined based..." No actual numbers. According to rule: never create Pay/Schedule/Benefits sections unless the posting actually states them. Since no specific pay range or amount given, we should NOT include Pay section. Schedule: No schedule info given. So omit. Thus sections: About the role, Responsibilities, Requirements, Qualifications, Benefits. Possibly also "Nice-to-Haves" could be part of Qualifications or separate but we can incorporate. We must not repeat job title as heading. No Job ID etc. We need to use

for section headings. Use

• for any list of duties/requirements/benefits. Use

  for prose. We need to preserve all substantive information; do not invent or summarize away detail. Remove boilerplate: cookie/navigation/legal/EEO/equal-opportunity/scam-warning, duplicated lines, application instructions. Also remove "About Legence" maybe? That's company description but not required? It's substantive about company but not role. The instruction: preserve ALL substantive information; do not invent or summarize away detail. The "About Legence" is about the company, could be considered substantive. However we need to decide if we include it. The sections we have are limited to role-specific headings; but we could include a section "About the Company" if we want, but not in prescribed headings list. The instruction says use headings for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). It doesn't forbid other headings, but says use

  for section headings (e.g. About the role, Responsibilities...). It implies we should use those headings for those sections if present. It doesn't say we cannot add other headings, but better to stick to those. The "About Legence" could be considered "About the role"? No. Could be considered "About the company" but not in list. Might be okay to include as a

  without heading? But we need to preserve all substantive information. Could embed it in a

  under maybe no heading? The instruction: "Use

  for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." It doesn't forbid other headings, but suggests those are the expected ones. Safer to include company description as a

  without a heading, maybe after the role description? But we need to keep structure. We could add a section "About the Company" using

  but not in list; risk of violating instruction? The instruction says use

  for section headings (e.g. About the role, Responsibilities...). It doesn't say you cannot use other headings, but the examples are given. I'd interpret that we should use those headings for those sections if present; other headings maybe not needed. But we can still include a heading for company info if we want, but it's not prohibited. However to be safe, we can include company description as a

  under no heading, maybe after the role description. But we need to preserve all substantive information: includes "Yearout Mechanical, a Legence Company Yearout Mechanical is a New Mexico based company..." and "About Legence" paragraph. We'll include that as a

  maybe under a heading "About the Company"? But if we add heading not in list, maybe okay. 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 these". So we can add other headings as needed. I'll add a heading "About the Company". That seems reasonable. Now we need to remove boilerplate: EEO, Equal Employment Opportunity, Employment Eligibility, Third-Party Recruiting Disclaimer, Reasonable Accommodations, etc. Also remove "Pay Disclosure & Considerations" because no actual pay. Remove "Equal Employment Opportunity Employer" etc. Remove "If you need assistance..." etc. Remove "Third-Party Recruiting Disclaimer". Remove "Employment Eligibility". Remove "Pay Disclosure & Considerations". Remove "Equal Employment Opportunity Employer". Also remove "Reasonable Accommodations" maybe? It's a boilerplate but could be considered substantive? It's about accommodations; but it's generic. Might be considered boilerplate; we can remove. Also remove "Nice-to-Haves (Preferred)"? It's substantive; we can keep as part of Qualifications or separate list. We need to format lists. Let's extract content: About the role paragraph: "As a Project Engineer, you’ll be the operational hub for complex mechanical (HVAC/Plumbing) projects—partnering with Project Managers and field teams to keep scope, schedule, cost, quality, and safety on track. You’ll touch everything from documentation and scheduling to BIM/CADD coordination, vendor management, and client communication." We'll put that in

  under

  About the role

  . Responsibilities list (What You’ll Do): - Project controls & docs: Own RFIs, submittals, change orders (COR/CO), meeting minutes, and logs. - Scheduling: Update master schedules (labor, equipment, fabrication, rentals); flag risks and pull-forward options. - Cost management: Support job cost control, vendor pricing, POs, and progress billings. - Field coordination: Assist QA/QC, pre-task/hazard analyses, site walks, and toolbox talks; drive punchlist closure. - BIM/CADD: Coordinate model updates and field integration with VDC/CADD partners. - Procurement: Source materials, track deliveries, resolve shortages; maintain vendor relationships. - Client/GC/Subs: Prep for and participate in project meetings; support subcontractor selection and oversight. - Closeout: Assemble O&M manuals, as-builts, and final turnover documents. We'll put each as
• . Requirements (What You’ll Bring background and industry exposure): - Background: Construction Management or Mechanical Engineering degree and 3–5 years in commercial construction or 10+ years relevant mechanical construction experience in lieu of degree. - Industry exposure: HVAC/Plumbing mechanical contractor experience on mid-to-large commercial projects (preferred). We'll put as
• . Qualifications (Tools, Strengths, Nice-to-Haves): Tools: Bluebeam, MS Project, Excel/Word; familiarity with BIM/CADD workflows (Revit/Navis/AutoCAD a plus). Strengths: Organized, detail-driven, great follow-through; clear written/verbal communication; collaborative with GC/owner and trade partners. Nice-to-Haves (Preferred): - Experience with submittal workflows, procurement, and vendor negotiations. - Exposure to estimating/takeoffs and preconstruction reviews. - Understanding of safety programs and quality systems in a self-perform environment. We could combine Tools and Strengths as separate
• or combine into one list with sub-items? Better to keep each as separate
• with bold label? But we need to preserve detail; we can include the label inside the
• . Eg
• Tools: Bluebeam, MS Project, Excel/Word; familiarity with BIM/CADD workflows (Revit/Navis/AutoCAD a plus).
Similarly for Strengths. Nice-to-Haves could be a separate
under a heading? But we only have Qualifications section; we can include them as
• items. Thus Qualifications
  with three items: Tools, Strengths, Nice-to-Haves (Preferred) with sublist? Could nest but not required. Simpler: each as
  • with the description. Benefits: We have Benefits Overview: Health & Welfare: Company Paid medical, dental, vision, prescription drug, accident & sickness benefit, basic group life and AD&D, and Employee Assistance Program Time Off Benefits: Paid vacation, company-paid holidays, and paid sick leave Financial Benefits: 401(k) retirement savings plan We'll put as
  • items. Now About Legence paragraph: "Legence (Nasdaq: LGN) is a leading provider of engineering, consulting, installation, and maintenance services for mission-critical systems in buildings. The company specializes in designing, fabricating, and installing complex HVAC, process piping, and other mechanical, electrical, and plumbing (MEP) systems—enhancing energy efficiency, reliability, and sustainability in new and existing facilities. Legence also delivers long-term performance through strategic upgrades and holistic solutions. Serving some of the world’s most technically demanding sectors, Legence counts over 60% of the Nasdaq-100 Index among its clients." We'll put as

    maybe under

    About the Company

    . Now also the initial description: "Yearout Mechanical, a Legence Company Yearout Mechanical is a New Mexico based company specializing in the installation of mechanical and process systems for the commercial, government, manufacturing and industrial communities of New Mexico and Texas. Since our incorporation in August of 1964, Yearout Mechanical has consistently grown and expanded its capabilities, reaching its present position as the premier mechanical contractor in New Mexico. Our mission is to be invaluable to our partners (clients, vendors, industry, and employees) so they cannot imagine success without us, by providing comfortable, reliable and efficient mechanical systems that meet our partners’ needs." We'll include that as

    maybe under same About the Company heading or separate? Could combine with Legence description. We'll put both under About the Company. Now ensure we don't include any boilerplate like "Equal Employment