Shop Technician (Mechanic) (Pump, Power & HVAC)
for section headings like About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. Use - for any list of duties/requirements/benefits, and
for prose. Do NOT repeat job title as heading. Do NOT put Job ID/requisition numbers as headings. Preserve all substantive info. Remove boilerplate: cookie/navigation/legal/EEO/equal-opportunity/scam-warning, duplicated lines, application instructions. Include a section only when posting has real, specific content for it. Avoid filler like "commensurate with experience", etc. Prefer few substantive sections over many thin ones.
We need to parse the posting.
Key sections:
- About the role: description at start: "Build the Future with Us — EquipmentShare is Hiring a Shop Technician (Mechanic) (Pump, Power & HVAC) At EquipmentShare, we’re not just filling a role — we’re assembling the best team on the planet to build something that’s never been built before. We’re on a mission to transform an industry that’s been stuck in the past by empowering contractors and communities through innovative technology, real-time support, and a team that truly cares.We’re hiring a Shop Technician (Mechanic) at our Advanced Solutions rental facility in Whitman, MA, and we’re looking for someone who’s ready to grow with us, bring energy and drive to their work, providing maintenance and repair for a variety of customer and company owned Pump, Power & HVAC equipment and help us build the future of construction. Technicians will have the opportunity to work on the newest equipment in the industry."
That's prose.
- Salary range: $17.00/hr - $38.00/hr. Factors including past experience and location may affect final compensation rate. Schedule: Monday to Friday, 7:00 AM to 5:00 PM, and offers overtime pay after working 40 hours. (This role is subject to on-call scheduling with additional compensation provided)
Thus we have Pay and Schedule sections.
- Primary Responsibilities: list of duties.
- Why EquipmentShare? (maybe "About the company" but we can treat as Benefits? Actually it's more about culture. Could be "Why EquipmentShare?" but we need headings from list: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We can map "Why EquipmentShare?" to Benefits? Or maybe we can create a Benefits section for perks. The "Why EquipmentShare?" includes culture description; we could put that under About the role? But we already have About the role. Could treat as "About the company" but not in allowed headings. We could incorporate into Benefits? Might be better to create a Benefits section for perks & benefits. The "Why EquipmentShare?" is more about company values; we could include under Benefits? Or we could create a separate section like "About the company" but not allowed. The instruction: Use headings for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). It says e.g., meaning those are examples, but we should prefer those headings. Likely we should stick to those headings. So we need to map content to those.
Thus sections:
- About the role: introductory paragraph.
- Responsibilities: list of primary responsibilities.
- Requirements: maybe combine Qualifications, Skills, Education and Experience, Physical Requirements, etc. Could have Requirements and Qualifications separate but we can combine if thin. The instruction: Prefer a few substantive sections over many thin ones. So we could have Requirements (including education, experience, physical, certifications) and Skills (maybe separate). But we have both Skills & Qualifications heading in the posting. Could make two sections: Skills and Qualifications. But that might be thin? However they have substantive content. Could combine into one "Requirements" section covering both skills and qualifications. But we need to follow allowed headings; we can use Skills and Qualifications as separate if they have content. The instruction says "Use
for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." So we can use those exact headings. So we can have sections: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. But we need to avoid filler. We'll see if each has content.
Let's extract content for each:
About the role: as above.
Responsibilities: list under "Primary Responsibilities". We'll list each bullet.
Requirements: maybe "Education and Experience:" plus "Physical Requirements:" plus "Must be able to move..." plus "This is a safety sensitive position..." plus "Employment is contingent on passing a background check..." plus "some roles require passing a drug test". Also "EPA 608 certification is preferred..." etc. That could be qualifications.
Qualifications: maybe "Advanced mechanical aptitude..." etc. Actually the posting has "Skills & Qualifications Required Skills/Abilities:" then list. Then "Education and Experience:" then list. Then "Physical Requirements:" then list. Then safety stuff.
Thus we could split: Skills (the list under Required Skills/Abilities), Qualifications (Education and Experience, Physical Requirements, certifications). But we have both Skills and Qualifications headings allowed.
Benefits: list under "Perks & Benefits". Also maybe "Monthly Family Dinner Night", "Competitive compensation", "Full medical, dental, and vision coverage", "Generous PTO + paid holidays", "401(k) + company match", "Tool and boot reimbursements", "Gym membership stipend + wellness programs", "Company events, food truck nights, and monthly team dinners", "16 hours of paid volunteer time per year", "Career advancement, leadership training, and professional development opportunities", "Access to industry leading diagnostic tools". Also "Year-round company provided OEM training" maybe under benefits.
Pay: salary range and note about experience/location.
Schedule: Monday to Friday 7am-5pm, overtime after 40 hours, on-call scheduling with additional compensation.
We must not include boilerplate like "EEO M/F/D/V", "Workplace For All", "A Workplace For All" etc. Also remove duplicated lines.
We must not include application instructions.
We must not include cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate.
Thus we will output HTML with sections.
We need to ensure we don't create empty sections. All sections will have content.
We'll use for each heading.
Inside each section, we will use
for prose,
- for lists.
We need to preserve all substantive information.
Let's draft.
First, About the role: combine the introductory paragraphs into one
. Might be long but okay.
Second, Responsibilities: list each duty.
We need to extract responsibilities list:
- Use our tech to create, assign, and monitor work orders, track machine service intervals, order parts, and diagnose issues faster by pulling data from hundreds of makes and models.
- With real-time information at your fingertips, you can determine the root cause and corrective action for each issue quickly, enabling you to work smarter, not harder.
- Practice safe job practices for repairing equipment
- Use technology (laptops and tablets) comfortably
- Perform preventive maintenance and repairs of power generators, diesel engines, electrical distribution equipment, HVAC equipment and/or oil free air compressors
- Troubleshoot equipment failures at the shop and on customer locations, and handle the repairs
- Work individually or with another technician(s) to set up and operate equipment at the shop and on customer sites
- Assist in the training of lower level technicians as needed
- Maintain paperwork/electronic documentation of work performed (work orders) in a complete and timely manner on a daily basis
- Assist with pick-up and delivery of equipment & parts
- Be knowledgeable of OSHA requirements (preferred)
- Year-round company provided OEM training
- Other duties, assigned as needed
We should keep all.
Third, Requirements: maybe we combine Education and Experience, Physical Requirements, and safety contingents.
But we have separate Skills and Qualifications sections. Let's decide:
Skills: list under Required Skills/Abilities:
- Must own tools applicable to position
- Advanced mechanical aptitude and working knowledge of tools
- Experience working on power generators and/or commercial HVAC equipment, performing inspections, maintenance, and repairs
- Experience with calculating nominal and effective tonnage and/or kW requirements, along with reading and knowing schematics
- Superior customer service, teamwork and verbal/written communication skills
- EPA 608 certification is preferred. If you do not already have the certification, you should be able to obtain it within 6-12 months of employment.
Qualifications: Education and Experience:
- High School diploma, Trade school certificate preferred
- Experience in equipment service, maintenance and repair preferred
Physical Requirements:
- Must be able to move, stand, stoop and bend freely
- Must be able to lift up to 50 pounds at times
Safety/Contingent:
- This is a safety sensitive position and any offer of employment will be contingent on passing a 10 panel drug screen
- Employment is contingent on passing a background check. Additionally, some roles require passing a drug test, depending on the job responsibilities.
We could put those under Qualifications or Requirements. Since we have both Skills and Qualifications headings, we can put Skills as above, Qualifications as Education+Experience+Physical+Safety.
But we also have Requirements heading allowed; we could use Requirements for Education+Experience+Physical+Safety, and Skills for skills list. Qualifications maybe not needed. However we have both Skills and Qualifications headings allowed; we could use both but ensure content.
Better to follow the examples: they listed Requirements, Qualifications, Skills as separate. So we can use all three.
Thus:
- Requirements: maybe Education and Experience + Physical Requirements + safety contingents? Or we could split: Requirements = Education and Experience, Qualifications = Physical Requirements + certifications, Skills = skills list. But we need to avoid thin sections.
Let's think: The posting has "Education and Experience:" and "Physical Requirements:" and safety notes. Those could be under Qualifications (since they are qualifications). Skills list is under Skills & Qualifications Required Skills/Abilities. So we could map:
Skills: the list under Required Skills/Abilities.
Qualifications: Education and Experience, Physical Requirements, safety contingents (drug screen, background check). That seems reasonable.
Requirements: maybe we could omit or combine? But we need to avoid filler. If we omit Requirements heading, that's fine; we only include sections with real content. So we can have About the role, Responsibilities, Skills, Qualifications, Benefits, Pay, Schedule. That's 7 sections.
Check if any content left for Requirements: maybe none separate. We'll skip Requirements.
Now Benefits: list perks.
We need to ensure we don't include filler like "restrictions apply" maybe okay.
Now Pay: salary range and note.
Schedule: Monday to Friday 7:00 AM to 5:00 PM, overtime after 40 hours, on-call scheduling with additional compensation.
Now we need to ensure we don't include duplicated lines. For example, "Year-round company provided OEM training" appears both in Responsibilities and maybe also under Benefits? Actually it's in Responsibilities list. We'll keep it there only.
Now produce HTML.
We'll wrap each section in
heading then content.
For lists, use - .
For prose, use
.
Let's craft.
About the role:
Build the Future with Us — EquipmentShare is Hiring a Shop Technician (Mechanic) (Pump, Power & HVAC). At EquipmentShare, we’re not just filling a role — we’re assembling the best team on the planet to build something that’s never been built before. We’re on a mission to transform an industry that’s been stuck in the past by empowering contractors and communities
for prose. Do NOT repeat job title as heading. Do NOT put Job ID/requisition numbers as headings. Preserve all substantive info. Remove boilerplate: cookie/navigation/legal/EEO/equal-opportunity/scam-warning, duplicated lines, application instructions. Include a section only when posting has real, specific content for it. Avoid filler like "commensurate with experience", etc. Prefer few substantive sections over many thin ones. We need to parse the posting. Key sections: - About the role: description at start: "Build the Future with Us — EquipmentShare is Hiring a Shop Technician (Mechanic) (Pump, Power & HVAC) At EquipmentShare, we’re not just filling a role — we’re assembling the best team on the planet to build something that’s never been built before. We’re on a mission to transform an industry that’s been stuck in the past by empowering contractors and communities through innovative technology, real-time support, and a team that truly cares.We’re hiring a Shop Technician (Mechanic) at our Advanced Solutions rental facility in Whitman, MA, and we’re looking for someone who’s ready to grow with us, bring energy and drive to their work, providing maintenance and repair for a variety of customer and company owned Pump, Power & HVAC equipment and help us build the future of construction. Technicians will have the opportunity to work on the newest equipment in the industry." That's prose. - Salary range: $17.00/hr - $38.00/hr. Factors including past experience and location may affect final compensation rate. Schedule: Monday to Friday, 7:00 AM to 5:00 PM, and offers overtime pay after working 40 hours. (This role is subject to on-call scheduling with additional compensation provided) Thus we have Pay and Schedule sections. - Primary Responsibilities: list of duties. - Why EquipmentShare? (maybe "About the company" but we can treat as Benefits? Actually it's more about culture. Could be "Why EquipmentShare?" but we need headings from list: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We can map "Why EquipmentShare?" to Benefits? Or maybe we can create a Benefits section for perks. The "Why EquipmentShare?" includes culture description; we could put that under About the role? But we already have About the role. Could treat as "About the company" but not in allowed headings. We could incorporate into Benefits? Might be better to create a Benefits section for perks & benefits. The "Why EquipmentShare?" is more about company values; we could include under Benefits? Or we could create a separate section like "About the company" but not allowed. The instruction: Use headings for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). It says e.g., meaning those are examples, but we should prefer those headings. Likely we should stick to those headings. So we need to map content to those. Thus sections: - About the role: introductory paragraph. - Responsibilities: list of primary responsibilities. - Requirements: maybe combine Qualifications, Skills, Education and Experience, Physical Requirements, etc. Could have Requirements and Qualifications separate but we can combine if thin. The instruction: Prefer a few substantive sections over many thin ones. So we could have Requirements (including education, experience, physical, certifications) and Skills (maybe separate). But we have both Skills & Qualifications heading in the posting. Could make two sections: Skills and Qualifications. But that might be thin? However they have substantive content. Could combine into one "Requirements" section covering both skills and qualifications. But we need to follow allowed headings; we can use Skills and Qualifications as separate if they have content. The instruction says "Use
for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." So we can use those exact headings. So we can have sections: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. But we need to avoid filler. We'll see if each has content.
Let's extract content for each:
About the role: as above.
Responsibilities: list under "Primary Responsibilities". We'll list each bullet.
Requirements: maybe "Education and Experience:" plus "Physical Requirements:" plus "Must be able to move..." plus "This is a safety sensitive position..." plus "Employment is contingent on passing a background check..." plus "some roles require passing a drug test". Also "EPA 608 certification is preferred..." etc. That could be qualifications.
Qualifications: maybe "Advanced mechanical aptitude..." etc. Actually the posting has "Skills & Qualifications Required Skills/Abilities:" then list. Then "Education and Experience:" then list. Then "Physical Requirements:" then list. Then safety stuff.
Thus we could split: Skills (the list under Required Skills/Abilities), Qualifications (Education and Experience, Physical Requirements, certifications). But we have both Skills and Qualifications headings allowed.
Benefits: list under "Perks & Benefits". Also maybe "Monthly Family Dinner Night", "Competitive compensation", "Full medical, dental, and vision coverage", "Generous PTO + paid holidays", "401(k) + company match", "Tool and boot reimbursements", "Gym membership stipend + wellness programs", "Company events, food truck nights, and monthly team dinners", "16 hours of paid volunteer time per year", "Career advancement, leadership training, and professional development opportunities", "Access to industry leading diagnostic tools". Also "Year-round company provided OEM training" maybe under benefits.
Pay: salary range and note about experience/location.
Schedule: Monday to Friday 7am-5pm, overtime after 40 hours, on-call scheduling with additional compensation.
We must not include boilerplate like "EEO M/F/D/V", "Workplace For All", "A Workplace For All" etc. Also remove duplicated lines.
We must not include application instructions.
We must not include cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate.
Thus we will output HTML with sections.
We need to ensure we don't create empty sections. All sections will have content.
We'll use for each heading.
Inside each section, we will use
for prose,
- for lists.
We need to preserve all substantive information.
Let's draft.
First, About the role: combine the introductory paragraphs into one
. Might be long but okay. Second, Responsibilities: list each duty. We need to extract responsibilities list: - Use our tech to create, assign, and monitor work orders, track machine service intervals, order parts, and diagnose issues faster by pulling data from hundreds of makes and models. - With real-time information at your fingertips, you can determine the root cause and corrective action for each issue quickly, enabling you to work smarter, not harder. - Practice safe job practices for repairing equipment - Use technology (laptops and tablets) comfortably - Perform preventive maintenance and repairs of power generators, diesel engines, electrical distribution equipment, HVAC equipment and/or oil free air compressors - Troubleshoot equipment failures at the shop and on customer locations, and handle the repairs - Work individually or with another technician(s) to set up and operate equipment at the shop and on customer sites - Assist in the training of lower level technicians as needed - Maintain paperwork/electronic documentation of work performed (work orders) in a complete and timely manner on a daily basis - Assist with pick-up and delivery of equipment & parts - Be knowledgeable of OSHA requirements (preferred) - Year-round company provided OEM training - Other duties, assigned as needed We should keep all. Third, Requirements: maybe we combine Education and Experience, Physical Requirements, and safety contingents. But we have separate Skills and Qualifications sections. Let's decide: Skills: list under Required Skills/Abilities: - Must own tools applicable to position - Advanced mechanical aptitude and working knowledge of tools - Experience working on power generators and/or commercial HVAC equipment, performing inspections, maintenance, and repairs - Experience with calculating nominal and effective tonnage and/or kW requirements, along with reading and knowing schematics - Superior customer service, teamwork and verbal/written communication skills - EPA 608 certification is preferred. If you do not already have the certification, you should be able to obtain it within 6-12 months of employment. Qualifications: Education and Experience: - High School diploma, Trade school certificate preferred - Experience in equipment service, maintenance and repair preferred Physical Requirements: - Must be able to move, stand, stoop and bend freely - Must be able to lift up to 50 pounds at times Safety/Contingent: - This is a safety sensitive position and any offer of employment will be contingent on passing a 10 panel drug screen - Employment is contingent on passing a background check. Additionally, some roles require passing a drug test, depending on the job responsibilities. We could put those under Qualifications or Requirements. Since we have both Skills and Qualifications headings, we can put Skills as above, Qualifications as Education+Experience+Physical+Safety. But we also have Requirements heading allowed; we could use Requirements for Education+Experience+Physical+Safety, and Skills for skills list. Qualifications maybe not needed. However we have both Skills and Qualifications headings allowed; we could use both but ensure content. Better to follow the examples: they listed Requirements, Qualifications, Skills as separate. So we can use all three. Thus: - Requirements: maybe Education and Experience + Physical Requirements + safety contingents? Or we could split: Requirements = Education and Experience, Qualifications = Physical Requirements + certifications, Skills = skills list. But we need to avoid thin sections. Let's think: The posting has "Education and Experience:" and "Physical Requirements:" and safety notes. Those could be under Qualifications (since they are qualifications). Skills list is under Skills & Qualifications Required Skills/Abilities. So we could map: Skills: the list under Required Skills/Abilities. Qualifications: Education and Experience, Physical Requirements, safety contingents (drug screen, background check). That seems reasonable. Requirements: maybe we could omit or combine? But we need to avoid filler. If we omit Requirements heading, that's fine; we only include sections with real content. So we can have About the role, Responsibilities, Skills, Qualifications, Benefits, Pay, Schedule. That's 7 sections. Check if any content left for Requirements: maybe none separate. We'll skip Requirements. Now Benefits: list perks. We need to ensure we don't include filler like "restrictions apply" maybe okay. Now Pay: salary range and note. Schedule: Monday to Friday 7:00 AM to 5:00 PM, overtime after 40 hours, on-call scheduling with additional compensation. Now we need to ensure we don't include duplicated lines. For example, "Year-round company provided OEM training" appears both in Responsibilities and maybe also under Benefits? Actually it's in Responsibilities list. We'll keep it there only. Now produce HTML. We'll wrap each section in
heading then content. For lists, use
- .
For prose, use
. Let's craft. About the role:
Build the Future with Us — EquipmentShare is Hiring a Shop Technician (Mechanic) (Pump, Power & HVAC). At EquipmentShare, we’re not just filling a role — we’re assembling the best team on the planet to build something that’s never been built before. We’re on a mission to transform an industry that’s been stuck in the past by empowering contractors and communities
- .
For prose, use