Early Career Process Engineer

We need to produce HTML fragment with headings

for 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 as heading. Must not include Job ID etc. Remove boilerplate. Must preserve all substantive info. We need to parse the posting. Overview: "Do you want to build an impactful career to change the world for the better? Geosyntec has an exciting opportunity for an Early Career Process Engineer to join our Water Process Engineering and Infrastructure Service Line in our Pittsburgh, PA, Atlanta, GA, or Phoenix, AZ office locations. This role will apply academic knowledge and practical experience to real-world consulting projects related to process engineering, water and wastewater treatment (including municipal and industrial), stormwater management and treatment, and groundwater management/treatment for a diverse national private and public sector client base. The position is ideal for an early-career engineer interested in developing strong technical capabilities while learning the business, communication, and project delivery skills needed for a successful consulting career. Geosyntec is an innovative, international engineering and consulting firm serving private and public-sector clients to address new ventures and complex problems involving our environment, natural resources, and civil infrastructure. Our engineers, scientists, technical and project employees serve our clients from offices across the world. Ranked by ENR as one of the top environmental engineering design firms, Geosyntec is internationally known for its technical leadership, broad experience, and exceptional client service. We invest in our people. Each employee is unique, and your career at Geosyntec will be too. We offer competitive pay and benefits, and well-being programs to support you and your family. To Learn More Visit: http://www.geosyntec.com/careers/ ." We need to remove application instructions (To Learn More Visit...). Also remove boilerplate like EEO etc (none). Keep substantive info: description of role, location, etc. Could be placed under "About the role" heading. Essential Duties And Responsibilities: list of duties. We'll put under

Responsibilities

with

