Sr. Fire and Life Safety Specialist (Sr. Building & Life Safety Specialist)
maybe under a heading? The instruction: use
for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). Do NOT repeat the job title as a heading. So we need to decide which sections to include based on content. We have content: description of role (responsibilities) listed as bullet-like sentences after "In the role of a Senior Building Code & Life Safety Specialist, we'll count on you to:" then many responsibilities. That's responsibilities. Then "Preferred Qualifications" and "Required Qualifications". Those are qualifications. Also "What We Believe", "Our Commitment", "Employee Network Groups" etc. Could be "About the role" or "About HDR"? Probably "About the role" could include the introductory paragraphs describing the role and impact. But we have to avoid filler. We also have "Schedule:Full-time", "Employee Status:Regular", "BusinessClass:Fire and Life Safety", "Primary Location:United States-Texas-Austin", "Other Locations:...". Those are metadata; we can fold into a short
or drop. The instruction: do NOT put Job ID / requisition numbers as headings — fold minor metadata into a short
or drop it. So we can include a
with location and schedule etc. We should not create Benefits, Pay sections unless posting actually states them. No benefits or pay mentioned. So omit those. We should not create a Schedule section unless posting actually states them. It does state Schedule:Full-time. So we could include Schedule section? The instruction: "never create Pay/Schedule/Benefits sections unless the posting actually states them." Since schedule is stated, we could include a Schedule section with that info. However they also say prefer a few substantive sections over many thin ones. Could fold schedule into a short
metadata. But they said we can fold minor metadata into a short
or drop it. Schedule is not minor? It's a detail. Could include in a
under maybe "About the role" or separate. Safer to include a short
with location and schedule. We need to preserve all substantive information; do not invent or summarize away detail. So we must keep all responsibilities text exactly as given (maybe as list items). Use
- for any list of duties/requirements/benefits. So responsibilities should be a list.
Similarly qualifications (preferred and required) could be separate lists under Requirements or Qualifications sections. The headings allowed: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We can choose which to use.
We have both Preferred and Required qualifications. Could combine under "Qualifications" with subheadings? But we cannot add extra headings beyond those? 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 suggests those as examples. Probably we should stick to those. Could have "Requirements" for required qualifications, and "Qualifications" for preferred? Or combine. Better: Use "Responsibilities" for the duties list. Use "Requirements" for required qualifications. Use "Qualifications" for preferred qualifications. Or maybe "Skills" for technical skills like AutoCAD, Revit, etc. But we can put those under Qualifications. We also have introductory paragraphs about HDR culture and role description before responsibilities. That could be "About the role". So we will have:
About the role
Intro paragraphs...
Responsibilities
- ... ...
Requirements
- ... ...
Qualifications
- ... ...
for metadata: location, schedule, employee status, business class. We must not repeat job title as heading. Good. We must remove boilerplate: EEO, equal-opportunity, scam-warning, cookie/navigation/legal, duplicated lines, application instructions. The posting includes At HDR, we are committed to the principles of employment equity... We should remove that. Also remove "Watch Our Story:' https://www.hdrinc.com/our-story'" maybe keep as part of intro? It's a link; but it's not boilerplate? It's a promotional link. Might be considered navigation? Probably safe to keep as part of intro? The instruction: remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate. The link to our story is not exactly those, but could be considered navigation. Safer to drop it? But we need to preserve ALL substantive information; the link is not substantive to the job. It's promotional. I'd drop it. Also remove duplicated lines: there is some repetition in responsibilities: "Develop non-routine and complex Life Safety designs for facilities in compliance with the International Code Council (ICC) and National Fire Protection Association (NFPA) Standards" and later "Develop non-routine and complex Life Safety design for facilities such as occupancy calculations, travel distances, code compliance drawings, passive fire protection systems, in compliance with the International Building & Fire codes and other Standards". Slightly different but similar. We must keep both as they are distinct. We must not invent or summarize away detail. So we need to keep each bullet exactly as in text. Let's extract the responsibilities list exactly as after "In the role of a Senior Building Code & Life Safety Specialist, we'll count on you to:" then each line ends with a period. We'll copy them. List: - Communicate the code requirements for the built environment effectively to city officials, developers, designers, and contractors. - Develop non-routine and complex Life Safety designs for facilities in compliance with the International Code Council (ICC) and National Fire Protection Association (NFPA) Standards - Develop non-routine and complex Life Safety design for facilities such as occupancy calculations, travel distances, code compliance drawings, passive fire protection systems, in compliance with the International Building & Fire codes and other Standards - Effectively network with other building, fire and life safety industry professionals. - Lead projects dedicated to Building Code & Life Safety Area of expertise - Researching building codes, regulations, life safety issues and providing analysis, recommendations, and support to a variety of clients and projects. - Building code research for project development and building design projects. - Lead and manage HDR code review teams to complete plan reviews for new projects developed by outside A/E firms. - Evaluate requests for alternate methods of compliance for the adopted codes. - Cross-examining test data (e.g., ASTM, UL) and building codes, or similar regulations (e.g., NFPA, ADA, FGI, etc.) for sufficient evidence of compliance and recommendations to obtain compliance. - Providing oversight and support for project quality control while interacting closely with project teams and authorities having jurisdiction. - Draft and edit code reviews and reports as appropriate for specified scopes of work. - Communicate with internal and external clients to obtain the appropriate data and quality control documentation. - Review and provide feedback on client quality assurance systems. - Provide education relevant to code and regulatory elements of our services and specific tools and techniques to other segments of HDR and to clients. - Through written and verbal communication, inform internal and external audiences on a variety of relevant topics. - Maintain membership in appropriate professional organizations as requested by or approved by HDR. - Perform other duties as needed Note some start with verb forms inconsistent; keep as is. Now Required Qualifications: - Associate degree in a closely related field or a High School diploma with a combination of education and relevant experience - Advanced Levels of NFPA, ICC Certifications or other specialized credentials related to the field of Fire & Life Safety - Strong computer skills using AutoCAD, Revit 3D Modeling and Microsoft Office - Ability to lead designs specific to area of expertise - An attitude and commitment to being an active participant of our employee-owned culture is a must Preferred Qualifications: - A minimum of 15 years Building Code & Life Safety design experience in systems design or regulatory enforcement - A minimum of five (5) years working in a Building Department or Fire Marshal’s Office - Detailed understanding of the role of a Municipality’s Building Department, specifically in the role of plan reviews, issuing permits and completing inspections. Now About the role: The introductory paragraphs before responsibilities: "At HDR, our employee-owners are fully engaged in creating a welcoming environment where each of us is valued and respected, a place where everyone is empowered to bring their authentic selves and novel ideas to work every day. As we foster a culture of inclusion throughout our company and within our communities, we constantly ask ourselves: What is our impact on the world? Each and every role throughout our organization makes a difference in our ability to change the world for the better. Read further to learn how you could help make great things possible not only in your community, but around the world. We believe building engineering is more than systems and structures, it’s about powering progress and enabling innovation. As part of HDR’s Building Engineering Services Group, you’ll help design the critical infrastructure that supports the digital age and shapes the spaces where people work, connect, and thrive. From high-performance data centers driving the future of AI to dynamic commercial environments, your work will directly support technological advancement, sustainability, and human experience. We bring together mechanical, electrical, structural, and civil engineering experts to solve complex design challenges with precision, creativity, and collaboration. Whether you're optimizing energy efficiency, integrating resilient systems, or engineering the backbone of next-generation facilities, your contributions will help define the future of the built environment. This isn’t just a job, it’s a chance to lead innovation, engineer impact, and build a legacy of excellence." Also there is "What We Believe" and "Our Commitment" sections after qualifications. Those are also substantive but could be considered about company culture. Could we include them under About the role as well? Might be redundant but we can include them as part of About the role to preserve all info. However we must not create thin sections. Adding them to About the role makes a longer paragraph, okay. Let's capture "What We Believe": "What We Believe HDR is our company. Together, we build on each other's life experiences and perspectives to make great things possible every day. This shapes our collaborative culture, encourages organizational trust and connects us closer to the clients and communities we serve." "Our Commitment As employee owners, we all have a role in creating an inclusive environment where each of us is welcomed, valued, respected and empowered to bring our authentic selves to work every day. Our eight Employee Network Groups (Asian Pacific, Black, Hispanic/Latino(a), LGBTQ+, People with Disabilities, Veterans, Women, Young Professionals) help create a sense of belonging and foster a supportive environment where everyone is empowered to engage and contribute. Each group has an executive sponsor and is open to all employees." We can include these as part of About the role paragraph(s). Might be okay. Now metadata: Primary Location:United States-Texas-Austin Other Locations:United States-Texas-Dallas, United States-Texas-Houston, United States-Texas-San Antonio Industry:Building Engineering Schedule:Full-time Employee Status:Regular BusinessClass:Fire and Life Safety Job Posting:Sep 14, 2026 We can make a short
with that info. Now ensure we don't include any boilerplate like EEO statement at end. Remove. Now produce HTML fragment:
About the role
... (combined intro + What We Believe + Our Commitment)
Responsibilities
- ...
Requirements
- ...
Qualifications
- ...
Primary Location: United States-Texas-Austin;