Jobs · Engineering · California

Fire Protection Engineer (5+Years)

Coffman Engineers · Los Angeles, CA · 1 mo ago
Engineering$100k/yrFull-time
We need to output HTML fragment with sections: About the role? Actually we need to use headings for sections like About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We must include only sections with real content. The posting includes Company Description, Job Description, Key responsibilities, Qualifications (minimum and preferred), Knowledge, Skills, & Abilities, Compensation And Benefits, Additional Information (Why You Want to Work Here, Coffman at a Glance), Applying (instructions) which we should remove (application instructions). Also we need to remove boilerplate like EEO, etc. Also remove duplicated lines. We need to preserve all substantive information, not invent or summarize away detail. Use

for section headings. Use
  • for any list of duties/requirements/benefits, and

    for prose. We need to decide sections: Possibly "About the role" could be Job Description summary. "Responsibilities" from Key responsibilities. "Requirements" maybe Minimum Qualifications. "Qualifications" maybe Preferred Qualifications? Or combine? The instruction: use headings for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). So we can have multiple sections; we should not repeat job title as heading. We need to include sections only when posting has real specific content. We have content for: - About the role: could be Job Description paragraph(s) describing role. - Responsibilities: list of key responsibilities. - Requirements: Minimum Qualifications. - Qualifications: Preferred Qualifications? Or maybe "Qualifications" heading for both? But we already used Requirements for minimum; Qualifications could be preferred. - Skills: Knowledge, Skills, & Abilities. - Benefits: Compensation And Benefits includes salary, overtime, bonus, hybrid schedule, 401k. - Pay: maybe separate salary? But we already have Benefits includes salary; but we could split Pay and Benefits. However instruction: include a section ONLY when posting has real, specific content for it. The posting includes "Compensation And Benefits" with salary range, overtime, bonus, hybrid schedule, 401k. So we could have Pay section for salary and maybe bonus, and Benefits for 401k, hybrid schedule? But hybrid schedule is schedule. Actually schedule is separate: Hybrid Work Schedule. So we could have Schedule section for hybrid schedule. Pay for salary, overtime, bonus. Benefits for 401k. Thus we need sections: About the role, Responsibilities, Requirements (minimum qualifications), Qualifications (preferred qualifications), Skills (knowledge, skills, abilities), Pay, Benefits, Schedule. Check each for content: - About the role: Job Description paragraph(s) before Key responsibilities. We'll capture that. - Responsibilities: list of key responsibilities (bulleted). We'll output

    • each. - Requirements: Minimum Qualifications bullet list? It's paragraph with bullet-like lines but not explicit bullet. We can treat each line as list item. We'll output
      • . - Qualifications: Preferred Qualifications similarly. - Skills: Knowledge, Skills, & Abilities paragraph list; we can treat as list. - Pay: Compensation And Benefits includes "Approximate Base Salary – $100,000 – $130,000 annually", "Paid overtime at 1.0 times hourly rate", "Competitive end-of-year discretionary bonus based on company/team/personal performance". We'll output as list. - Benefits: "401k with maximum of 5% Contribution Matching for 9% Employee Contribution". Also maybe "Hybrid Work Schedule" is schedule, not benefit. So Benefits only 401k. - Schedule: "Hybrid Work Schedule (subject to change)". We'll output as

        maybe. We must remove boilerplate: EEO, equal opportunity, etc. Also remove "Additional Information Why You Want to Work Here" etc? That's not in the prescribed headings; but we could maybe include as "About the company"? Not in list. The instruction says use headings for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). It doesn't forbid other headings, but says "use

        for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)". It implies we should use those headings where appropriate. It doesn't say we cannot add other headings, but better to stick to those. The "Why You Want to Work Here" and "Coffman at a Glance" could be considered "About the role"? Not exactly. Might be considered company description; but we already have Company Description at top. Could we include that as "About the role"? Probably not; but we could treat Company Description as part of "About the role"? The instruction: "Do NOT repeat the job title as a heading (the page already shows it)". It didn't say we cannot include company description. But we need to preserve ALL substantive information. So we need to include company description somewhere. Where to put? Could be a paragraph before About the role? Since we cannot add arbitrary headings not in list? 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 we should use those for sections. However we need to include company description; maybe we can put it in a

        before any heading, as introductory prose. That's acceptable. Similarly, "Additional Information Why You Want to Work Here" and "Coffman at a Glance" are substantive; we need to preserve them. Where to put? Could be part of "About the role"? Not really. Could be a separate section like "About the company". But not in list. However we could incorporate them into a

        after the headings, maybe as a general description. The instruction: "Prefer a few substantive sections over many thin ones." So we could combine company description and additional info into a single

        or maybe a section like "About the company". But the instruction didn't prohibit other headings; it just gave examples. It says "use

        for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)". The "e.g." suggests those are examples, not exclusive. So we could add other headings like "About the company". But to be safe, we could just include them as

        paragraphs without headings, after the sections. That would preserve info. We must remove application instructions, EEO, etc. Let's extract content. Company Description paragraph: "At Coffman Engineers, we serve as both prime consultant and sub consultant on projects large and small, including commercial, retail, institutional, government, industrial, and project/construction management. Incorporated in 1979, we have employees in more than 24 locations serving clients across the United States and overseas. To meet client objectives and to integrate our many disciplines, we can create teams comprised of civil, structural, mechanical, electrical, fire protection, and corrosion control, as well as project/construction managers and professionals in a variety of specialty services. This ability has made us a leader in the engineering and construction communities, and has strengthened our reputation as being progressive, innovative, and a great place to work." Job Description paragraph(s) before Key responsibilities: "Coffman Engineers is seeking a highly skilled and self-motivated Fire Protection Engineer with at least five (5) years of experience to join our growing Downtown Los Angeles office. The successful candidate will support the design and delivery of fire protection engineering projects while working closely with clients, architects, contractors, authorities having jurisdiction, and multidisciplinary project teams. This role focuses on project delivery, technical analysis and design, client coordination, and supporting the continued growth of our fire protection engineering practice. The successful candidate will contribute to projects from planning through construction while collaborating with engineers across multiple disciplines and Coffman offices. This position is ideal for an engineer who enjoys responsibility, client interaction, and technical problem solving while developing project management and leadership skills. The role offers the opportunity to grow with an established fire protection group while contributing to the long-term success of the Downtown Los Angeles office." Key responsibilities list (starting with "Key responsibilities will include:" then bullet lines). We'll capture each line. List: - Provide fire/life safety consulting services for a variety of building types and clients. - Perform building and fire code analysis, egress analysis, fire-resistance-rated construction analysis, and life safety evaluations. - Design and analyze automatic fire suppression, fire detection, alarm, and mass notification systems. - Prepare engineering calculations, technical reports, code studies, plans, specifications, and construction documents. - Support smoke control system design, analysis, testing, and special inspection activities. - Develop code alternatives, engineering judgments, and performance-based design approaches where appropriate. - Coordinate fire protection and life safety requirements with architectural, structural, civil, mechanical, electrical, and low voltage disciplines. - Manage project tasks and deliverables while maintaining quality, schedule, and budget objectives. - Participate in client meetings, site visits, field investigations, construction meetings, and discussions with authorities having jurisdiction. - Review submittals, shop drawings, RFIs, contractor requests, and field conditions during construction. - Assist with proposal development, scope preparation, and fee estimates. - Support client development efforts through strong project delivery, technical excellence, and client relationships. - Coordinate with other Coffman offices to balance workload and share technical expertise. - Contribute to office growth initiatives and maintain positive relationships within the local A/E/C community. - The successful individual will assist project managers, department leadership, and business development staff in developing technical proposals and supporting client relationships. - Candidates should be comfortable working directly with architects, owners, contractors, authorities having jurisdiction, and other project stakeholders while delivering high-quality engineering consulting services. Note: The last two bullets maybe part of responsibilities but also qualifications? We'll keep them in responsibilities. Minimum Qualifications paragraph: "Minimum Qualifications Minimum of 5 years of professional experience in fire protection engineering or consulting.Bachelor’s degree in Fire Protection Engineering, Fire Sciences, or related engineering field.FE/EIT required, PE preferred.Experience performing fire/life safety code analysis and designing fire protection systems for building projects.Experience applying the California Building Code, California Fire Code, applicable NFPA standards, and local permitting processes.Experience preparing construction documents, technical reports, and engineering calculations using industry-standard software tools.Strong written and verbal communication skills.Demonstrated ability to manage multiple assignments and responsibilities." We need to split into list items. The text is concatenated without spaces after periods? Actually there are missing spaces after periods. We'll still split by sentences. Preferred Qualifications paragraph: "Preferred Qualifications California Fire Protection Engineer PE registration.Experience coordinating with multidisciplinary project teams.Experience with fire suppression, fire alarm, and mass notification system design and analysis.Experience performing building and fire code analysis, egress analysis, and passive fire protection evaluations.Experience with smoke control systems, special inspections, commissioning, or acceptance testing.Experience developing code alternatives, engineering judgments, or performance-based design approaches.Experience with healthcare, aerospace, industrial, laboratory, higher education, K-12, civic, commercial, or institutional projects.Experience with construction administration and contractor coordination.Experience managing project scope, schedule, budget, and client communication.Proficiency with Revit, AutoCAD, Bluebeam, and Microsoft Office Suite.Experience with CONTAM, FDS, Pathfinder, hydraulic calculation software, or other fire protection engineering tools.Experience preparing proposals, scopes, and fee estimates.Experience collaborating with the Southern California architectural and engineering community.Participation in SFPE, NFPA, or other professional organizations.Experience in performing field investigations and existing-building assessments." Knowledge, Skills, & Abilities paragraph: "Knowledge, Skills, & Abilities Self-starter, persistent, and follows through in a consistent manner.Passionate about client service and takes ownership of work product.Able to multi-task and prioritize in a fast-paced environment.Possesses strong critical thinking, organizational, and analytical abilities.Maintains positive working relationships with internal and

Similar jobs