HVAC Service Technician

We need to output HTML fragment with sections: About the role? The posting includes description paragraphs. We need headings: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. Use

for each heading only if there is real specific content. Must not repeat job title as heading. Must not include Job ID etc. Must preserve all substantive info. Remove boilerplate (cookie/navigation/legal/EEO etc). The posting includes many sections: description, compensation, qualifications, what you get (benefits), responsibilities. We need to map content to sections. We have "Skills mandatory. Ego encouraged." That's weird but maybe part of description. We'll treat as part of About the role. We need to include sections only when posting has real specific content. Let's extract: About the role: The introductory paragraph(s) describing role: "Come Work For Us Before Your Boss Does ..." etc. Also "We're looking for an HVAC Service Technician ..." etc. Also "This is a residential service role out of our Randolph shop..." etc. Also "No on-call. Year-round work..." etc. Also "Weekly pay." etc. Also "Compensation: $110,000 - $150,000 - Hourly or performance pay, whichever is higher." That's pay. But we need separate Pay section. Responsibilities: list of duties. Requirements/Qualifications: The posting has "Qualifications What you need..." then bullet list of requirements. Also "What actually sets you apart" personal traits. Skills: maybe "Skills mandatory. Ego encouraged." Could be a Skills section. Benefits: "WHAT YOU GET Schedule & pay ..." includes schedule and pay but we separate schedule and pay sections. Benefits includes health & retirement, time off, tools & gear, growth & culture. Pay: compensation details. Schedule: schedule info: NO ON-CALL, Weekly pay, Year-round work, plenty of overtime, flexible hours. We must not create sections with filler like "commensurate with experience". Ensure we only include sections with real content. Let's craft HTML:

About the role

Come Work For Us Before Your Boss Does Some people know they're good. They take pride in being better than average. They get the details right — even the ones most people wouldn't notice. Why? Because there's a right way and a wrong way, and people are depending on you to do it the right way. We're looking for an HVAC Service Technician we can be proud to have on our team — because you're proud to be on it. You know the equipment. You know the codes. You know how to explain things to homeowners when they ask. The work gets done right the first time. The paperwork gets filled out and filed. The customer ends the visit confident, satisfied, and knowing more about their system than they did before you showed up. Callbacks are rare — and when they happen, you own them. This is a residential service role out of our Randolph shop, running a fully stocked take-home van across the South Shore and Greater Boston. No on-call. Year-round work — heating, cooling, and maintenance keep the schedule full through every season.

But note schedule info also belongs in Schedule section; we might keep some schedule info in About but not duplicate. However we need to preserve all substantive info; we can keep schedule info in Schedule section and not repeat. But About can still mention No on-call, Year-round work? Might be okay but could be duplicate. Better to keep About focusing on role description, not schedule specifics. We'll keep About as the narrative up to "We're looking for an HVAC Service Technician..." and maybe exclude schedule specifics. Let's extract About: Up to "We're looking for an HVAC Service Technician we can be proud to have on our team — because you're proud to be on it." plus maybe the following sentences about knowing equipment etc. We'll include all descriptive sentences before schedule specifics. Let's craft:

Come Work For Us Before Your Boss Does Some people know they're good. They take pride in being better than average. They get the details right — even the ones most people wouldn't notice. Why? Because there's a right way and a wrong way, and people are depending on you to do it the right way. We're looking for an HVAC Service Technician we can be proud to have on our team — because you're proud to be on it. You know the equipment. You know the codes. You know how to explain things to homeowners when they ask. The work gets done right the first time. The paperwork gets filled out and filed. The customer ends the visit confident, satisfied, and knowing more about their system than they did before you showed up. Callbacks are rare — and when they happen, you own them.

That seems good. Now Responsibilities: list bullet points. We'll create

