Mobile Trailer Technician
for sections: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. Only include sections that have real specific content. No job title heading. No Job ID. Remove boilerplate like EEO, etc. Also remove application instructions, navigation, cookie, etc. Must preserve all substantive info.
We need to parse the posting.
Content:
Intro: "You got the tools, the skills, and the drive to do it right — we got the outfit that'll back you up. Come join Prestige Fleet Services, the fastest-growing fleet maintenance name in the country, where we're looking for real techs who know their way around under a hood. Our leadership's got your back and wants to see you succeed, not just clock in and out. We've also got cutting-edge tech that cuts down on paperwork, so you can spend more time wrenching and less time buried in admin work. We're a family-oriented company, proud to serve our community, and we want hardworking techs like you to grab your toolbox and grow with us."
Then "About Us Prestige Fleet Services has been keeping trucks and trailers on the road for over 40 years. Started in Georgia, we've grown into a multi-state operation, but we've never lost sight of what matters showing up, doing the job right, and taking care of the people who trust us with their fleet. Our techs work, tackling everything from brakes and diagnostics to engine work and welding. If you like hands-on work, solving real problems, and being part of a crew that's got your back, you'll fit right in here. We hire for skill and work ethic, and we invest in the people who bring it."
Then ">>Ability to do Structural Body Work is a Must"
Then "WHAT TO EXPECT" list:
- Diagnose, inspect, and repair Class 8 trailers, including brakes, electrical, hydraulic, lift-gate, and suspension systems
- Perform trailer patchwork and minor structural repairs as needed
- Perform preventive maintenance and DOT inspections; service and replace parts like tires, hubs, and axles
- Write work orders and open/close repair orders on a company device for mobile road calls and in-yard work
- Test systems for performance and ensure trailers meet DOT safety requirements
- Manage service truck inventory and source parts from local vendors
- Complete inspection reports and DOT documentation accurately and on time
- Deliver strong customer service and report findings to management
Then "WHAT IT TAKES":
- 3+ years of experience repairing Commercial Class 8 Trailers.
- Experienced in performing annual federal inspections and brake inspections.
- Valid Driver’s License with acceptable driving record & no suspensions.
- Ability to lift 50+ pounds.
- Comfortable working with Computers for billing and work orders.
- Follows verbal and written work orders to stay on track with daily repairs.
- Confident explaining a diagnosis over the phone and helping the customer decide next steps on repairs.
- Self-motivated with excellent organization and planning skills.
Then "WHAT WILL HELP YOU STAND OUT":
- Experience with stick welding.
- Your own tools.
- Certifications are a plus | EPA 608/609/Universal & ASE.
Then "WHAT WE OFFER YOU":
- Competitive Weekly Pay
- Overtime Opportunities and Weekly Bonus Opportunities
- Shifts available to meet your lifestyle
- Paid Time Off
- Holiday Pay
- Comprehensive Medical, Dental and Vision Insurance
- Health Savings Account option
- Additional Wellness Resources
- Life insurance offerings
- Supplemental Insurance plans
- Retirement plans with company match
- Continuing training & more
Then "Prestige Fleet Services is an equal opportunity, affirmative action employer..." (EEO) - remove.
Then "The Company Epika is a network of mobile and in-shop preventative maintenance service centers focused on commercial fleets across the country. Our company was built by partnering with and investing in the best-of-the-best in every market we serve and partnering with private equity firm Ares. For more information, visit www.EpikaFleet.com." This seems like extra info about parent company; maybe keep as part of About Us? It's substantive but not boilerplate. Could include in About Us.
Then "USD $36.00 - USD $40.00 /Hr." This is pay info.
We need sections: About the role (maybe combine About Us and intro?), Responsibilities (WHAT TO EXPECT), Requirements (WHAT IT TAKES), Qualifications (maybe WHAT WILL HELP YOU STAND OUT?), Skills (maybe certifications?), Benefits (WHAT WE OFFER YOU), Pay (USD $36-40/hr), Schedule (Shifts available to meet your lifestyle). However schedule is part of benefits; but we can create Schedule section if we have specific schedule info: "Shifts available to meet your lifestyle". That's schedule info.
We must not create sections with filler like "commensurate with experience". We have actual content.
We need to decide which headings to use. 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. 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.
Thus we need to decide which sections have real specific content.
- About the role: we have introductory paragraphs about company and role. Could be About the role (or About Us). We'll include About the role with prose.
- Responsibilities: WHAT TO EXPECT list is duties. So Responsibilities section with
.
- Requirements: WHAT IT TAKES list is requirements. So Requirements section with .
- Qualifications: maybe WHAT WILL HELP YOU STAND OUT is qualifications/preferred qualifications. Could be Qualifications section.
- Skills: maybe we could separate certifications as Skills? But we could also include under Qualifications. The instruction says prefer a few substantive sections over many thin ones. So maybe combine Qualifications and Skills into one section? But we have separate headings list; we can choose to include only those with content. We have content for Qualifications (preferred qualifications). Skills maybe not explicitly listed besides "Ability to lift 50+ pounds", "Comfortable working with Computers", "Confident explaining a diagnosis", etc. Those are more like requirements. Could treat Skills as part of Requirements. To avoid thin sections, we could omit Skills section.
- Benefits: WHAT WE OFFER YOU list is benefits. So Benefits section.
- Pay: we have USD $36.00 - USD $40.00 /Hr. So Pay section.
- Schedule: we have "Shifts available to meet your lifestyle". That's schedule info. So Schedule section.
Thus we will have sections: About the role, Responsibilities, Requirements, Qualifications, Benefits, Pay, Schedule.
We need to ensure we don't include filler. All content is specific.
We need to output only HTML fragment, no /, no markdown fences.
We'll structure:
About the role
...combined intro and About Us...
Responsibilities
- ...
...
Requirements
- ...
...
Qualifications
- Experience with stick welding.
- Your own tools.
- Certifications are a plus | EPA 608/609/Universal & ASE.
Benefits
- Competitive Weekly Pay
- Overtime Opportunities and Weekly Bonus Opportunities
- Shifts available to meet your lifestyle
- Paid Time Off
- Holiday Pay
- Comprehensive Medical, Dental and Vision Insurance
- Health Savings Account option
- Additional Wellness Resources
- Life insurance offerings
- Supplemental Insurance plans
- Retirement plans with company match
- Continuing training & more
But note "Shifts available to meet your lifestyle" appears also in Benefits list; but we also have Schedule section. To avoid duplication, we could move that to Schedule section only, not duplicate in Benefits. However the Benefits list includes it; we could keep it in Benefits and not have Schedule separate, but we need Schedule section if we have specific schedule info. The instruction: prefer a few substantive sections over many thin ones. If we put schedule info in Benefits, we could omit Schedule section. But we also have Pay separate. The Benefits list includes many items; moving schedule out may be okay. However the Benefits list originally includes "Shifts available to meet your lifestyle". If we remove it from Benefits, we are altering content (removing). We must preserve ALL substantive information. So we need to keep that info somewhere. We could keep it in Benefits and also have Schedule section with same info? That would duplicate. Duplication is to be avoided: "Remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines". Duplicated lines should be removed. So we should not duplicate the same line. So we need to decide where to place it. Since schedule is a specific aspect, we could create Schedule section and remove it from Benefits list. But then we are removing it from Benefits list, which is part of the original Benefits section. However the instruction says preserve ALL substantive information; we are not removing the info, just relocating it. That's okay as long as it's present somewhere. The Benefits section would then lack that item, but the info is still present in Schedule section. Is that considered preserving? Probably yes, as long as the info appears somewhere. However the Benefits section originally had that line; moving it may be considered altering the grouping but not losing info. The instruction didn't forbid reordering. It said preserve ALL substantive information; do NOT invent or summarize away detail. So moving is fine.
Thus we will have Benefits list without the shift line, and Schedule section with that line.
Similarly, Pay section: we have pay info; we should not duplicate it in Benefits (we already removed Competitive Weekly Pay from Benefits? Actually Benefits list includes "Competitive Weekly Pay". That's also pay info. We have Pay section with specific range. We should avoid duplication. So we should remove "Competitive Weekly Pay" from Benefits list, and keep Pay section with the range. However the Benefits list also includes "Overtime Opportunities and Weekly Bonus Opportunities". That's separate.
Thus Benefits list will exclude Competitive Weekly Pay and Shifts available to meet your lifestyle.
Now we need to ensure we keep all other benefits.
Let's extract Benefits list exactly as given:
- Competitive Weekly Pay
- Overtime Opportunities and Weekly Bonus Opportunities
- Shifts available to meet your lifestyle
- Paid Time Off
- Holiday Pay
- Comprehensive Medical, Dental and Vision Insurance
- Health Savings Account option
- Additional Wellness Resources
- Life insurance offerings
- Supplemental Insurance plans
- Retirement plans with company match
- Continuing training & more
We'll keep all except the first
- for any list of duties/requirements/benefits, and
for prose. Do NOT repeat the job title as a heading. 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. Thus we need to decide which sections have real specific content. - About the role: we have introductory paragraphs about company and role. Could be About the role (or About Us). We'll include About the role with prose. - Responsibilities: WHAT TO EXPECT list is duties. So Responsibilities section with
- .
- Requirements: WHAT IT TAKES list is requirements. So Requirements section with
- ... ...
- ... ...
- Experience with stick welding.
- Your own tools.
- Certifications are a plus | EPA 608/609/Universal & ASE.
- Competitive Weekly Pay
- Overtime Opportunities and Weekly Bonus Opportunities
- Shifts available to meet your lifestyle
- Paid Time Off
- Holiday Pay
- Comprehensive Medical, Dental and Vision Insurance
- Health Savings Account option
- Additional Wellness Resources
- Life insurance offerings
- Supplemental Insurance plans
- Retirement plans with company match
- Continuing training & more
- .
- Qualifications: maybe WHAT WILL HELP YOU STAND OUT is qualifications/preferred qualifications. Could be Qualifications section.
- Skills: maybe we could separate certifications as Skills? But we could also include under Qualifications. The instruction says prefer a few substantive sections over many thin ones. So maybe combine Qualifications and Skills into one section? But we have separate headings list; we can choose to include only those with content. We have content for Qualifications (preferred qualifications). Skills maybe not explicitly listed besides "Ability to lift 50+ pounds", "Comfortable working with Computers", "Confident explaining a diagnosis", etc. Those are more like requirements. Could treat Skills as part of Requirements. To avoid thin sections, we could omit Skills section.
- Benefits: WHAT WE OFFER YOU list is benefits. So Benefits section.
- Pay: we have USD $36.00 - USD $40.00 /Hr. So Pay section.
- Schedule: we have "Shifts available to meet your lifestyle". That's schedule info. So Schedule section.
Thus we will have sections: About the role, Responsibilities, Requirements, Qualifications, Benefits, Pay, Schedule.
We need to ensure we don't include filler. All content is specific.
We need to output only HTML fragment, no /, no markdown fences.
We'll structure:
About the role
...combined intro and About Us...
Responsibilities
Requirements
Qualifications
Benefits