• each duty. Education and Licensure: includes required and preferred. Could be under Requirements or Qualifications. We need to decide sections: maybe "Requirements" for required items, "Qualifications" for preferred? Or "Education and Licensure" could be under Requirements. The instruction says use headings like About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. So we need to map content accordingly. We have: - Overview description: could be About the role. - Responsibilities: Essential Duties And Responsibilities. - Education and Licensure: includes required Bachelor's degree, preferred advanced degree, preferred experience, preferred EI/EIT. Could go under Requirements (required) and Qualifications (preferred). But we have both Requirements and Qualifications headings available. We'll put required items under Requirements, preferred under Qualifications. - Skills, Experience And Qualifications: includes many items: preferred experience, required foundational understanding, preferred experience/coursework, required interest, preferred ability to use tools, preferred experience preparing drawings, required strong technical writing etc, required ability to manage multiple assignments, required willingness to perform fieldwork, required Health & Safety training etc, required Valid US driver's license. This section mixes required and preferred. We'll need to split: required items go to Requirements (if not already there) or maybe Skills? But we have Skills heading. The instruction says use Skills heading for skills. So we could put skill-related items under Skills. However we also have Requirements and Qualifications. Let's think: The posting has "Skills, Experience And Qualifications" heading. We could treat that as Skills section. But we also have Education and Licensure separate. We could map: - About the role: overview paragraph. - Responsibilities: Essential Duties And Responsibilities. - Requirements: required items from Education and Licensure (Bachelor's degree required) plus required items from Skills, Experience And Qualifications (foundational understanding, interest, strong technical writing/communication/collaboration, ability to manage multiple assignments, willingness to perform fieldwork, health & safety training, valid US driver's license). Also maybe "Ability to organize, evaluate, and communicate technical data using tools..." is preferred, not required. So not in Requirements. - Qualifications: preferred items from Education and Licensure (advanced degree, academic/internship/co-op/research/practical project experience, EI/EIT certification) plus preferred items from Skills, Experience And Qualifications (experience in process engineering etc, experience/coursework involving treatment technologies, ability to use tools, experience preparing drawings, etc). Also maybe "Experience preparing or supporting engineering drawings..." is preferred. - Skills: maybe we could put the skill-based required items? But we already placed required technical writing etc under Requirements. However we could also have a Skills section for skill-based items (both required and preferred). But we have limited headings; we could combine skill items under Skills, and keep Requirements for education/licensure required, Qualifications for preferred education/licensure. But the instruction says we can choose which sections to include based on real content. We need to avoid thin sections. Let's see what content we have for each potential section: About the role: we have overview paragraph (substantive). Good. Responsibilities: we have a list of duties (substantive). Good. Requirements: we have required items: Bachelor's degree required; foundational understanding required; interest required; strong technical writing, communication, collaboration required; ability to manage multiple assignments required; willingness to perform fieldwork required; health & safety training required; valid US driver's license required. That's a decent list. Qualifications: we have preferred items: advanced degree preferred; academic/internship/co-op/research/practical project experience preferred; EI/EIT certification preferred; experience in process engineering etc preferred; experience/coursework involving treatment technologies etc preferred; ability to use tools (Excel, GIS, AutoCAD, etc) preferred; experience preparing drawings etc preferred. That's also substantive. Skills: we could list skill-based items: ability to organize, evaluate, communicate technical data using tools (preferred); strong technical writing etc (required but we already placed under Requirements). However we could still have a Skills section for both required and preferred skill items, but then we'd duplicate. Better to not duplicate. Perhaps we can put skill-based items under Skills, and move required technical writing etc there, and not duplicate under Requirements. But then Requirements would lose some required items. However we could keep Requirements focused on education/licensure and maybe other non-skill requirements like willingness to travel, driver's license, health & safety. Let's examine. The posting's "Skills, Experience And Qualifications" includes both skill and experience items. It might be appropriate to treat that as Skills section. Then we could have Requirements for education/licensure (Bachelor's degree required) and maybe other mandatory items like driver's license, health & safety, willingness to travel, ability to manage multiple assignments (these are more like requirements). Qualifications for preferred education/experience. Thus: - About the role: overview. - Responsibilities: duties. - Requirements: Bachelor's degree required; valid US driver's license required; satisfactory driving record; health & safety training, medical monitoring, client-driven drug and background testing may be required; willingness to perform fieldwork (including site inspections, sampling, monitoring, pilot testing support, construction observation, equipment checks, occasional overnight travel) required; ability to manage multiple assignments, meet deadlines, ask thoughtful technical questions, follow quality procedures, contribute to high-quality consulting deliverables required. Also maybe "foundational understanding of process engineering principles..." is required but that's more skill/knowledge; but we could put under Skills. However it's a foundational understanding, could be considered a qualification. But we have Qualifications for preferred; maybe we put foundational understanding under Requirements as it's required. Let's decide. - Qualifications: preferred items: advanced degree; academic/internship/co-op/research/practical project experience; EI/EIT certification; experience in process engineering, water treatment, wastewater treatment, environmental engineering, civil infrastructure, groundwater management, stormwater treatment, or related consulting work; foundational understanding of process engineering principles... (but that's required actually). Hmm. Better to follow the posting's own categorization: Education and Licensure (required Bachelor's, preferred advanced degree, preferred experience, preferred EI/EIT). Skills, Experience And Qualifications (preferred experience, required foundational understanding, preferred experience/coursework, required interest, preferred ability to use tools, preferred experience preparing drawings, required strong technical writing etc, required ability to manage multiple assignments, required willingness to perform fieldwork, required health & safety, required driver's license). This is messy. Given the instruction to prefer a few substantive sections over many thin ones, we could combine Requirements and Qualifications into one section? But we have headings defined; we can choose to include only those with real content. We could include About the role, Responsibilities, Requirements (combining required education/licensure and other mandatory items), Qualifications (preferred education/experience/skills), and Skills (maybe we can omit if overlapping). But we need to avoid duplication. Let's think: The posting's "Skills, Experience And Qualifications" includes both skill and experience items, many of which are required or preferred. We could treat that as Skills section, and put all items there (both required and preferred). Then we could have Requirements only for education/licensure (Bachelor's degree required) and maybe driver's license etc? But driver's license is also in that section. However we could move driver's license to Requirements as it's a requirement. But then Skills would still have many items. Alternatively, we could have: - About the role - Responsibilities - Requirements (education/licensure + mandatory items like driver's license, health & safety, willingness to travel, ability to manage multiple assignments) - Qualifications (preferred education/experience/certifications) - Skills (technical skills: foundational understanding, ability to use tools, technical writing, etc.) But that may be many sections; but each would have substantive content. We need to avoid thin sections like Pay, Schedule, Benefits unless mentioned. Benefits: posting mentions "We offer competitive pay and benefits, and well-being programs to support you and your family." That's a statement about benefits and pay. It mentions competitive pay and benefits, well-being programs. That's substantive enough for Benefits and Pay sections? The instruction says: never create Pay/Schedule/Benefits sections unless the posting actually states them. It does state competitive pay and benefits, and well-being programs. So we can include Benefits and Pay sections. However we need to avoid filler like "commensurate with experience". The posting says "competitive pay and benefits, and well-being programs". That's not filler; it's specific enough? It's somewhat generic but it's stated. We'll include them. Schedule: not mentioned. So omit Schedule. Thus we will have sections: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay. Now we need to fill each with appropriate content, using
  • for lists,

    for prose. We must not repeat job title as heading. Not include Job ID etc. We must preserve ALL substantive information; do not invent or summarize away detail. So we need to include all details from the posting, but we can reorganize. Let's extract all substantive sentences/bullets. Overview paragraph: - "Do you want to build an impactful career to change the world for the better?" - "Geosyntec has an exciting opportunity for an Early Career Process Engineer to join our Water Process Engineering and Infrastructure Service Line in our Pittsburgh, PA, Atlanta, GA, or Phoenix, AZ office locations." - "This role will apply academic knowledge and practical experience to real-world consulting projects related to process engineering, water and wastewater treatment (including municipal and industrial), stormwater management and treatment, and groundwater management/treatment for a diverse national private and public sector client base." - "The position is ideal for an early-career engineer interested in developing strong technical capabilities while learning the business, communication, and project delivery skills needed for a successful consulting career." - "Geosyntec