Entry Level Water Resources Engineer

We need to output HTML fragment with sections: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. Only include sections where there is real specific content. We must not repeat job title. Must not include Job ID etc. Remove boilerplate. Must preserve all substantive info. Let's parse the job description. Content: - Job Description: Dewberry is currently seeking an Entry Level Water Resources Engineer to perform water resource work in our Gainesville, VA office. Individual will develop concept and final design of stormwater facilities/treatment, perform floodplain studies, analyze stormwater quality, design stream restoration, dam design, dam retrofit, dam retrofit, and perform dam break studies among other projects and tasks. - About the company: Dewberry is a leading, market-facing professional services firm with more than 60 locations and 2,500 professionals nationwide. What sets us apart from our competitors is our people. At Dewberry, we seek out exceptional talent and strive to deliver the highest quality of services to our clients. Whether you’re an experienced professional or a new graduate, you’ll have the chance to collaborate with the best and brightest and work on innovative and complex projects at the forefront of the industry. Our commitment to excellence stems from our personal integrity and from other defining attributes, which we call “Dewberry at Work,” that have inspired our employees to be successful for more than a half-century. - Required Skills & Required Experience: Bachelor’s degree in Civil Engineering with a focus in Water Resources or related field is required; Knowledge of floodplain delineation, storm water management, culvert and bridge hydraulics, and drainage design; 0 - 1 year of experience; previous internship(s) preferred; Strong verbal and written communication skills are required; Proficiency in MS Office software; Ability to work in a team environment. - Don’t meet every single requirement? ... (encouragement to apply). This is boilerplate? It's a statement encouraging applicants; maybe we keep as part of "About the role" or "Requirements"? It's not a list; it's prose. We'll keep it as prose maybe under "About the role" or "Requirements". It's not boilerplate like EEO; it's a motivational note. We'll keep. - At this time, Dewberry will not sponsor a new applicant for work authorization. (This is a condition; maybe part of Requirements? It's a note about sponsorship. Could be included under Requirements as a note.) - Dewberry is an Equal Opportunity Employer... (EEO boilerplate) remove. - Only recipients of an offer... background screening... (legal boilerplate) remove. - Notice to Third Party Recruiters... (legal) remove. - Salary Range: The projected range for this position is $82,500 - $85,000 annually. Depending upon other factors, i.e., skills, experience, location, market conditions, the range may vary slightly. - Program Information: As An Entry-level Hire, You’ll Be Part Of a Class Of Peers With 0-1 Year Of Professional Experience. Our Entry-level Program Comes Together On a Regular Basis For Professional Development Events And Team Building Activities Led By An Advisory Team To Form lasting connections with peers in your class. Gain a better understanding of career growth and meaningful opportunities to align with your professional goals. Expand your knowledge of Dewberry and what we do. Thus we have sections: - About the role: could include the initial description of the role and maybe the company description? Usually "About the role" describes the job. We'll put the first paragraph (Dewberry is currently seeking... individual will develop concept...). Also maybe include the company description? Could be "About the company" but not a required heading. We have only allowed headings: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We could put company description under About the role or maybe under Responsibilities? Better to put role description under About the role. - Responsibilities: list of duties: develop concept and final design of stormwater facilities/treatment, perform floodplain studies, analyze stormwater quality, design stream restoration, dam design, dam retrofit, perform dam break studies among other projects and tasks. - Requirements: maybe education, experience, etc. Could be split into Requirements (education, experience) and Qualifications (maybe same). But we have both headings; we need to decide what to put where. Usually Requirements are mandatory; Qualifications are preferred. But we can combine. However we must not create empty sections. We have content for both maybe. Let's extract: Required Skills & Required Experience: - Bachelor’s degree in Civil Engineering with a focus in Water Resources or related field is required - Knowledge of floodplain delineation, storm water management, culvert and bridge hydraulics, and drainage design - 0 - 1 year of experience; previous internship(s) preferred - Strong verbal and written communication skills are required - Proficiency in MS Office software - Ability to work in a team environment - Don’t meet every single requirement? ... (encouragement) - At this time, Dewberry will not sponsor a new applicant for work authorization. We could treat these as Requirements. Qualifications maybe could be empty; but we must not create a Qualifications heading without real specific content. So we should omit Qualifications section. Skills: maybe we could separate technical skills vs soft skills. But we already have skills in Requirements. Could create a Skills section for proficiency in MS Office, communication, teamwork. But we already have them. However we need to avoid duplication. The instruction: "Prefer a few substantive sections over many thin ones." So we could combine Requirements and Skills into one section maybe "Requirements". But we have both headings allowed; we can choose to include only Requirements and omit Skills if we think it's thin. However we have specific skills like MS Office proficiency, communication, teamwork. Those could be considered Skills. But we could put them under Requirements as well. To avoid thin sections, we could have Requirements (including education, experience, technical knowledge) and Skills (soft skills and software). That would be two substantive sections. Let's decide: - Requirements: Bachelor’s degree in Civil Engineering with focus in Water Resources or related field; Knowledge of floodplain delineation, storm water management, culvert and bridge hydraulics, and drainage design; 0 - 1 year of experience; previous internship(s) preferred; At this time, Dewberry will not sponsor a new applicant for work authorization. - Skills: Strong verbal and written communication skills; Proficiency in MS Office software; Ability to work in a team environment; Don’t meet every single requirement? ... (encouragement) maybe also here. But the encouragement note is not a skill; it's a statement. Could be placed under About the role or maybe under Requirements as a note. Better to include it under Requirements as a note. We also have Benefits: The posting mentions Program Information about entry-level program, professional development events, team building activities, lasting connections, career growth, expand knowledge of Dewberry. That's like benefits/program. So we can create a Benefits section with that content. Pay: Salary range $82,500 - $85,000 annually, may vary slightly. Schedule: Not mentioned. No schedule info. So we omit Schedule. Now we need to output HTML fragment with headings

for each section, and

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

  for prose. We need to decide which content is list vs prose. Responsibilities: list of duties ->

  • each duty. Requirements: could be list of items (education, knowledge, experience, sponsorship note). Use
    • . Skills: list of items (communication, MS Office, teamwork). Use
      • . Benefits: list of program items (entry-level hire class, professional development events, team building activities, lasting connections, career growth understanding, expand knowledge). Could be list. Pay: prose (salary range). Use

        . We also need About the role: prose describing role and maybe company overview. Use

        . We must not repeat job title. Not include Job ID etc. We must remove boilerplate: EEO, background screening, third party recruiters, etc. We must preserve all substantive information. Let's extract exact text for each piece. About the role: "Dewberry is currently seeking an Entry Level Water Resources Engineer to perform water resource work in our Gainesville, VA office. Individual will develop concept and final design of stormwater facilities/treatment, perform floodplain studies, analyze stormwater quality, design stream restoration, dam design, dam retrofit, and perform dam break studies among other projects and tasks. Dewberry is a leading, market-facing professional services firm with more than 60 locations and 2,500 professionals nationwide. What sets us apart from our competitors is our people. At Dewberry, we seek out exceptional talent and strive to deliver the highest quality of services to our clients. Whether you’re an experienced professional or a new graduate, you’ll have the chance to collaborate with the best and brightest and work on innovative and complex projects at the forefront of the industry. Our commitment to excellence stems from our personal integrity and from other defining attributes, which we call “Dewberry at Work,” that have inspired our employees to be successful for more than a half-century." That's a lot; but it's substantive. We'll keep as prose. Responsibilities: list: - develop concept and final design of stormwater facilities/treatment - perform floodplain studies - analyze stormwater quality - design stream restoration - dam design - dam retrofit - perform dam break studies - among other projects and tasks (maybe include as a bullet) We'll include each as

      • . Requirements: list: - Bachelor’s degree in Civil Engineering with a focus in Water Resources or related field is required - Knowledge of floodplain delineation, storm water management, culvert and bridge hydraulics, and drainage design - 0 - 1 year of experience; previous internship(s) preferred - At this time, Dewberry will not sponsor a new applicant for work authorization. - Don’t meet every single requirement? At Dewberry we are dedicated to building a diverse and inclusive workplace for our employees. So if you’re excited about this role, but your past experience doesn’t align perfectly with every qualification in the position description, we encourage you to apply anyways. You may just be the right candidate for this or other opportunities. We could keep the encouragement as a separate
      • or as prose within Requirements. Since it's not a requirement but a note, maybe we put it as a

        after the list. But instruction: Use

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

          for prose. So we can have a list for the concrete requirements, then a

          for the encouragement note. Thus Requirements section:

          • ... (education),
          • ... (knowledge),
          • ... (experience),
          • ... (sponsorship)
          then

          encouragement note. Skills: list: - Strong verbal and written communication skills are required - Proficiency in MS Office software - Ability to work in a team environment We could make each

        • . Benefits: list from Program Information: - As An Entry-level Hire, You’ll Be Part Of a Class Of Peers With 0-1 Year Of Professional Experience. - Our Entry-level Program Comes Together On a Regular Basis For Professional Development Events And Team Building Activities Led By An Advisory Team To Form lasting connections with peers in your class. - Gain a better understanding of career growth and meaningful opportunities to align with your professional goals. - Expand your knowledge of Dewberry and what we do. We'll make each
        • . Pay:

          The projected range for this position is $82,500 - $85,000 annually. Depending upon other factors, i.e., skills, experience, location, market conditions, the range may vary slightly.

          Now we need to output only HTML fragment, no /, no markdown. Let's craft. We'll start with

          About the role