Civil Design Engineer

We need to output HTML fragment with sections: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. Only include sections that have real specific content. We must not repeat job title. No Job ID. Remove boilerplate, EEO, etc. Keep substantive info. We need to parse the posting. Key content: - Intro: "Do you like working with different project teams in a fast-paced environment? Are you interested in joining an organization focused on making a positive impact? If so, we’d like to talk with you about growing with us. EnSafe is accepting applications for a Civil Design Engineer based out of our EnSafe Nashville, Knoxville, TN, or Bowling Green, KY offices". This is about the role. - "EnSafe is an employee-owned global environmental consulting and engineering firm. We strive to provide innovative, creative solutions for our clients. EnSafe specializes in custom solutions in Environmental Management and Planning, Civil Design Engineering, Environmental Restoration, Natural & Water Resources, Health & Safety, and Technology, with offices in the U.S." - "As a Civil Design Engineer, you will work on various projects in an environment that fosters creativity, collaboration at all levels, a culture of support, and professional growth. EnSafe emphasizes empowering staff to practice our profession passionately and without limitations." That's about the role. - Duties/Responsibilities: list bullet points. - Skills/Experience: Minimum Skills Required: list. - Why Join EnSafe? includes sections: Employee-Owned Advantage, Commitment to Growth and Wellness, Purpose‑Driven Work, Safety as a Value, Not Just a Service, A Culture of Freedom & Ownership, Challenging, Creative Work. - About EnSafe: description. - Also mention: "Regional travel is required; national travel for client meetings is likely." That could be part of Requirements or maybe Schedule? It's travel requirement. - No explicit Pay or Schedule given. So we should NOT create Pay or Schedule sections. - Benefits: The "Why Join EnSafe?" sections essentially are benefits. So we can create a Benefits section with those bullet points. - Qualifications: maybe combine Skills/Experience? The instruction: Use headings for sections like About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We need to decide which to use. We have content for About the role (intro). Responsibilities (duties). Requirements (maybe minimum skills required). Qualifications (maybe PE, degree, experience). Skills (maybe critical thinking etc). Benefits (Why Join EnSafe). About EnSafe could be part of About the role or separate? Could be included in About the role. But we have a heading "About EnSafe" but not in allowed list; we could incorporate into About the role or maybe not output as separate heading because not in list. The instruction: Use

for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). So we should only use those headings. So we need to map content to those headings. Thus: -

About the role

: include intro paragraph about EnSafe, location, mission, work environment. -

Responsibilities

: list duties. -

Requirements

: maybe include minimum skills required: Bachelor’s degree in civil engineering with Civil 3D/CAD experience; minimum 5 years civil design experience; Current PE in respective state; previous experience with civil engineering design capabilities with both municipal and industrial clients. -

Qualifications

