ENVIRONMENTAL ENGINEER II

We need to output HTML fragment with sections: headings

for sections like About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. Only include sections that have real specific content. We must not repeat job title. Remove boilerplate, navigation, EEO, etc. Must preserve all substantive info. We need to parse the posting. Key info: - Position: Environmental Engineer II? Actually posting says "Environmental Engineer II position" in Conditions of Employment. Title maybe Environmental Engineer II. - Under general supervision, performs a broad range of engineering duties requiring the application of public health, environmental and civil engineering principles, practices, and theories; and performs related work as required. - This is an Open Competitive/Countywide Promotional recruitment being conducted to fill a current full-time vacancy in the Washoe County Sheriff’s Office. - The list established from this recruitment may be used to fill future vacancies throughout the County as they occur. - This position is in a flexibly staffed class series. The hiring department has the discretion to hire at any level within the class series for which the applicant may be qualified. Applicants interested in being considered for each level within the series must submit an application for each position. - For more information on this position, please see the Job Specification at https://www.washoecounty.gov/humanresources/Careers/jobspecs.php - Minimum Qualifications: One year of professional engineering experience in the applicable area of assignment: environmental, public health, public works AND a bachelor’s degree from an accredited college or university in civil engineering, hydrology, sanitary engineering, environmental engineering or a closely related field; OR an equivalent combination of education and experience. - License Or Certificate: A valid driver's license is required at the time of appointment and must be maintained for continued employment in this classification. - The Ideal Candidate Will Possess: list of bullet points (strong analytical and problem-solving skills... etc). That's a list of desired skills/qualities. - Conditions of Employment: WCEA Non-Supervisory CBA covers the position. Background checks will be conducted... etc. Also residency requirement: Must reside in Nevada or neighboring California communities (Truckee, South Lake Tahoe, Susanville) as of first day of work. Salary info: Washoe County hires all new employees at the minimum rate of the salary range and eligible employees may receive an annual merit increase of 5% until they reach the maximum salary for the classification. Upon promotion, current Washoe County employees are placed at the minimum rate of the salary range for the higher classification of the new position OR a promotional calculation, whichever is greater. - Also mention Total Compensation Package link: "Please click here for the Total Compensation Package for this job classification which includes county paid employee health benefits after 30 days of employment, county paid retirement benefits, vacation accruals, etc. The Total Compensation Package outlines the various benefits offered by Washoe County and the annual earnings based on the entry level salary for the job classification." Thus we have Benefits info: county paid employee health benefits after 30 days, county paid retirement benefits, vacation accruals, etc. Also maybe other benefits not detailed. Pay: Not specific numbers, but mention that new employees hired at minimum rate of salary range, eligible for annual merit increase of 5% until max. That's pay info but not specific numbers. The rule: do NOT include Pay section unless posting actually states them. It does state something about pay: "Washoe County hires all new employees at the minimum rate of the salary range and eligible employees may receive an annual merit increase of 5% until they reach the maximum salary for the classification." That's pay info (though not numeric). Should we include Pay section? The instruction: "never create Pay/Schedule/Benefits sections unless the posting actually states them." It does state something about pay (minimum rate, merit increase). So we can include Pay section with that info. Schedule: Not mentioned. No schedule info. So omit Schedule. Benefits: we have info about health benefits after 30 days, retirement benefits, vacation accruals, plus link to Total Compensation Package. So we can include Benefits section. Now sections: About the role (maybe from first paragraph). Responsibilities (duties). Requirements (minimum qualifications). Qualifications (maybe ideal candidate?). Skills (maybe from ideal candidate list). Benefits. Pay. We need to avoid duplication. Let's extract. About the role: Could be the description: "Under general supervision, performs a broad range of engineering duties requiring the application of public health, environmental and civil engineering principles, practices, and theories; and performs related work as required. This is an Open Competitive/Countywide Promotional recruitment being conducted to fill a current full-time vacancy in the Washoe County Sheriff’s Office. The list established from this recruitment may be used to fill future vacancies throughout the County as they occur. This position is in a flexibly staffed class series. The hiring department has the discretion to hire at any level within the class series for which the applicant may be qualified. Applicants interested in being considered for each level within the series must submit an application for each position. For more information on this position, please see the Job Specification at https://www.washoecounty.gov/humanresources/Careers/jobspecs.php" That seems appropriate for About the role. Responsibilities: Could be the bullet list of duties? The posting didn't have explicit bullet list of duties besides the general description. Could treat the same as About role? Might be thin. But we need to include only if real specific content. The posting does not list specific duties beyond that. Could we still include Responsibilities with that same description? Might duplicate. Better to not include Responsibilities if it's just same as About. However we need to capture the engineering duties: "performs a broad range of engineering duties requiring the application of public health, environmental and civil engineering principles, practices, and theories; and performs related work as required." That's a responsibility. Could put that as a

