EC Resource Teacher
for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). So we can include About the role, Responsibilities, Requirements, Schedule. Possibly also Qualifications if we have separate content; but we have education/experience requirements; we could put that under Requirements. Qualifications could be duplicate. Better to have Requirements covering education/experience. Also maybe Skills? Not explicit. So we will output:
About the role
Position summary text.
Responsibilities
- ... each duty as list item.
Requirements
Education/Experience Requirements text.
Schedule
Work Schedule: 10 Month Position.
We must preserve all substantive information, not invent or summarize away detail. Need to include all essential duties exactly as given, but we can list them asmaybe with line breaks or
- . Since it's a list, we can use
- . But the instruction: Use
- for any list of duties/requirements/benefits. So we should use list for requirements.
Also Physical Requirements: "Ability to safely and successfully perform the essential job functions consistent with the ADA, FMLA and other federal, state and local standards, including meeting qualitative and/or quantitative productivity standards
Ability to maintain regular, punctual attendance consistent with the ADA, FMLA and other federal, state and local standards"
These are also requirements; we could include them under Requirements as well. But the instruction: Use
- for any list of duties/requirements/benefits. So we can combine education/experience and physical requirements into a single list under Requirements, or separate sections? Probably better to have Requirements section containing both education/experience and physical requirements as list items.
We also have Salary Schedule, Reports To, Salary Grade, Work Location, FLSA Status, Work Schedule. Those are metadata; we could incorporate them into a short
or drop. The instruction: "Do NOT put Job ID / requisition numbers as headings — fold minor metadata into a short
or drop it." So we can include a short paragraph at top maybe after About the role? But we already have About the role as position summary. We could add a
with metadata like "Salary Schedule: Certified; CHCCS Salary Schedule. Reports To: School Principal. Salary Grade: Teacher, eligible for local supplement. Work Location: School. FLSA Status: Exempt. Work Schedule: 10 Month Position." However we already have Schedule section for Work Schedule. Might be redundant. But we could keep Schedule section only for Work Schedule, and put other metadata in a short paragraph. But the instruction: "Prefer a few substantive sections over many thin ones." So maybe we combine metadata into a short paragraph under About the role or separate? Could add a
after About the role containing those details. However About the role is supposed to be position summary; we could still add extra paragraph there but it's okay. Better: Keep About the role as position summary only. Then add a
for metadata (maybe titled "Position Details"? Not a heading). Then Responsibilities, Requirements, Schedule. But we must not create extra headings not listed. So we can just add a
after About the role before Responsibilities. Let's craft:
About the role
At CHCCS, a teacher's goal is to provide each student with the help, counsel, and learning experience needed to make progress toward educational goals established, to create a flexible instructional program and a class environment favorable to learning and personal growth, and to establish effective rapport with pupils; to motivate pupils to develop skills, attitudes and knowledge needed to live a rewarding life in an ever-changing world.
Salary Schedule: Certified; CHCCS Salary Schedule. Reports To: School Principal. Salary Grade: Teacher, eligible for local supplement. Work Location: School. FLSA Status: Exempt.
Then Responsibilities list. Then Requirements list (education/experience + physical). Then Schedule section:Schedule
Work Schedule: 10 Month Position.
Check that we didn't miss any substantive info: The position summary we captured. The essential duties we captured unique list. The education/experience we captured. Physical requirements we captured. The schedule we captured. The salary schedule etc we captured in metadata paragraph. We removed boilerplate like "Disclosure" etc. Good. Now output HTML fragment only. Let's construct. Be careful to escape any HTML special characters; none present. We'll output:About the role
At CHCCS, a teacher's goal is to provide each student with the help, counsel, and learning experience needed to make progress
- for any list of duties/requirements/benefits. So we can combine education/experience and physical requirements into a single list under Requirements, or separate sections? Probably better to have Requirements section containing both education/experience and physical requirements as list items.
We also have Salary Schedule, Reports To, Salary Grade, Work Location, FLSA Status, Work Schedule. Those are metadata; we could incorporate them into a short
- for any list of duties/requirements/benefits. So we should use list for requirements.
Also Physical Requirements: "Ability to safely and successfully perform the essential job functions consistent with the ADA, FMLA and other federal, state and local standards, including meeting qualitative and/or quantitative productivity standards
Ability to maintain regular, punctual attendance consistent with the ADA, FMLA and other federal, state and local standards"
These are also requirements; we could include them under Requirements as well. But the instruction: Use