Field Service Technician
for section headings. Use - for any list of duties/requirements/benefits, and
for prose.
We need to decide what goes into prose vs list.
Probably About the role: a paragraph describing role.
Responsibilities: list.
Requirements: list (maybe Required Qualifications).
Qualifications: list (Preferred Qualifications).
Skills: maybe list of skills like ability to read documents, mathematical calculations, etc. Could be included under Requirements or Skills. Since we have both Required and Preferred qualifications, we could treat Required as Requirements, Preferred as Qualifications. Skills could be separate but we might not have explicit skills list beyond those. Could combine some into Skills: ability to work independently, clear speaking manner, goal setting, time management, independent judgment, self-motivation, etc. But those are already in Requirements. To avoid duplication, maybe we put those under Requirements and keep Qualifications for preferred. Skills could be omitted if no distinct content. But we need to include a section only when posting has real specific content. If we don't have distinct skills beyond those already captured, we could omit Skills section. However the instruction says "Prefer a few substantive sections over many thin ones." So we can omit Skills if not needed.
Thus sections: About the role, Responsibilities, Requirements (Required Qualifications), Qualifications (Preferred Qualifications), Benefits, Pay.
Check if any other sections like "About Airgas" could be considered About the role? Probably not; that's company description. Could be omitted as not required heading. The instruction says use headings for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). So we should only use those headings if we have content. The company description "About Airgas" is not one of those headings, so we should not include it. We should drop that content? But we must preserve ALL substantive information; do not invent or summarize away detail. However we cannot create a heading not in the list? The instruction says use
for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). It doesn't forbid other headings, but says "Use for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." It implies we should use those headings for sections. It doesn't say we cannot add other headings, but to follow the pattern we likely should only use those. The company description is substantive; we could put it under About the role? But About the role is for role description, not company. However we could incorporate company description into About the role paragraph? Might be stretching. Better to include a separate paragraph without heading? The instruction says output ONLY the HTML fragment; we can include
for prose anywhere. So we can include a paragraph about Airgas without a heading. That's allowed.
Thus we will include:
About the role
... role description ...
Responsibilities
... list ...
Requirements
... required qualifications ...
Qualifications
... preferred qualifications ...
Benefits
... benefits list ...
Pay
Pay Range: $30-40/hr
We must not repeat job title as heading. Good.
We must not put Job ID/requisition numbers as headings; we have none.
We must remove boilerplate: EEO, legal, etc. We'll drop those paragraphs.
We must preserve all substantive information: need to ensure we include all details from responsibilities, requirements, qualifications, benefits, pay.
Let's extract details precisely.
From posting:
**Role description** (the paragraph after early access): "The (Cryogenic) Field Service Technician is responsible for installing and servicing on-site nitrogen generation plants and bulk medical or industrial gas systems in a safe and operationally effective manner, in accordance with all federal, state/provincial and local codes, and Airgas policies. Supports the installation and upkeep of nitrogen on-site generation equipment. Supports cryogenic bulk installations both at Airgas facilities and customer sites. Restores and optimizes pressure reduction equipment associated with bulk delivery systems. Evaluates and provides solutions for electrical systems associated with N2 generation and cryogenic installations, including: motor controls and relays, low pressure, high pressure and liquid level alarm systems. Installs decals and warning signs for the proper identification of hazards, warnings, ownership, normal operational settings, emergency contacts, etc. Performs installation of piping systems in accordance with company SOP's. Performs Site Surveys to build alignment with all federal, state/provincial and local codes. Fosters a secure environment by providing fencing to protect installations from tampering or unauthorized entry. Performs periodic preventative maintenance tasks on N2 generation equipment based on the PM schedule. Performs annual inspections of all bulk installation sites to ensure their condition and excellent operation. Champions and upholds safety policies and procedures to nurture a secure workplace. Maintains an appropriate stock of recommended parts necessary to restore typical installations within the assigned customer base. Collaborates on additional projects as needed."
We'll put that as prose under About the role.
**Responsibilities**: Could be same as role description but we need to list duties. The role description already includes many duties; we could treat that as responsibilities list. But we already used it as About the role prose. To avoid duplication, we could split: About the role short summary, Responsibilities list of duties. However the instruction says preserve all substantive information; we can keep the role description as prose and also list responsibilities as bullet points, but that would duplicate content. Better to treat the role description as About the role (prose) and then Responsibilities as a list of the same duties but maybe we can condense? But we must not invent or summarize away detail; we can list them as bullet points preserving detail. The About the role could be a brief summary: "The Cryogenic Field Service Technician installs and services on-site nitrogen generation plants and bulk medical or industrial gas systems, ensuring compliance with codes and Airgas policies." That would be summarizing, which might be considered summarizing away detail. The instruction says do NOT invent or summarize away detail. So we should not summarize; we need to keep all detail. So perhaps we should not have an About the role section at all, or we can put the full description as prose under About the role, and then Responsibilities could be omitted to avoid duplication. But we need to follow the instruction: include a section ONLY when the posting has real, specific content for it. If we put the full description under About the role, we have content. Then Responsibilities could be omitted because we already covered duties in About the role. However the instruction expects we might have both sections; but it's okay to omit Responsibilities if we feel it's redundant. However we need to ensure we preserve all substantive information; we have it in About the role. So we can omit Responsibilities.
But the instruction says "Use for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." It doesn't require us to use all; just examples. So we can choose.
Thus we will have:
About the role
Full description...
Requirements
Required qualifications list
Qualifications
Preferred qualifications list
Benefits
Benefits list
Pay
Pay Range: $30-40/hr
We need to ensure we include all details from benefits and pay.
for prose. We need to decide what goes into prose vs list. Probably About the role: a paragraph describing role. Responsibilities: list. Requirements: list (maybe Required Qualifications). Qualifications: list (Preferred Qualifications). Skills: maybe list of skills like ability to read documents, mathematical calculations, etc. Could be included under Requirements or Skills. Since we have both Required and Preferred qualifications, we could treat Required as Requirements, Preferred as Qualifications. Skills could be separate but we might not have explicit skills list beyond those. Could combine some into Skills: ability to work independently, clear speaking manner, goal setting, time management, independent judgment, self-motivation, etc. But those are already in Requirements. To avoid duplication, maybe we put those under Requirements and keep Qualifications for preferred. Skills could be omitted if no distinct content. But we need to include a section only when posting has real specific content. If we don't have distinct skills beyond those already captured, we could omit Skills section. However the instruction says "Prefer a few substantive sections over many thin ones." So we can omit Skills if not needed. Thus sections: About the role, Responsibilities, Requirements (Required Qualifications), Qualifications (Preferred Qualifications), Benefits, Pay. Check if any other sections like "About Airgas" could be considered About the role? Probably not; that's company description. Could be omitted as not required heading. The instruction says use headings for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). So we should only use those headings if we have content. The company description "About Airgas" is not one of those headings, so we should not include it. We should drop that content? But we must preserve ALL substantive information; do not invent or summarize away detail. However we cannot create a heading not in the list? The instruction says use
for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). It doesn't forbid other headings, but says "Use for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." It implies we should use those headings for sections. It doesn't say we cannot add other headings, but to follow the pattern we likely should only use those. The company description is substantive; we could put it under About the role? But About the role is for role description, not company. However we could incorporate company description into About the role paragraph? Might be stretching. Better to include a separate paragraph without heading? The instruction says output ONLY the HTML fragment; we can include
for prose anywhere. So we can include a paragraph about Airgas without a heading. That's allowed. Thus we will include:
About the role
... role description ...
Responsibilities
- ... list ...
Requirements
- ... required qualifications ...
Qualifications
- ... preferred qualifications ...
Benefits
- ... benefits list ...
Pay
Pay Range: $30-40/hr
We must not repeat job title as heading. Good. We must not put Job ID/requisition numbers as headings; we have none. We must remove boilerplate: EEO, legal, etc. We'll drop those paragraphs. We must preserve all substantive information: need to ensure we include all details from responsibilities, requirements, qualifications, benefits, pay. Let's extract details precisely. From posting: **Role description** (the paragraph after early access): "The (Cryogenic) Field Service Technician is responsible for installing and servicing on-site nitrogen generation plants and bulk medical or industrial gas systems in a safe and operationally effective manner, in accordance with all federal, state/provincial and local codes, and Airgas policies. Supports the installation and upkeep of nitrogen on-site generation equipment. Supports cryogenic bulk installations both at Airgas facilities and customer sites. Restores and optimizes pressure reduction equipment associated with bulk delivery systems. Evaluates and provides solutions for electrical systems associated with N2 generation and cryogenic installations, including: motor controls and relays, low pressure, high pressure and liquid level alarm systems. Installs decals and warning signs for the proper identification of hazards, warnings, ownership, normal operational settings, emergency contacts, etc. Performs installation of piping systems in accordance with company SOP's. Performs Site Surveys to build alignment with all federal, state/provincial and local codes. Fosters a secure environment by providing fencing to protect installations from tampering or unauthorized entry. Performs periodic preventative maintenance tasks on N2 generation equipment based on the PM schedule. Performs annual inspections of all bulk installation sites to ensure their condition and excellent operation. Champions and upholds safety policies and procedures to nurture a secure workplace. Maintains an appropriate stock of recommended parts necessary to restore typical installations within the assigned customer base. Collaborates on additional projects as needed." We'll put that as prose under About the role. **Responsibilities**: Could be same as role description but we need to list duties. The role description already includes many duties; we could treat that as responsibilities list. But we already used it as About the role prose. To avoid duplication, we could split: About the role short summary, Responsibilities list of duties. However the instruction says preserve all substantive information; we can keep the role description as prose and also list responsibilities as bullet points, but that would duplicate content. Better to treat the role description as About the role (prose) and then Responsibilities as a list of the same duties but maybe we can condense? But we must not invent or summarize away detail; we can list them as bullet points preserving detail. The About the role could be a brief summary: "The Cryogenic Field Service Technician installs and services on-site nitrogen generation plants and bulk medical or industrial gas systems, ensuring compliance with codes and Airgas policies." That would be summarizing, which might be considered summarizing away detail. The instruction says do NOT invent or summarize away detail. So we should not summarize; we need to keep all detail. So perhaps we should not have an About the role section at all, or we can put the full description as prose under About the role, and then Responsibilities could be omitted to avoid duplication. But we need to follow the instruction: include a section ONLY when the posting has real, specific content for it. If we put the full description under About the role, we have content. Then Responsibilities could be omitted because we already covered duties in About the role. However the instruction expects we might have both sections; but it's okay to omit Responsibilities if we feel it's redundant. However we need to ensure we preserve all substantive information; we have it in About the role. So we can omit Responsibilities. But the instruction says "Use for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." It doesn't require us to use all; just examples. So we can choose.
Thus we will have:
About the role
Full description...
Requirements
- Required qualifications list
Qualifications
- Preferred qualifications list
Benefits
- Benefits list
Pay
Pay Range: $30-40/hr
We need to ensure we include all details from benefits and pay.