Apprentice Fire Sprinkler Inspector
FSS Technologies · Bemidji, MN · 4 wk ago
Management$18–$25/hrFull-time
We need to output HTML fragment with headings for sections: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. Only include sections if posting has real specific content. We need to parse the posting.
We have sections: About FSS Technologies (company overview) maybe "About the role"? The posting includes "Position Overview" and "Essential Functions" etc. We need to map to headings.
We must not repeat job title as heading. No Job ID etc.
We need to include sections only when posting has real specific content.
Let's identify content:
- About the role: Could be "Position Overview" describing Apprentice Fire Sprinkler Inspector, entry-level field-based training, work alongside qualified inspector, etc. That's substantive.
- Responsibilities: Essential Functions list duties: inspection and testing, system impairments and customer coordination, documentation and reporting, safety and vehicle use, training and development. Those are responsibilities.
- Requirements: Qualifications section includes Required qualifications: age, HS diploma, driver's license, math skills, mechanical aptitude, ability to use smartphone/tablet, follow instructions, pass pre-employment screening. Also maybe "Preferred" but that's not required.
- Qualifications: Might be overlapping with Requirements. The instruction says use headings for sections like About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We need to decide which to include. Possibly we can combine Requirements and Qualifications? But they are separate headings. We need to include only if posting has real specific content for that heading.
We have "Qualifications" section in posting (the "Qualifications" heading). It includes Required and Preferred. So we can put that under
for sections: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. Only include sections if posting has real specific content. We need to parse the posting.
We have sections: About FSS Technologies (company overview) maybe "About the role"? The posting includes "Position Overview" and "Essential Functions" etc. We need to map to headings.
We must not repeat job title as heading. No Job ID etc.
We need to include sections only when posting has real specific content.
Let's identify content:
- About the role: Could be "Position Overview" describing Apprentice Fire Sprinkler Inspector, entry-level field-based training, work alongside qualified inspector, etc. That's substantive.
- Responsibilities: Essential Functions list duties: inspection and testing, system impairments and customer coordination, documentation and reporting, safety and vehicle use, training and development. Those are responsibilities.
- Requirements: Qualifications section includes Required qualifications: age, HS diploma, driver's license, math skills, mechanical aptitude, ability to use smartphone/tablet, follow instructions, pass pre-employment screening. Also maybe "Preferred" but that's not required.
- Qualifications: Might be overlapping with Requirements. The instruction says use headings for sections like About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We need to decide which to include. Possibly we can combine Requirements and Qualifications? But they are separate headings. We need to include only if posting has real specific content for that heading.
We have "Qualifications" section in posting (the "Qualifications" heading). It includes Required and Preferred. So we can put that under Qualifications
.
We also have "Requirements" maybe not explicit separate heading; but we could treat the "Required" part as Requirements. However the posting already has a Qualifications heading with Required and Preferred. To avoid duplication, we could put Requirements as the "Required" subset inside Qualifications? But instruction says use headings for those categories; we can include both if content distinct. Might be okay to have Requirements (the required qualifications) and Qualifications (maybe preferred?). But that seems redundant.
Better: Use "Requirements" for the required qualifications, and "Qualifications" for preferred or additional qualifications? However the posting lumps them together under "Qualifications". Could split: Required -> Requirements, Preferred -> Qualifications. That seems plausible.
We also have "Skills": maybe we can extract skills from responsibilities: mechanical aptitude, ability to use smartphone/tablet, basic math, communication, etc. Could be a Skills section.
We have "Benefits": The posting includes "What We Offer" with Pay, Growth, Training, Equipment, Benefits (medical, dental, vision, 401k, life insurance, PTO, holidays). So we have Benefits content.
We have "Pay": explicit Pay: $18 – $25 per hour.
We have "Schedule": The posting mentions "Work a full-time schedule that may include early starts, overtime, and occasional evening or weekend work when customer operations require it. Some overnight travel within the FSS service territory may be required." That's schedule info.
Thus we can include all sections.
Now we need to format: Use for each section heading. Use - for any list of duties/requirements/benefits. Use
for prose.
We must preserve ALL substantive information; do not invent or summarize away detail. Remove boilerplate etc.
We need to output only HTML fragment, no /, no markdown fences.
Let's craft.
First, maybe a short paragraph for metadata? Not needed.
We'll start with
About the role
then containing position overview description.
Then
Responsibilities
then with each essential function category as - maybe with sub-bullets? The instruction says use
- for any list of duties/requirements/benefits. Could nest? Probably just top-level list items; we can include sub-details within
- as prose.
We need to preserve all substantive information: So each duty list item should include the details from the posting.
Let's extract duties:
Essential Functions categories:
1. Inspection and Testing
- Help perform scheduled inspections, tests, and maintenance on wet pipe, dry pipe, pre-action, deluge, and antifreeze sprinkler systems, standpipes, and fire pumps.
- Visually inspect sprinklers, piping, hangers, bracing, control valves, gauges, fire department connections, and signage, and look for leaks, corrosion, painted or loaded sprinklers, obstructions, and missing parts.
- Help operate control valves and perform main drain tests, waterflow alarm (inspector’s test) tests, and valve supervisory (tamper) switch tests.
- Help perform dry pipe valve trip tests, quick-opening device tests, air supply and low-air alarm checks, and fire pump tests.
- Check antifreeze concentration, spare sprinkler cabinets, gauge dates, and other items required by NFPA 25.
- Perform minor maintenance and corrective work as directed by your supervising inspector, within the limits of your apprentice status and applicable state licensing law.
2. System Impairments and Customer Coordination
- Before any test, confirm with the building contact and the alarm monitoring company that the system may be tested, and follow FSS impairment procedures whenever a system is taken out of service.
- Before leaving a site, confirm that every system you worked on is back in service, control valves are open and supervised, and the building contact and monitoring company have been notified.
- Treat customers, building occupants, and site staff with courtesy and respect their property, schedules, and site rules.
3. Documentation and Reporting
- Record inspection and test results accurately and completely in FSS forms or software, including photos of deficiencies.
- Record only work that was actually performed and conditions that were actually observed. Falsifying, estimating, or copying forward inspection results is prohibited and is grounds for discipline up to and including termination.
- Report deficiencies to your supervising inspector the same day, and report any condition that could prevent a system from working (such as a closed valve, frozen pipe, or major leak) immediately.
4. Safety and Vehicle Use
- Follow the FSS Safety Program, OSHA requirements, and all site-specific safety rules, and wear required personal protective equipment (PPE).
- Use ladders, lifts, and equipment only after you have been trained and authorized to use them.
- Report every injury, near miss, property damage, and vehicle incident to your supervisor immediately, following FSS incident reporting procedures.
- Drive a company vehicle between job sites safely and in compliance with FSS vehicle, fleet, and distracted driving policies.
5. Training and Development
- Complete all assigned classroom, online, and on-the-job training, and keep an accurate record of your training hours.
- Work toward NICET Level I certification in Inspection and Testing of Water-Based Systems within the timeframe set in your training plan, and toward higher levels after that.
- Obtain and keep current any apprentice or trainee registration required by the state where you work.
Now Requirements (Required qualifications):
- At least 18 years of age.
- High school diploma or GED.
- Valid driver’s license and a driving record that meets the standards of FSS and its insurance carrier.
- Basic math skills, including reading pressure gauges and performing simple calculations.
- Mechanical aptitude and willingness to learn how fire protection systems work.
- Ability to use a smartphone or tablet to complete reports.
- Ability to follow written and verbal instructions and to communicate clearly with coworkers and customers.
- Successful completion of pre-employment screening after a conditional offer of employment, which may include a background check, motor vehicle record review, and drug screen, as permitted by applicable state and local law.
Preferred qualifications (we could put under Qualifications heading):
- Experience in a trade such as plumbing, pipefitting, HVAC, mechanical service, or fire protection, including military experience.
- Vocational or technical school coursework.
- OSHA 10-Hour Construction certification.
- Experience with hand tools, ladders, and aerial or scissor lifts.
Physical Demands and Work Environment: Could be part of Requirements? Might be separate but not in headings list. Could be included under Requirements as additional details. But we have no heading for Physical Demands; we could incorporate into Requirements as a list item.
But we need to preserve all substantive information. So we should include Physical Demands and Work Environment somewhere. Perhaps under Requirements as a subsection? Or we could create a separate section but not in allowed headings; better to incorporate into Requirements as list items.
Similarly, "What We Offer" includes Pay, Growth, Training, Equipment, Benefits. We have separate headings for Pay, Benefits, maybe also Training? Not in list but we could put under Benefits or maybe under Qualifications? The instruction only lists those headings; we should not create extra headings like Growth or Training. So we need to fit that content into allowed sections: Pay, Benefits, maybe Schedule. The "Growth", "Training", "Equipment" could be placed under Benefits? Or maybe under Qualifications? But they are not exactly qualifications. Could be placed under Benefits as part of "What We Offer". However Benefits heading is for benefits like medical, dental, vision, 401k, life insurance, PTO, holidays. The "What We Offer" also includes Growth, Training, Equipment. We could incorporate those into Benefits section as additional bullet points, but that might be misleading. However instruction says include a section ONLY when the posting has real, specific content for it — never emit a heading followed by filler/placeholder text. It does not forbid adding extra content under a heading that is not exactly matching but still relevant. For Benefits, we could list the benefits plus also mention growth path, training, equipment as part of what's offered. That seems okay.
Pay section: we have Pay: $18 – $25 per hour. Starting pay depends on skills, experience, and certifications. Because this position is non-exempt, you will be paid for all hours worked, including overtime as required by law.
Schedule section: we have schedule info: full-time schedule that may include early starts, overtime, occasional evening or weekend work when customer operations require it. Some overnight travel within the FSS service territory may be required.
Now we need to avoid boilerplate: remove EEO etc. Also remove "Commitment to Inclusion" etc.
Now produce HTML.
We'll structure:
About the role
...
Responsibilities
- ...
...
Requirements
- ...
...
Qualifications
- ...
...
Skills
Maybe we can list skills derived: mechanical aptitude, basic math, ability to use smartphone/tablet, communication, ability to follow instructions, etc. But many of those are already in Requirements. Could still create Skills section with those. However we risk duplication. But instruction says preserve ALL substantive information; duplication is okay as long as we don't lose info. But we should avoid unnecessary duplication? Not prohibited. However better to avoid redundancy; but we can still include Skills with items like mechanical aptitude, basic math, ability to use smartphone/tablet, communication, ability to follow instructions, etc. However many are already in Requirements; but it's okay.
Alternatively we could omit Skills if we think it's covered. But we need to decide if posting has real specific content for Skills. It does mention mechanical aptitude, basic math skills, ability to use smartphone/tablet, ability to follow written and verbal instructions, communicate clearly. Those are skills. So we can create Skills section.
Now Benefits section: include medical, dental, vision insurance, 401(k), life insurance, paid time off, paid holidays, plus mention growth path, training, equipment.
Pay section: include pay range and note
- for any list of duties/requirements/benefits. Use
for prose. We must preserve ALL substantive information; do not invent or summarize away detail. Remove boilerplate etc. We need to output only HTML fragment, no /, no markdown fences. Let's craft. First, maybe a short paragraph for metadata? Not needed. We'll start with
About the role
thencontaining position overview description. Then
Responsibilities
then- with each essential function category as
- maybe with sub-bullets? The instruction says use
- for any list of duties/requirements/benefits. Could nest? Probably just top-level list items; we can include sub-details within
- as prose.
We need to preserve all substantive information: So each duty list item should include the details from the posting.
Let's extract duties:
Essential Functions categories:
1. Inspection and Testing
- Help perform scheduled inspections, tests, and maintenance on wet pipe, dry pipe, pre-action, deluge, and antifreeze sprinkler systems, standpipes, and fire pumps.
- Visually inspect sprinklers, piping, hangers, bracing, control valves, gauges, fire department connections, and signage, and look for leaks, corrosion, painted or loaded sprinklers, obstructions, and missing parts.
- Help operate control valves and perform main drain tests, waterflow alarm (inspector’s test) tests, and valve supervisory (tamper) switch tests.
- Help perform dry pipe valve trip tests, quick-opening device tests, air supply and low-air alarm checks, and fire pump tests.
- Check antifreeze concentration, spare sprinkler cabinets, gauge dates, and other items required by NFPA 25.
- Perform minor maintenance and corrective work as directed by your supervising inspector, within the limits of your apprentice status and applicable state licensing law.
2. System Impairments and Customer Coordination
- Before any test, confirm with the building contact and the alarm monitoring company that the system may be tested, and follow FSS impairment procedures whenever a system is taken out of service.
- Before leaving a site, confirm that every system you worked on is back in service, control valves are open and supervised, and the building contact and monitoring company have been notified.
- Treat customers, building occupants, and site staff with courtesy and respect their property, schedules, and site rules.
3. Documentation and Reporting
- Record inspection and test results accurately and completely in FSS forms or software, including photos of deficiencies.
- Record only work that was actually performed and conditions that were actually observed. Falsifying, estimating, or copying forward inspection results is prohibited and is grounds for discipline up to and including termination.
- Report deficiencies to your supervising inspector the same day, and report any condition that could prevent a system from working (such as a closed valve, frozen pipe, or major leak) immediately.
4. Safety and Vehicle Use
- Follow the FSS Safety Program, OSHA requirements, and all site-specific safety rules, and wear required personal protective equipment (PPE).
- Use ladders, lifts, and equipment only after you have been trained and authorized to use them.
- Report every injury, near miss, property damage, and vehicle incident to your supervisor immediately, following FSS incident reporting procedures.
- Drive a company vehicle between job sites safely and in compliance with FSS vehicle, fleet, and distracted driving policies.
5. Training and Development
- Complete all assigned classroom, online, and on-the-job training, and keep an accurate record of your training hours.
- Work toward NICET Level I certification in Inspection and Testing of Water-Based Systems within the timeframe set in your training plan, and toward higher levels after that.
- Obtain and keep current any apprentice or trainee registration required by the state where you work.
Now Requirements (Required qualifications):
- At least 18 years of age.
- High school diploma or GED.
- Valid driver’s license and a driving record that meets the standards of FSS and its insurance carrier.
- Basic math skills, including reading pressure gauges and performing simple calculations.
- Mechanical aptitude and willingness to learn how fire protection systems work.
- Ability to use a smartphone or tablet to complete reports.
- Ability to follow written and verbal instructions and to communicate clearly with coworkers and customers.
- Successful completion of pre-employment screening after a conditional offer of employment, which may include a background check, motor vehicle record review, and drug screen, as permitted by applicable state and local law.
Preferred qualifications (we could put under Qualifications heading):
- Experience in a trade such as plumbing, pipefitting, HVAC, mechanical service, or fire protection, including military experience.
- Vocational or technical school coursework.
- OSHA 10-Hour Construction certification.
- Experience with hand tools, ladders, and aerial or scissor lifts.
Physical Demands and Work Environment: Could be part of Requirements? Might be separate but not in headings list. Could be included under Requirements as additional details. But we have no heading for Physical Demands; we could incorporate into Requirements as a list item.
But we need to preserve all substantive information. So we should include Physical Demands and Work Environment somewhere. Perhaps under Requirements as a subsection? Or we could create a separate section but not in allowed headings; better to incorporate into Requirements as list items.
Similarly, "What We Offer" includes Pay, Growth, Training, Equipment, Benefits. We have separate headings for Pay, Benefits, maybe also Training? Not in list but we could put under Benefits or maybe under Qualifications? The instruction only lists those headings; we should not create extra headings like Growth or Training. So we need to fit that content into allowed sections: Pay, Benefits, maybe Schedule. The "Growth", "Training", "Equipment" could be placed under Benefits? Or maybe under Qualifications? But they are not exactly qualifications. Could be placed under Benefits as part of "What We Offer". However Benefits heading is for benefits like medical, dental, vision, 401k, life insurance, PTO, holidays. The "What We Offer" also includes Growth, Training, Equipment. We could incorporate those into Benefits section as additional bullet points, but that might be misleading. However instruction says include a section ONLY when the posting has real, specific content for it — never emit a heading followed by filler/placeholder text. It does not forbid adding extra content under a heading that is not exactly matching but still relevant. For Benefits, we could list the benefits plus also mention growth path, training, equipment as part of what's offered. That seems okay.
Pay section: we have Pay: $18 – $25 per hour. Starting pay depends on skills, experience, and certifications. Because this position is non-exempt, you will be paid for all hours worked, including overtime as required by law.
Schedule section: we have schedule info: full-time schedule that may include early starts, overtime, occasional evening or weekend work when customer operations require it. Some overnight travel within the FSS service territory may be required.
Now we need to avoid boilerplate: remove EEO etc. Also remove "Commitment to Inclusion" etc.
Now produce HTML.
We'll structure:
About the role
...
Responsibilities
- ... ...
Requirements
- ... ...
Qualifications
- ... ...
Skills
Maybe we can list skills derived: mechanical aptitude, basic math, ability to use smartphone/tablet, communication, ability to follow instructions, etc. But many of those are already in Requirements. Could still create Skills section with those. However we risk duplication. But instruction says preserve ALL substantive information; duplication is okay as long as we don't lose info. But we should avoid unnecessary duplication? Not prohibited. However better to avoid redundancy; but we can still include Skills with items like mechanical aptitude, basic math, ability to use smartphone/tablet, communication, ability to follow instructions, etc. However many are already in Requirements; but it's okay. Alternatively we could omit Skills if we think it's covered. But we need to decide if posting has real specific content for Skills. It does mention mechanical aptitude, basic math skills, ability to use smartphone/tablet, ability to follow written and verbal instructions, communicate clearly. Those are skills. So we can create Skills section. Now Benefits section: include medical, dental, vision insurance, 401(k), life insurance, paid time off, paid holidays, plus mention growth path, training, equipment. Pay section: include pay range and note
- maybe with sub-bullets? The instruction says use