Fire Sprinkler Technician

We need to output HTML fragment with sections for headings where content exists. Use

for section headings like About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We need to decide which sections have content. From posting: Job Summary (but we shouldn't repeat job title). There's a "Job Summary JOB DESCRIPTION" then description of responsibilities. We can treat that as "About the role" maybe? Actually "Job Summary" is like about the role. We'll output

About the role

with paragraph(s) summarizing responsibilities? But we need to preserve all substantive info; we can't summarize away detail. We need to keep details but can format as paragraphs and lists. We have sections: Essential Job Duties (list). Qualifications (Education, Training, Certifications; Experience, Knowledge, Skill Requirements; Communication Skills; Systems And Software Skills; Other Qualifications; Physical & Work Environment Requirements). Benefits (list). About Us (company description). Core Values (list). Also maybe Pay/Schedule not present, so omit. We must not include boilerplate like EEO etc. Remove duplicated lines. Also remove application instructions (none). Remove cookie/navigation/legal etc. We need to preserve all substantive info: duties list, qualifications details, benefits list, about us, core values. We must not create sections with placeholder text. So only include sections where we have real content. We'll produce:

About the role

with paragraph(s) from Job Summary? The Job Summary includes: "The responsibility of a Fire Sprinkler Technician is to successfully lay out, fabricate, assemble, install fires sprinkler systems, as well as maintain piping systems, fixtures, sprinklers and industrial processing systems." That's substantive. We'll put that in a

. Then

Responsibilities

with

• list of essential job duties. Then

  Qualifications

  maybe we can break into sub-sections? But only allowed headings from list; we could still use

  Qualifications

  and inside include paragraphs and lists for each subcategory. That's okay. Then

  Skills

  maybe combine communication, systems/software, other qualifications? But we have separate categories: Communication Skills, Systems And Software Skills, Other Qualifications, Physical & Work Environment Requirements. Could put them under Qualifications or Skills. Since we have a Skills heading allowed, we could put communication, systems/software, other qualifications there. Physical & Work Environment maybe also under Skills? Or we could create a separate section for Requirements? But we have Requirements heading allowed. Could put Experience, Knowledge, Skill Requirements under Requirements. However we already have Qualifications heading; maybe better to follow typical structure: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits. But we must not create empty sections. Let's map: - About the role: job summary paragraph. - Responsibilities: essential job duties list. - Requirements: Experience, Knowledge, Skill Requirements (3-5 years experience, etc.) plus maybe Physical & Work Environment Requirements? Could be separate but we can include under Requirements. - Qualifications: Education, Training, Certifications; maybe also Other Qualifications? But Other Qualifications includes driver's license, drug policy, background screening. Could be under Qualifications. - Skills: Communication Skills, Systems And Software Skills. - Benefits: benefits list. - About Us: company description (maybe under About the role? But we already used About the role for job summary. Could add another section "About the company" but not in allowed headings list. Allowed headings: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. No "About Us". So we need to fit About Us somewhere else, maybe under Qualifications? Not ideal. Could we treat About Us as part of "About the role"? Might be okay to extend that paragraph with company description. The instruction: "Use

  for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." It says e.g., meaning those are examples, not exclusive? It says use

  for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). Likely they expect only those headings. So we should not add other headings like About Us. We need to incorporate that content somewhere else, maybe under Qualifications or Skills? But that would be weird. Perhaps we can treat About Us as part of "About the role" heading, combining job summary and company description. That seems acceptable: About the role can include both role description and company info. Thus we will have About the role paragraph containing both the job summary and the About Us description. Now we need to ensure we don't repeat job title as heading (we aren't). No Job ID. Now we need to strip boilerplate: EEO statements, equal opportunity, etc. Also remove duplicated lines. Also remove "We are fully committed to equal opportunities..." etc. Also remove "Summit Fire & Security participates in E-Verify..." etc. Also remove "While this job description is intended to be an accurate reflection..." etc. Also remove "We are an Equal Opportunity, Affirmative Action employer." etc. Also remove "Summit Fire & Security is an equal-opportunity employer committed to diversity..." etc. Also remove "We are fully committed to equal opportunities..." etc. Also remove "Other duties may be assigned." maybe keep? It's part of duties but it's generic; we can keep as part of responsibilities list? It's not substantive detail; maybe we can keep but it's not boilerplate. It's okay. Now we need to preserve all substantive info: duties list, qualifications details, benefits list, core values. Core Values: not in allowed headings but we can include under Qualifications or Skills? Could add a section "Qualifications" and include core values as a list? But core values are not qualifications. However we could put them under "About the role" as well? Might be okay to include under "About the role" after company description. But the instruction: "Prefer a few substantive sections over many thin ones." So we could have a section "Qualifications" and include core values as a list inside it? Might be confusing. Alternatively, we could add a section "Skills" and include core values there? Not ideal. Maybe we can treat core values as part of "About the role" as well, describing company culture. That seems plausible: About the role includes role description, company overview, core values. Thus About the role will have multiple paragraphs: job summary, company description, core values. Now we need to format lists: For responsibilities, we have list items: - Install pipe systems and valves - Cut, thread, assemble and bond piping and tubes according to specifications - Modify, clean and maintain pipe systems, units and fittings - Remove and replace worn components - Follow blueprints to meet product specifications - Calculate material measurements to verify specifications - Mentor and coach Fire Sprinkler Fitter Apprentice’s and Helpers on proper installation techniques - Ensure company provided vehicle is clean and well maintained in accordance with company policies. - Other duties may be assigned. We'll put each as

  . Now Qualifications: we have several subcategories. Education, Training, Certifications: - HS Diploma or equivalent, required. - Advanced technical school training or related work experience, preferred. - Current Fire Sprinkler License, required. Experience, Knowledge, Skill Requirements: - 3-5 years’ experience installing pipe systems and valves, required. - 5+ years’ experience, preferred. - Must be able to work alone and as part of a team. - Basic math skills, mechanical aptitude, problem solving skills, customer service skills, decision making skills, ability to multitask, ability to meet project schedules, ability to plan and organize, troubleshooting skills, and the ability to train other is required. Communication Skills: - Must have the ability to effectively read, write and communicate in English with employees and customers. Systems And Software Skills: - Ability to operate a computer, tablet and read electronic blueprints required. - Experience with SalesForce and Microsoft Office is preferred. Other Qualifications: - Valid driver’s license with acceptable driving record required - Must be able to comply with SFS’s Drug and Alcohol policy and Background screening requirements, which may also include customer specific requirements based on contractual agreement Physical & Work Environment Requirements: - Reasonable accommodations may be made to enable individuals with disabilities to perform Essential Job Duties. - Physical Requirements: While performing the duties of this job, the employee is frequently required to bend, ascend and descend step stools, ladders and stairs, kneel, lift 50lbs, sit, stoop, twist, and work at heights. - Work Environment: Frequent local travel and occasional regional and non-regional travel is required. Employee will frequently be required to work inside and outside in hot/cold temperatures and be exposed to loud noises, cramped quarters, dust, fumes and odors, standing on hard surfaces, and electrical hazards frequently. Employees will occasionally be exposed to chemicals, moving machinery, uneven and slippery surfaces. Employee must consistently wear all appropriate personal protective equipment, as required by company safety policies. We need to preserve all that. We'll format as paragraphs or lists. We can group each subcategory under

  ? Not allowed; only

  for section headings. But we can use

  with bold headings? The instruction only says use

  for section headings; doesn't forbid using other headings like

  or . But to be safe, we can just use

  with bold text using or just plain sentences. We'll keep it simple: under

  Qualifications

  , we will have paragraphs for each bullet group, maybe using

  • for each requirement. But we have many items; we could make a big list. Better: Use
    • for each distinct requirement line. We'll combine all qualification items into a single list? Might lose grouping but still preserve all info. The instruction: "Use
      • for any list of duties/requirements/benefits". So we can use lists for requirements. Thus under Qualifications we can have a
        with each requirement as
        • . That includes education, experience, communication, systems, other qualifications, physical requirements. But physical requirements are lengthy sentences; we can still put each sentence as
        • . That's okay. Now Benefits: list as
          • . Now About the role: we will have paragraphs. Now we need to ensure we don't include boilerplate like EEO etc. We'll remove those paragraphs. Now we need to output only HTML fragment. Let's craft. First, About the role: Paragraph 1: "The responsibility of a Fire Sprinkler Technician is to successfully lay out, fabricate, assemble, install fire sprinkler systems, as well as maintain piping systems, fixtures, sprinklers and industrial processing systems." Paragraph 2: Company description from About Us: "Are you interested in working for the nation’s leading fire protection company and beginning a rewarding and satisfying career that helps save the lives of thousands each year? Do you want to be a part of a growing and expanding team of industry experts? If so, exploring career opportunities with Summit Fire & Security may be right for you! Summit Fire & Security, a subsidiary of SFP Holding, Inc. (Summit Companies), is a full-service provider for fire detection, suppression, and security with a full suite of capabilities that includes design, installation, testing, inspections, and maintenance. We serve customers across many verticals on a local, regional, and national scale. We’re proud of our well-deserved reputation for quality work that’s completed by our talented and experienced installation workforce. Summit Fire &