under Responsibilities. Requirements: Minimum Qualifications and License/Certificate. Qualifications: maybe the Ideal Candidate Will Possess list (these are desired qualifications/skills). Could treat as Qualifications or Skills. The instruction: Use headings for Requirements, Qualifications, Skills. We need to decide. We have Minimum Qualifications (requirements). Then Ideal Candidate Will Possess (skills/qualities). Could split: Requirements = Minimum Qualifications + License. Qualifications = Ideal Candidate list (maybe also includes experience/education? but that's already in Requirements). Skills = maybe the same list? Might be redundant. Better to have Requirements (minimum quals + license) and Skills (ideal candidate attributes). Qualifications maybe not needed. But we need to follow instruction: "Use

for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." It's just examples; we can choose which to include. We should include About the role, Responsibilities, Requirements, Skills, Benefits, Pay. Let's craft. Responsibilities: list of duties: maybe bullet list: "Perform engineering duties applying public health, environmental, and civil engineering principles, practices, and theories; perform related work as required." Could also include field work: collecting water quality samples, analyzing monitoring data, using field observations to support engineering evaluations and regulatory compliance (from ideal candidate). But that's more skill. We'll keep responsibilities simple. Requirements: Minimum Qualifications + License. We'll format as

• for each. Minimum Qualifications: "One year of professional engineering experience in the applicable area of assignment: environmental, public health, public works AND a bachelor’s degree from an accredited college or university in civil engineering, hydrology, sanitary engineering, environmental engineering or a closely related field; OR an equivalent combination of education and experience." License: "A valid driver's license is required at the time of appointment and must be maintained for continued employment in this classification." Skills: Ideal Candidate Will Possess list (multiple bullet points). We'll extract each sentence. List: - strong analytical and problem-solving skills with the ability to evaluate technical data, perform engineering calculations, and develop practical, effective solutions to environmental engineering challenges. - ability to interpret engineering plans, technical reports, regulations, and environmental standards. - comfortable performing field work, including collecting water quality and environmental samples, analyzing monitoring data, and using field observations to support engineering evaluations and regulatory compliance. - excellent written and verbal communication skills, with the ability to clearly explain technical information to coworkers, developers, consultants, regulatory agencies, and the public. - organized, detail-oriented, and able to manage multiple projects and priorities while producing accurate, high-quality work and meeting established deadlines. - enjoy working both in the office and in the field, adapting to a variety of engineering assignments, water quality sampling, site inspections and project needs. - strong commitment to environmental stewardship, public health, regulatory compliance, and the delivery of exceptional public service. - work collaboratively with multidisciplinary teams and external stakeholders to achieve practical, timely and effective project outcomes while fostering positive working relationships. - embrace public service while seeking innovative, practical solutions to complex environmental engineering challenges. We'll put each as
• . Benefits: mention county paid employee health benefits after 30 days, county paid retirement benefits, vacation accruals, etc. Also link to Total Compensation Package. We'll include as
  • . Pay: mention that Washoe County hires all new employees at the minimum rate of the salary range and eligible employees may receive an annual merit increase of 5% until they reach the maximum salary for the classification. Also upon promotion, current employees placed at minimum rate of salary range for higher classification OR promotional calculation whichever greater. We'll include that. Now ensure we don't include boilerplate like EEO, Veteran points, application process, etc. Remove all that. We must preserve all substantive information; we are removing a lot of procedural details (application process, exam details, background check details, residency requirement? Wait residency requirement is substantive: "Washoe County requires its employees to reside in the state of Nevada or neighboring California communities such as Truckee, South Lake Tahoe or Susanville as of their first day of work." That's a condition of employment; should we include? It's not in the headings list but could be part of Requirements or maybe a separate section like "Conditions". But we only have headings list; we could include it under Requirements as an additional bullet. It's a requirement (residency). So include in Requirements. Also background check info: maybe not needed as it's procedural but still substantive? It's about conditions of employment. Could be included under Requirements? But it's more about hiring process. The instruction: remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. Background check info is not exactly boilerplate; it's a condition. Might be considered part of Conditions of Employment. Could be included under Requirements or a separate section like "Conditions". Since we don't have a heading for Conditions, we could add it under Requirements as a bullet. However the instruction says to prefer a few substantive sections over many thin ones. Adding many bullets under Requirements is fine. We need to decide what to keep. The posting includes a lot of details about background check, fingerprint fee, residency, etc. Those are substantive. We should preserve them. So we should include them somewhere. We could add a section "Conditions of Employment" but not in the list. The instruction says use headings e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. It doesn't forbid other headings? It says "use

    for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." The e.g. suggests those are examples but we could still use other headings? Safer to stick to those. We can incorporate conditions into Requirements or maybe Benefits? Residency is not benefit. Could be under Requirements as a requirement: "Must reside in Nevada or neighboring California communities (Truckee, South Lake Tahoe, Susanville) as of first day of work." Background check: Could be under Requirements as well: "Must pass a state and federal background check (f