Special Education Teacher
for sections: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. Only include sections that have real specific content.
We have posting: Setting: Schools Job Type: Travel Pay: 1600 Week Hours: 40.00 Location: DeForest, WI
Then description: The Special Education Teacher, under the direction of the Special Education Program Administrator provides quality services to special education students, kindergarten through grade 12. The Special Education Teacher has a commitment to team participation in planning and implementation of student programs including special instruction, tutorial assistance and consultation with general education staff.
Then Minimum Requirements list: Bachelor’s Degree from an accredited university preferred; Valid state teaching certificate as required by state, contract/district regulations; Minimum of one year experience in teaching environment preferred; State Teacher Certification; Type: Standard Elementary Teaching preferred; State Teacher Certification; Type: Standard Secondary Teaching preferred; State Teacher Certification; Type: Standard Special Teaching preferred; Endorsement: Learning Behavior Specialist (LBS1) preferred; Complies with all relevant professional standards of practice; Current CPR if applicable; TB questionnaire, PPD or chest x-ray if applicable; Current Health certificate (per contract or state regulation); Must meet all federal, state and local requirements; Must be at least 18 years of age.
Then Benefits: At Amergis, we firmly believe that our employees are the heartbeat of our organization and we are happy to offer the following benefits: Competitive pay & weekly paychecks; Health, dental, vision, and life insurance; 401(k) savings plan; Awards and recognition programs; Benefit eligibility is dependent on employment status.
Then About Amergis paragraph.
We need to remove boilerplate: EEO etc. Also remove navigation, cookie, legal, duplicated lines, application instructions. There's no explicit application instructions.
We need to decide sections: About the role (maybe description of role). Responsibilities (maybe the description of duties). Requirements (minimum requirements). Qualifications (maybe certifications). Skills (maybe not present). Benefits (present). Pay (present: Pay: 1600 Week Hours: 40.00). Schedule (maybe Hours: 40.00 indicates schedule). Setting: Schools Job Type: Travel Location: DeForest, WI could be part of About the role or maybe separate but not a heading.
We must not repeat job title as heading. The job title is Special Education Teacher. Not to repeat.
We need to include sections only when posting has real specific content.
We have content for About the role: maybe the first paragraph describing role under direction etc. That's about role.
Responsibilities: maybe the same paragraph includes responsibilities: providing quality services, commitment to team participation, planning and implementation, special instruction, tutorial assistance, consultation. Could be considered responsibilities.
Requirements: Minimum Requirements list.
Qualifications: maybe the certifications list could be qualifications. But we have overlapping. We could combine Requirements and Qualifications? But we need to follow headings if content exists. We have both Minimum Requirements and certifications; they could be considered Requirements. Qualifications maybe not separate.
Skills: not explicitly listed; we could omit.
Benefits: present.
Pay: present: Pay: 1600 Week Hours: 40.00. So we can have Pay section with that info.
Schedule: Hours: 40.00 indicates full-time schedule. Could be Schedule section.
We need to avoid filler like "commensurate with experience". Not present.
We must not include duplicated lines.
We need to output only HTML fragment, no /, no markdown fences.
Thus produce something like:
About the role
The Special Education Teacher, under the direction of the Special Education Program Administrator provides quality services to special education students, kindergarten through grade 12. The Special Education Teacher has a commitment to team participation in planning and implementation of student programs including special instruction, tutorial assistance and consultation with general education staff.
Responsibilities
- Provide quality services to special education students (K‑12)
- Participate in team planning and implementation of student programs
- Deliver special instruction and tutorial assistance
- Consult with general education staff
with that sentence. But we need to use
- for any list of duties/requirements/benefits. The responsibilities are not a list originally; they are a sentence. So we should not convert to list unless we have a list. The instruction: "Use
- for any list of duties/requirements/benefits". If it's not a list, we can use
. So we keep responsibilities as
. Similarly for Requirements: they are a list of items separated by semicolons or line breaks. We could treat as list. Use
- .
Qualifications: maybe not needed.
Benefits: they are a list after colon: Competitive pay & weekly paychecks; Health, dental, vision, and life insurance; 401(k) savings plan; Awards and recognition programs; Benefit eligibility is dependent on employment status. That's a list; we can use
- .
Pay: we have "Pay: 1600 Week Hours: 40.00". Could be a
. Schedule: maybe "Week Hours: 40.00" indicates schedule; we could include in Pay section or separate Schedule. Since we have both Pay and Hours, we could make a Schedule section with "40 hours per week". But the posting says "Week Hours: 40.00". That's schedule info. So we can have Schedule section with that. We must not create Pay/Schedule/Benefits sections unless posting actually states them. It does state Pay and Week Hours. So we can have both. Now we need to avoid repeating job title as heading. Not needed. We must not put Job ID/requisition numbers as headings; none. We must remove boilerplate: EEO etc. The posting includes "Amergis is an equal opportunity/affirmative action employer..." That's boilerplate; we should remove. Also remove duplicated lines: none. Now produce HTML fragment. Let's craft:
About the role
The Special Education Teacher, under the direction of the Special Education Program Administrator provides quality services to special education students, kindergarten through grade 12. The Special Education Teacher has a commitment to team participation in planning and implementation of student programs including special instruction, tutorial assistance and consultation with general education staff.
Responsibilities
The Special Education Teacher, under the direction of the Special Education Program Administrator provides quality services to special education students, kindergarten through grade 12. The Special Education Teacher has a commitment to team participation in planning and implementation of student programs including special instruction, tutorial assistance and consultation with general education staff.
But that duplicates the about role text. Actually the about role and responsibilities are same sentence. Might be redundant. Perhaps we should combine: About the role could be brief description; Responsibilities could be the same but we risk duplication. The instruction: "Preserve ALL substantive information; do NOT invent or summarize away detail." If we duplicate, we are preserving but also repeating. Might be okay but better to avoid duplication by having only one section that captures both. However we need to decide which heading to use. The posting includes a description that could be considered both about role and responsibilities. We could choose to put it under About the role and not have Responsibilities section (since no separate responsibilities list). But we need to include a section only when posting has real specific content for it. The posting does not have a separate responsibilities section; it's just the description. So we should not create a Responsibilities heading if there is no distinct responsibilities content beyond the description. So we will have About the role only. Now Requirements: we have a list of minimum requirements. We'll make a Requirements section with- .
Qualifications: maybe we can treat the certifications as qualifications. But they are also part of minimum requirements. To avoid duplication, we could have Requirements include all those items. Qualifications maybe not needed.
Skills: none.
Benefits: we have list.
Pay: we have Pay: 1600 Week Hours: 40.00. Could be a
under Pay section. Schedule: we could have Schedule section with "40 hours per week". But the posting says Week Hours: 40.00. That is essentially schedule. We could include that in Pay section or separate. Since we have both Pay and Hours, we could make a Pay section with "Pay: $1600 per week" and a Schedule section with "40 hours per week". However the posting says "Pay: 1600 Week Hours: 40.00". It doesn't specify currency but likely dollars. We'll keep as given. We must not create Pay/Schedule/Benefits sections unless posting actually states them. It does state Pay and Week Hours. So we can have both. Now we need to ensure we don't include filler like "commensurate with experience". Not present. Now produce final HTML. Let's list items: About the role paragraph as above. Requirements list items: - Bachelor’s Degree from an accredited university preferred - Valid state teaching certificate as required by state, contract/district regulations - Minimum of one year experience in teaching environment preferred - State Teacher Certification; Type: Standard Elementary Teaching preferred - State Teacher Certification; Type: Standard Secondary Teaching preferred - State Teacher Certification; Type: Standard Special Teaching preferred - Endorsement: Learning Behavior Specialist (LBS1) preferred - Complies with all relevant professional standards of practice - Current CPR if applicable - TB questionnaire, PPD or chest x-ray if applicable - Current Health certificate (per contract or state regulation) - Must meet all federal, state and local requirements - Must be at least 18 years of age We need to preserve the exact wording. Use
- for each.
Benefits list:
- Competitive pay & weekly paychecks
- Health, dental, vision, and life insurance
- 401(k) savings plan
- Awards and recognition programs
- Benefit eligibility is dependent on employment status
Pay section: maybe
Pay: 1600
but also include Week Hours? Actually Week Hours is schedule. We'll separate. Pay:Pay: 1600
Schedule:Week Hours: 40.00
or "40 hours per week". We'll keep as given. Now ensure we don't include any extra text like "Preferred" etc. It's fine. Now output HTML fragment. We must not include or . Just the fragment. Let's produce:About the role
The Special Education Teacher, under the direction of the Special Education Program Administrator provides quality services to special education students, kindergarten through grade 12. The Special Education Teacher has a commitment to team participation in planning and implementation of student programs including special instruction, tutorial assistance and consultation with general education staff.
Requirements
- Bachelor’s Degree from an accredited university preferred
- Valid state teaching certificate as required by state, contract/district regulations
- Minimum of one year experience in teaching environment preferred
- State Teacher Certification; Type: Standard Elementary Teaching preferred
- State Teacher Certification; Type: Standard Secondary Teaching preferred
- .
Qualifications: maybe we can treat the certifications as qualifications. But they are also part of minimum requirements. To avoid duplication, we could have Requirements include all those items. Qualifications maybe not needed.
Skills: none.
Benefits: we have list.
Pay: we have Pay: 1600 Week Hours: 40.00. Could be a
- .
Pay: we have "Pay: 1600 Week Hours: 40.00". Could be a
- .
Qualifications: maybe not needed.
Benefits: they are a list after colon: Competitive pay & weekly paychecks; Health, dental, vision, and life insurance; 401(k) savings plan; Awards and recognition programs; Benefit eligibility is dependent on employment status. That's a list; we can use
- for any list of duties/requirements/benefits". If it's not a list, we can use