Field Service Technician
for sections like About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. Only include sections if posting has real specific content. We must not repeat job title. No metadata like Job ID. Remove boilerplate: cookie/navigation/legal/EEO/equal-opportunity/scam-warning, duplicated lines, application instructions. Also remove "AI Use in Our Interview Process", "Drug Testing Requirements", "Equal Employment Opportunity & Hiring Requirements", "Flexibility & Evolving Responsibilities"? The latter may be considered boilerplate? It's about flexibility; maybe keep if substantive? It says "Flexibility & Evolving Responsibilities This job posting is intended to convey the general nature..." That's generic boilerplate; likely remove. Also "Special Considerations" maybe keep? It includes travel, physical requirements. Could be part of Requirements or Qualifications. We'll need to extract substantive info.
Let's parse the posting:
- Opening: "The specific pay rate and level, if applicable, will depend on the successful candidate’s qualifications, prior experience and location." This is about pay but vague; we should not create Pay section unless specific numbers. So we omit Pay.
- “A Day In the Life” As a Field Service Technician you will maintain modular equipment in the field at customer sites and at the branch. You will perform problem solving maintenance for but not limited to mechanical, electrical and plumbing systems. You will also perform routine maintenance, cleaning and construction in the field of modular buildings. Update and record information on company assets and systems. Perform routine evaluations of work to be performed. Safely operate Company provided vehicle ( for section headings, - for lists,
for prose.
We must preserve all substantive information; do not invent or summarize away detail. So we need to keep details exactly as given, but we can format into lists.
We need to avoid duplication: Some duties appear in both "A Day In the Life" and "What You’ll Do". We should combine but not lose any detail. We should ensure we don't omit any specifics.
Let's extract each piece.
**A Day In the Life** prose:
- As a Field Service Technician you will maintain modular equipment in the field at customer sites and at the branch.
- You will perform problem solving maintenance for but not limited to mechanical, electrical and plumbing systems.
- You will also perform routine maintenance, cleaning and construction in the field of modular buildings.
- Update and record information on company assets and systems.
- Perform routine evaluations of work to be performed.
- Safely operate Company provided vehicle (About the Role
with paragraph from "A Day In the Life".
- for prose. We must preserve all substantive information; do not invent or summarize away detail. So we need to keep details exactly as given, but we can format into lists. We need to avoid duplication: Some duties appear in both "A Day In the Life" and "What You’ll Do". We should combine but not lose any detail. We should ensure we don't omit any specifics. Let's extract each piece. **A Day In the Life** prose: - As a Field Service Technician you will maintain modular equipment in the field at customer sites and at the branch. - You will perform problem solving maintenance for but not limited to mechanical, electrical and plumbing systems. - You will also perform routine maintenance, cleaning and construction in the field of modular buildings. - Update and record information on company assets and systems. - Perform routine evaluations of work to be performed. - Safely operate Company provided vehicle (About the Role
Responsibilities
with combined list from "A Day In the Life" duties and "What You’ll Do". But we already used "A Day In the Life" for About the Role; maybe we should not duplicate. Could treat "A Day In the Life" as About the Role (overview) and Responsibilities as detailed list from "What You’ll Do". However "A Day In the Life" also contains duties; but we can keep it as overview paragraph, not list. That's fine. -Requirements
with Must Haves and Nice to Haves and Special Considerations (physical). Could split into Qualifications and Skills but we can combine. -Benefits
with perks list. -Schedule
with Monday-Friday Dayshift. We must not create sections with filler. All have content. Now format. For About the Role: usecontaining the sentences. Could keep as one paragraph. For Responsibilities: use
- each item.
For Requirements: we could split into
Requirements
and then- for Must Haves and Nice to Haves and Special Considerations. But we might want to separate Must Haves vs Nice to Haves? Not required; we can just list all.
But we should preserve the distinction? The instruction: preserve ALL substantive information; do not invent or summarize away detail. Listing them together still preserves detail; not losing any. It's okay.
For Benefits:
- each perk.
For Schedule:
maybe. Now ensure we don't include any boilerplate like "EEO", "Drug Testing", etc. Check for any leftover: The text includes "#MMMC Monday-Friday Dayshift". We'll keep that. Now produce HTML. Let's craft. About the Role paragraph: "As a Field Service Technician you will maintain modular equipment in the field at customer sites and at the branch. You will perform problem solving maintenance for but not limited to mechanical, electrical and plumbing systems. You will also perform routine maintenance, cleaning and construction in the field of modular buildings. Update and record information on company assets and systems. Perform routine evaluations of work to be performed. Safely operate Company provided vehicle (<10,000lbs GVW) to travel to various locations and service modular and related equipment. Duties include installing and repairing equipment, and training customer employees on how to maintain machinery. Perform trial run of machinery to ensure performance rates and quality meet established specifications while delivering exceptional customer experiences." That's from A Day In the Life. Now Responsibilities list: combine items from What You’ll Do (maybe also include some from A Day In the Life that are not
- each perk.
For Schedule:
- for Must Haves and Nice to Haves and Special Considerations. But we might want to separate Must Haves vs Nice to Haves? Not required; we can just list all.
But we should preserve the distinction? The instruction: preserve ALL substantive information; do not invent or summarize away detail. Listing them together still preserves detail; not losing any. It's okay.
For Benefits: