Lead Consultant - Fire and Life Safety Engineering

We need to output HTML fragment with sections: headings

for sections like About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. Only include sections that have real specific content. We need to parse the job description. Key sections: - About the role: The description includes "This Opportunity WSP, a world-class multi-disciplinary engineering consulting firm, is seeking an experienced Lead Consultant - Fire and Life Safety Engineering for our Denver, CO office. We work closely with architects and owners from around the world on large, complex projects with a focus on sustainability and energy performance of the built environment. Our engineers work on high quality, high-profile, national and international projects. The Lead Consultant will be an integral member of our national Fire & Life Safety specialty practice. It is anticipated that this position will be responsible as a subject matter expert regarding applicable Codes." We can treat that as About the role. - Responsibilities: The "Your Impact" bullet list: Interpretation of building code, life safety, and fire code requirements... etc. That's a list of duties. - Requirements/Qualifications: There's "Who You Are Required Qualifications" and "Preferred Qualifications". Also "Required Qualifications" includes 7-10 years experience, degree, PE license, supervisory experience desirable, experience in fire protection engineering design applications, excellent communication skills. Preferred: Health Care experience. - Skills: Could be extracted from required qualifications: communication skills, etc. But we may combine with qualifications. - Benefits: "WSP Benefits" paragraph describing benefits. - Pay: "Compensation Expected Salary (Colorado only): $115,200 - $120,000" plus explanation. - Schedule: Not mentioned. So we should not include Schedule. - About WSP: Could be separate section maybe "About the company" but not in list of allowed headings. The allowed headings are About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We could put "About WSP" maybe under About the role? But we have "About the role" already. The "About WSP" paragraph is more about company. Could be omitted or placed under About the role? The instruction: "Use

for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." It says e.g., not exclusive. But we should prefer those headings. Could we add another heading like "About the Company"? Not in list but maybe allowed as e.g. However they say "Use

for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." This suggests those are examples; we could use others if needed but better to stick to those. The "About WSP" could be considered part of About the role? Might be okay to include as a separate section "About the Company" but not in list; risk. Safer to incorporate that info into About the role or maybe omit as boilerplate? It's not boilerplate; it's substantive about the company. Could include under About the role as additional paragraph. We must not repeat job title as heading. No Job ID. We must remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. At end there is EEO statement, notice to third party agencies. Remove those. We must preserve ALL substantive information; do not invent or summarize away detail. Thus we need to extract all substantive info and format. Let's list substantive content: - About the role / company overview: WSP is a world-class multi-disciplinary engineering consulting firm, seeking Lead Consultant - Fire and Life Safety Engineering for Denver, CO office. Work closely with architects and owners worldwide on large, complex projects focusing on sustainability and energy performance. Engineers work on high-quality, high-profile national and international projects. Lead Consultant integral member of national Fire & Life Safety specialty practice. Position responsible as subject matter expert regarding applicable codes. - Responsibilities (Your Impact): * Interpretation of building code, life safety, and fire code requirements (familiarity with ICC and NFPA codes, including IBC and NFPA 101). * Negotiating with authorities having jurisdiction on fire safety designs and proposals. * Review of architectural drawings for compliance with building and fire code requirements. * Producing fire and life safety strategy documents with limited guidance to inform and support chosen building form throughout design process. * Design of fire protection and life safety systems including automatic fire sprinkler systems, fire detection and alarm systems, smoke management systems, and egress systems. * Commissioning of fire protection and life safety systems in commercial, institutional and industrial facilities. * Directly interfacing with clients. * Organizing in-house resources. * Following quality control review processes of all project documentation. * Developing project proposals and budgets. * Conducting financial management of all projects. * Mentoring junior staff. * Preparing technical reports/specifications. * Participating in department initiatives. * Contributing to overall business development of the company. - Required Qualifications: * 7 to 10 years of relevant post-education experience in engineering discipline and prior fire and life safety design experience. * Bachelor or Master of Science Degree in Fire Protection Engineering, or related engineering discipline with a P.E. license. * Professional Engineering (PE) license. * Supervisory experience is highly desirable. * Experience in fire protection engineering design applications. * Excellent verbal and written communication skills. - Preferred Qualifications: * Health Care experience. - Benefits: * Comprehensive suite of benefits focused on health and financial stability: medical, dental, vision, disability, life; retirement savings; paid sick leave; paid vacation (or other personal time); paid parental leave; paid time off for bereavement, voting, and/or attendance at naturalization proceedings. - Pay: * Expected Salary (Colorado only): $115,200 - $120,000. * Note: WSP USA providing compensation range that company in good faith believes it might pay/offer for this position within Colorado, based on successful applicant’s education, experience, knowledge, skills, abilities, internal equity, specific geographic location. WSP USA reserves right to ultimately pay more or less than posted range and offer additional benefits and other compensation, depending on circumstances not related to applicant’s sex or other protected status. - About WSP (company description): * WSP USA is the U.S. operating company of WSP, one of the world's leading engineering and professional services firms. * Dedicated to serving local communities; engineers, planners, technical experts, strategic advisors, construction management professionals. * Designs lasting solutions in buildings, transportation, energy, water, environment markets. * More than 15,000 employees in over 300 offices across the U.S.; partner with clients to help communities prosper. * Website: www.wsp.com * Flexible and agile workplace model while meeting client needs. * Employees afforded comprehensive suite of benefits including medical, dental, vision, disability, life, retirement savings focused on health and financial stability. * Want to give employees challenges to grow careers and knowledge base. * Daily contributions essential in meeting client objectives, goals, challenges. We should not repeat benefits twice; we have benefits section already; the About WSP also mentions benefits but we can keep it as part of About WSP. We must not include boilerplate like EEO, notice to third party agencies, etc. Now produce HTML with

