Civil Designer Engineer-in-Training (EIT)

We need to produce HTML fragment with sections: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. Only include sections that have real specific content. Must not repeat job title as heading. Must not include Job ID etc. Must preserve all substantive info, no invented details. Remove boilerplate like cookie/navigation/legal/EEO etc. The provided text includes "Why DOWL?" intro, then description, then "Site Design", then "Summary", then "Job Responsibilities And Duties", then many subpoints, then "Education And/or Experience", "Certificates, Licenses, Registrations", "Physical Demands", "Work Environment". We need to map content to sections. We need to decide which sections have content. - About the role: Could be the introductory paragraph about DOWL and the role summary. The "Why DOWL?" and "Site Design" and "Summary" could be about the role. We'll put that in

About the role

with paragraphs. - Responsibilities: The "Job Responsibilities And Duties" section includes many bullet-like items. We'll extract list items. - Requirements: Could be education/experience, certificates, etc. Might be separate sections: Requirements (education/experience) and Qualifications (maybe certificates). But we need to decide based on content. - Skills: Could be technical expertise, software, teamwork, etc. - Benefits: The posting mentions "great benefits" but no specifics. It says "We support your growth, offer great benefits, and foster a culture..." No specific benefits listed. Since we must not create Benefits section unless posting actually states them (specific). It only says "great benefits" generic, not specific. So we should not include Benefits section. - Pay: Not mentioned. So omit. - Schedule: Not mentioned. Omit. Thus we will have sections: About the role, Responsibilities, Requirements, Qualifications, Skills maybe. But we need to avoid thin sections. Let's see content: About the role: includes why DOWL, site design, summary. Good. Responsibilities: many items. Requirements: Education and/or Experience (Bachelor's required, 2 years experience, etc). Also Certificates, Licenses, Registrations (EIT/EI required, driver's license). Could be combined into Requirements. Qualifications: maybe technical expertise, software proficiency, etc. But we could treat those as Skills. Skills: Software, technical fundamentals, teamwork, project delivery, understanding budget/schedule, industry standards, client interaction, etc. Thus we can have: - About the role (intro) - Responsibilities (list) - Requirements (education/experience, certificates/licenses, physical demands? maybe physical demands is separate but could be part of Requirements? Might be better as its own section but we don't have a heading for Physical Demands; we could include under Requirements or maybe under Qualifications? The instruction says use headings for given list; we can add other headings only if they match those? It says use

for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). It implies we should use those headings; we can also possibly add other headings if needed? It says "Use

