Field Service Technician

We need to output HTML fragment with sections: About the role? Actually the posting includes description of company, tasks, responsibilities, who you are, skill requirements, beneficial qualities, benefits, overnight travel benefits, about us. We need to use

for section headings like About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We must not repeat job title. We need to include sections only when posting has real specific content. We need to preserve all substantive info, no boilerplate. We need to decide which sections to include. The posting includes: tasks & responsibilities (list of duties). Who are you? Core Responsibilities (maybe about safety etc). Skill Requirements. Beneficial Qualities. Benefits (including overnight travel benefits). About Us (mission). Pay? Not explicitly mentioned except "Competitive pay". That's a mention of pay but not specific amount. The rule: 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. It does state "Competitive pay". That's a statement about pay, albeit vague but it's still a statement. Should we include Pay section? The rule says 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"). "Competitive pay" is vague but not exactly placeholder like "not specified". It's a statement but not specific. Might be considered filler? The instruction: "never create Pay/Schedule/Benefits sections unless the posting actually states them." It does state "Competitive pay". So we could include Pay section with that line. However they also say "Prefer a few substantive sections over many thin ones." Might combine Pay into Benefits? But they have separate headings for Benefits and Pay. We could include Benefits section covering benefits, and maybe Pay section with "Competitive pay". Schedule? Not mentioned except overnight travel frequency (2-4 nights a week). That's schedule info. Could include Schedule section with that detail. However they said never create Schedule unless posting actually states them. It does state average overnight travel will be 2-4 nights a week. That's schedule info. So we could include Schedule. We need to avoid duplication: Overnight Travel Benefits appears twice; we should include once. We need to remove boilerplate: cookie/navigation/legal/EEO etc. Not present. We need to use

for section headings. Use

