2026/2027 Lincoln Elementary Special Education Paraeducator

We need to output HTML fragment with sections: headings

for sections like About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. Use

• for any list of duties/requirements/benefits, and

  for prose. Do NOT repeat job title as heading. Do NOT put Job ID / requisition numbers as headings — fold minor metadata into a short

  or drop it. Preserve ALL substantive information; do NOT invent or summarize away detail. Remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. IMPORTANT: include a section ONLY when the posting has real, specific content for it — 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. Prefer a few substantive sections over many thin ones. We have content: Executive Summary (list of duties). Essential Duties And Functions (list). Knowledge Skills And Abilities Required (list). Education And Licensure (list). Physical Requirements (table). Working Conditions (table). Terms Of Employment (some text). Evaluation (some text). Equal Employment Opportunity Statement (boilerplate to remove). Also statements about scope etc (boilerplate). We need to remove EEO etc. We need to decide sections: maybe "About the role" (Executive Summary). "Responsibilities" (Essential Duties And Functions). "Requirements" (Knowledge Skills And Abilities Required + Education And Licensure). "Skills" maybe part of Requirements. Could combine. "Qualifications" maybe Education And Licensure. "Physical Requirements" maybe a section? But we only create sections if posting has real specific content. Physical Requirements is a table with specifics; we could include as a section "Physical Requirements". Similarly "Working Conditions". "Terms Of Employment" maybe as a section "Terms". "Evaluation" maybe not needed? Could be part of About? But we need to preserve all substantive info. We can include a section "Evaluation". However we need to avoid thin sections; but we can combine similar. We must not create Pay/Schedule/Benefits unless posting actually states them. There's no pay or schedule specifics. So we omit those sections. We need to use

  for section headings. Use

  • for any list of duties/requirements/benefits, and

    for prose. Thus we need to convert lists into

    • . For Executive Summary bullet points: they are sentences separated by no explicit bullet but each line starts with a verb. We'll treat each as list item. Essential Duties And Functions: each line starts with a verb; we can list. Knowledge Skills And Abilities Required: list items: "Earned high school diploma or education equivalent". That's one. Education And Licensure: two items: "High School Diploma or GED", "Para Educator Certificate or equivalent preferred". Physical Requirements: It's a table with columns Activity and Amount of Time. We need to represent as list? Could be a
      with each activity and its frequency. Could also be a

      describing. But rule: Use

      • for any list of duties/requirements/benefits. Physical Requirements is not exactly a list of duties but could be considered a list. We'll output as
        • each activity with its frequency. Working Conditions similar. Terms Of Employment: prose: "Work year as established by the Board of Directors. Salary established by district adopted salary schedules." That's two sentences; we can put in

          . Evaluation: "Performance of this job will be evaluated in accordance with federal and state law, board policy, and the preceding job description." That's prose;

          . We must remove duplicated lines, boilerplate. Also remove "Equal Employment Opportunity Statement" and following lines about scope etc. Also remove "Nothing in this job description restricts the Board's right..." etc. We need to preserve all substantive information: that includes the statements about scope? Those are boilerplate but maybe considered substantive? The instruction says remove EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. The scope statement maybe not boilerplate but could be considered generic; but it's not EEO. However it's a generic disclaimer. Might be considered boilerplate? Not sure. Safer to keep? The instruction: "Remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions." The scope statement is legal boilerplate? It says "The statements contained herein describe the scope of responsibility and essential functions of this position, but should not be considered to be an all-inclusive listing of work requirements. Individuals may perform other duties as assigned. Nothing in this job description restricts the Board's right to assign or reassign duties and responsibilities to this job at any time unless restricted by law or a negotiated contract." That's legal boilerplate. Likely should be removed as legal. So we remove that. Thus we keep: Executive Summary, Essential Duties And Functions, Knowledge Skills And Abilities Required, Education And Licensure, Physical Requirements, Working Conditions, Terms Of Employment, Evaluation. Now we need to decide headings. Use

          for each section. Could we combine some? For brevity, we could have sections: About the role (Executive Summary), Responsibilities (Essential Duties), Requirements (Knowledge Skills And Abilities Required + Education And Licensure), Physical Requirements, Working Conditions, Terms Of Employment, Evaluation. But we need to avoid thin sections; each has substantive content. We'll output HTML fragment. Let's craft:

          About the role

          • support a safe, positive teaching and learning environment
          • assist in the development of students' physical and intellectual growth
          • support social, emotional, and behavioral development
          • establish positive and productive relationships
          • effectively integrate the technology to support student learning
          • practice ethical and professional standards of conduct on an ongoing basis

          Responsibilities

          • Maintain confidentiality of information in accordance with Federal Education Rights and Privacy Act (FERPA).
          • Supervise and assist students, including out of classroom activities (bus duty, recess, field trips, lunchroom).
          • Implement behavior management strategies using the same emphasis and techniques as the teacher.
          • Perform clerical duties as assigned (copying, filing, bulletin boards, grading papers, typing).
          • Assist students in use of computers.
          • Carry out teacher's educational plans for small groups or individual students including serving students who may have Individual Education Plans (IEPs) or 504 Plans.
          • Monitor student progress using the same method as the teacher.
          • Communicate with teachers regarding the progress of students.
          • Attend staffing at the request of the teacher, principal or parent.
          • Perform all other duties as assigned by the principal.

          Requirements

          • Earned high school diploma or education equivalent
          • High School Diploma or GED
          • Para Educator Certificate or equivalent preferred
          But note "Earned high school diploma or education equivalent" is under Knowledge Skills And Abilities Required. Education And Licensure separate. Could combine but we might duplicate "High School Diploma". Might be okay but could be considered duplication. Better to separate: Knowledge Skills And Abilities Required (maybe as "Knowledge, Skills and Abilities") and Education And Licensure as "Qualifications". But we need headings only from allowed list: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We can use Requirements and Qualifications separately. Let's do:

          Requirements

          • Earned high school diploma or education equivalent

          Qualifications

          • High School Diploma or GED
          • Para Educator Certificate or equivalent preferred
          But we also might want a Skills section? Could combine knowledge skills and abilities as Skills. However we already used Requirements for the diploma. Could put knowledge skills and abilities under Skills. Let's think: The posting has "Knowledge Skills And Abilities Required" which is basically a requirement: high school diploma or equivalent. That's more a qualification. So we could have Requirements: high school diploma or equivalent. Qualifications: Para Educator Certificate preferred. But we also have Education And Licensure: High School Diploma or GED (same as requirement) and Para Educator Certificate preferred. So duplication. Better to have one section "Requirements" that includes both the diploma and certificate preferred. But we need to avoid duplication. Let's list: Requirements: - High School Diploma or GED - Para Educator Certificate or equivalent preferred That covers both. The "Earned high school diploma or education equivalent" is same as diploma. So we can just list those two. Thus we have:

          Requirements

          • High School Diploma or GED
          • Para Educator Certificate or equivalent preferred
          Now we need Skills section? Could be omitted if no specific skills beyond those. The posting didn't list specific skills like communication, etc. So we skip Skills. Now Physical Requirements: we need to list each activity with its frequency. Let's extract from the table: Physical Activity Amount of Time Occasionally (1%-32%) Frequently (33%-65%) Constantly (66%-100%) Stationary Position X Moving X Talking X Hearing X Handling X Reaching X Typing X Repetitive Motion X Balance X Lift 0-10 Pounds X Lift 11-25 Pounds X Lift 26-50 Pounds X Lift Over 50 Pounds X Operate Motor Vehicle X Interpretation: The X indicates which frequency? Actually the table likely has columns: Occasionally, Frequently, Constantly. The X under each column indicates the frequency. But the formatting lost columns. We need to infer: Usually they'd have X under the appropriate column. But we don't know which column each X belongs to. The snippet shows each line ends with " X". Probably they omitted column headings and just placed X under the appropriate column but we can't know. However we need to preserve ALL substantive information; we cannot guess. We could output as a list of activities with the note that frequency is indicated in the original table (but we can't reproduce). Maybe we can output as a

          describing that physical requirements include stationary position, moving, talking, hearing, handling, reaching, typing, repetitive motion, balance, lifting various weights, and operating a motor vehicle, with frequencies as indicated in the original table. But that might be summarizing. The instruction says do NOT invent or summarize away detail. We need to preserve the detail; we could output the table as HTML but the rules only mention using

          ,

          • ,

            . They didn't forbid using . It says use

            • for any list of duties/requirements/benefits, and

              for prose. It doesn't say we cannot use other tags. But to be safe, we could represent as

              • each activity with its frequency if we can infer. Let's try to infer: Usually the order of columns is Occasionally, Frequently, Constantly. The X's likely appear under the column that matches the frequency. The snippet shows each line ends with " X". Could be that they placed X under the Constantly column? Not sure. Given uncertainty, maybe better to output as