Civil Engineer (Senior Level)
for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). So we should map content to these headings.
We need to decide which sections to include based on content.
- About the role: we have description of role (About The Position). Could also include Who We Are? Might be better as About the role.
- Responsibilities: list of duties: develop designs, assist with construction support, site visits, field data collection, engineering calculations, design using CAD, spatial analysis/GIS, review/apply hydraulic modeling results, technical writing of specs, reports, presentation slides, construction observation. Also coordinating design development, technical quality, delivery, leading teams, mentoring, managing scope/schedule/budget. Also collaborate with scientists etc.
- Requirements: Required Qualifications (BS, PE, etc). Could also include Additional Requirements (work authorization, travel, driver's license). Could be under Requirements.
- Qualifications: Preferred Qualifications (10+ years, project management, CSI specs, AACE, hydrologic/hydraulic modeling, BIM/Revit). Could be separate.
- Skills: maybe list technical skills: AutoCAD Civil 3D, HEC-RAS, etc. But we already have them in qualifications. Might combine.
- Benefits: list: Competitive salary, Bonus Program - Annual and quarterly, Comprehensive medical/dental/vision package, 401(k) with 4% match employer match and 100% immediate vesting, 10 Floating Holidays, Paid Time Off, Short-Term Disability, Paid Parental Leave, Tuition Assistance, Employee Ownership.
- Pay: Salary range $110,000-$156,000/year (based on experience). Could be separate Pay section.
- Schedule: Hybrid environment, prefer 2-3 days a week in office. Also multiple office locations. Could be Schedule.
We must not create sections with filler like "commensurate with experience". Pay section we have actual numbers, so okay.
We must not repeat job title as heading.
We must not include Job ID etc.
We must remove boilerplate: EEO, equal opportunity, scam-warning, etc. Also remove "Our Process" maybe? It's not required but could be considered part of About the role? Might be considered extra but not required sections; we can drop it as it's not in the list of allowed headings. The instruction: "Prefer a few substantive sections over many thin ones." So we could combine some.
We need to output only HTML fragment, no /, no markdown fences.
We'll produce something like:
About the role
...
Responsibilities
- ... ...
Requirements
- ... ...
Preferred Qualifications
- ... ...
Benefits
- ... ...
Pay
$110,000‑$156,000 per year (based on experience)
Schedule
Hybrid work model with preference for 2‑3 days in the office per week; positions available in Portland, OR; Seattle, WA; Pittsfield, ME; Falmouth, ME; and Madison, WI.
We need to ensure we preserve all substantive info. Let's extract details. About the role: combine About The Position and Who We Are? The Who We Are is about company; maybe we can include in About the role as a brief description. But we must not invent. We'll include the description from About The Position (the paragraph about working with senior staff, collaboration, expertise, scope, project work includes site visits etc). Also we could add a sentence about Kleinschmidt being employee-owned consulting firm specializing in hydropower for 60+ years, focusing on engineering, regulatory, environmental solutions, etc. That is substantive and not boilerplate. So include. Responsibilities: list of duties from About The Position and earlier bullet points: develop designs, assist with construction support for dam removals, embankment dam repairs, fish passage facilities, recreation facilities, renewable energy projects, stream restorations. Also site visits, field data collection, engineering calculations and analysis, design using CAD programs, spatial analysis or data processing in GIS, review and application of hydraulic modeling results, technical writing of specifications, reports and presentation slides, construction observation. Also coordinating design development, technical quality, delivery of engineering projects, leading multidisciplinary teams, mentoring junior staff, performing technical quality reviews, managing project scope, schedule, budget. Also collaborating with scientists, data analysts, engineers, licensing experts to develop innovative solutions for renewable energy projects. We'll put these as list items. Requirements: Required Qualifications plus Additional Requirements. - BS in Civil Engineering or related field - Development and technical review of construction drawings, notes, typical details, specifications, material schedules, and quantity takeoffs. - Advanced proficiency with AutoCAD Civil 3D, including alignments, profiles, corridors, grading design, earthwork modeling, and preparation of existing conditions basemaps from publicly available datasets. - Prior experience with civil site development for roadways and drainage, land development, dam decommissioning or removal, stream restoration, and/or fish passage engineering - Experience serving as a task lead or project engineer responsible for coordinating design development, technical quality, and delivery of engineering projects. - Demonstrated ability to lead multidisciplinary engineering teams, mentor junior staff, perform technical quality reviews, and manage project scope, schedule, and budget. - Professional Engineer (PE) license - Must possess permanent authorization to work in the United States - Must be willing to travel and possess a valid driver's license Preferred Qualifications: list. - 10+ years of progressively responsible civil engineering practice, including project leadership and client-facing responsibilities. - Project Management Experience - Working knowledge of CSI-format specifications and construction documentation. - Familiarity with AACE cost estimation methodologies, including development of Opinion of Probable Construction Cost (OPCC). - Demonstrated ability to lead hydrologic and hydraulic evaluations using HEC-RAS, HEC-HMS, SRH-2D, HydroCAD, or similar modeling platforms. - Familiarity with BIM workflows and model coordination using Autodesk Revit. Benefits: list. - Competitive salary - Bonus Program - Annual and quarterly - Comprehensive medical/dental/vision package - 401(k) with 4% match employer match and 100% immediate vesting - 10 Floating Holidays - Paid Time Off - Short-Term Disability - Paid Parental Leave - Tuition Assistance - Employee Ownership Pay: Salary range. Schedule: Hybrid, 2-3 days in office, multiple locations. We must avoid duplication: Salary appears both in Benefits (Competitive salary) and Pay. We should not duplicate. In Benefits we have "Competitive salary" as a bullet; but we also have Pay section with exact range. To avoid duplication, we could either keep Benefits without the salary bullet, or keep Pay and remove Competitive salary from Benefits. Since we have exact range, better to keep Pay section and omit Competitive salary from Benefits. So Benefits list will exclude that bullet. Now ensure we don't include any boilerplate like "Kleinschmidt is an Equal Opportunity and Affirmative Action employer." Remove. Also remove "Our Process" etc. Now produce HTML. We need to use for headings. Use - for lists. Use
for prose.
We must not include any extra text outside HTML.
Let's craft.
Check for any placeholders like "commensurate with experience" - we have "based on experience" which is okay because it's specific? It's not placeholder like "commensurate with experience" but it's still a phrase. The instruction says never emit a heading followed by filler/placeholder text (e.g. "commensurate with experience", "not specified", "N/A", "varies", "TBD") and never create Pay/Schedule/Benefits sections unless the posting actually states them. We have Pay section with actual numbers, okay. The phrase "based on experience" is not a placeholder; it's a description. So fine.
Now produce final HTML.
We'll need to escape any special characters? Not needed.
Let's write.
for prose. We must not include any extra text outside HTML. Let's craft. Check for any placeholders like "commensurate with experience" - we have "based on experience" which is okay because it's specific? It's not placeholder like "commensurate with experience" but it's still a phrase. The instruction says never emit a heading followed by filler/placeholder text (e.g. "commensurate with experience", "not specified", "N/A", "varies", "TBD") and never create Pay/Schedule/Benefits sections unless the posting actually states them. We have Pay section with actual numbers, okay. The phrase "based on experience" is not a placeholder; it's a description. So fine. Now produce final HTML. We'll need to escape any special characters? Not needed. Let's write.