• for any list of duties/requirements/benefits. Use

  for prose. We need to preserve all substantive information. Let's extract content: Company description: "Who is DESOTEC? To protect the planet – that’s our mission at DESOTEC. From air, soil and gas to water and other liquids: at DESOTEC, we purify through sustainable, mobile filter solutions based on activated carbon. Through a smart rental model, our filters are distributed to production companies all over the US. When the carbon inside of the filters is saturated, we make sure to retrieve it for reactivation. That is how we unburden our customers of the administrative, moral, logistical, and ecological consequences of their purification needs. The result: they can focus 100% on what really counts - sustainable production." That's about the company; could be "About Us" section. Tasks & responsibilities: bullet list: - Execute carbon exchanges at customer sites with slurry tankers. - While at the customer site, you will operate the tanker, air compressor, customer equipment, and various forms of man lifts if needed. - Transport the Hurricane vacuum unit to and from customers' sites with a truck. - While at the customer's site, you will be responsible for using the Hurricane to remove the spent carbon from the customer's vessel. - Once the vessel is empty, you will use a forklift to fill it with bulk bags of fresh carbon. - Loading and unloading techniques may vary. - Operate specially designed mobile filter hydraulic trailer at customer’s sites to exchange spent filters with fresh ones. - Assist with loading and unloading filters and tankers at the Darlington Hub. Who are you? Core Responsibilities: - Create and sustain a safe working environment and culture within the company - Communicate well with customers - Must be able to work well in a team environment - Ensure company property is well-maintained - Desire to learn Skill Requirements: - Active Driver’s License - Perform physical functions per job requirements - Solution-oriented mindset - Proficient with mechanical tools and equipment Beneficial Qualities: - 2 years Field Service experience - Hazardous Materials Endorsement - Dry bulk experience - HAZWOPER 40 - Industrial Vacuum Experience - CDL Benefit: Desotec will cover the cost of obtaining a CDL-A license with a 12-month commitment and a promotion to Field Service Technician-C (FSTC) upon completion Overnight Travel Benefits: When overnight travel is required, technicians will have the option of company-paid hotel accommodations along with an $85 daily meal allowance for overnight stays. Average overnight travel will be 2-4 nights a week What's in it for you? (Benefits list): - Benefits effective immediately - Competitive pay - Dollar-for-dollar 401(k) match up to 4% - 10 paid holidays - Paid parental leave - Company-paid vision insurance - Company-paid short-term disability coverage - Company-paid long-term disability coverage - Career growth and development opportunities - On-the-job training - Company-paid hotels during overnight travel - $85/day meal allowance while traveling Overnight Travel Benefits repeated. About Us: purpose and mission etc. We need to avoid duplication: Overnight Travel Benefits appears twice; we can combine. We need to decide sections: Possibly: - About the role (maybe a brief description of role? Not explicitly given; we have tasks & responsibilities. Could use "Responsibilities" heading for tasks. "About the role" maybe not needed. We have "Who are you?" which is like "Requirements" or "Qualifications". Could map to "Requirements" (skill requirements) and "Qualifications" (beneficial qualities). But we have both skill requirements and beneficial qualities. We have "Benefits" section. We have "Pay" (competitive pay). We have "Schedule" (overnight travel frequency). We have "About Us" (company mission). We need to use headings exactly as given: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We must not create headings without real content. Let's see if we have content for each: - About the role: Could be a brief description of the role (maybe from tasks?). The posting doesn't have a separate "About the role" paragraph; but we could use the initial description of tasks as about the role. However we already have Responsibilities for tasks. Might be okay to have About the role with a short paragraph summarizing the role: e.g., "As a Field Service Technician, you will perform carbon exchanges, operate equipment, and assist with logistics." That's derived from tasks. That's substantive. - Responsibilities: list of duties (tasks & responsibilities + core responsibilities? Actually core responsibilities are more about safety etc. Could be part of Responsibilities. We'll combine tasks and core responsibilities under Responsibilities. - Requirements: maybe skill requirements (active driver's license, physical functions, solution-oriented mindset, proficient with mechanical tools). That's specific. - Qualifications: beneficial qualities (2 years field service, hazmat endorsement, etc.) plus maybe the CDL benefit? Actually CDL is a beneficial quality. Also the benefit of covering CDL cost could be under Benefits. - Skills: maybe we could list mechanical tools proficiency etc. But we already have Skills heading; we could put "Proficient with mechanical tools and equipment" etc. However we already used skill requirements. Might be redundant. Better to follow typical mapping: Requirements = mandatory; Qualifications = preferred; Skills = maybe specific abilities. But we have limited distinct categories. We could assign: - Requirements: Active Driver’s License, Perform physical functions per job requirements, Solution-oriented mindset. - Qualifications: 2 years Field Service experience, Hazardous Materials Endorsement, Dry bulk experience, HAZWOPER 40, Industrial Vacuum Experience, CDL. - Skills: Proficient with mechanical tools and equipment (maybe also operating tanker, air compressor, forklift, man lifts, Hurricane unit, mobile filter hydraulic trailer). But those are more duties. Could put under Responsibilities. Given the instruction to prefer few substantive sections over many thin ones, maybe we combine some. But we must use the headings exactly as given if we include them. We could include only those headings that have substantive content. Let's evaluate each: - About the role: we can write a short paragraph summarizing the role based on tasks. That's substantive. - Responsibilities: we have a list of duties (tasks & responsibilities + core responsibilities). That's substantive. - Requirements: we have skill requirements (active driver's license, physical functions, solution-oriented mindset, proficient with mechanical tools). That's substantive. - Qualifications: we have beneficial qualities (2 years field service, hazmat endorsement, dry bulk, HAZWOPER 40, industrial vacuum experience, CDL). That's substantive. - Skills: we could list specific skills like operating tanker, air compressor, forklift, man lifts, Hurricane unit, mobile filter hydraulic trailer. But those are more duties. Could be considered skills. However we already used skill requirements for similar. Might be thin. Could omit Skills section if not enough distinct content. But we need to decide. - Benefits: we have list of benefits (immediate benefits, competitive pay, 401k match, holidays, parental leave, insurances, career growth, on-the-job training, company-paid hotels, meal allowance). That's substantive. - Pay: we have "Competitive pay". That's a statement but maybe too thin. Could combine into Benefits. But we have separate Pay heading; if we include it, we need to put something like "Competitive pay". That's not placeholder but it's vague. Might be acceptable. However the instruction says prefer few substantive sections over many thin ones. Including Pay as a separate thin section may be discouraged. Could omit Pay and include competitive pay under Benefits. - Schedule: we have overnight travel frequency (2-4 nights a week). That's schedule info. Could be a short paragraph. That's substantive. Thus we could include sections: About the role, Responsibilities, Requirements, Qualifications, Benefits, Schedule. Omit Skills and Pay. But we need to ensure we don't miss any substantive info: The benefit of covering CDL cost is under Benefits? Actually it's under "Benefit: Desotec will cover the cost of obtaining a CDL-A license..." That's a benefit. So include in Benefits. Now we need to format. We'll produce HTML fragment:

  About the role

  As a Field Service Technician at DESOTEC, you will perform carbon exchanges at customer sites, operate slurry tankers, Hurricane vacuum units, forklifts, man lifts, and mobile filter hydraulic trailers, and assist with loading/unloading at the Darlington Hub while maintaining safety and equipment standards.

  Responsibilities

  • Execute carbon exchanges at customer sites with slurry tankers.
  • Operate the tanker, air compressor, customer equipment, and various man lifts as needed.
  • Transport the Hurricane vacuum unit to and from customer sites with a truck.
  • Use the Hurricane to remove spent carbon from customer vessels.
  • Use a forklift to fill vessels with bulk bags of fresh carbon.
  • Loading and unloading techniques may vary.