HVAC Technician 1

We need to output HTML fragment only, with headings

for sections: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. Only include sections that have real specific content. We must not repeat job title as heading. No Job ID etc. Remove boilerplate, navigation, legal, EEO, etc. Preserve all substantive info. We need to parse the posting. Content: - Intro paragraph about Sunbelt Rentals (company description). This could be "About the role"? Actually "About the role" is typical heading for description of role. The intro about company could be considered "About the role"? Might be better as a paragraph before headings. The instruction: Use

for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). Use

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

  for prose. Do NOT repeat the job title as a heading (the page already shows it) and do NOT put Job ID / requisition numbers as headings — fold minor metadata into a short

  or drop it. Preserve ALL substantive information; do NOT invent or summarize away detail. Remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. IMPORTANT: include a section ONLY when the posting has real, specific content for it — 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. Prefer a few substantive sections over many thin ones. Output ONLY the HTML fragment — no /, no markdown code fences. Thus we need to decide which sections to include. We have: - Position Objective (maybe part of About the role) - Position Responsibilities (list) - Requirements (list) - Base Pay Range (Pay) - Benefits description (Benefits) - Paid time off details (maybe part of Benefits or separate? Could be Benefits) - Schedule? Not explicitly given except "on call for emergency service and is available on a rotating schedule for emergency service response calls on weekends and evenings". That's schedule info. Could be a Schedule section. - Qualifications? Not separate; Requirements includes education & experience. - Skills? Not explicit but could be derived from responsibilities: mechanical inclination, basic math, etc. But we should not invent. If not explicit, we should not create Skills section. Thus sections: About the role (maybe combine Position Objective and company intro?), Responsibilities, Requirements, Pay, Benefits, Schedule. Check if we have enough content for each. About the role: Could include Position Objective and maybe company description? The posting includes "Join Our Team! Sunbelt Rentals strives..." That's company overview. Could be considered About the role? Usually About the role is description of the role. The Position Objective is: "The HVAC Technician 1 demonstrates a level of professionalism through positive communication and appearance and provides an exemplary level of service to our customers. This role delivers portable HVAC equipment to the customer, demonstrating skills and performance in the use, operation, and repair of all company equipment. Additionally, this role works primarily in the shop to keep it organized, clean and safe and learns how to check in, clean and prepare equipment for rental support other tech staff on large jobs." That's substantive. So we can put that under About the role. Responsibilities: list of duties (bulleted). We'll put

  • each. Requirements: list: Education & Experience: 1-2 years of experience in a service-related role interacting with customers; Must possess basic math skills; Must be mechanically inclined; Must have a valid driver's license and clean driving record free from points; Must be at least 21 years or older; Must be able to work some after hours and weekend work during peak times. We'll put as
    • . Pay: Base Pay Range: $20.89 - 30.02 Starting rate of pay may vary based on factors including, but not limited to, position offered, location, education, training, and/or experience. Also mention to visit website for more info on benefits. But we should not include application instructions. The line "Please visit https://www.sunbeltrentals.com/careers/ for more information on our benefits and to join our Talent Network." is application instruction? It's a link for more info; might be considered boilerplate? It's not exactly application instruction but it's a link to benefits. Since we already have Benefits section, we could drop that line. The instruction says remove application instructions. That line is more like a referral to benefits; could be considered application instruction. Safer to drop it. Benefits: "Sunbelt also provides a comprehensive benefits package to its full-time employees. This package includes: Health, Dental and Vision plans 401(k) Match Volunteer time off Short-term and long-term disability Accident, Life and Travel insurance, as well as flexible spending Tuition Reimbursement Options Employee Assistance Program (EAP) Length of Service Awards You will become eligible for benefits on the first of the month following 30 days from your start date." Also PTO details: "Sunbelt offers team members the following paid time off from work, subject to Sunbelt’s policies (unless specified in a collective bargaining agreement): 12-25 vacation days depending on years of service 5 sick days 6 holidays 2 half day holidays 2 floating holidays 1 inclusion day 1 volunteer day" We can combine these into Benefits section as a list. Schedule: "Is on call for emergency service and is available on a rotating schedule for emergency service response calls on weekends and evenings". That's schedule info. Also "Must be able to work some after hours and weekend work during peak times" from Requirements but that's about availability. We'll put schedule info under Schedule. We should not create Qualifications or Skills sections unless explicit. Not needed. Now produce HTML fragment. Structure:

      maybe intro paragraph? The instruction says use

      for prose. We could include a brief intro about the company? But that might be considered boilerplate? It's substantive about the company but not required. Could include as a

      before headings. It's not a heading. It's okay. We need to avoid repeating job title. Not needed. Thus:

      Join Our Team! Sunbelt Rentals strives to be the customer's first choice in the equipment rental industry. From pumps to scaffolding to general construction tools, we aim to be the only call needed to outfit a job site with the proper equipment. Not only do we offer a vast fleet that ranks among the best in the industry, we pair it all with a friendly and knowledgeable staff. Our employees are our greatest asset, and although we present a comprehensive equipment offering, our expertise and service are what truly distinguish us from the competition. We pride ourselves on investing in our workforce and offer competitive benefits, as well as extensive on-the-job training for all eligible employees. As a highly successful national company, we are constantly looking for talented individuals to support our growth. If you are interested in pursuing a rewarding career, we invite you to review our opportunities!

      Then

      About the role

      followed by

      Position Objective: The HVAC Technician 1 demonstrates a level of professionalism through positive communication and appearance and provides an exemplary level of service to our customers. This role delivers portable HVAC equipment to the customer, demonstrating skills and performance in the use, operation, and repair of all company equipment. Additionally, this role works primarily in the shop to keep it organized, clean and safe and learns how to check in, clean and prepare equipment for rental support other tech staff on large jobs.

      Then

      Responsibilities

      • Communicates professionally with customers, managers and sales engineers to schedule deliveries, pick-ups and service calls
      ... etc. We need to list each responsibility exactly as in posting. Responsibilities list from posting: - Communicates professionally with customers, managers and sales engineers to schedule deliveries, pick-ups and service calls - Delivers and installs rented HVAC equipment and trains the authorized operator (and/or customer) on the safe use of the equipment - Directs customers to sign appropriate paperwork; keeps track of serial numbers - Successfully troubleshoots the operation, function, specifications, capabilities and controls of any piece of rental equipment - Operates company vehicle safely and follows all company safety policies - Cleans and tests returned equipment, making sure operation and appearance are up to standards - Completes appropriate paperwork for deliveries, pick-ups and service calls - Installs flexible gas hose on both propane and natural gas applications - Implements proper and safe procedures to check gas connections - Works with managers and sales engineers to maintain accurate records and tracking of in-stock and rented equipment - Is on call for emergency service and is available on a rotating schedule for emergency service response calls on weekends and evenings Note the last one also appears in schedule; but we can keep it under Responsibilities as it's a duty. For Schedule we may extract schedule info. Now Requirements list: - Education & Experience: 1-2 years of experience in a service-related role interacting with customers - Must possess basic math skills - Must be mechanically inclined - Must have a valid driver's license and clean driving record free from points - Must be at least 21 years or older - Must be able to work some after hours and weekend work during peak times Now Pay:

      Pay

      Base Pay Range: $20.89 - 30.02 Starting rate of pay may vary based on factors including, but not limited to, position offered, location, education, training, and/or experience.

      Now Benefits: We need to list benefits as
      • . Also include PTO details maybe as separate list or combined. Benefits list: - Health, Dental and Vision plans - 401(k) Match - Volunteer time off - Short-term and long-term disability - Accident, Life and Travel insurance, as well as flexible spending - Tuition Reimbursement Options - Employee Assistance Program (EAP) - Length of Service Awards - Eligibility: You will become eligible for benefits on the first of the month following 30 days from your start date. PTO: - 12-25 vacation days depending on years of service - 5 sick days - 6 holidays - 2 half day holidays - 2 floating holidays - 1 inclusion day - 1 volunteer day We could combine into one Benefits section with two sublists? But instruction: Use
        • for any list of duties/requirements/benefits. So we can have a single
          with all items, or separate
          for each category. Probably simplest: one
          with all benefit items including PTO items. Now Schedule: We have schedule info: "Is on call for emergency service and is available on a rotating schedule for emergency service response calls on weekends and evenings". Also maybe "Must be able to work some after hours and weekend work during peak times" but that's in Requirements. We'll put schedule as

          maybe. Thus

          Schedule

          Is on call for emergency service and is available on a rotating schedule for emergency service response calls on weekends and evenings.

          We should not duplicate content; the responsibility list already includes that line. But we can keep it in Schedule as separate; but that would duplicate. The instruction says preserve ALL substantive information; do NOT invent or summarize away detail. Duplication is okay if it's present in original? The original has that line only once under Responsibilities. If we also put it under Schedule, we'd be duplicating. Better to not duplicate; we could move that line to Schedule and remove from Responsibilities? But then we'd lose it from Responsibilities. The responsibility list includes that line; we could keep it there and not have Schedule section. But