Municipal Stormwater Permit Assistance Specialist

We need to output HTML fragment with sections: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule as appropriate. Use

for headings. Use

• for any list of duties/requirements/benefits. Use

  for prose. Do NOT repeat job title as heading. Do NOT put Job ID/requisition numbers as headings. Remove boilerplate: cookie/navigation/legal/EEO/equal-opportunity/scam-warning, duplicated lines, application instructions. Preserve all substantive info. Include a section only when posting has real specific content. Avoid filler like "commensurate with experience". Pay section only if posting actually states them. The posting includes Monthly Salary: $4,059.92 - $4,940.13 | Commensurate with experience and qualifications. That's a salary range but also says commensurate with experience. The instruction: never emit a heading followed by filler/placeholder text (e.g., "commensurate with experience", "not specified", "N/A", "varies", "TBD") and never create Pay/Schedule/Benefits sections unless the posting actually states them. So we can include Pay section with the salary range, but we must avoid filler like "commensurate with experience". The posting includes both range and "Commensurate with experience and qualifications". We could include just the range and maybe note that it's based on experience. But the phrase "commensurate with experience" is filler; we should avoid that phrase. We could output the range and maybe not include the phrase. The instruction: never emit a heading followed by filler/placeholder text (e.g., "commensurate with experience", ...). So if we include Pay section, we must not have that phrase. We could just put the salary range. That's substantive. So Pay section:

  Pay

  $4,059.92 - $4,940.13 per month

  . That avoids filler. Schedule: The posting mentions full time (100% FTE), temporary position, overtime eligible, temporary end date renewed annually. It doesn't give specific schedule like hours per week. It says full time. That's schedule info. Should we include Schedule section? The posting states "This is a full time (100% FTE), temporary position." That's schedule info (full-time). So we can include Schedule:

  Schedule

  Full-time (100% FTE), temporary position renewed annually.

  . That's substantive, not filler. Benefits: The posting lists benefits: paid sick and vacation leave; paid holidays; medical, dental, life and disability insurance; retirement; deferred compensation; optional supplemental retirement accounts; training and development; employee tuition waiver. That's substantive. So Benefits section. About the role: The Opportunity paragraph describes role. Could be About the role. Responsibilities: The Percentage Breakdown of Job Functions gives percentages: 40% Program Implementation, 30% Communication Internal/External, 25% Coordinate in-person and online Training/Workshops/Events, 5% Other duties as assigned. That's responsibilities. Requirements: The Required Qualifications list bullet-like sentences. Could be Requirements. Qualifications: Preferred Qualifications list. Skills: Could be derived from Required Qualifications: demonstrated skill in effective communication, ability to work with diverse group, etc. But we already have Requirements and Qualifications sections; Skills may be redundant. The instruction: prefer a few substantive sections over many thin ones. We could combine Requirements and Qualifications into one? But they ask to use headings for those specific headings if content exists. We have content for Required Qualifications and Preferred Qualifications. Could make Requirements section for required, and Qualifications section for preferred. Skills maybe not needed if covered. But we could still include Skills if we have distinct skill statements not captured elsewhere. The Required Qualifications includes: Demonstrated experience working with stormwater-related groups..., Experience working with the Western Washington or Eastern Phase II stormwater permit(s) requirements., Must have valid driver's license..., Demonstrated skill in effective communication..., Act as a liaison..., Ability to work with diverse group..., Willingness to develop understanding of SWMMEW and SWMMWW. Those are skills/experience. Preferred Qualifications includes familiarity with research topics, experience writing grant proposals, experience developing surveys, experience creating outreach materials, knowledge of other NPDES permits. Those could be considered Skills or Qualifications. To avoid thin sections, we could merge Required and Preferred into Requirements and Qualifications as per headings. Let's follow the instruction: Use headings for About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We'll include those that have substantive content. We have: - About the role: The Opportunity paragraph. - Responsibilities: Percentage Breakdown. - Requirements: Required Qualifications. - Qualifications: Preferred Qualifications. - Skills: Could we extract skill statements not already in Requirements? The Required Qualifications already includes skill statements. Might be redundant. But we could still include Skills if we have distinct skill statements like "Demonstrated skill in effective communication (written and oral)", "Ability to work with a diverse group", etc. However those are already in Requirements. To avoid thin sections, maybe we omit Skills section. The instruction: prefer a few substantive sections over many thin ones. So we can omit Skills if it would be thin. We'll include only About the role, Responsibilities, Requirements, Qualifications, Benefits, Pay, Schedule. Check if any other sections like "Schedule" we have. Now we need to remove boilerplate: application instructions, EEO, etc. Also remove lines like "Online applications must be received before 11:59pm on: September 27, 2026". That's application instruction; remove. Also "If a date is not listed above, review the Applicant Instructions below for more details." Remove. Also "Available Title(s) 1132-YN_ADMINPRO - Extension Coordinator Business Title Municipal Stormwater Permit Assistance Specialist Employee Type Admin. Professional (+) (Fixed Term) Position Details". The job title and ID should not be heading; we can incorporate minor metadata into a short

  or drop it. The instruction: do NOT put Job ID / requisition numbers as headings — fold minor metadata into a short

  or drop it. So we could include a short paragraph with the position details like Employee Type, etc. But maybe we can drop it as not essential? The instruction says preserve ALL substantive information; do NOT invent or summarize away detail. The position details like Employee Type Admin. Professional (+) (Fixed Term) is substantive. Should we keep it? It's metadata about the position. Could be placed in a short

  after the heading? But we cannot use headings for it. We could include a

  with that info. However we already have About the role section; we could incorporate that info there? The About the role currently is just the Opportunity paragraph. We could add a short paragraph after the heading with the position details (Employee Type, etc.) but that might be considered metadata. The instruction: fold minor metadata into a short

  or drop it. So we can add a

  after the About the role heading (or before) containing the position details: Employee Type Admin. Professional (+) (Fixed Term), Location: Puyallup, WA. Remote/hybrid options available within Western Washington. Also maybe Position Sponsorship Eligibility: Not eligible for work visa sponsorship. That's also metadata. We could include that in a short

  . However we need to avoid duplication. The posting also includes Area/College, Department Name, Location. Those are metadata. We'll include them in a short

  under About the role or maybe as a separate

  without heading. Since we cannot use headings for them, we just put them in a paragraph. We must not include application instructions, background check, EEO, etc. Now let's extract substantive content: About the role: The Opportunity paragraph: "As the Municipal Stormwater Permit Assistance Specialist, you will support the Washington Stormwater Center’s (WSC) municipal technical assistance program by helping build capacity and providing technical assistance to Washington Phase II Permittees, with a particular focus on Eastern Washington jurisdictions. In this role, you will assist permittees in meeting the requirements of their Municipal Separate Stormwater Sewer (MS4) Permits. You will work remotely as part of the Washington Stormwater Center, which is based at the Puyallup Research and Extension Center, while maintaining strong partnerships with communities across the state. This position includes travel to permitted jurisdictions in Eastern Washington and may also require trips to the WSC offices in Puyallup." We could also include the position details: Employee Type Admin. Professional (+) (Fixed Term), Location: Puyallup, WA. Remote/hybrid options available within Western Washington. Position Sponsorship Eligibility: Not eligible for work visa sponsorship. Area/College: College of Agricultural, Human and Natural Resource Sciences (CAHNRS). Department Name: Washington Stormwater Center. We'll put those in a

  after the opportunity paragraph maybe. Responsibilities: The Percentage Breakdown: 40% Program Implementation, 30% Communication Internal/External, 25% Coordinate in-person and online Training/Workshops/Events, 5% Other duties as assigned. We'll make a

  • list. Requirements: Required Qualifications: list of statements. We'll make a
    • list. Qualifications: Preferred Qualifications: list. Benefits: list. Pay: salary range. Schedule: full-time temporary. Now ensure we don't include filler like "Commensurate with experience and qualifications". We'll omit that phrase. Now produce HTML fragment. We need to output only HTML, no markdown fences. Let's craft:

      About the role

      As the Municipal Stormwater Permit Assistance Specialist, you will support the Washington Stormwater Center’s (WSC) municipal technical assistance program by helping build capacity and providing technical assistance to Washington Phase II Permittees, with a particular focus on Eastern Washington jurisdictions. In this role, you will assist permittees in meeting the requirements of their Municipal Separate Stormwater Sewer (MS4) Permits. You will work remotely as part of the Washington Stormwater Center, which is based at the Puyallup Research and Extension Center, while maintaining strong partnerships with communities across the state. This position includes travel to permitted jurisdictions in Eastern Washington and may also require trips to the WSC offices in Puyallup.

      Employee Type: Admin. Professional (+) (Fixed Term). Location: Puyallup, WA. Remote/hybrid options available within Western Washington. Position Sponsorship Eligibility: Not eligible for work visa sponsorship. Area/College: College of Agricultural, Human and Natural Resource Sciences (CAHNRS). Department: Washington Stormwater Center.

      Responsibilities

      • 40% Program Implementation
      • 30% Communication Internal/External
      • 25% Coordinate in-person and online Training/Workshops/Events
      • 5% Other duties as assigned

      Requirements

      • A Bachelor’s degree in a relevant extension program discipline and two (2) years of related program experience. Any combination of relevant education and experience may be substituted for the educational requirement on a year-for-year basis.
      • Demonstrated experience working with stormwater-related groups: federal, state, private, tribal, non-governmental organization (NGO), and academic stakeholders, or similar experience working with diverse groups of stakeholders.
      • Experience working with the Western Washington or Eastern Phase II stormwater permit(s) requirements.
      • Must have, or be able to obtain by time of hire, a valid driver’s license and meet requirements in accordance with SPPM 7.10 and departmental driving standards.
      • Demonstrated skill in effective communication (written and oral) in a variety of styles for different types of audiences.