Chief Engineer

We need to output only HTML fragment, using

for section headings (About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). We must not repeat job title as heading. We need to include sections only when posting has real specific content. We have content: About the role (description), Responsibilities (Essential Functions), Requirements (Education Requirement, Experience Requirement, Travel Requirement maybe), Skills (Skills And Qualifications), Benefits (Job Benefits). No explicit Pay or Schedule info, so we should not create those sections. Also we should not include headings with filler. We need to preserve all substantive information, no invented content. Remove boilerplate: EEO, legal, etc. Also remove duplicated lines. Also remove navigation/cookie etc. We need to format using

for each section heading. Use

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

  for prose. We need to decide what goes where. Section headings: About the role (intro paragraph). Responsibilities (Essential Functions). Requirements (Education Requirement, Experience Requirement, Travel Requirement maybe). Skills (Skills And Qualifications). Benefits (Job Benefits). Possibly also Qualifications? But we have Skills And Qualifications combined; we could put under Skills heading. Or we could have Qualifications separate but we have content that fits Skills. The instruction: use headings for e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We can choose which to include. We have content for About the role, Responsibilities, Requirements, Skills, Benefits. Qualifications maybe overlapping with Skills; we could omit Qualifications if not distinct. Better to include Skills heading and put the skills list there. Requirements heading for education/experience/travel. We need to ensure we don't create empty sections. Now extract content. About the role: The paragraph after "We are currently seeking a Chief Engineer to join our Wagman Heavy Civil team." up to maybe before "Skills And Qualifications". Let's capture: "We are currently seeking a Chief Engineer to join our Wagman Heavy Civil team. The Chief Engineer is the senior engineering leader, responsible for overseeing all construing and engineering activities across Wagman Heavy Civil, Inc. The role provides technical direction, ensures engineering excellence, and supports the successful delivery of complex heavy civil projects. The Chief Engineer lead engineering efforts, collaborates with operations and executive leadership, and serves as the primary engineering liaison with clients and partners. Wagman is a fourth generation, family-owned company with offices in Pennsylvania and Virginia and is headquartered in York, PA. Founded in 1902, Wagman is a nationally recognized leader in the industry. We are multi-faceted construction firm with major operations in heavy civil, general construction and geotechnical construction services. Core competencies include design-build, infrastructure, marine construction, modified concrete, grooving and grinding, and geotechnical construction services. This is a safety sensitive position requiring work on construction sites with various safety hazards inherent in heavy construction. This position is subject to drug testing and compliance policies associated with our status as a Federal Contractor." We need to preserve all substantive info. Note there is a typo "construing" but we keep as is. Responsibilities: Essential Functions list. We'll convert each bullet to

