SPECIAL EDUCATION TEACHER - RESOURCE SPLIT (0.5 MEEKER/ 0.5 KARSHNER)

We need to output HTML fragment with sections for headings where there is content. The posting includes: - Location: Meeker Elementary & Karshner Elementary - Position: Special Education Teacher - Resource - FTE: 1.0 SPLIT (0.5 MEEKER/ 0.5 KARSHNER) - Rate: See Salary Schedule - Calendar: 180-Day - Description: RESOURCE = provides in-class or pull-out services to students with identified needs in all building locations. - Internal Candidates: ... (some text) - External Candidates: ... (some text) - To expedite processing, provide a minimum of 3 professional references... - Proof of Qualification: Candidates must hold or be able to obtain a teaching certificate with OSPI, including the appropriate endorsement. - Benefits And Wages: Refer to the Certificated Staff, Non-Supervisory Employees (PEA)-WEA agreements, salary schedules, calendars, and benefits here. - Additional Information For External Candidates: ... (some text) - For questions, please contact the Human Resources Department at personnel@puyallupsd.org We need to remove boilerplate: cookie/navigation/legal/EEO/equal-opportunity/scam-warning, duplicated lines, application instructions? The instructions say: "Remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions." So we should remove application instructions like "To expedite processing, provide a minimum of 3 professional references..."? That is an application instruction. Also "Proof of Qualification" maybe considered requirement? It's a qualification requirement, not instruction. But "To expedite processing..." is definitely an instruction, should be removed. Also "Internal Candidates Current PEA employees..." is internal candidate info, maybe keep as part of description? It's not boilerplate. "External Candidates (Including current PSD Substitutes and NON-Continuing PEA contracts) Apply to this vacancy through the Frontline applicant system." That's application instruction, should be removed. Also "For questions, please contact the Human Resources Department at personnel@puyallupsd.org" is contact info, maybe keep? It's not boilerplate but could be considered contact. The instruction says remove application instructions, but contact info maybe okay. However they said "Remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions." So contact info is not an instruction, it's just contact. Might keep. We need to preserve all substantive information. So we need to include location, position, FTE split, rate (see salary schedule), calendar (180-Day), description of role, internal candidates info, external candidates info? Actually external candidates instruction to apply via Frontline is application instruction, remove. But we might keep the note about external candidates eligibility? The line: "External Candidates (Including current PSD Substitutes and NON-Continuing PEA contracts) Apply to this vacancy through the Frontline applicant system." The substantive part is that external candidates including PSD substitutes and non-continuing PEA contracts can apply. That's info about eligibility. The instruction to apply via Frontline is application instruction, we can drop that phrase but keep the eligibility. So we could rephrase: "External Candidates (Including current PSD Substitutes and NON-Continuing PEA contracts) may apply." But we must not invent or summarize away detail. We can keep the eligibility part and drop the instruction phrase. However we must not change meaning drastically. Could keep the sentence but remove the instruction clause? Might be considered editing. Safer to keep the whole sentence? But it's an application instruction. The instruction says remove application instructions. So we should remove that sentence entirely? But then we lose info about external candidates eligibility. However the eligibility is also mentioned in internal candidates line. Might be okay to drop because it's not crucial? But we should preserve substantive information. The eligibility is substantive. Could we keep a shortened version: "External Candidates (Including current PSD Substitutes and NON-Continuing PEA contracts) may apply." That's still substantive and not an instruction. It removes the "Apply to this vacancy through the Frontline applicant system." which is instruction. That seems acceptable. Similarly, "Internal Candidates Current PEA employees with a Continuing or Provisional contract may bid internally by following this link." That's internal candidate info plus instruction to follow link. We could keep the eligibility part and drop the instruction. So: "Internal Candidates: Current PEA employees with a Continuing or Provisional contract may bid internally." Remove "by following this link." "Proof of Qualification Candidates must hold or be able to obtain a teaching certificate with OSPI, including the appropriate endorsement." That's a requirement, keep. "Benefits And Wages Refer to the Certificated Staff, Non-Supervisory Employees (PEA)-WEA agreements, salary schedules, calendars, and benefits here." That's a reference to benefits, not specific details. The instruction says: never create Benefits section unless posting actually states them. It does state benefits via reference, but not specific benefits. It says "Refer to ... benefits here." That's not specific benefit details. Should we include a Benefits section? The rule: "never create Pay/Schedule/Benefits sections unless the posting actually states them." It does state benefits via reference, but not actual benefits. I'd argue it's stating that benefits exist per agreement, but not enumerating. Might be considered stating them indirectly. Safer to not create a Benefits section because we don't have specific benefit details. However we could include a short paragraph under a generic "Benefits" heading? The rule says never create Benefits section unless posting actually states them. It does state them via reference, but not explicit. I'd lean to not create a Benefits section. Similarly Pay: "Rate: See Salary Schedule" - that's a reference to pay schedule, not specific pay. The rule: never create Pay section unless posting actually states them. It does not state specific pay, just says see schedule. So we should not create a Pay section. Schedule: "Calendar: 180-Day" - that's a schedule detail (180-day calendar). That is specific: 180-Day. So we can create a Schedule section with that info. We need to use

