Fire Alarm Systems Design Engineer

We need to output HTML fragment only, with headings

for sections: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. Only include sections that have real specific content. We must not repeat job title. Remove boilerplate, navigation, legal, EEO, duplicated lines, application instructions. Must preserve all substantive info. Let's parse the posting. Content: - Position Location: This role supports our Central region. (metadata, maybe minor, we can fold into short p or drop). Not a heading. - Intro paragraph about Siemens: "Here at Siemens, we take pride..." etc. This is about company, maybe "About Siemens" but not required as a heading? The instruction says use headings for sections like About the role, Responsibilities, etc. There's no explicit "About the role" heading in source, but we can create one if we have content. The intro about Siemens could be considered "About the role"? Actually "About the role" would be description of role. The posting includes description: "Fire Alarm Systems Design Engineers create unique design solutions..." and bullet list of duties. So we can put that under "About the role" or "Responsibilities". The instruction: Use

for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). So we need to decide which sections to include based on content. We have: - Responsibilities: list of duties (Design fire alarm systems..., Perform peer to peer review..., Make recommendations..., Assist in choosing..., Provide general electrical calculations...). That's substantive. - Requirements: Basic Qualifications: High school diploma or GED, 3+ years experience, must be able to demonstrate knowledge..., ability to read diagrams, proficiency in AutoCAD and design and Microsoft Office, Must have NICET I Fire Alarm certification and willing to get NICET II within 2 years, Legally authorized to work in US. - Preferred Qualifications: Associate or Bachelor’s Degree. - Skills: maybe implied: knowledge of fire alarm components, AutoCAD, etc. Could be separate Skills section. - Benefits: The posting mentions "You’ll Benefit From Siemens offers a variety of health and wellness benefits to our employees. Details regarding our benefits can be found here: link". That's a benefits statement but not specific details. It says "variety of health and wellness benefits". That's somewhat generic but still a statement. The instruction: never create Benefits section unless posting actually states them. It does state that Siemens offers a variety of health and wellness benefits, with a link. That's enough to include Benefits section? It's not specific like "medical, dental, 401k". But it's still a statement about benefits. I'd include a Benefits section with a paragraph summarizing that. - Pay: The posting includes "The pay range for this position is $43,911 - $75,276 annually. The actual wage offered may be lower or higher depending on budget and candidate experience, knowledge, skills, qualifications, and premium geographic location." That's specific pay range. So we include Pay section. - Schedule: Not mentioned. So omit Schedule. - About the role: Could be a short paragraph summarizing role purpose. The intro about Siemens is more about company. The role description is in responsibilities. We could still have an About the role section with a brief summary: "Fire Alarm Systems Design Engineers create unique design solutions to meet specific customer requirements for commercial building fire alarm systems in new and existing facilities. This team member makes recommendations for productivity improvements and cost reductions to increase customer satisfaction and job profitability." That's from the posting. So we can put that under About the role. - Requirements: Already have Basic Qualifications. - Qualifications: Could combine Basic and Preferred? The instruction lists Qualifications as a possible heading separate from Requirements. Might be redundant. We could treat Requirements as basic qualifications, and Qualifications as preferred? But better to follow typical: Requirements = mandatory, Qualifications = preferred. However the posting uses "Basic Qualifications" and "Preferred Qualifications". So we could map Basic Qualifications to Requirements, and Preferred Qualifications to Qualifications. Or we could have Requirements include both basic and preferred? The instruction says use headings e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. So we can have both Requirements and Qualifications sections. Thus: - About the role: paragraph summarizing role. - Responsibilities: ul list of duties. - Requirements: ul list of basic qualifications (high school diploma/GED, 3+ years experience, knowledge of engineering fundamentals, knowledge of components, ability to read diagrams, proficiency in AutoCAD and MS Office, NICET I certification and willingness to get NICET II within 2 years, legally authorized to work in US). - Qualifications: ul list of preferred qualifications (Associate or Bachelor’s Degree). Also maybe mention Veteran careers tags? Those are not qualifications; they are hashtags for outreach. Could be considered part of company's commitment but not needed. We'll ignore. - Skills: Could list specific skills: knowledge of fire alarm system components, AutoCAD, MS Office, electrical calculations, etc. But many of those are already in Requirements. To avoid duplication, we could omit Skills or combine. The instruction: prefer a few substantive sections over many thin ones. So maybe we skip Skills section and incorporate skills into Requirements/Qualifications. But we need to follow instruction: Use headings only when posting has real specific content. If we don't have distinct skills beyond those listed, we could omit Skills. - Benefits: paragraph about health and wellness benefits and link. - Pay: paragraph with pay range and note. - Schedule: omitted. Now we need to output only HTML fragment, no /, no markdown fences. We'll produce something like:

About the role

Fire Alarm Systems Design Engineers create unique design solutions to meet specific customer requirements for commercial building fire alarm systems in new and existing facilities. This team member makes recommendations for productivity improvements and cost reductions to increase customer satisfaction and job profitability.

