Jobs · Information Technology · Wisconsin

Wastewater Treatment Engineer - Entry Level

SEH · Delafield, WI · 1 mo ago
Information Technology$65k–$75k/yrFull-time
We need to output only HTML fragment, using

for section headings,
  • for lists,

    for prose. No markdown fences. No html/body tags. We need to include sections only when posting has real specific content. Remove boilerplate, navigation, legal, EEO, EEO, etc. Also remove duplicated lines. Keep all substantive info. Let's parse the job posting. First paragraph: "Imagine being an employee-owner of a company guided by engaged and empowered team members like yourself. Where a culture of respect, flexibility, and accountability aren't just ideals - they're our foundation, and diverse backgrounds and perspectives are valued as drivers of innovation and growth. Join us, as together, we are Building a Better World for All of Us®. You belong at SEH SEH is currenting searching for a Wastewater Treatment Engineer - Entry Level to join our talented Water/Wastewater team!" We need to not repeat job title as heading. So we can start with a paragraph describing the company and role. Then there is a section: "Why Our Employee-owners Love SEH" with quotes. That's a section heading: "Why Our Employee-owners Love SEH". Use

    . Then bullet list of quotes? They are separate quotes each preceded by dash and role. Could treat each as
  • inside
      . They are prose but we can list them. Then "Why You’ll Love SEH" with bullet points: Collaborate..., Being 100% employee-owned..., Career development..., Work arrangements..., Flexible holidays..., Paid Family Leave... That's a list. Then "This Opportunity" paragraph describing tasks. Then "Essential Qualifications" list. Then "Preferred Qualifications" list. Then "Who We Are" paragraph. Then "Base compensation is expected to be in the range of $65,000 and $75,000 based on skill set and experience." That's Pay info -> we need a Pay section heading

      Pay

      with that content. Then "Check out our full benefits package at SEH Hiring Journey." That's Benefits info? It mentions benefits package but not details. The rule: never create Benefits section unless posting actually states them. It says "Check out our full benefits package at SEH Hiring Journey." That's not stating benefits, just a reference. So we should not create a Benefits section. Then "Due to current business and operational considerations, unable to hire employees residing in the following states at this time: AK, AR, CA, CT, DE, HI, KY, MA, RI, VT, and PR." That's location restriction; could be part of a paragraph. Then "Candidates willing to relocate should indicate this in their application." That's application instruction? It's about relocation indication; but we are to remove application instructions. The rule: remove application instructions. So we should drop that line. Then "The selected candidate must be authorized to work for any employer in the U.S. without requiring visa sponsorship now or in the future." That's a requirement (work authorization). Could be part of Qualifications? It's a requirement. We'll include in Essential Qualifications maybe as a bullet. Then "SEH is an Equal Opportunity Employer..." that's EEO boilerplate; remove. Then "Notice to Third Party Agencies..." remove. Now we need to decide sections. Potential sections: - About the role? Could use a heading "About the role" but we already have introductory paragraph. Could use

      About the role

      for the paragraph describing the opportunity? However the instruction: use

      for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). So we can use those headings if appropriate. We have content that matches: - About the role: could include the introductory paragraph about employee-owner culture and the role. - Responsibilities: could be the "This Opportunity" paragraph describing tasks. - Requirements / Qualifications: we have Essential Qualifications and Preferred Qualifications. Could combine into Requirements? Or separate Qualifications and Skills? The instruction says we can use Qualifications heading. We'll likely have a Qualifications section with both essential and preferred as lists. - Skills: maybe not separate; we could embed skills within qualifications. - Pay: we have compensation range. - Schedule: not mentioned. - Benefits: not detailed enough. Thus we will output sections: About the role, Responsibilities, Qualifications, Pay. We need to ensure we don't create empty sections. Let's craft. About the role: combine the initial imaginative paragraph and the "You belong at SEH..." plus maybe the "Why Our Employee-owners Love SEH" quotes? Actually those quotes are more about culture; could be part of About the role or separate section "Why Our Employee-owners Love SEH". But we have limited headings list; we could still use a custom heading? The instruction says use

      for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). It doesn't forbid other headings, but says use

      for section headings (e.g. those). It might be okay to use other headings as long as they are

      . Safer to stick to those examples. However we can still use About the role to encompass culture and quotes. Thus About the role

      About the role

      then a

      containing the imaginative paragraph, the "You belong at SEH..." sentence, and maybe the quotes as a

      • ... . But we need to preserve all substantive information; we can include quotes as list items. Responsibilities

        Responsibilities

        then a

        with the "This Opportunity" paragraph describing tasks. Qualifications

        Qualifications

        then we need to list Essential Qualifications and Preferred Qualifications. Could use two
          lists with headings? But we cannot add extra headings besides

          . Could embed subheadings as or just plain text inside

          before list. Probably okay to have a

          "Essential Qualifications:" then

            ..., then another

            "Preferred Qualifications:" then

              ... . That preserves info. Pay

              Pay

              then

              with compensation range. We also need to include location restriction (states unable to hire) and work authorization requirement. Where to put? Could be part of Qualifications as additional bullet points. Or maybe a separate section "Requirements"? But we already have Qualifications. We'll add them as bullet points under Essential Qualifications maybe. Also note: "Candidates willing to relocate should indicate this in their application." Remove as application instruction. Now check for duplicated lines: The phrase "Experience in the design and construction of municipal, state, federal, or industrial wastewater treatment projects" appears both in Essential Qualifications and Preferred Qualifications (they are same). We should not duplicate? The instruction: Preserve ALL substantive information; do NOT invent or summarize away detail. Duplicate lines are present in source; we should keep them? It says remove duplicated lines. So we should remove duplicate lines. So we need to deduplicate that line. Keep it once maybe under Essential Qualifications; Preferred Qualifications could be empty? But Preferred Qualifications currently only has that line (duplicate). If we remove duplicate, Preferred Qualifications would have no content; then we should not emit a Preferred Qualifications heading if it ends up empty. So we can omit Preferred Qualifications section entirely, or we could keep it but note that it's same as essential; but to avoid duplication we should not repeat. So we will not include Preferred Qualifications as a separate list; we can mention that there are no additional preferred qualifications beyond essentials. Thus Qualifications section will have Essential Qualifications list (including work authorization and location restriction maybe). We'll also include "Previous engineering internship experience; Wastewater specific highly preferred" as a bullet. Now let's craft the HTML. We need to ensure no or . Just fragment. Let's write:

              About the role

              Imagine being an employee-owner of a company guided by engaged and empowered team members like yourself. Where a culture of respect, flexibility, and accountability aren't just ideals - they're our foundation, and diverse backgrounds and perspectives are valued as drivers of innovation and growth. Join us, as together, we are Building a Better World for All of Us®. You belong at SEH SEH is currently searching for a Wastewater Treatment Engineer - Entry Level to join our talented Water/Wastewater team!

              • “I was on vacation last week and had zero concerns that my colleagues would help out with anything that came into my inbox!” – GIS Analyst
              • “What company has a CEO who cares enough to seek out one-on-one conversations ranging from ‘How are you?’ to ‘What do you think would help the company?’ SEH, that's who.” – Civil Engineering Technician
              • “Having the feeling that my voice matters and believing that SEH truly cares about the employees is so satisfying!” – Sr Financial Analyst
              • “It feels good having colleagues and supervisors that provide support and resources for growth and learning!” – Civil Engineer
              • “This is the first company I've worked for with a true entrepreneurial spirit.” – Sr Mechanical Engineer

              Responsibilities

              Join our wastewater infrastructure team to support the planning, design, and construction of a variety of wastewater treatment projects. Develop creative solutions to complex wastewater treatment and conveyance challenges, working closely with our team of engineers, designers and other professionals. Collaborate with multi-discipline teams to deliver innovative project solutions. Build and strengthen client relationships in collaboration with experienced project managers.

              Qualifications

              Essential Qualifications:

              • Bachelor's degree in civil or environmental engineering, or a related field
              • Experience in the design and construction of municipal, state, federal, or industrial wastewater treatment projects
              • Basic knowledge of wastewater treatment systems, equipment, and regulations
              • Previous engineering internship experience; Wastewater specific highly preferred
              • Strong interest and classes related to Wastewater/Water Treatment
              • Authorized to work for any employer in the U.S. without requiring visa sponsorship now or in the future
              • Unable to hire employees residing in the following states at this time: AK, AR, CA, CT, DE, HI, KY, MA, RI, VT, and PR

              Pay

              Base compensation is expected to be in the range of $65,000 and $75,000 based on skill set and experience.

              We removed Benefits section, Schedule, etc. Check for any leftover boilerplate: removed EEO, third party notice, etc. Check for any duplicated lines: we removed duplicate experience line. Check for any placeholder like "commensurate with experience" - not present. Check for any "not specified" - none. Check for any "varies" - none. Check for any "TBD" - none. Check for any "N/A" - none. Check for any application instructions: we removed "Candidates willing to relocate should indicate this in their application." Good. Check for any navigation/cookie/legal: removed. Now ensure we didn't miss any substantive info: The "Why You’ll Love SEH" bullet points: we omitted them! That's substantive. We need to include them somewhere. They are benefits/culture points. Could be placed under About the role as a list, or we could create a separate section "Why You’ll Love SEH" but we don't have a heading for that; we could incorporate them into About the role as a list after the quotes. Let's add them. We have already a list of quotes under About the role. We can add another list for "Why You’ll Love SEH". Or we can merge them into one list but better to keep separate with a heading

Similar jobs