Preschool Teacher
for section headings, - for lists, and
for prose. I should not repeat the job title as a heading. I should fold minor metadata into a short
or drop it. I should preserve ALL substantive information. I should remove boilerplate. I should include a section ONLY when the posting has real, specific content for it.
Let me structure this:
- Requirements section: has bullet points, so use
-
- Qualifications section: has prose, so use
- Responsibilities section: has multiple subsections with bullet points. I could make each subsection a separate
or keep them under one Responsibilities heading with sub-lists. The rules say use for section headings like "Responsibilities". The subsections (Professionalism, Child Interaction, etc.) could be but the rules only mention for section headings. I'll use for main sections and maybe for subsections? The rules say "use for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)". It doesn't mention subsections. I think I should keep the main sections as and for the responsibilities subsections, I could either make them separate headings or use or just list them as part of the responsibilities. Since they are distinct categories, I'll make them headings as well? But that might create too many sections. The rules say "Prefer a few substantive sections over many thin ones." So maybe keep Responsibilities as one and use with nested lists or separate for each category with a bold label. However, the example shows using for section headings. I'll make each responsibility category a separate because they are substantial.
Let me check the content: Professionalism has 8 bullet points, Child Interaction has 5, Program & Environment Maintenance has 5, Parent Relationships has 2, Work Environment has 4 bullet points. That's substantial.
Human Resources has 8 bullet points.
Physical Demands has 4 bullet points.
Compensation is a single line.
I'll create sections for:
- Requirements
- Qualifications
- Professionalism (under Responsibilities)
- Child Interaction
- Program & Environment Maintenance
- Parent Relationships
- Work Environment
- Human Resources
- Physical Demands
- Compensation (Pay)
But the rules say "use for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)". So "Responsibilities" is a suggested heading. I could have one "Responsibilities" heading and then subsections. But the rules also say "include a section ONLY when the posting has real, specific content for it". Each subsection has real content. I think it's okay to have multiple headings for each responsibility category. However, the example list includes "Responsibilities" as a single heading. I'll follow the pattern: use for each major section. The posting has "Responsibilities will include, but will not be limited to the following:" and then subsections. I'll make "Responsibilities" an and then each subsection as an ? But the rules don't mention . They only say use for section headings. I could use for each subsection as well, but that might be too many. I'll use for the main sections: Requirements, Qualifications, Responsibilities, Human Resources, Physical Demands, Compensation. And within Responsibilities, I'll use for the category names and then for each.
But the rules say "Use - for any list of duties/requirements/benefits, and
for prose." It doesn't forbid using
. However, to be safe, I'll use for each distinct section. The posting has clear sections: Requirements, Qualifications, Responsibilities (with subsections), Human Resources, Physical Demands, Compensation. I'll make each subsection of Responsibilities a separate because they are distinct duty categories. That seems appropriate.
Let me write the HTML.
First, Requirements: it's a list. I'll use Requirements
then - for each bullet.
Qualifications: prose, so
Qualifications
then for the text.
Responsibilities: I'll create
for each category: Professionalism, Child Interaction, Program & Environment Maintenance, Parent Relationships, Work Environment. Each with - .
Human Resources:
Human Resources
then - .
Physical Demands:
Physical Demands
then - .
Compensation:
Pay
then with the wage.
I need to ensure I don't include any boilerplate. The text seems clean.
Now, I'll write the HTML fragment. No markdown code fences, just the HTML.
Let me parse the content carefully.
Requirements:
• 2 – 5 years of experience in ECE program,
• 12 – 24 ECE units, need to be enrolled in units toward GE units, OR
• CTC Associate Teacher permit.
Qualifications: The person selected for this position is required to possess an "Associate" Child Development Teaching Permit or higher with at least 6 months classroom experience. Individuals who do not possess but qualify, must obtain a Child Development Associate Permit, or higher, within 6 months of NBCC employment. Associate Teachers are required to work collegially as a team member with other center staff and respond positively to all management supervision and feedback.
Responsibilities:
Professionalism:
• Adheres to all NBCC policies and procedures as mandated by Executive, Program, and/or Educational Resource Director.
• In cooperation with the teaching team, maintain general housekeeping tasks (to provide and orderly, professional environment and atmosphere).
• Obtain and maintain certification of Pediatric First Aid and Pediatric CPR as required by California State Licensing
• Engage in regular self-assessment/goal setting and participate in timely evaluation of job performance with the Head Teacher and/or Site Supervisor.
• In cooperation with the Head Teacher, staff and/or Site Supervisor, obtain appropriate substitutes when ill, for vacation, and any other time off site for any reason.
• Attend all scheduled NBCC Staff Development Days.
• Demonstrate ability to work as a collegial team member with respect, trust, and professionalism with co-workers.
• Demonstrate professional demeanor at all times.
• Support teaching team in implementing specific child behavior plans, intervention, and resource referrals.
Child Interaction:
• Adheres to all CCL Personal Rights requirements. Children in childcare programs must not be subjected to corporal or unusual punishment, including yelling, spanking, humiliation, mental abuse, or punitive interference with daily living functions such as speaking, sleeping or toileting.
• Give warmth and positive attention to each and every child in the classroom.
• Recognize and consider each child in relationship to cultural and/ ethnic background, as well as respond to each unique individual child with dignity and respect. Foster positive self-esteem through respectful interactions with children and staff.
• Practice positive re-enforcement and re-direction methods. Children in childcare programs must not be subjected to corporal or unusual punishment, including spanking, humiliation, mental abuse, or punitive interference with daily living functions such as speaking, sleeping or toileting.
Program & Environment Maintenance:
• In cooperation with all the teaching staff, maintain required supervision of children at all times (inside and outside) in accordance with California State Licensing regulations ratio standards. Aides, who do not have at least 12 CORE ECE units, may not be left alone with children without supervision).
• Assist teaching staff in maintaining a safe, orderly arrangement and inviting appearance in all classrooms (including outside play areas).
• In cooperation with staff, conduct the daily set-up of classrooms and outside play areas in an inviting fashion as to promote positive exploration and developmental progress.
• In cooperation with the teaching team, maintain classroom documents: daily meal counts, classroom rosters, and such reports.
• Report to the Head Teacher or Site Supervisor, in writing, all injuries incurred by children or staff.
Parent Relationships:
• Develop meaningful relationships with parents through facilitation of open, responsive communication on a continual basis.
• Promptly direct any relevant feedback (positive or negative issues) to the Head Teacher and/or Site Supervisor.
Work Environment:
• Noise level in the work environment is frequently loud.
• Will work outdoors and indoors
• Will use computers, tablets, cell phone (if provided), and other office equipment
• Will work alone and with other peers and supervisors
Human Resources:
• Employee Rights (see Employee Handbook).
• Health screening as required in section 101216(g)
• Tuberculosis test & document as specified in section 101216(g).
• Criminal Record Clerance and/or criminal records exemption (DOJ, CACI & FBI).
• Valid Driver’s License (if transporting children).
• Child Abuse Managed Reporter Training (online).
• Employee Rights (Lic 9052).
• Proof of Immunizations for MMR, Tdap & Flu.
• Current CPR & First Aid.
Physical Demands:
• Health clearance by a physician.
• Ability to fulfill physical requirements of the job including lifting up to 50 pounds, range of movement including squatting, bending, reaching, standing, and sitting.
• Proof of current Immunizations (Measles, Pertussis, Influenza, COVID-19).
• T.B. clearance within the past year.
Compensation details: 27.25-31 Hourly Wage
Now, I'll write the HTML. I'll use
for each section. For Responsibilities subsections, I'll use as well, but maybe prefix with "Responsibilities: "? The rules say "use for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)". So "Responsibilities" is a heading. I could have one Responsibilities
and then use for subsections, but the rules don't mention . I'll use for each subsection and make the heading descriptive, e.g., "Professionalism", "Child Interaction", etc. That seems fine.
Alternatively, I could have Responsibilities
and then each category as a with a label. But the rules say "Use - for any list of duties/requirements/benefits". It doesn't say how to label the lists. I think using
for each category is acceptable as they are sections.
I'll do:
Requirements
...
Qualifications
...
Professional
for prose. I should not repeat the job title as a heading. I should fold minor metadata into a short
or drop it. I should preserve ALL substantive information. I should remove boilerplate. I should include a section ONLY when the posting has real, specific content for it. Let me structure this: - Requirements section: has bullet points, so use
-
- Qualifications section: has prose, so use
- Responsibilities section: has multiple subsections with bullet points. I could make each subsection a separate
or keep them under one Responsibilities heading with sub-lists. The rules say use
for section headings like "Responsibilities". The subsections (Professionalism, Child Interaction, etc.) could be
but the rules only mention
for section headings. I'll use
for main sections and maybe
for subsections? The rules say "use
for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)". It doesn't mention subsections. I think I should keep the main sections as
and for the responsibilities subsections, I could either make them separate
headings or use or just list them as part of the responsibilities. Since they are distinct categories, I'll make them
headings as well? But that might create too many sections. The rules say "Prefer a few substantive sections over many thin ones." So maybe keep Responsibilities as one
and use
- with nested lists or separate
- for any list of duties/requirements/benefits, and
for prose." It doesn't forbid using
. However, to be safe, I'll use
for each distinct section. The posting has clear sections: Requirements, Qualifications, Responsibilities (with subsections), Human Resources, Physical Demands, Compensation. I'll make each subsection of Responsibilities a separate
because they are distinct duty categories. That seems appropriate. Let me write the HTML. First, Requirements: it's a list. I'll use
Requirements
then- for each bullet.
Qualifications: prose, so
Qualifications
thenfor the text. Responsibilities: I'll create
for each category: Professionalism, Child Interaction, Program & Environment Maintenance, Parent Relationships, Work Environment. Each with
- .
Human Resources:
Human Resources
then- .
Physical Demands:
Physical Demands
then- .
Compensation:
Pay
thenwith the wage. I need to ensure I don't include any boilerplate. The text seems clean. Now, I'll write the HTML fragment. No markdown code fences, just the HTML. Let me parse the content carefully. Requirements: • 2 – 5 years of experience in ECE program, • 12 – 24 ECE units, need to be enrolled in units toward GE units, OR • CTC Associate Teacher permit. Qualifications: The person selected for this position is required to possess an "Associate" Child Development Teaching Permit or higher with at least 6 months classroom experience. Individuals who do not possess but qualify, must obtain a Child Development Associate Permit, or higher, within 6 months of NBCC employment. Associate Teachers are required to work collegially as a team member with other center staff and respond positively to all management supervision and feedback. Responsibilities: Professionalism: • Adheres to all NBCC policies and procedures as mandated by Executive, Program, and/or Educational Resource Director. • In cooperation with the teaching team, maintain general housekeeping tasks (to provide and orderly, professional environment and atmosphere). • Obtain and maintain certification of Pediatric First Aid and Pediatric CPR as required by California State Licensing • Engage in regular self-assessment/goal setting and participate in timely evaluation of job performance with the Head Teacher and/or Site Supervisor. • In cooperation with the Head Teacher, staff and/or Site Supervisor, obtain appropriate substitutes when ill, for vacation, and any other time off site for any reason. • Attend all scheduled NBCC Staff Development Days. • Demonstrate ability to work as a collegial team member with respect, trust, and professionalism with co-workers. • Demonstrate professional demeanor at all times. • Support teaching team in implementing specific child behavior plans, intervention, and resource referrals. Child Interaction: • Adheres to all CCL Personal Rights requirements. Children in childcare programs must not be subjected to corporal or unusual punishment, including yelling, spanking, humiliation, mental abuse, or punitive interference with daily living functions such as speaking, sleeping or toileting. • Give warmth and positive attention to each and every child in the classroom. • Recognize and consider each child in relationship to cultural and/ ethnic background, as well as respond to each unique individual child with dignity and respect. Foster positive self-esteem through respectful interactions with children and staff. • Practice positive re-enforcement and re-direction methods. Children in childcare programs must not be subjected to corporal or unusual punishment, including spanking, humiliation, mental abuse, or punitive interference with daily living functions such as speaking, sleeping or toileting. Program & Environment Maintenance: • In cooperation with all the teaching staff, maintain required supervision of children at all times (inside and outside) in accordance with California State Licensing regulations ratio standards. Aides, who do not have at least 12 CORE ECE units, may not be left alone with children without supervision). • Assist teaching staff in maintaining a safe, orderly arrangement and inviting appearance in all classrooms (including outside play areas). • In cooperation with staff, conduct the daily set-up of classrooms and outside play areas in an inviting fashion as to promote positive exploration and developmental progress. • In cooperation with the teaching team, maintain classroom documents: daily meal counts, classroom rosters, and such reports. • Report to the Head Teacher or Site Supervisor, in writing, all injuries incurred by children or staff. Parent Relationships: • Develop meaningful relationships with parents through facilitation of open, responsive communication on a continual basis. • Promptly direct any relevant feedback (positive or negative issues) to the Head Teacher and/or Site Supervisor. Work Environment: • Noise level in the work environment is frequently loud. • Will work outdoors and indoors • Will use computers, tablets, cell phone (if provided), and other office equipment • Will work alone and with other peers and supervisors Human Resources: • Employee Rights (see Employee Handbook). • Health screening as required in section 101216(g) • Tuberculosis test & document as specified in section 101216(g). • Criminal Record Clerance and/or criminal records exemption (DOJ, CACI & FBI). • Valid Driver’s License (if transporting children). • Child Abuse Managed Reporter Training (online). • Employee Rights (Lic 9052). • Proof of Immunizations for MMR, Tdap & Flu. • Current CPR & First Aid. Physical Demands: • Health clearance by a physician. • Ability to fulfill physical requirements of the job including lifting up to 50 pounds, range of movement including squatting, bending, reaching, standing, and sitting. • Proof of current Immunizations (Measles, Pertussis, Influenza, COVID-19). • T.B. clearance within the past year. Compensation details: 27.25-31 Hourly Wage Now, I'll write the HTML. I'll use
for each section. For Responsibilities subsections, I'll use
as well, but maybe prefix with "Responsibilities: "? The rules say "use
for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)". So "Responsibilities" is a heading. I could have one
Responsibilities
and then usefor subsections, but the rules don't mention
. I'll use
for each subsection and make the heading descriptive, e.g., "Professionalism", "Child Interaction", etc. That seems fine. Alternatively, I could have
Responsibilities
and then each category as a- with a label. But the rules say "Use
- for any list of duties/requirements/benefits". It doesn't say how to label the lists. I think using
for each category is acceptable as they are sections. I'll do:
Requirements
- ...
Qualifications
...
Professional
- for any list of duties/requirements/benefits". It doesn't say how to label the lists. I think using
- .
Compensation:
- .
Physical Demands:
- .
Human Resources:
- for each bullet.
Qualifications: prose, so
- for each category with a bold label. However, the example shows using
for section headings. I'll make each responsibility category a separate
because they are substantial. Let me check the content: Professionalism has 8 bullet points, Child Interaction has 5, Program & Environment Maintenance has 5, Parent Relationships has 2, Work Environment has 4 bullet points. That's substantial. Human Resources has 8 bullet points. Physical Demands has 4 bullet points. Compensation is a single line. I'll create sections for: - Requirements - Qualifications - Professionalism (under Responsibilities) - Child Interaction - Program & Environment Maintenance - Parent Relationships - Work Environment - Human Resources - Physical Demands - Compensation (Pay) But the rules say "use
for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)". So "Responsibilities" is a suggested heading. I could have one "Responsibilities" heading and then subsections. But the rules also say "include a section ONLY when the posting has real, specific content for it". Each subsection has real content. I think it's okay to have multiple
headings for each responsibility category. However, the example list includes "Responsibilities" as a single heading. I'll follow the pattern: use
for each major section. The posting has "Responsibilities will include, but will not be limited to the following:" and then subsections. I'll make "Responsibilities" an
and then each subsection as an
? But the rules don't mention
. They only say use
for section headings. I could use
for each subsection as well, but that might be too many. I'll use
for the main sections: Requirements, Qualifications, Responsibilities, Human Resources, Physical Demands, Compensation. And within Responsibilities, I'll use for the category names and then
- for each.
But the rules say "Use
- for any list of duties/requirements/benefits, and