for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." That suggests we should limit to those headings. So we should map content to those categories only. So we need to fit everything into those categories. Thus we need to decide what goes where. About the role: general description of company and role. Responsibilities: duties. Requirements: education/experience, certificates/licenses, maybe physical demands? Physical demands could be considered a requirement. Qualifications: maybe technical expertise, software proficiency, etc. Skills: maybe soft skills like teamwork, communication, etc. But there is overlap. We need to ensure we don't duplicate content. We must preserve all substantive information; we can split but not repeat same info in multiple sections? The instruction: "Preserve ALL substantive information; do NOT invent or summarize away detail." It doesn't forbid duplication, but better to avoid redundancy. We'll try to allocate each piece to one section. Let's extract substantive pieces: From intro: - DOWL is a top-ranked, multi-disciplined consulting firm with over 60 years of experience in civil engineering and related services. - In-house expertise spans Civil and Land Development, Construction-Related Services, Transportation and Structures, and Water and Environmental Services. - At DOWL, you’re valued. We support your growth, offer great benefits, and foster a culture of integrity, professionalism, and teamwork. - Site Design: At DOWL, you'll be part of a team that delivers a full spectrum of civil engineering services to both public and private clients making a meaningful impact on communities and infrastructure across the region. - We take pride in our ability to solve complex planning, environmental, and design challenges, navigate funding and permitting hurdles, and guide projects from concept through construction with precision and care. - Our strong reputation is built on a commitment to quality and the personal attention we bring to every project. - If you're passionate about creating practical, lasting solutions and want to grow with a company that values both technical excellence and client relationships, we invite you to join us. Summary (Civil Designer 2): - Responsible for performing moderately complex calculations and comprehensive design services for a variety of civil engineering and site development projects. - Expected to exercise a strong work ethic, demonstrate desire to learn new design concepts, apply judgement and discretion, and have excellent organizational and communication skills. - Successful Civil Designer 2 demonstrates developing proficiency with drafting fundamentals and AutoCAD Civil 3D design software. - Other duties include making site visits, coordinating with clients and approval agencies, preparing construction documents, estimating construction costs, and preparing written reports. - Expected to work well with others, absorb and apply constructive criticism, and seek guidance from more experienced members of the team as necessary. - Works under the guidance of a licensed professional engineer. Job Responsibilities And Duties (list): - Software Microsoft Office (Outlook, Word, Excel) - Developing - Market Sector Software (AutoCAD/C3D, HydroCAD, AutoTurn/Vehicle Tracking) - Developing - Technical Expertise Solid understanding of technical fundamentals - Performs basic technical tasks with market sector with limited oversight - Performs quality control of basic deliverables - Eager to learn and expand skill set - Teamwork: Team player who follows the direction of others, asks good questions, and retains information provided. Shares information with those less experienced. - Project Delivery: Produces The Following Under Limited Direction/oversight From Others: - Identify design criteria - Site layout and grading - Utility plans and profiles - Street plans and profiles - Tentative plans - Permitting exhibits - Construction plans - Traffic control plans - Erosion control plans - Quantity takeoffs - Specifications - Technical reports and memos - Storm calculations - ADA designs - Offsite improvements designs - Permit applications - Construction details and notes - Services during construction (RFI and submittal review, construction observation and inspection, and record drawings) - Understanding Budget and Schedule: Moderate understanding of scopes, schedules, and budgets. With guidance, predicts the level of effort for individual tasks and successfully deliver tasks within that level of effort. Monitors results on moderately complex projects. - Industry Standards and Regulations: Understands And Employs The Following Design Codes: Local jurisdiction, Local DOT, PROWAG, ASTM, AWWA, MUTCD, DEQ - Client Interaction: Limited direct interaction, commonly in group settings. Responds to emails, attends meetings, and answers questions/comments with limited autonomy. - Other: Other duties as assigned. - Level of Work/Accountability: Performs moderately complex technical work on projects for the assigned market sector. Operates with limited autonomy - work is supervised by more senior staff. Education And/or Experience: - Bachelor's Degree required - Years of experience required: 2 years - Years of experience required with advanced degree: 1 year Certificates, Licenses, Registrations: - EIT/EI required - Driving is an essential job function or a valid driver’s license is required to support legitimate business purposes Physical Demands: - While performing the duties of this position, the employee is regularly required to sit. - The employee is required to talk and hear. - The employee is regularly required to stand, walk, and use hands. - The employee must occasionally lift and/or move up to 25 pounds. - Specific vision abilities required by this position include close vision and ability to adjust focus. Work Environment: - The noise level in the work environment is usually moderate. Now map to headings. About the role: include company overview, site design paragraph, summary maybe. Responsibilities: list of duties from Job Responsibilities And Duties (the bullet list). Could also include the summary duties? But we can keep summary in About the role. Requirements: Education and/or Experience, Certificates/Licenses, Physical Demands? Physical demands could be a requirement. We'll include. Qualifications: maybe Technical Expertise, Software proficiency, etc. But we already have Software under Responsibilities? Actually the list includes Software Microsoft Office etc. That could be under Skills. Let's think. Skills: could include technical expertise, software, teamwork, project delivery, understanding budget/schedule, industry standards, client interaction. Qualifications: maybe education/experience? But we already used that for Requirements. Hmm. We need to avoid duplication. Let's assign: - About the role: company overview, site design, summary (role purpose). - Responsibilities: the list of duties (the big list under Job Responsibilities And Duties). - Requirements: Education/Experience, Certificates/Licenses, Physical Demands. - Qualifications: maybe nothing left? Could be "Developing proficiency with drafting fundamentals and AutoCAD Civil 3D design software" but that's skill. Could be "Strong work ethic, desire to learn, judgement, discretion, organizational and communication skills" - those are skills. - Skills: Technical expertise, software proficiency, teamwork, project delivery, understanding budget/schedule, industry standards, client interaction, etc. Thus we have four sections: About the role, Responsibilities, Requirements, Skills. Qualifications maybe omitted if no specific content left. But we need to check if any content fits Qualifications better than Skills. The heading list includes Qualifications; we could put things like "Bachelor's Degree required" under Qualifications, but we already put that under Requirements. Could shift. Better to follow typical job posting: Requirements = education/experience, certificates. Qualifications = preferred qualifications (maybe none). Skills = technical and soft skills. Since we have no explicit "Preferred qualifications", we could omit Qualifications section. Thus final sections: About the role, Responsibilities, Requirements, Skills. Check that we have real specific content for each. About the role: we have multiple paragraphs. Responsibilities: we have list items. Requirements: we have education/experience, certificates/licenses, physical demands. Skills: we have technical expertise, software, teamwork, project delivery, understanding budget/schedule, industry standards, client interaction. We must ensure we don't leave out any substantive info. Let's verify each piece is covered. Company overview: included in About the role. Site design paragraph: included. Summary (role purpose): included. Job Responsibilities And Duties list: included under Responsibilities. Education/Experience: included under Requirements. Certificates/Licenses: included under Requirements. Physical Demands: included under Requirements. Technical Expertise: "Solid understanding of technical fundamentals" etc. We'll put under Skills. Software: Microsoft Office, AutoCAD/C3D, HydroCAD, AutoTurn/Vehicle Tracking - under Skills. Teamwork: under Skills. Project Delivery list: under Skills. Understanding Budget and Schedule: under Skills. Industry Standards and Regulations: under Skills. Client Interaction: under Skills. Other duties as assigned: maybe under Responsibilities