headings and appropriate

• for lists,

  for prose. We need to decide which sections to include: - About the role (maybe combine with About WSP? Could have two sections: About the role and About the company. But only allowed headings list includes About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. Could treat About WSP as part of About the role or maybe as a separate "About the company" but not in list. Safer to merge About WSP into About the role? However About the role currently is about the position; About WSP is about company. Could still be under About the role heading but include both. That may be okay. Alternatively we could create a section "About the company" but risk being considered not following instruction. The instruction says "Use

  for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." The "e.g." implies these are examples, not exclusive. So we could add another heading like "About the Company". But to be safe, we can stick to the given examples and put company info under About the role or maybe under a separate "About WSP" heading but that is not in examples; risk. I'll include About the role (position overview) and then maybe a separate "About the Company" heading? I think it's okay to add as it's still a heading; they didn't forbid other headings, just gave examples. However they said "Use

  for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." This suggests we should use those headings for those sections; if we have other content we could still use

  but maybe not those exact headings. Safer to use only those headings; we can put company info under About the role or maybe under a separate "About the role" but we already have role overview. Could split: first paragraph about role, second about company. That's fine. Thus sections:

  About the role

  WSP, a world-class multi-disciplinary engineering consulting firm, is seeking an experienced Lead Consultant - Fire and Life Safety Engineering for our Denver, CO office. We work closely with architects and owners from around the world on large, complex projects with a focus on sustainability and energy performance of the built environment. Our engineers work on high quality, high-profile, national and international projects. The Lead Consultant will be an integral member of our national Fire & Life Safety specialty practice. It is anticipated that this position will be responsible as a subject matter expert regarding applicable codes.

  WSP USA is the U.S. operating company of WSP, one of the world's leading engineering and professional services firms. Dedicated to serving local communities, we are engineers, planners, technical experts, strategic advisors and construction management professionals. WSP USA designs lasting solutions in the buildings, transportation, energy, water and environment markets. With more than 15,000 employees in over 300 offices across the U.S., we partner with our clients to help communities prosper. www.wsp.com WSP provides a flexible and agile workplace model while meeting client needs. Employees are also afforded a comprehensive suite of benefits including medical, dental, vision, disability, life, and retirement savings focused on providing health and financial stability throughout the employee’s career. At WSP, we want to give our employees the challenges they seek to grow their careers and knowledge base. Your daily contributions to your team will be essential in meeting client objectives, goals and challenges.

  But that duplicates benefits; we already have Benefits section. Might be okay but could be repetitive. However we must preserve ALL substantive information; not summarizing away detail. The benefits description appears twice in the posting (once under "WSP Benefits" and again in "About WSP"). We need to preserve both? The instruction: "Preserve ALL substantive information; do NOT invent or summarize away detail." If we omit one occurrence, we are summarizing away detail (duplicate). But duplicates are allowed to be removed? They said "Remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions." Duplicated lines: we can remove duplicated lines. The benefits appear twice; it's a duplicated line (or duplicated content). So we can remove one occurrence. So we should keep only one benefits section. Good. Thus we will have Benefits section only once. Now Responsibilities: list. Requirements: maybe combine Required Qualifications and