Civil Engineer (Entry-Mid Level)

We need to output HTML fragment with sections: About the role? Actually the posting includes "About The Position", "Who We Are", "Our Process", "Benefits". Also "Required Qualifications", "Preferred Qualifications", "Additional Requirements". Also "Salary". Also maybe "Schedule" (hybrid 2-3 days a week). Also "Location" maybe not required but we can include as part of About? The instruction: Use

for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). Use

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

  for prose. Do NOT repeat the job title as a heading (the page already shows it) and do NOT put Job ID / requisition numbers as headings — fold minor metadata into a short

  or drop it. Preserve ALL substantive information; do NOT invent or summarize away detail. Remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. IMPORTANT: include a section ONLY when the posting has real, specific content for it — 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. Prefer a few substantive sections over many thin ones. Output ONLY the HTML fragment — no /, no markdown code fences. Thus we need to decide which sections to include. The posting includes: - About The Position (description of role, duties) - Who We Are (company description) - Our Process (hiring process) - Benefits (list) - Required Qualifications (list) - Preferred Qualifications (list) - Additional Requirements (list) - Salary (Pay) - Schedule (hybrid 2-3 days a week) - Location (multiple office locations) maybe not required but could be part of About? The instruction says we can include sections like About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. So we can map: - About the role: maybe combine About The Position and Who We Are? But they said "About the role" is a possible heading. We could have "About the role" containing description of role and maybe company overview? However they said "Prefer a few substantive sections over many thin ones." So we could combine some. We need to preserve all substantive information. Let's list all substantive content: Job title: Entry-Mid level Civil Engineer (but we don't repeat as heading). Description: full-time opening to work with multi-disciplinary team to develop designs and assist with construction support for dam removals, embankment dam repairs, fish passage facilities, recreation facilities, renewable energy projects, and stream restorations. Multiple office locations in US: Portland, OR; Seattle, WA; Pittsfield, ME; Falmouth, ME; Madison, WI. Hybrid environment: work from office and remotely, requires coming into office 2-3 days a week. Salary: $68,000-$125,000/year (based on experience) Required Qualifications: - BS in Civil Engineering or related field - Erosion & sediment control and stormwater management design experience - Prior exposure to engineering design/construction support tasks - Proficient with AutoCAD Civil 3D - Engineer in Training (EIT) Preferred Qualifications: - 4+ years of experience in civil engineering - Direct project experience using AutoCAD Civil 3D to advance design, including the use of alignments, profiles, corridors, grading, and civil basemap preparation with publicly available data products. - Drawing development and review of notes, typical details, material schedules, and quantities. - Experience with CSI standard specifications format and content. - Experience with AACE's cost estimation classes and preparation of OPCC. - Prior experience with civil site development for roadways and drainage, land development, dam decommissioning or removal, stream restoration, and/or fish passage engineering - Experience with ArcGIS, HEC-RAS, SRH2D, HEC-HMS, or HydroCAD. Additional Requirements: - Must possess permanent authorization to work in the United States - Must be willing to travel and possess a valid driver's license About The Position (detailed duties): - Work directly with senior staff on all stages of project delivery from conceptual designs to issued for bid construction drawings. - Project work will require close collaboration with scientists, data analysts, engineers, and licensing experts to develop innovative solutions that support renewable energy projects. - Through these projects you will gain specialized expertise related to civil site design, hydraulic fish passage, slope and embankment protection, and stream channel design for dam decommissioning, fish passage barrier correction, and embankment dam protection. - The scope and scale of projects at Kleinschmidt will engage your curiosity and facilitate professional growth. - Project work will include 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, and construction observation. Who We Are: - Kleinschmidt is one of the few employee-owned consulting firms in North America specializing in hydropower and we have been doing it for more than 60 years. - We focus on developing engineering, regulatory, and environmental solutions that benefit our clients by lowering cost, shortening schedules, and improving regulatory relationships. - Our work spans the USA and Canada and typically involves either a river/stream, a hydropower dam, a non-hydropower dam, a renewable energy source (e.g., wind or solar), or some combination of these physical structures. - We are a specialty consulting firm and don't do cookie-cutter land development-type projects! - Our people are passionate, engaged, and enjoy learning from one another while working on unique and creative projects. - Technical excellence is at the heart of our continued success, and we strongly encourage learning and continuous improvement to create professional growth, mentoring, and new opportunities for our employees. Our Process: - After careful review of resumes, we will notify those we are interested in interviewing. - We may ask for more details with an initial screening. - Our process normally involves up to two interviews. - The top candidate will then be asked to provide 2-3 references and offered a benefits call, a unique step in our process where we describe our full benefits package. - The final step is an offer sent via email. Benefits: - 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 Also note: "Competitive salary" is redundant with salary range; but we keep. We need to avoid boilerplate: EEO statement, etc. Remove that. We need to avoid duplicated lines: there is duplicate salary line later; we should include only once. We need to avoid application instructions: none. Now decide sections. Potential sections: - About the role (could combine About The Position and Who We Are? But maybe better to have "About the role" for role description, and "About the company" not in list but we could incorporate into About the role or maybe "Who we are" not a standard heading but we could still include as a section if we want. The instruction says use headings like 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)." The e.g. suggests those are examples but not exclusive. However to be safe, we can stick to those headings. We can map content to those. We have: - About the role: could include description of role (About The Position) and maybe company overview? But we could also add a separate "About the company" but not in list. Safer to stick to given headings. We have Responsibilities: we could list duties from About The Position (site visits, etc.) as a list. We have Requirements: could include Required Qualifications and Additional Requirements? Or we could separate Qualifications (Required and Preferred) and Skills. We have Qualifications: could list Required and Preferred. We have Skills: maybe list software skills (AutoCAD Civil 3D, ArcGIS, HEC-RAS, etc.) but those are already in qualifications. We have Benefits: list. We have Pay: salary range. We have Schedule: hybrid 2-3 days a week. We also have Location: multiple office locations. Not in the list but could be included in About the role or maybe as a short p. We also have Our Process: hiring process. Not in list but could be included as a section maybe "Process". But instruction says prefer few substantive sections over many thin ones. Could we incorporate process into About the role? Not really. But we could omit it if we think it's less substantive? However it's substantive info about hiring process. The instruction says "Preserve ALL substantive information". So we need to include it somewhere. Could we add a section "Process" as an h3? Not in the examples but maybe allowed. The instruction says "Use

  for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." The e.g. suggests those are typical but not exclusive. However to be safe, we could include a section "Our Process" as an h3. It's not forbidden. The instruction does not say we cannot use other headings. It just gives examples. So we can include. Similarly, "Who We Are" could be a section "About the company". But we could incorporate into About the role or maybe a separate section "About the company". But to keep few sections, we could merge Who We Are into About the role? But that might be mixing role description with company description. However we could have a section "About the company" as an h3. But the instruction says "Prefer a few substantive sections over many thin ones." So we should aim for maybe 5-6 sections. Let's think: we could have: - About the role (description of role and maybe company overview) - Responsibilities (list of duties) - Qualifications (required and preferred) - Benefits - Pay - Schedule - Process (hiring process) - Location (office locations) maybe as a short p under About the role. But that's many sections. We could combine some: e.g., About the role includes role description and company overview and location. Responsibilities separate. Qualifications separate. Benefits separate. Pay separate. Schedule separate. Process separate. That's 7 sections. Maybe we can combine Pay and Schedule into a "Compensation & Schedule" section? But instruction says use headings like Pay, Schedule. It didn't forbid combining but we should follow examples. However we can keep them separate. Given the instruction to prefer few substantive sections over many thin ones, we could try to reduce sections by merging where appropriate. Potential merging: - About the role: include role description, company overview, location. - Responsibilities: list of duties. - Qualifications: include required and preferred. - Benefits: list. - Pay: salary range. - Schedule: hybrid. - Process: hiring steps. That's 7 sections. Could we combine Pay and Schedule into a "Compensation & Schedule"? But then we deviate from examples. Might be okay but risk. Alternatively, we could drop Process if we consider it less substantive? But we must preserve all substantive information. The process is substantive but maybe we could incorporate into About the role as a short paragraph? Not ideal but could be done: "Our hiring process involves up to two interviews, reference checks, and a benefits call before offer." That preserves info. So we could omit a separate Process section.