Commercial HVAC Apprentice Service Technician – Union

We need to output HTML fragment with sections: About the role, Responsibilities, Requirements (maybe combine Required Qualifications and Preferred Qualifications?), Benefits, Pay, Schedule? The posting includes "What You’ll Gain" includes benefits like 401k, paid travel time, on-call schedule, company vehicle, tools, safety PPE. Also "Benefits" section later mentions benefits under union agreements. Also "Pay Range". Also schedule? There's mention of on-call schedule for better work-life balance (rotations every 7-8 weeks). That's schedule info. So we can include Schedule section. We must not repeat job title as heading. Use

for each section heading. Use

• for lists. Use

  for prose. We must preserve all substantive info, not invent. Remove boilerplate: About Carrier paragraph (maybe keep? It's about company, not role; but it's substantive? The instruction: "Preserve ALL substantive information; do NOT invent or summarize away detail." The About Carrier is company overview; it's not role-specific but still part of posting. Should we keep? The instruction about sections: use headings for sections like About the role, Responsibilities, etc. The "About Carrier" could be considered "About the company". Not listed as a section heading we must use; but we could include as a

  before sections. It's not prohibited. We'll keep it as a paragraph. We must remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. So remove the EEO statement, Job Applicant's Privacy Notice, etc. Also remove "Applications will be accepted for at least 3 days from Job Posting Date. Job Posting Date: 09/24/2026". That's application instruction/metadata; remove. Also remove "Carrier is An Equal Opportunity/Affirmative Action Employer..." etc. Remove. We need to include sections only when posting has real specific content. We have: - About the role: we have "About This Role" paragraph. That's substantive. Use heading

  About the role

  and then paragraph(s). - Responsibilities: "What You’ll Do" list. Use heading

  Responsibilities

  and
  • each duty. - Requirements: "Required Qualifications" list. Use heading

    Requirements

    (or Qualifications). Could also separate Required and Preferred but we can combine? The instruction: prefer few substantive sections over many thin ones. Could combine Required and Preferred into Requirements? But we have separate headings for Required Qualifications and Preferred Qualifications. Might be better to have Requirements (required) and maybe Skills? But we have "Preferred Qualifications" which could be considered "Preferred Qualifications" but we could incorporate into Requirements as a sublist? However instruction: Use headings for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). So we could have Requirements and Qualifications separate? Actually they list both Requirements and Qualifications as possible headings. We could use Requirements for required qualifications, and Qualifications for preferred? But they said "Prefer a few substantive sections over many thin ones." So maybe combine required and preferred into one Requirements section, but we could also have a Skills section for communication etc. However we have "Preferred Qualifications" includes basic understanding of building automation controls, excellent communication skills, experience using Salesforce and ServiceMax is a plus. Those could go under Skills. But we can also put them under Requirements as "Preferred" bullet. Given instruction to prefer few sections, we can have: About the role, Responsibilities, Requirements (covering both required and preferred), Benefits, Pay, Schedule. We must not create Pay/Schedule/Benefits sections unless posting actually states them. It does state Pay Range, Benefits, and schedule (on-call rotations). So include those. Now extract content: About This Role paragraph: "Step into a role where you don’t just work on HVAC systems-you redefine service excellence. At Carrier, being a Commercial HVAC Journeyman Service Technician means more than just fixing equipment, it means delivering solutions customers can count on. When you show up, the customers can relax, because they know you bring unmatched technical skills, sharp problem-solving instincts, and the kind of professionalism that has defined Carrier for over 100 years. This is a role for someone who thrives on challenge, not someone who wants to be stuck behind a desk. You’ll be out in the field, solving problems others can’t, with access to world-class training, cutting-edge tools, and an environment that fosters continuous learning. Being great at this job means combining deep technical knowledge with top-notch communication and customer service skills. That’s the Carrier way. But our service technicians just call it really good at what they do. It takes Carrier, It takes you." We'll keep that as

    . Responsibilities list: The bullet points after "What You’ll Do As a Commercial HVAC Service Technician, you understand the importance of providing expert and quality service. We are looking for an individual who has:" then list: - Inspect and maintain air-conditioning and HVAC systems to ensure efficient operation - Diagnosing and repairing mechanical and electrical malfunctions in heating and cooling units - Install, replace, and calibrate HVAC equipment, including thermostatic controls and liquid lines - Maintain chilled and hot water supply systems and adjust internal control systems - Service rooftop units, gas packs, heat pumps, split systems, and related controls. - Assemble and install metal ductwork and assist in HVAC system planning and design - Ensure compliance with City, State, and EPA regulations by maintaining detailed maintenance records - Identify and mitigate risks to maintain a safe working environment - Collaborate with management to support safety and operational standards We need to preserve exactly as given; note some have capitalization variations. We'll keep them. Requirements: Required Qualifications list: - 5+ years practical working experience in the HVAC Industry - Ability to Push / Pull / Lift 50lbs - EPA Universal Certification - Must be able to stand, crawl, sit, squat of extended period of time, climb a ladder, and the ability to work on rooftop - High School Diploma/GED - Possess and maintain valid and current Driver’s License and be insurable by the company’s insurance carrier Preferred Qualifications list: - Basic understanding of building automation controls - Excellent communication skills, both written and verbal - Experience using Salesforce and ServiceMax is a plus We could combine into Requirements section with subheadings? But we cannot add extra headings besides allowed ones. Could we put a note "Preferred:" inside list? Probably okay to just list them as items; we can differentiate by adding "(Preferred)" in text? That would be adding info not present. Better to keep them as separate bullet points but we could note they are preferred? The instruction: do not invent or summarize away detail. Adding "(Preferred)" is inventing. So we should keep them as is, but we need to indicate which are required vs preferred? The original text separates them; if we combine into one list we lose that distinction. That's summarizing away detail (the distinction). So we should keep two subsections: Required Qualifications and Preferred Qualifications. But we only have allowed headings: Requirements, Qualifications, Skills. We could use "Requirements" for required, and "Qualifications" for preferred. That seems acceptable: Required Qualifications -> heading Requirements; Preferred Qualifications -> heading Qualifications. That preserves distinction without inventing. Thus:

    Requirements

    with required items.

    Qualifications

    with preferred items. Now Benefits: The posting has "What You’ll Gain" includes: - Opportunity for 401k - Paid travel time after the first hour and on-call schedule for better work-life balance (rotations every 7-8 weeks in most locations) - Company provided vehicle with gas cards - All necessary tools provided - Key Safety and PPE Benefits include: - Comprehensive Protection: Steel-toed boots, Carrier-branded uniforms with FR protection, HVAC gloves, hard hats, and face shields - Enhanced Eye Safety: Standard safety goggles provided, with an option for prescription eyewear if needed - Advanced Safety Support: Fall protection provided where required, plus respirators and earplugs as needed - You will have autonomy to execute, backed by the camaraderie, continuous support, and resources of a dedicated team within a large, world-renowned company Then later "Benefits" section: "Benefits are provided under applicable union agreements and generally include medical insurance, retirement, tuition reimbursement, vacation, holidays, and other time off. Benefits and eligibility vary by agreement." We need to preserve all substantive info. So we should combine these into Benefits section. Could we split into subpoints? We'll just list as
    • items. We must not create Benefits section unless posting actually states them. It does. Now Pay: "Pay Range The hourly rate for this position is between $24.00 - $48.00 per hour. Factors which may affect pay within this range include, but are not limited to, skills, education, experience, and other unique qualifications of the successful candidate." We'll put that as

      under

      Pay

      . Schedule: The posting mentions on-call schedule for better work-life balance (rotations every 7-8 weeks in most locations) inside What You’ll Gain. Also maybe other schedule info? Not much else. So we can create Schedule section with that detail. However note that schedule info is already in Benefits (What You’ll Gain). But we can still create Schedule section with that detail; but we must not duplicate content? The instruction: Preserve ALL substantive information; do NOT invent or summarize away detail. Duplication is okay as long as we preserve. But we should avoid duplicate lines? It says remove duplicated lines. So we should not repeat the same sentence twice. So we need to decide where to put schedule info: either in Benefits or Schedule, but not both. Since schedule is a specific aspect, we could put it under Schedule and not repeat in Benefits. However Benefits also includes other items like 401k, vehicle, tools, safety PPE, autonomy, etc. The schedule info is part of What You’ll Gain; we could move it to Schedule and keep Benefits without that line. That would avoid duplication. Let's do that. Thus Benefits section will include: - Opportunity for 401k - Company provided vehicle with gas cards - All necessary tools provided - Key Safety and PPE Benefits include: - Comprehensive Protection: Steel-toed boots, Carrier-branded uniforms with FR protection, HVAC gloves, hard hats, and face shields - Enhanced Eye Safety: Standard safety goggles provided, with an option for prescription eyewear if needed - Advanced Safety Support: Fall protection provided where required, plus respirators and earplugs as needed - You will have autonomy to execute, backed by the camaraderie, continuous support, and resources of a dedicated team within a large, world-renowned company - Benefits are provided under applicable union agreements and generally include medical insurance, retirement, tuition reimbursement, vacation, holidays, and other time off. Benefits and eligibility vary by agreement. Note: The "Key Safety and PPE Benefits include:" is a heading-like phrase; we could keep as a

      then nested list? But we must use

      • for any list of duties/requirements/benefits. So we need to treat the safety items as a list. Could do:
      • Key Safety and PPE Benefits include:
        • Comprehensive Protection: Steel-toed boots, Carrier-branded uniforms with FR protection, HVAC gloves, hard hats, and face shields
        • Enhanced Eye Safety: Standard safety goggles provided, with an option for prescription eyewear if needed
        • Advanced Safety Support: Fall protection provided where required, plus