Senior Construction Project Manager - NorCal

We need to output HTML fragment with sections: headings

for sections like About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. Use

• for any list of duties/requirements/benefits, and

  for prose. Do NOT repeat job title as heading. Do NOT put Job ID/requisition numbers as headings. Preserve all substantive info. Remove boilerplate: unsolicited candidate intro, location? Location is substantive? It says "Location: Candidate must be located in the NorCal / Bay Area, CA area." That's location requirement, we should keep. Background check requirement also substantive. About Frontline Wildfire Defense: keep. About This Opportunity: keep. Key Responsibilities: list. Leadership & Team Development etc. Process Improvement & Innovation. Administrative & Support Tasks. Qualifications: Must-Have and Nice-to-Have. Compensation & Benefits: includes pay range and benefits. Also "And much more!" and "Join Our Mission!" etc. Also diversity statement: we should remove EEO boilerplate? The instruction says remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate. So we should remove the diversity and inclusion statement at end. Also remove "Please note that we do not accept unsolicited candidate introductions..." that's boilerplate? It's a note about recruiters; maybe considered boilerplate? It's not EEO but maybe still considered boilerplate? It's a policy statement; I'd remove it as it's not substantive job content. Keep location and background check requirement. We need sections: maybe About the company (About Frontline Wildfire Defense), About the role (About This Opportunity), Responsibilities (Key Responsibilities plus sub-sections?), Requirements (Qualifications), Benefits (Compensation & Benefits). Pay is part of Compensation & Benefits. Schedule? Not mentioned explicitly; there is ability to work remotely and travel across California, occasional nights and weekends. That's schedule info. Could include under Schedule section? But we should only include sections when posting has real specific content. There's mention of occasional nights and weekends, remote work, travel. That's schedule-related. Could create a Schedule section with that info. However we could also fold into Responsibilities or About the role. The instruction: prefer a few substantive sections over many thin ones. So maybe we keep sections: About the company, About the role, Responsibilities, Qualifications, Compensation & Benefits. Possibly also Background check and Location as a short p under About the role or separate? Could include as a short p under About the role. We must not invent sections like Skills if not present. There's no explicit Skills section; we have qualifications includes skills. So we can put Qualifications. We need to use

  for section headings. Use

  • for any list of duties/requirements/benefits. Use

    for prose. We need to preserve all substantive info. Let's extract content. First, About Frontline Wildfire Defense paragraph(s). We'll keep as

    . About This Opportunity: paragraph(s). We'll keep. Key Responsibilities: there are bullet-like sentences under headings: Project Management & Execution, Customer & Stakeholder Management, Leadership & Team Development, Process Improvement & Innovation, Administrative & Support Tasks. Each has multiple sentences. We could treat each heading as a subsection? But we only have

    for section headings; we could make each of those as

    ? Not allowed? Only

    for section headings. We could keep them as

    with bold? But we must not invent headings not allowed? We could keep them as inside

    . But better to keep as

    with the sentences. However we need to use

    • for any list of duties/requirements/benefits. The responsibilities are a list; we could make each responsibility area as
    • . But there are sub-bullets inside each. Could flatten: each bullet sentence as
    • . But we need to preserve structure? The instruction: Use
      • for any list of duties/requirements/benefits. So we should wrap the responsibilities in a
        with
        • items. Each item can contain multiple sentences. That seems appropriate. Similarly Qualifications: Must-Have and Nice-to-Have lists. We'll make
          • for each qualification item. Benefits: list of benefits: Company-provided cell phone and laptop, Medical, Dental, and Vision Insurance, 401(k) retirement plan, Flexible time off + 14 paid holidays (yes, your birthday is one of them!), Work-from-home stipend to support your remote setup, Remote-first work environment, fostering work-life balance and autonomy, Company-provided equipment, And much more! (maybe vague). We'll list the concrete ones. Pay: $120,000 - $160,000 DOE. That's pay. We'll include in Compensation & Benefits section maybe as a

            before benefits list. Schedule: Ability to work remotely and travel across California, including occasional nights and weekends. Could be a

            under About the role or separate Schedule section. Since we have schedule info, we could make a Schedule section with that

            . But we prefer few sections; maybe we incorporate into About the role paragraph. Location: Candidate must be located in the NorCal / Bay Area, CA area. Could be a

            under About the role. Background Check Requirement: paragraph(s). Could be a

            under About the role or separate? It's substantive; we could make a section Background Check? Not in allowed headings list but we could still use

            for any section heading; the list is examples, not exclusive. So we could add a heading Background Check. But the instruction: "Use

            for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." It gives examples but not exclusive; we can use other headings as needed. However they say "include a section ONLY when the posting has real, specific content for it". So we could add a Background Check section. But to keep few sections, maybe we fold into About the role. Let's decide sections: - About the company (About Frontline Wildfire Defense) - About the role (About This Opportunity + Location + Background Check) - Responsibilities (Key Responsibilities) - Qualifications (Must-Have and Nice-to-Have) - Compensation & Benefits (Pay + Benefits) That's 5 sections. Now we need to output HTML fragment only, no /. We'll output something like:

            About Frontline Wildfire Defense

            ...

            About the Role

            As a Construction Project Manager, you will be responsible for overseeing the end-to-end installation of Frontline Wildfire Defense Systems. Your role will be crucial in ensuring high-quality execution, staying within budget and timelines, and delivering an exceptional customer experience. This is a high-impact position with leadership potential as we continue to scale.

            Location: Candidate must be located in the NorCal / Bay Area, CA area.

            Background Check Requirement: As part of our hiring process, Frontline Wildfire Defense conducts comprehensive background checks for all new hires. These checks typically cover the past 7–10 years and may include employment and education verification. For roles that require work in the field, driving record verification is also required. Employment offers are contingent upon the successful completion of these background checks.

            Responsibilities

            • Project Management & Execution: Lead and oversee all system installations, ensuring projects are completed on time, within scope, and on budget. Develop efficient processes for supply chain, inventory management, job costing, and system installation. Oversee material procurement and tracking, ensuring timely deliveries and proper inventory management. Work closely with inspectors, local building officials, and fire departments to ensure compliance with regulations.
            • Customer & Stakeholder Management: Serve as the primary point of contact for homeowners, contractors, architects, and builders, ensuring smooth communication and expectation management. Provide technical support and guidance to customers throughout the installation and maintenance process. Collaborate with sales and business development teams, participating in site visits, customer consultations, and project scoping.
            • Leadership & Team Development: Recruit, train, and manage installation team members, including foremen, subcontractors, and third-party installation partners. Foster a positive, team-oriented culture, ensuring seamless collaboration between field and office teams. Provide coaching, feedback, and performance evaluations to continuously improve team expertise and efficiency.
            • Process Improvement & Innovation: Work closely with engineers and product teams to improve system design, installation processes, and performance. Help develop technical documentation and training materials to support internal teams and customers. Implement best practices in project tracking, reporting, and financial forecasting.
            • Administrative & Support Tasks: Oversee site audits, design engineering processes, and permitting. Provide operations and maintenance support to existing customers. Assist in vehicle maintenance management, backflow testing, T&M agreements, and ensuring compliance with tax exemptions when placing orders.

            Qualifications

            Must-Have

            • 5+ years of experience in construction project management, preferably in residential or fire protection systems.
            • Strong understanding of residential construction, permitting, and fire safety regulations.
            • Experience managing contractors, architects, and local inspectors.
            • Proven ability to manage multiple projects simultaneously and work within tight deadlines.
            • Excellent communication and problem-solving skills, with a customer-first approach.
            • Proficiency in Google Suite (Slides, Docs, Sheets, Gmail, Calendar, Drive) and Slack.
            • Must have a valid driver’s license and reliable vehicle for travel to job sites.
            • Ability to work remotely and travel across California, including occasional nights and weekends.

            Nice-to-Have

            • Experience working with fire protection systems or wildfire defense solutions.
            • Familiarity with construction financials, forecasting, and project costing.
            • Knowledge of lean construction methodologies to optimize project efficiency.

            Compensation & Benefits

            Pay: $120,000 - $160,000 DOE

            • Company-provided cell phone and laptop
            • Medical, Dental, and Vision Insurance
            • 401(k) retirement plan
            • Flexible time off + 14 paid holidays (yes, your birthday is one of them!)
            • Work-from-home stipend to support your remote setup
            • Remote-first work environment, fostering work-life balance and autonomy
            • Company-provided equipment
            We should also include "And much more!" maybe as a

            but it's vague; could omit as filler? It's not specific; maybe we can omit as it's not substantive. The instruction: do not include filler/placeholder text like "and much more!"? It's vague; better to omit. Also we need to ensure we didn't repeat job title as heading. We didn't. We removed EEO boilerplate. Check that we preserved all substantive info: About Frontline, About This Opportunity, location, background check, responsibilities (all bullet points), qualifications must-have and nice-to-have, pay, benefits list. Did we miss anything: "Join Our Mission!" etc is promotional; could be considered boilerplate? It's a call to action; maybe we should keep? It's not a list of duties etc. It's a motivational paragraph. Could be considered substantive? It's basically encouraging to apply. Might be considered boilerplate but it's part of posting. The instruction: remove cookie/navigation/legal/EEO/equal-opportun