• . Essential Functions list: - Serve as the senior engineering authority for all construction engineering activities, including design, review, and approval of engineering solutions for heavy civil projects. - Provide technical leadership and mentorship to a multi-location engineering team - Partner with project managers and field operations to ensure constructability, safety, and quality execution of engineering plans. - Establish and enforce engineering standards, procedures, and quality control practices across all job sites. - Perform engineering risk assessments and lead constructability reviews for complex bridge and highway projects. - Ensure compliance with federal, state, and local regulations (DOT, OSHA, etc.) - Act as a primary engineering liaison with owners, DOT agencies, consultants, and design partners. - Support preconstruction, estimating, and bid strategy through technical input. - Oversee and approve engineering calculations, drawings, and technical documentation, including signing/sealing when required. - Drive continuous improvement through innovation and engineering best practices. - Travel to active project sites to support teams and ensure alignment. Also maybe Physical Requirements? Those could be under Requirements? But they are physical requirements, maybe part of Requirements? However the instruction: Use headings for Requirements (maybe includes education, experience, travel, physical). We could include Physical Requirements under Requirements as a list. But we need to decide if we want a separate section? Not listed as a heading option but we could include under Requirements. The instruction says use headings for 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)." So we can use those headings; we could also add other headings if needed but better to stick to those. Physical requirements could be part of Requirements. Requirements: Education Requirement Bachelor's in Civil Engineering, Master's Degree in Civil / Structural En (typo). Experience Requirement 10+ years' experience in progressive civil engineering. Special Skills Deep knowledge of heavy civil construction methods, structural systems Travel Requirement Open to travel. Also Physical Requirements list. We need to preserve all substantive info. So we should include Education, Experience, Travel, Physical Requirements under Requirements. We could structure as a

  with items: Education Requirement..., Experience Requirement..., Special Skills..., Travel Requirement..., Physical Requirements (maybe a sublist?). But we need to keep it as list items; physical requirements could be a list within a list? Might be okay to just list each physical requirement as separate
  • . However that might lose grouping. Could do a nested list:
  • Physical Requirements:
    ...
  . That's acceptable. Now Skills: Skills And Qualifications list: - Deep knowledge of heavy civil construction methods, structural systems, and transportation engineering - Strong understanding of DOT standards, specifications, and regulatory compliance requirements - Demonstrated ability to lead, mentor, and develop engineering talent - Expertise in risk management, constructability analysis, and engineering problem-solving - Experience with multi-project oversight, budgeting, and engineering resource planning - Strong communication skills with ability to engage executives, field teams, and external stakeholders - Proficiency in engineering tools and software - Ability to travel regularly to project sites Also Education Required: Bachelor’s Degree in Civil Engineering Preferred: Master’s Degree in Civil / Structural Engineering or Construction Engineering (but we already have education in Requirements; we might duplicate. However we should not repeat content? The instruction: Preserve ALL substantive information; do NOT invent or summarize away detail. So we need to include that info somewhere. If we already put Education Requirement under Requirements, we might duplicate if we also put under Skills. Better to keep Education under Requirements only, and not duplicate. But the Skills And Qualifications section also includes Education Required and Preferred. Since we already captured Education Requirement earlier, we could omit duplication to avoid redundancy. However the instruction says preserve ALL substantive information; duplication is not prohibited but might be considered redundant. It didn't forbid duplication, but better to avoid repeating same info. We'll keep Education under Requirements and not repeat under Skills. Now Benefits: Job Benefits list: - Medical/Vision/Dental Insurance - Flexible Spending Accounts for Healthcare and Dependent Care - Disability and Life Insurance - Wellness Programs that include Orthopedic Care - 401(k) Retirement Plan with Company Matching Contribution - Tuition Reimbursement - Employee Assistance Program - Adoption Assistance - 8 paid holidays - Paid Time Off Also maybe "Our Values" etc but that's boilerplate? It's values description; could be considered substantive but not a standard heading. The instruction says remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. Values might be considered substantive but not a standard heading; we could include under About the role? But it's separate. However we have no heading for Values; we could incorporate into About the role as a paragraph? But that might be stray. The instruction: Prefer a few substantive sections over many thin ones. So we could add a section "Values" but not in the list of allowed headings. Better to incorporate into About the role or maybe under a separate heading "About the company". But not in list. Since we must use headings from the list, we could put values under About the role as additional paragraph. That seems okay. Similarly Wagman Culture and EEO statements are boilerplate; we should remove. Thus final HTML:

  About the role

  ... (the paragraph)

  Responsibilities

  • ...
  ...

  Requirements

  • Education Requirement: Bachelor's in Civil Engineering
  • Experience Requirement: 10+ years' experience in progressive civil engineering
  • Special Skills: Deep knowledge of heavy civil construction methods, structural systems
  • Travel Requirement: Open to travel
  • Physical Requirements:
    • Able to lift up to 30 pounds from ground level to waist level.
    • Able to bend, squat and kneel occasionally throughout a scheduled work shift.
    • Able to climb ladders, if required.
    • Continuous standing and walking required while outside.
    • Able to perform simple grasping and fine manipulation tasks with both hands.
    • Working outdoors in wet, muddy, cold, hot, and humid weather, may occur during site visits.
    • Acceptable corrected vision (in both eyes) and acceptable corrected hearing required.

  Skills

  • Deep knowledge of heavy civil construction methods, structural systems, and transportation engineering
  • Strong understanding of DOT standards, specifications, and regulatory compliance requirements
  • Demonstrated ability to lead, mentor, and develop engineering talent
  • Expertise in risk management, constructability analysis, and engineering problem-solving
  • Experience with multi-project oversight, budgeting, and engineering resource planning
  • Strong communication skills with ability to engage executives, field teams, and external stakeholders
  • Proficiency in engineering tools and software
  • Ability to travel regularly to project sites

  Benefits

  • Medical/Vision/Dental Insurance
  • Flexible Spending Accounts for Healthcare and Dependent Care
  • Disability and Life Insurance
  • Wellness Programs that include Orthopedic Care
  • 401(k) Retirement Plan with Company Matching Contribution
  • Tuition Reimbursement
  • Employee Assistance Program
  • Adoption Assistance
  • 8 paid holidays
  • Paid Time Off
  We need to ensure no extra whitespace or markdown. Output only HTML fragment. Check for any leftover boilerplate: We removed EEO, values, culture, etc. Also removed "Job: Chief Engineer Location: York, PA" maybe we should keep location? It's substantive metadata. The instruction: do NOT put Job ID / requisition numbers as headings — fold minor metadata into a short

  or drop it. Location is minor metadata; we could fold into About the role paragraph or a short p. Since we already have About the role paragraph that mentions Wagman is headquartered in York, PA. So location is already covered. Good. Check for duplicated lines: We have "Deep knowledge of heavy civil construction methods, structural systems" appears both in Requirements Special Skills and Skills list (first skill includes