for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). We need to decide which headings to use based on content. We have: - About the role: maybe a short description of what the role does: "RESOURCE = provides in-class or pull-out services to students with identified needs in all building locations." - Responsibilities: could be same as description? Might be redundant. We could combine. - Requirements/Qualifications: "Proof of Qualification Candidates must hold or be able to obtain a teaching certificate with OSPI, including the appropriate endorsement." - Skills: not explicitly listed. - Benefits: we decided not to create. - Pay: not create. - Schedule: "Calendar: 180-Day" - Also we have location and FTE split info. Where to put? Could be under "About the role" or a separate section like "Position Details". But headings limited to those listed. We could put location and FTE under "About the role" as part of description. - Internal Candidates and External Candidates info: maybe under "Qualifications" or "Eligibility". Could be part of "Requirements". Might be better to have a section "Eligibility" but not in list. Could incorporate into "Requirements" or "Qualifications". Since we have Qualifications heading, we can put certification requirement there. Internal/External candidate eligibility could be under "About the role" or a separate note. But we need to preserve all substantive info. Could add a paragraph under "About the role" about internal/external eligibility. We must not repeat job title as heading. The page already shows it, so we don't add heading for position. We must not put Job ID/requisition numbers as headings. There's AP7907 Location: ... That's job ID. We should not make a heading for it; we can fold minor metadata into a short

or drop it. So we can include location and maybe job ID in a paragraph. We need to output only HTML fragment, no /, no markdown. Let's structure:

Job ID: AP7907

maybe? But they said fold minor metadata into a short

or drop it. So we can have a

containing location, FTE split, rate reference, calendar. Better:

Location: Meeker Elementary & Karshner Elementary. Position: Special Education Teacher - Resource. FTE: 1.0 split (0.5 Meeker/0.5 Karshner). Rate: See Salary Schedule. Calendar: 180-Day.

Then sections:

About the role

RESOURCE provides in-class or pull-out services to students with identified needs in all building locations.

Maybe also include internal/external eligibility note:

Internal candidates: Current PEA employees with a Continuing or Provisional contract may bid internally. External candidates (including current PSD Substitutes and non‑continuing PEA contracts) may apply.

But that might be better under a heading like "Eligibility". Not in list. Could put under "Requirements". However requirements heading is for qualifications. Could add a

Requirements

with certification requirement and eligibility. Let's decide:

Requirements

• Hold or be able to obtain a teaching certificate with OSPI, including the appropriate endorsement.
• Internal candidates: Current PEA employees with a Continuing or Provisional contract may bid internally.
• External candidates (including current PSD Substitutes and non‑continuing PEA contracts) may apply.

But the internal/external eligibility is not a requirement per se, but it's about who can apply. Could be under "About the role". However we need to avoid thin sections. Maybe combine into one

About the role

with paragraphs covering description and eligibility. Let's do:

About the role

RESOURCE provides in-class or pull-out services to students with identified needs in all building locations.

Internal candidates: Current PEA employees with a Continuing or Provisional contract may bid internally. External candidates (including current PSD Substitutes and non‑continuing PEA contracts) may apply.

Then

Qualifications

with certification requirement. Then

Schedule

with 180-Day calendar. We should not create Pay or Benefits sections. We need to ensure we don't create empty sections. Now check for any other substantive info: "Benefits And Wages Refer to the Certificated Staff, Non-Supervisory Employees (PEA)-WEA agreements, salary schedules, calendars, and benefits here." This is a reference to benefits and wages. Since we are not creating Benefits or Pay sections, we could mention that benefits and wages are per the referenced agreements in a paragraph under About the role or Qualifications. But we must not invent details. We could add a sentence: "Benefits and wages are governed by the Certificated Staff, Non‑Supervisory Employees (PEA)-WEA agreements, salary schedules, and calendars." That's not inventing, it's restating. It's substantive. We can include that under About the role or a separate note. But we must be careful not to create a Benefits section. Adding a sentence is fine. Thus final HTML:

Location: Meeker Elementary & Karshner Elementary. Position: Special Education Teacher - Resource. FTE: 1.0 split (0.5 Meeker/0.5 Karshner). Rate: See Salary Schedule. Calendar: 180-Day.

About the role

RESOURCE provides in-class or pull-out services to students with identified needs in all building locations.