Responsibilities

• Design fire alarm systems for buildings, including floorplan drawings with system device locations, riser diagrams, device wiring details, panel mounting and wiring details, bills of materials, and sequences of operations to meet the intent of the project plans, specifications, and contract documents.
• Perform peer to peer review of engineering documents.
• Make recommendations related to productivity improvement and cost reduction to increase customer satisfaction.
• Assist in choosing the appropriate mix of products and installation methods to provide the most cost-effective solution.
• Provide general electrical calculations, including battery calculations, voltage drop calculations, conduit fills, power supply sizing, etc.

Requirements

• High school diploma or state-recognized GED
• 3+ years experience in Fire Alarm design
• Knowledge of engineering fundamentals of fire systems or equivalent field experience with fire system controls
• Knowledge of the following fire alarm system components: fire alarm panels, strobe booster panels, spot detectors (smoke, heat, carbon monoxide), duct-mounted smoke detectors, projected beam smoke detectors, aspirating smoke detectors (VESDA), monitor modules, relay modules (form A and form C), manual pull stations, notification devices (speaker/strobes, horn/strobes, strobes, bells), Class A/Class B/Class X circuits, state and local fire codes, and NFPA 72 national fire code
• Ability to read and interpret electrical diagrams
• Proficiency in AutoCAD and design and Microsoft Office
• Must have NICET I Fire Alarm certification and willing to get NICET II within 2 years
• Legally authorized to work in the United States on a continual and permanent basis without company sponsorship

Qualifications

• Associate or Bachelor’s Degree (preferred)

Benefits

Siemens offers a variety of health and wellness benefits to employees; details can be found at https://www.benefitsquickstart.com/siemens/index.html.

Pay

The pay range for this position is $43,911 – $75,276 annually. The actual wage offered may be lower or higher depending on budget and candidate experience, knowledge, skills, qualifications, and premium geographic location.

Check for any duplicated lines: we removed boilerplate like "Position Location: This role supports our Central region." Could fold into a short p but not needed as heading. Might include as a short paragraph under About the role? But it's minor metadata; we could drop it. The instruction: "Do NOT put Job ID / requisition numbers as headings — fold minor metadata into a short

or drop it." So we could include a short p about location. But we already have About the role paragraph; we could add location there. However the location is not about the role but about where it supports. Could add a sentence: "This role supports the Central region." Might be okay to include in About the role paragraph. Let's incorporate: "This role supports the Central region." Add to About the role paragraph. Thus About the role paragraph: "Fire Alarm Systems Design Engineers create unique design solutions to meet specific customer requirements for commercial building fire alarm systems in new and existing facilities. This team member makes recommendations for productivity improvements and cost reductions to increase customer satisfaction and job profitability. This role supports the Central region." Now check for any other boilerplate: "Ready to create your own journey? Join us today!" That's a call to action, maybe considered application instruction; we should remove. "About Siemens" paragraph is company description; we could include as part of About the role? Not needed. The instruction says we can include About the role but not About the company. However we could include a short paragraph about Siemens under About the role? Might be considered filler. Better to omit company description as not required. The posting also includes "We know that the only way a business thrives is if our people are thriving..." etc. That's fluff; we should remove as boilerplate. Also "Our Smart Buildings help to create efficient, safe, adaptable, and responsible environments..." etc. That's also fluff. Remove. Also "You’ll Benefit From Siemens offers a variety of health and wellness benefits..." we kept. Also "The pay range for this position is $43,911 - $75,276 annually." we kept. Also "The actual wage offered may be lower or higher depending on budget and candidate experience, knowledge, skills, qualifications, and premium geographic location." we kept. Also "We value your unique identity and perspective..." that's EEO; remove. Also "We welcome you to bring your authentic self and transform the everyday with us." remove. Also "#VeteranCareers #TransitioningServiceMember #MilitarySpouse" remove. Also "Ready to create your own journey? Join us today!" remove. Also "About Siemens" paragraph remove. Also "Our Commitment to Equity and Inclusion..." remove. Thus final HTML includes sections: About the role, Responsibilities, Requirements, Qualifications, Benefits, Pay. Check that we didn't miss any substantive content: The responsibilities list includes all bullet points. The requirements list includes all basic qualifications. The qualifications list includes preferred degree. The benefits includes the statement about health and wellness benefits and link. Pay includes range and note. We omitted "Must be able to demonstrate:Knowledge of engineering fundamentals..." we included as separate bullet. We omitted "Knowledge of the following fire alarm system components: ..." we included. We omitted "The ability to read and interpret electrical diagrams" included. We omitted "3+ Proficiency in AutoCAD and design and Microsoft Office" we included as "Proficiency in AutoCAD and design and Microsoft Office". Note the original says "3+ Proficiency in AutoCAD and design and Microsoft Office