• each. Responsibilities list from posting: - Diagnose and repair residential heating and cooling equipment — gas furnaces, boilers, heat pumps, ductless mini-splits, and central AC - Perform precision tune-ups and preventive maintenance that catch problems before the customer feels them - Present clear repair-versus-replace options and let the homeowner make an informed decision — no pressure, no confusion - Diagnose and recommend indoor air quality solutions where they genuinely solve a problem - Document every job accurately in ServiceTitan on your company iPad — photos, findings, recommendations, and pricing before you leave the driveway - Communicate proactively with dispatch and the customer on timing, findings, and next steps - Mentor apprentices and newer techs — they're already watching how you work - Own your callbacks and resolve them fast, cleanly, and without drama - Keep your van organized, stocked, and looking like a rolling ad for a company you're proud of - Earn 5-star reviews that build the reputation of the whole team Now Requirements/Qualifications: The posting has "Qualifications What you need" list: - High school diploma or GED - Minimum 3 years of residential HVAC field experience plus formal training - EPA Universal - Valid, unrestricted driver's license and a clean driving record - A professional set of hand tools worthy of someone with your skills Then "What actually sets you apart" personal traits: - Personal pride in doing the best work, every time - The ability to teach without condescending - A knack for customer communication that makes it easy for homeowners to ask questions, understand your recommendations, and feel confident in their decisions - A real desire to see those five stars come in after you finish a job We could treat these as Requirements or Qualifications. The heading "Qualifications" is appropriate. We'll put all under

  Qualifications

  with a
  . Now Skills: The posting starts with "Skills mandatory. Ego encouraged." That's maybe a Skills section. We'll create

  Skills

  with

  Skills mandatory. Ego encouraged.

  Or maybe we can incorporate into Qualifications but better to follow instruction: Use Skills heading if there is real specific content. There is that line. We'll include. Now Benefits: The posting has "WHAT YOU GET Schedule & pay ..." but we will separate schedule and pay. Benefits includes health & retirement, time off, tools & gear, growth & culture. Let's extract: Health & retirement: - Health insurance - 100% company-paid dental - 100% company-paid vision - 100% company-paid life insurance - 401(k) with 4% company match Time off: - PTO from day one - 3 weeks paid vacation, growing from there (negotiable) - Paid birthday off Tools & gear: - New, fully stocked take-home van - Company iPad and company phone - Uniforms provided - Boot and sneaker allowance Growth & culture: - Ongoing paid training, sometimes out of state - A real career path — we promote from within - Employee of the Month recognition and prizes - Monthly contests with extra prizes - Supportive leadership that has your back We'll put these under Benefits heading with subheadings? The instruction only says use

  for section headings (About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). It doesn't forbid inner headings, but we can just list as

  with items; we could also group with

  headings but not required. Simpler:

  Benefits

  then
  • each benefit item. But we need to preserve all info; grouping is fine. Now Pay: Compensation details: "Compensation: $110,000 - $150,000 - Hourly or performance pay, whichever is higher. Every pay period. The higher the performance, the higher the pay." Also earlier: "Weekly pay. How you get paid, honestly: hourly or performance pay, whichever is higher — every pay period. But let's be straight with each other. The hourly is a floor, not a plan. Our techs don't live there, and the ones who thrive here treat it as a number they never think about. Performance pay is measured on the things you actually control: your average ticket, your close rate, your callback rate, and the reviews your customers leave. There's only upside. We'll walk you through the entire plan, line by line, before you accept an offer — no surprises". Also "WHAT YOU GET Schedule & payNO ON-CALLHourly or performance pay, whichever is higher — every pay periodUpside on performance payWeekly payYear-round work — no seasonal layoffsPlenty of overtime available if you want it, including SaturdaysFlexible hours and scheduling available". Some of that is schedule. We'll create Pay section with details about compensation range and pay structure. Now Schedule: schedule specifics: NO ON-CALL, Weekly pay (but weekly pay already in Pay? Might duplicate but schedule section about schedule not pay). Actually weekly pay is both pay and schedule. But we can keep schedule info: NO ON-CALL, Year-round work — no seasonal layoffs, Plenty of overtime available if you want it, including Saturdays, Flexible hours and scheduling available. Also maybe "Weekly pay" but we can mention in Pay only. We'll keep schedule as above. Now we must not create sections with filler like "commensurate with experience". We have real content. Now produce HTML fragment. Order: About the role, Responsibilities, Qualifications, Skills, Benefits, Pay, Schedule. (Requirements maybe same as Qualifications; we used Qualifications only). The instruction list includes Requirements and Qualifications separate; but we can combine if content overlaps. However we have content for both? The posting has "Qualifications What you need" and "What actually sets you apart". That's qualifications. There's no separate "Requirements" besides those. Could treat Requirements as same as Qualifications. But to follow instruction, we could have both Requirements and Qualifications sections if we split: Requirements = the hard requirements (diploma, experience, EPA, license, tools). Qualifications = the personal traits (pride, ability to teach, communication, desire for 5 stars). That seems reasonable. Thus:

    Requirements

    with list of hard requirements.

    Qualifications

    with list of personal traits. Now Skills: "Skills mandatory. Ego encouraged." Now Benefits as above. Now Pay. Now Schedule. Let's craft. Check for any duplicate content: Ensure we didn't miss any substantive info like "No on-call." appears in Schedule; we also mentioned in About? We removed from About. Good. "Year-round work — heating, cooling, and maintenance keep the schedule full through every season." That's schedule info; we will include in Schedule. "Plenty of overtime available if you want it, including Saturdays" schedule. "Flexible hours and scheduling available" schedule. Now Pay: include compensation range, hourly vs performance pay, weekly pay