Public Works Division Manager - Fargo

We need to output HTML fragment with sections: headings

for sections like About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We must only include sections that have real specific content. No placeholder. Must not repeat job title as heading. No Job ID etc. Remove boilerplate. We need to parse the posting. Key sections: - About the role: maybe a paragraph summarizing role. The posting begins: "Civil Science is seeking an experienced Public Works Division Manager to lead our public works practice in North Dakota. As a Division Manager, you'll report to the Area Manager and oversee Project Managers, Engineers, Surveyors, and support staff within the Public Works Division. This is an excellent opportunity for a licensed engineer who thrives in team leadership, business development, and delivering technical excellence." That's about the role. - Responsibilities: There are "Division Leadership & Strategic Responsibilities" and "Business Development Responsibilities". Those are responsibilities. - Requirements: "Required Qualifications" includes ND PE, Bachelor's degree, 12+ years experience, etc. Also "Physical Requirements". Those are requirements. - Qualifications: Might be overlapping with required qualifications. But we can treat "Required Qualifications" as Qualifications. However we need to avoid duplication. The instruction: Use headings for sections like About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We can decide which to include. We have content for: - About the role (paragraph) - Responsibilities (two bullet lists) - Requirements (maybe include education, experience, licensure, physical requirements) - Qualifications (maybe same as required qualifications? Could combine but we need to decide. Could treat "Required Qualifications" as Qualifications, and "Physical Requirements" as part of Requirements. Or we could have Requirements include education/experience/licensure, and Qualifications include skills/competencies. But we also have "Key Competencies" which could be Skills. - Skills: "Key Competencies" list: Strategic thinking, Financial acumen, Business development & relationship-building, Leadership & talent acquisition/development, Technical and North Dakota regulatory/funding expertise, Communication & negotiation skills. - Benefits: "Why Join Civil Science?" includes ownership, room to grow, work-life harmony, comprehensive benefits list. Also "Comprehensive Benefits (Fulltime Employees): Enjoy three weeks of PTO, eight holidays, medical, dental, vision, life insurance, short/long-term disability, tuition reimbursement, and a 401K plan." - Pay: Not mentioned. No salary info. So we should NOT include Pay section. - Schedule: Not mentioned. No schedule info. So omit. We also have other info: "Candidates must have a valid driver’s license and be able to pass both a criminal background check and driving record review." That's a requirement maybe. Also visa sponsorship statement, EEO etc - remove boilerplate. We need to preserve all substantive information, not invent or summarize away detail. Must not omit substantive info. So we need to include driver's license, background check, etc. We need to format lists with

• . For prose use

  . We must not include headings with empty or placeholder content. Thus produce something like:

  About the role

  Civil Science is seeking an experienced Public Works Division Manager to lead our public works practice in North Dakota. As a Division Manager, you'll report to the Area Manager and oversee Project Managers, Engineers, Surveyors, and support staff within the Public Works Division. This is an excellent opportunity for a licensed engineer who thrives in team leadership, business development, and delivering technical excellence.

  Responsibilities

  Division Leadership & Strategic Responsibilities

  • Set strategic direction for the public works division, aligned with company goals.
  • Lead division level planning, budgeting, forecasting, and performance tracking.
  • Drive division-level quality, risk management, and safety compliance.
  • Develop staff through mentoring, hiring, and company performance management programs.
  • Represent Civil Science in municipal, regional, and state forums and industry organizations.

  Business Development Responsibilities

  • Lead business development efforts for the ND public works market, including identifying new clients, pursuing strategic opportunities, and overseeing proposal development.
  • Monitor municipal funding cycles and position the Division for upcoming opportunities.
  • Cultivate long-term relationships with agencies, councils, and community partners.
  But we are only allowed to use

  for section headings. The instruction: "use

  for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." It doesn't forbid using other headings like

  inside? It says use

  for section headings. It might be okay to use

  for subheadings? Not explicitly prohibited, but safer to stick to only

  for sections. Could we embed subheadings as or just as part of

  ? Probably better to keep only

  headings and use

  • for lists; we can include the subheadings as part of list items or as

    with bold. But we need to preserve the structure. Could do:

    Responsibilities

    Division Leadership & Strategic Responsibilities:

    ...

    Business Development Responsibilities:

    ...
    That uses

    for the subheading lines. That's acceptable. Similarly for Requirements: we can have subheadings like "Education & Experience", "Physical Requirements", etc. Qualifications: maybe we treat "Required Qualifications" as Qualifications heading. Skills: "Key Competencies" as Skills. Benefits: "Why Join Civil Science?" and "Comprehensive Benefits". We need to ensure we include all substantive info: driver's license, background check, driving record review, visa sponsorship statement (though that's more boilerplate? It's about visa sponsorship; it's substantive but maybe considered EEO? It's not boilerplate; it's a specific statement about visa sponsorship. We should keep it? The instruction: Remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate. Visa sponsorship is not exactly EEO; it's about work visa. Might be considered legal? It's about sponsorship; maybe keep as it's substantive. But it's more about company policy; could be considered legal. However it's a specific statement about willingness to sponsor. I'd keep it as part of Requirements or Qualifications? Probably as a requirement: "Civil Science evaluates and determines on a case-by-case basis whether it is willing to sponsor an individual to receive a temporary or permanent work visa". That's substantive. Also EEO statement is boilerplate; remove. Thus we need to include that visa sponsorship line. Now craft HTML. We'll have sections: - About the role - Responsibilities - Requirements - Qualifications - Skills - Benefits No Pay, Schedule. Now fill content. About the role: as above. Responsibilities: combine both sets. We'll do:

    Responsibilities

    Division Leadership & Strategic Responsibilities:

    • Set strategic direction for the public works division, aligned with company goals.
    • Lead division level planning, budgeting, forecasting, and performance tracking.
    • Drive division-level quality, risk management, and safety compliance.
    • Develop staff through mentoring, hiring, and company performance management programs.
    • Represent Civil Science in municipal, regional, and state forums and industry organizations.

    Business Development Responsibilities:

    • Lead business development efforts for the ND public works market, including identifying new clients, pursuing strategic opportunities, and overseeing proposal development.
    • Monitor municipal funding cycles and position the Division for upcoming opportunities.
    • Cultivate long-term relationships with agencies, councils, and community partners.
    Requirements: include education, experience, licensure, driver's license, background check, visa sponsorship, physical requirements. We could split into subheadings: "Education & Experience", "Licensure & Other Requirements", "Physical Requirements". Use

    ...:

    then
    . Content: Education & Experience: - Bachelor’s degree in civil engineering - 12+ years of experience with strong technical background in public works and civil infrastructure projects specifically involving water, sewer, storm sewer and land development. - Proven ability to develop and sustain revenue-generating client relationships in the North Dakota public works market. Licensure & Other Requirements: - North Dakota PE (Professional Engineer) - Strong communication, organization, and leadership skills. - Ability to travel and meet client needs throughout North Dakota and potentially in surrounding states. - Valid driver’s license and ability to pass a criminal background check and driving record review. - Civil Science evaluates and determines on a case-by-case basis whether it is willing to sponsor an individual to receive a temporary or permanent work visa (e.g., E-3, H-1B, H-1B1, or TN visa status). Physical Requirements: - Prolonged periods sitting at a desk and working on a computer. - Must be able to lift up to 50 pounds at times. - Must be able to work on active construction sites, which may include uneven terrain, exposure to varying weather conditions, and moderate to high noise levels. - Frequently required to stand, walk, sit, climb, balance, stoop, kneel, crouch, or crawl. Qualifications: maybe we can treat "Required Qualifications" as same as above? But we already used them. Could we instead put "Key Competencies" under Skills, and under Qualifications put something like "Proven ability to develop and sustain revenue-generating client relationships..." etc. But we already used that. To avoid duplication, we could treat Qualifications as a summary of the required qualifications (maybe same as Requirements). But we need to avoid repeating content. The instruction: Preserve ALL substantive information; do NOT invent or summarize away detail. So we cannot omit any info. If we put some info under Requirements and some under Qualifications, we must ensure we don't miss any. We could split: Requirements: education, experience, licensure, driver's license, background check, visa sponsorship. Qualifications: skills like communication, organization, leadership, ability to travel. But those are also in Required Qualifications list. Actually the list under "Required Qualifications" includes: North Dakota PE, Bachelor’s degree, 12+ years experience..., Proven ability to develop..., Strong communication..., Ability to travel... So those are qualifications. Then there is a separate "Physical Requirements". And "Key Competencies". So we could map: - Requirements: Education & Experience (Bachelor's, 12+ years, proven ability) - Qualifications: Licensure & Other Requirements (ND PE, communication, organization, leadership, travel ability, driver's license, background check, visa sponsorship) - Skills: Key Competencies (strategic thinking, financial acumen, etc.) - Benefits: as described. But we also have Physical Requirements; maybe that goes under Requirements as well. We need to ensure we don't lose any info. Let's list all substantive info blocks: 1. About the role paragraph. 2. Division Leadership & Strategic Responsibilities (list) 3. Business Development Responsibilities (list) 4. Required Qualifications bullet list: - North Dakota PE - Bachelor’s degree in civil engineering - 12+ years of experience with strong technical background in public works and civil infrastructure projects specifically involving water, sewer, storm sewer and land development. - Proven ability to develop and sustain revenue-generating client relationships in the North Dakota public works market. - Strong communication, organization, and leadership skills. - Ability to travel and meet client needs throughout North Dakota and potentially in surrounding states. 5. Physical Requirements