: maybe include critical thinking, problem-solving, strong work ethic, attention to detail, ability to work on multiple projects, group management and mentoring, regional travel required, national travel likely. Could also include "Ability to work on multiple projects, across various services and in a fast-paced environment." That's a skill. But we also have a separate Skills heading. Could split: Requirements = education, experience, licensure. Qualifications = soft skills, abilities. Skills = technical skills like Civil 3D/CAD? But we already used that in Requirements. Might be overlapping. Better: Use Requirements for education/experience/licensure. Use Qualifications for soft skills and abilities. Use Skills for technical skills like Civil 3D/CAD experience (though that's also education). But we can keep Skills for "Civil 3D/CAD experience" and maybe "critical thinking and problem-solving skills" etc. However we need to avoid duplication. Let's decide: - About the role: intro. - Responsibilities: duties list. - Requirements: Bachelor’s degree in civil engineering with Civil 3D/CAD experience; minimum of 5 years of civil design experience, preferably with an Engineering consulting firm; Current PE in the respective state; Previous experience with civil engineering design capabilities with both municipal and industrial clients. - Qualifications: Critical thinking and problem-solving skills; Strong work ethic with attention to detail; Ability to work on multiple projects, across various services and in a fast-paced environment; Group management and mentoring; Regional travel is required; national travel for client meetings is likely. - Skills: maybe we could list "Civil 3D/CAD experience" but that's already in Requirements. Could instead list "Proficiency in Civil 3D/CAD" as a skill. But to avoid duplication, maybe we skip Skills section if content overlaps. However we need to include a section only when posting has real specific content. We have technical skill: Civil 3D/CAD experience. Could put under Skills. But we already put Civil 3D/CAD in Requirements. Could move it to Skills and keep Requirements more about degree, years, PE, experience. Let's do: Requirements: Bachelor’s degree in civil engineering; minimum of 5 years of civil design experience, preferably with an Engineering consulting firm; Current PE in the respective state; Previous experience with civil engineering design capabilities with both municipal and industrial clients. Skills: Civil 3D/CAD experience; Critical thinking and problem-solving skills; Strong work ethic with attention to detail; Ability to work on multiple projects, across various services and in a fast-paced environment; Group management and mentoring. Qualifications: maybe we could combine with Skills? But we need distinct headings. Could use Qualifications for "Regional travel is required; national travel for client meetings is likely." and maybe "Ability to work on multiple projects..." but that's already in Skills. Better: Use Qualifications for travel requirement and maybe "Group management and mentoring". But we already have group management in Skills. Let's think: The posting lumps "Skills/Experience Minimum Skills Required:" then list includes degree, Civil 3D/CAD, 5 years experience, PE, experience with municipal/industrial, critical thinking, problem-solving, strong work ethic, attention to detail, ability to work on multiple projects, group management and mentoring, regional travel required, national travel likely. Thus we can split: - Requirements: education, years experience, PE, experience with municipal/industrial. - Skills: Civil 3D/CAD, critical thinking, problem-solving, strong work ethic, attention to detail, ability to work on multiple projects, group management and mentoring. - Qualifications: Regional travel required; national travel likely. But Qualifications heading might be weird for travel only. Could instead put travel under Skills as well. But we need to avoid thin sections. Maybe we combine travel into Skills as a bullet. Thus we could have only About the role, Responsibilities, Requirements, Skills, Benefits. No Qualifications. But the instruction says we can use those headings; we don't have to use all. So we can omit Qualifications if not needed. Thus sections: - About the role - Responsibilities - Requirements - Skills - Benefits Now we need to extract Benefits from "Why Join EnSafe?" paragraphs. Benefits content: - Employee-Owned Advantage: ESOP, shared rewards. - Commitment to Growth and Wellness: personalized career development, mentorship, employee wellness initiatives such as health tracking tools. - Purpose‑Driven Work: mission focuses on impactful environmental, health, and safety consulting; making a real difference; backed by technical credibility. - Safety as a Value, Not Just a Service: safety deeply embedded; prioritizing employee well-being; safety part of everything. - A Culture of Freedom & Ownership: freedom to take initiative, achieve goals, shape career path; flexible, entrepreneurial environment. - Challenging, Creative Work: workdays fast-paced, dynamic, opportunities to tackle projects in environmental consulting, health & safety, engineering, technology; calls for creativity, innovation, agile problem-solving. Also maybe "EnSafe began as a two-person firm in 1980..." that's About EnSafe, could be part of About the role or maybe separate but we can incorporate into About the role. We need to preserve all substantive information; do not invent or summarize away detail. So we need to keep the specifics. Thus we will produce HTML:

About the role

EnSafe is accepting applications for a Civil Design Engineer based out of our EnSafe Nashville, Knoxville, TN, or Bowling Green, KY offices. EnSafe is an employee-owned global environmental consulting and engineering firm. We strive to provide innovative, creative solutions for our clients. EnSafe specializes in custom solutions in Environmental Management and Planning, Civil Design Engineering, Environmental Restoration, Natural & Water Resources, Health & Safety, and Technology, with offices in the U.S. As a Civil Design Engineer, you will work on various projects in an environment that fosters creativity, collaboration at all levels, a culture of support, and professional growth. EnSafe emphasizes empowering staff to practice our profession passionately and without limitations. EnSafe began as a two-person firm in 1980, navigating complex regulatory compliance issues on behalf of our clients. We nurture our people with growth and development opportunities. We build enduring, trustful relationships with each of our clients, with a focus on high ethical and safety standards. We build this reputation by attracting high-quality people and retaining them for the long term. At EnSafe, we are dedicated to fostering a diverse and authentic workplace.

Responsibilities

• Support and lead engineering design efforts for site civil, stormwater drainage, industrial wastewater, and utility infrastructure projects.
• Contribute to a variety of projects, including civil site design, solid waste management and landfill design, impoundments, and the development of plans and profiles.
• Develop engineering designs and deliverables to support regulatory permitting, site development, technical specifications, and bid documents.
• Collaborate with multidisciplinary teams to evaluate challenges and develop practical engineering solutions.
• Participate in and coordinate design and construction meetings with clients, contractors, and subcontractors, including pre-bid meetings.
• Plan, schedule, and execute detailed phases of engineering and design work to meet project objectives and timelines.
• Support business development activities through proposal preparation, marketing initiatives, project management, and ongoing client engagement as appropriate.

Requirements

• Bachelor’s degree in civil engineering
• Minimum of 5 years of civil design experience, preferably with an Engineering consulting firm
• Current PE in the respective state
• Previous experience with civil engineering design capabilities with both municipal and industrial clients

Skills

• Civil 3D/CAD experience
• Critical thinking and problem-solving skills
• Strong work ethic with attention to detail
• Ability to work on multiple projects, across various services and in a fast-paced environment
• Group management and mentoring
• Regional travel is required; national travel for client meetings is likely

Benefits

• Employee-Owned Advantage: EnSafe is 100% employee-owned, with an ESOP (Employee Stock Ownership Plan) since 1997; when EnSafe succeeds, you succeed too, turning company growth