Campus Instructional Aide - 1.0 hrs at Multiple Sites
for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). Use - for any list of duties/requirements/benefits, and
for prose. Do NOT repeat the job title as a 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 need to parse the posting: It's a Campus Instructional Aide - 1.0 hrs at Multiple Sites at Beaumont Unified School District. Contains:
- Application Deadline 9/22/2026 4:00 PM Pacific
- Date Posted 9/15/2026
- Contact Christian Diaz
- Number of Openings 2
- Salary Pay dependent on experience
- Add'l Salary Info $20.08 - $27.49 per hour
- Length of Work Year 195 Days / Monday - Friday /See notes
- Employment Type Part Time
- About The Employer (description)
- Job Summary (description)
- Requirements / Qualifications (Associates degree or 60 semester units, CPR/First Aid Certification (No Online CPR Certifications), Proof of HS Graduation)
- Comments and Other Information: Brookside Elementary (1 Position) Schedule: 11:00 AM - 12:00 PM; Summerwind Trails School (1 Position) Schedule: TBD
- Also repeated: Incomplete applications etc. (application instructions) which we should remove.
- Also repeated: EXPERIENCE CREDIT: max 3 years external, max starting salary $22.59 per hour (Range 6/Step 4). This is substantive info about pay/experience credit. Should we include? It's about pay and experience credit. It's specific. Should we include in Pay section? Possibly.
- Also repeated: Non-discrimination statement (EEO) which we should remove as boilerplate.
- Also repeated: Links Related To This Job etc. (boilerplate) remove.
We need to keep substantive info: About The Employer, Job Summary, Requirements/Qualifications, Pay (salary range, experience credit max starting salary), Schedule (specific schedules for each site), maybe Benefits? Not mentioned. No benefits specifics. So we should not create Benefits section.
We need to decide sections: About the Employer (maybe "About the Employer" or "About the role"? The instruction says use headings like About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. They gave examples but we can use appropriate headings. The posting has "About The Employer" and "Job Summary". Could combine into "About the role" or separate? Probably better to have "About the Employer" as a section heading? The instruction says use
for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). It doesn't forbid other headings, but suggests those as examples. We could use "About the Employer" as a heading; it's similar to About the role. Or we could use "About the role". I'd use "About the Employer" as it's present.
We also have Requirements / Qualifications combined. Could make a single section "Requirements / Qualifications". Or separate Requirements and Qualifications but they are same content. Probably one section.
We have Pay: we have salary range $20.08 - $27.49 per hour, and experience credit max starting salary $22.59 per hour. That's substantive. So we should have a Pay section.
We have Schedule: we have Brookside Elementary schedule 11:00 AM - 12:00 PM; Summerwind Trails School schedule TBD. TBD is placeholder; we should not create a schedule section with TBD? The instruction: never emit a heading followed by filler/placeholder text (e.g. "commensurate with experience", "not specified", "N/A", "varies", "TBD"). So if we include Schedule section, we must have real specific content for it. We have one specific schedule (Brookside) and one TBD. If we include Schedule section, we would have to include both; but the TBD is filler. Better to avoid Schedule section entirely, or we could include only the specific schedule info within another section like "Assignment Details". But instruction says we can create sections only when posting has real, specific content for it. It doesn't forbid mixing specific and placeholder within same section? It says never emit a heading followed by filler/placeholder text. If we put Schedule heading and then list both schedules, the TBD is filler, making the heading followed by filler text (since part of content is filler). That might violate. Safer to not include Schedule section. Instead we could embed the schedule info in a paragraph under "About the Employer" or "Job Summary"? But that might be odd. Perhaps we can create a section "Site Assignments" but not in the list of examples. The instruction says use for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). It gives examples but not exclusive list. So we could create a heading like "Site Assignments". That would be okay as long as we have real specific content. We have Brookside schedule specific, Summerwind TBD (not specific). Could we omit the TBD line? We must preserve ALL substantive information; we cannot invent or summarize away detail. The TBD is substantive? It's placeholder indicating schedule not determined. It's still information (that schedule is TBD). But it's filler/placeholder. The instruction says never emit a heading followed by filler/placeholder text (e.g. "commensurate with experience", "not specified", "N/A", "varies", "TBD"). So if we include TBD, that's filler. So we should not include a section that would contain TBD as the only content for that site. However we could still include the Brookside schedule and mention that Summerwind Trails schedule is TBD in a note? That would still include TBD. Might be considered filler. Better to avoid mentioning TBD altogether? But we must preserve ALL substantive information. Is TBD substantive? It's essentially "to be determined". It's not a specific schedule. The instruction says do not create sections with filler/placeholder text. It doesn't say we cannot mention TBD in prose; it says never emit a heading followed by filler/placeholder text. If we include a paragraph that says "Summerwind Trails School schedule: TBD", that is filler text within a paragraph. Is that disallowed? The instruction says "never emit a heading followed by filler/placeholder text (e.g. 'commensurate with experience', 'not specified', 'N/A', 'varies', 'TBD')". It seems to refer to the content directly under a heading being just filler. If we embed TBD inside a paragraph with other info, it's still filler text but not the sole content. Might be okay? Safer to avoid TBD entirely? But we would be omitting information (that schedule is TBD). That might be considered summarizing away detail. However the instruction says "Preserve ALL substantive information; do NOT invent or summarize away detail." TBD is not substantive detail; it's lack of detail. So maybe we can omit it because it's not substantive. The phrase "Schedule: TBD" is not substantive; it's just indicating unknown. So we could drop it. That seems acceptable.
Thus we can include only Brookside schedule specifics.
We could create a section "Schedule" with just the Brookside schedule (11:00 AM - 12:00 PM). That's specific. No filler. That would be okay.
We also have Length of Work Year 195 Days / Monday - Friday /See notes. That's substantive about work year length and days. Could be part of Schedule or a separate section "Work Year". But we can include under Schedule or maybe a separate "Work Year" section. The instruction examples include Schedule but not Work Year. We could incorporate into Schedule section: "Length of Work Year: 195 Days, Monday-Friday". That's specific.
Thus Schedule section could contain: Length of Work Year 195 Days / Monday - Friday; Brookside Elementary schedule 11:00 AM - 12:00 PM; Summerwind Trails School schedule TBD (maybe omit). We'll omit TBD.
Now Pay section: include salary range $20.08 - $27.49 per hour; experience credit max starting salary $22.59 per hour (Range 6/Step 4). Also note "Salary Pay dependent on experience". We'll include that.
Requirements/Qualifications: Associates degree or 60 semester units; CPR/First Aid Certification (No Online CPR Certifications); Proof of HS Graduation.
About the Employer: the paragraph describing district.
Job Summary: the paragraph about assisting, clerical, etc.
We should not include application instructions, EEO, links, etc.
We need to output only HTML fragment, no /, no markdown.
We'll structure:
About the Employer
...
Job Summary
...
Requirements / Qualifications
- Associates degree or 60 semester units
- CPR/First Aid Certification (No Online CPR Certifications)
- Proof of HS Graduation
Pay
Salary dependent on experience; hourly range $20.08 - $27.49. With a maximum of three (3) years of external experience credited, the highest starting salary for an external new hire is $22.59 per hour (Range 6/Step 4).
Schedule
Length of work year: 195 days, Monday–Friday. Brookside Elementary position: 11:00 AM – 12:00 PM. (Summerwind Trails School schedule to be determined.)
We included TBD phrased as "to be determined". That's not TBD literal; it's a phrase. Might be acceptable. But we could also omit the Summerwind line entirely. However we need to preserve ALL substantive information; the Summerwind schedule being TBD is not substantive. So we can omit.
Thus Schedule section: "Length of work year: 195 days, Monday–Friday. Brookside Elementary position: 11:00 AM – 12:00 PM."
Now check for any other substantive info: Number of Openings 2, Contact Christian Diaz, Application Deadline, Date Posted. Those are minor metadata; instruction says fold minor metadata into a short or drop it. We could include a brief paragraph at top with that info. But we must not create headings for them. Could add a
with that info before sections. However the instruction says "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 with those details. Let's include a paragraph: "Posted 9/15/2026; application deadline 9/22/20
for prose. Do NOT repeat the job title as a 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 need to parse the posting: It's a Campus Instructional Aide - 1.0 hrs at Multiple Sites at Beaumont Unified School District. Contains: - Application Deadline 9/22/2026 4:00 PM Pacific - Date Posted 9/15/2026 - Contact Christian Diaz - Number of Openings 2 - Salary Pay dependent on experience - Add'l Salary Info $20.08 - $27.49 per hour - Length of Work Year 195 Days / Monday - Friday /See notes - Employment Type Part Time - About The Employer (description) - Job Summary (description) - Requirements / Qualifications (Associates degree or 60 semester units, CPR/First Aid Certification (No Online CPR Certifications), Proof of HS Graduation) - Comments and Other Information: Brookside Elementary (1 Position) Schedule: 11:00 AM - 12:00 PM; Summerwind Trails School (1 Position) Schedule: TBD - Also repeated: Incomplete applications etc. (application instructions) which we should remove. - Also repeated: EXPERIENCE CREDIT: max 3 years external, max starting salary $22.59 per hour (Range 6/Step 4). This is substantive info about pay/experience credit. Should we include? It's about pay and experience credit. It's specific. Should we include in Pay section? Possibly. - Also repeated: Non-discrimination statement (EEO) which we should remove as boilerplate. - Also repeated: Links Related To This Job etc. (boilerplate) remove. We need to keep substantive info: About The Employer, Job Summary, Requirements/Qualifications, Pay (salary range, experience credit max starting salary), Schedule (specific schedules for each site), maybe Benefits? Not mentioned. No benefits specifics. So we should not create Benefits section. We need to decide sections: About the Employer (maybe "About the Employer" or "About the role"? The instruction says use headings like About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. They gave examples but we can use appropriate headings. The posting has "About The Employer" and "Job Summary". Could combine into "About the role" or separate? Probably better to have "About the Employer" as a section heading? The instruction says use
for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). It doesn't forbid other headings, but suggests those as examples. We could use "About the Employer" as a heading; it's similar to About the role. Or we could use "About the role". I'd use "About the Employer" as it's present.
We also have Requirements / Qualifications combined. Could make a single section "Requirements / Qualifications". Or separate Requirements and Qualifications but they are same content. Probably one section.
We have Pay: we have salary range $20.08 - $27.49 per hour, and experience credit max starting salary $22.59 per hour. That's substantive. So we should have a Pay section.
We have Schedule: we have Brookside Elementary schedule 11:00 AM - 12:00 PM; Summerwind Trails School schedule TBD. TBD is placeholder; we should not create a schedule section with TBD? The instruction: never emit a heading followed by filler/placeholder text (e.g. "commensurate with experience", "not specified", "N/A", "varies", "TBD"). So if we include Schedule section, we must have real specific content for it. We have one specific schedule (Brookside) and one TBD. If we include Schedule section, we would have to include both; but the TBD is filler. Better to avoid Schedule section entirely, or we could include only the specific schedule info within another section like "Assignment Details". But instruction says we can create sections only when posting has real, specific content for it. It doesn't forbid mixing specific and placeholder within same section? It says never emit a heading followed by filler/placeholder text. If we put Schedule heading and then list both schedules, the TBD is filler, making the heading followed by filler text (since part of content is filler). That might violate. Safer to not include Schedule section. Instead we could embed the schedule info in a paragraph under "About the Employer" or "Job Summary"? But that might be odd. Perhaps we can create a section "Site Assignments" but not in the list of examples. The instruction says use for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). It gives examples but not exclusive list. So we could create a heading like "Site Assignments". That would be okay as long as we have real specific content. We have Brookside schedule specific, Summerwind TBD (not specific). Could we omit the TBD line? We must preserve ALL substantive information; we cannot invent or summarize away detail. The TBD is substantive? It's placeholder indicating schedule not determined. It's still information (that schedule is TBD). But it's filler/placeholder. The instruction says never emit a heading followed by filler/placeholder text (e.g. "commensurate with experience", "not specified", "N/A", "varies", "TBD"). So if we include TBD, that's filler. So we should not include a section that would contain TBD as the only content for that site. However we could still include the Brookside schedule and mention that Summerwind Trails schedule is TBD in a note? That would still include TBD. Might be considered filler. Better to avoid mentioning TBD altogether? But we must preserve ALL substantive information. Is TBD substantive? It's essentially "to be determined". It's not a specific schedule. The instruction says do not create sections with filler/placeholder text. It doesn't say we cannot mention TBD in prose; it says never emit a heading followed by filler/placeholder text. If we include a paragraph that says "Summerwind Trails School schedule: TBD", that is filler text within a paragraph. Is that disallowed? The instruction says "never emit a heading followed by filler/placeholder text (e.g. 'commensurate with experience', 'not specified', 'N/A', 'varies', 'TBD')". It seems to refer to the content directly under a heading being just filler. If we embed TBD inside a paragraph with other info, it's still filler text but not the sole content. Might be okay? Safer to avoid TBD entirely? But we would be omitting information (that schedule is TBD). That might be considered summarizing away detail. However the instruction says "Preserve ALL substantive information; do NOT invent or summarize away detail." TBD is not substantive detail; it's lack of detail. So maybe we can omit it because it's not substantive. The phrase "Schedule: TBD" is not substantive; it's just indicating unknown. So we could drop it. That seems acceptable.
Thus we can include only Brookside schedule specifics.
We could create a section "Schedule" with just the Brookside schedule (11:00 AM - 12:00 PM). That's specific. No filler. That would be okay.
We also have Length of Work Year 195 Days / Monday - Friday /See notes. That's substantive about work year length and days. Could be part of Schedule or a separate section "Work Year". But we can include under Schedule or maybe a separate "Work Year" section. The instruction examples include Schedule but not Work Year. We could incorporate into Schedule section: "Length of Work Year: 195 Days, Monday-Friday". That's specific.
Thus Schedule section could contain: Length of Work Year 195 Days / Monday - Friday; Brookside Elementary schedule 11:00 AM - 12:00 PM; Summerwind Trails School schedule TBD (maybe omit). We'll omit TBD.
Now Pay section: include salary range $20.08 - $27.49 per hour; experience credit max starting salary $22.59 per hour (Range 6/Step 4). Also note "Salary Pay dependent on experience". We'll include that.
Requirements/Qualifications: Associates degree or 60 semester units; CPR/First Aid Certification (No Online CPR Certifications); Proof of HS Graduation.
About the Employer: the paragraph describing district.
Job Summary: the paragraph about assisting, clerical, etc.
We should not include application instructions, EEO, links, etc.
We need to output only HTML fragment, no /, no markdown.
We'll structure:
About the Employer
About the Employer
...
Job Summary
...
Requirements / Qualifications
- Associates degree or 60 semester units
- CPR/First Aid Certification (No Online CPR Certifications)
- Proof of HS Graduation
Pay
Salary dependent on experience; hourly range $20.08 - $27.49. With a maximum of three (3) years of external experience credited, the highest starting salary for an external new hire is $22.59 per hour (Range 6/Step 4).
Schedule
Length of work year: 195 days, Monday–Friday. Brookside Elementary position: 11:00 AM – 12:00 PM. (Summerwind Trails School schedule to be determined.)
We included TBD phrased as "to be determined". That's not TBD literal; it's a phrase. Might be acceptable. But we could also omit the Summerwind line entirely. However we need to preserve ALL substantive information; the Summerwind schedule being TBD is not substantive. So we can omit. Thus Schedule section: "Length of work year: 195 days, Monday–Friday. Brookside Elementary position: 11:00 AM – 12:00 PM." Now check for any other substantive info: Number of Openings 2, Contact Christian Diaz, Application Deadline, Date Posted. Those are minor metadata; instruction says fold minor metadata into a shortor drop it. We could include a brief paragraph at top with that info. But we must not create headings for them. Could add a
with that info before sections. However the instruction says "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 with those details. Let's include a paragraph: "Posted 9/15/2026; application deadline 9/22/20