26-27 Viola Teaching Artist - El Sistema Somerville
for each heading. Use - for any list of duties/requirements/benefits, and
for prose. Do NOT repeat job title as heading. Do NOT put Job ID etc. Remove boilerplate, navigation, legal, EEO, equal-opportunity, scam-warning, duplicated lines, application instructions. Preserve all substantive info. Include a section only when posting has real, specific content for it — never emit heading followed by filler/placeholder text. Prefer few substantive sections over many thin ones.
We need to parse the posting.
Content:
Position Summary: paragraph about inclusive environment, fairness, equity, inclusion, valuing diversity, supporting educators, induction, mentorship, professional development, growth, supporting whole child, trusting culture.
Essential Functions & Responsibilities: bullet list (though not bullet but sentences). It says: Develop and teach engaging group lessons that: (list). Then bullet-like items: Establish routines and encourage development of strong fundamental musical skills; Incorporate a variety of strategies (movement, ear training, music reading, bowing/plucking) and activities (exercises, games, demonstration, listening, etc); Maintain excellent classroom management; Adapt to the needs of students at various levels and with various learning styles; Encourage peer teaching; Collaborate closely with the administration and faculty to achieve program-wide learning goals; Maintaining a positive and nurturing classroom environment; Set and maintain high standards for student behavior and music learning; Enforce program rules and policies.
Qualifications And Skills: list: Excellent musicianship and artistry as a teacher/performer; Strong understanding of violia pedagogy (typo: violia? but keep as is); Strong commitment to El Sistema’s philosophy of social change through music; Experience working with children grades 3rd-8th grade from diverse ethnic and economic backgrounds; Strong interpersonal and communication skills; Self-motivated and willing to collaborate in a team-teaching environment; At least 2 years of prior teaching experience preferred; Bachelor’s or equivalent degree in Music Performance or Music Education.
Terms Of Employment: Position Type: Part Time; School Year Schedule / Up to 19 work hours per week; Monday, Tuesday, Thursday & Friday - 1:00pm-5:45pm; FLSA Classification: Non Exempt; Union Status: Non Union; Benefits: Non Benefits Eligible position.
Physical Requirements: description: Mobility: Frequent walking, standing, and navigating stairs. Lifting/Strength: Ability to lift, push, pull, or carry objects ranging from 10 to 30 lbs (e.g., books, supplies, equipment). Physical Dexterity: Bending, crouching, kneeling, stooping, and reaching to assist students. Stationary Tasks: Remaining in a stationary position (sitting/standing) for long periods.
Reporting Relationships: Position Reports to: The Director of El Sistema - Somerville.
Then EEO statement: The Somerville Public Schools does not discriminate... (boilerplate). Remove.
We need to decide sections: About the role (position summary). Responsibilities (essential functions). Requirements (maybe combine qualifications and skills? The spec says we have separate headings for Qualifications and Skills. But we can combine if content thin? The instruction: Prefer a few substantive sections over many thin ones. So we could have sections: About the role, Responsibilities, Qualifications (including skills), Terms of Employment (maybe schedule, benefits, pay). However we have separate headings for Benefits, Pay, Schedule. We need to include a section only when posting has real, specific content for it. The posting includes Schedule (Part Time, up to 19 hrs per week, days/times). It includes Benefits: Non Benefits Eligible position. It does NOT include Pay (no salary). So we should not create Pay section because no specific pay info. Benefits: we have "Non Benefits Eligible position" which is specific content (though it's a statement that it's not benefits eligible). That is substantive; we should include Benefits section with that statement. Schedule: we have specifics, include Schedule section.
We could also include a Requirements section for things like physical requirements? But maybe we can incorporate physical requirements into Responsibilities? Not exactly. Could create a Requirements section for qualifications (education, experience) and maybe physical requirements? But we have Qualifications and Skills headings separate. We could combine Qualifications and Skills into one section titled Qualifications (including skills). Or we could have two sections: Qualifications and Skills. But the instruction says prefer few substantive sections over many thin ones. So better to combine.
Thus sections: About the role (position summary). Responsibilities (essential functions). Qualifications (including skills and education/experience). Benefits. Schedule. Possibly also Reporting Relationships? Could be part of About the role or Responsibilities? Might be its own section but not in list of allowed headings. The allowed headings are only those listed: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. So we cannot add Reporting Relationships as a heading; we could fold that into About the role or Responsibilities as prose. Similarly Physical Requirements could be folded into Responsibilities or Requirements? There is a Requirements heading allowed. We could use Requirements for physical requirements and maybe also for qualifications? But we already have Qualifications. Perhaps we use Requirements for physical requirements and maybe other mandatory requirements (like eligibility to work?). But we have qualifications already covering education/experience. The spec says we can use Requirements heading for any list of duties/requirements/benefits. So we could put physical requirements under Requirements. However we also have Qualifications and Skills separate. To avoid many thin sections, we could combine Qualifications and Skills into one Qualifications section, and put physical requirements under Requirements. That yields sections: About the role, Responsibilities, Qualifications, Requirements, Benefits, Schedule. That's six sections, maybe okay. But we could also merge Requirements into Qualifications if we think it's thin. However physical requirements are substantive; we could include them under Responsibilities? Not exactly responsibilities but could be considered job demands. The spec says we can use
- for any list of duties/requirements/benefits. So we could put physical requirements as a list under Responsibilities? Might be okay but better to have Requirements.
We need to avoid filler like "commensurate with experience". Not present.
Now we need to output HTML fragment only, no /, no markdown fences.
We'll produce:
About the role
Somerville Public Schools strives to create an inclusive and racially affirming environment that welcomes and values the diversity of our staff and students. We foster fairness, equity, and inclusion to create a workplace environment where everyone is treated with respect and dignity. We welcome and value different perspectives and experiences in our staff, recognizing the powerful impact that a diverse workforce has on all students. We are committed to supporting educators through a strong induction and mentorship program, educator-driven professional development, and opportunities for professional growth and advancement. As a district, we are also committed to supporting the whole child by promoting a trusting, mutually respectful and inspiring culture that values the individuality of our students and the professionalism of the field.
Responsibilities
- Develop and teach engaging group lessons that establish routines and encourage development of strong fundamental musical skills
- Incorporate a variety of strategies (movement, ear training, music reading, bowing/plucking) and activities (exercises, games, demonstration, listening, etc)
- Maintain excellent classroom management
- Adapt to the needs of students at various levels and with various learning styles
- Encourage peer teaching
- Collaborate closely with the administration and faculty to achieve program-wide learning goals
- Maintain a positive and nurturing classroom environment
- Set and maintain high standards for student behavior and music learning
- Enforce program rules and policies
Qualifications
- Excellent musicianship and artistry as a teacher/performer
- Strong understanding of viola pedagogy
- Strong commitment to El Sistema’s philosophy of social change through music
- Experience working with children grades 3rd‑8th from diverse ethnic and economic backgrounds
- Strong interpersonal and communication skills
- Self‑motivated and willing to collaborate in a team‑teaching environment
- At least 2 years of prior teaching experience preferred
- Bachelor’s or equivalent degree in Music Performance or Music Education
Requirements
- Mobility: Frequent walking, standing, and navigating stairs
- Lifting/Strength: Ability to lift, push, pull, or carry objects ranging from 10 to 30 lbs (e.g., books, supplies, equipment)
- Physical Dexterity: Bending, crouching, kneeling, stooping, and reaching to assist students
- Stationary Tasks: Remaining in a stationary position (sitting/standing) for long periods
Benefits
Non Benefits Eligible position
Schedule
Part‑time, up to 19 work hours per week; Monday, Tuesday, Thursday & Friday – 1:00 pm‑5:45 pm (School Year)
We need to ensure we didn't repeat job title. No mention of Pay. No mention of EEO. We removed duplicated lines. Ensure we didn't include any boilerplate like "The Somerville Public Schools does not discriminate...". Good.
Check that we preserved all substantive info: Position summary captured. Responsibilities captured all bullet points. Qualifications captured all listed. Requirements captured physical demands. Benefits captured "Non Benefits Eligible position". Schedule captured part-time schedule. Reporting Relationships omitted but we could fold into About the role? Not required. The spec says preserve ALL substantive information; do NOT invent or summarize away detail. Reporting Relationships is substantive: "Position Reports to: The Director of El Sistema - Somerville". We omitted it. That would be losing substantive info. We need to include it somewhere. Where can we put? Not a heading allowed, but we can fold into About the role or Responsibilities as prose. Probably best to add a sentence in About the role or Responsibilities. Since it's about reporting line, maybe add to About the role after the summary. Let's add a sentence: "The position reports to the Director of El Sistema - Somerville." That preserves info.
Also we might need to include "FLSA Classification: Non Exempt" and "Union Status: Non Union". Those are substantive. Where to put? Could be in About the role or Responsibilities? Could add to About the role as additional sentences. Or we could create a separate section? Not allowed headings besides those. Could add to About the role or Responsibilities. Probably About the role is fine.
We also have "Position Type: Part Time" already captured in Schedule. Good.
We need to ensure we didn't lose any substantive info: The position summary includes mention of supporting educators, induction, mentorship, professional development, growth, supporting whole child, trusting culture. We captured that.
We also have "Essential Functions & Responsibilities The essential functions or responsibilities listed below are intended only as illustrations of the various types of work that may be performed. The omission of specific statements of duties does not exclude them from the position if the work is similar, related, or a logical assignment to the position". That's boilerplate-ish but it's part of the description. It's not a list of duties, it's a disclaimer. Should we keep? It's substantive? It's more of a generic statement. The instruction: Remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. This line is not exactly
for prose. Do NOT repeat job title as heading. Do NOT put Job ID etc. Remove boilerplate, navigation, legal, EEO, equal-opportunity, scam-warning, duplicated lines, application instructions. Preserve all substantive info. Include a section only when posting has real, specific content for it — never emit heading followed by filler/placeholder text. Prefer few substantive sections over many thin ones. We need to parse the posting. Content: Position Summary: paragraph about inclusive environment, fairness, equity, inclusion, valuing diversity, supporting educators, induction, mentorship, professional development, growth, supporting whole child, trusting culture. Essential Functions & Responsibilities: bullet list (though not bullet but sentences). It says: Develop and teach engaging group lessons that: (list). Then bullet-like items: Establish routines and encourage development of strong fundamental musical skills; Incorporate a variety of strategies (movement, ear training, music reading, bowing/plucking) and activities (exercises, games, demonstration, listening, etc); Maintain excellent classroom management; Adapt to the needs of students at various levels and with various learning styles; Encourage peer teaching; Collaborate closely with the administration and faculty to achieve program-wide learning goals; Maintaining a positive and nurturing classroom environment; Set and maintain high standards for student behavior and music learning; Enforce program rules and policies. Qualifications And Skills: list: Excellent musicianship and artistry as a teacher/performer; Strong understanding of violia pedagogy (typo: violia? but keep as is); Strong commitment to El Sistema’s philosophy of social change through music; Experience working with children grades 3rd-8th grade from diverse ethnic and economic backgrounds; Strong interpersonal and communication skills; Self-motivated and willing to collaborate in a team-teaching environment; At least 2 years of prior teaching experience preferred; Bachelor’s or equivalent degree in Music Performance or Music Education. Terms Of Employment: Position Type: Part Time; School Year Schedule / Up to 19 work hours per week; Monday, Tuesday, Thursday & Friday - 1:00pm-5:45pm; FLSA Classification: Non Exempt; Union Status: Non Union; Benefits: Non Benefits Eligible position. Physical Requirements: description: Mobility: Frequent walking, standing, and navigating stairs. Lifting/Strength: Ability to lift, push, pull, or carry objects ranging from 10 to 30 lbs (e.g., books, supplies, equipment). Physical Dexterity: Bending, crouching, kneeling, stooping, and reaching to assist students. Stationary Tasks: Remaining in a stationary position (sitting/standing) for long periods. Reporting Relationships: Position Reports to: The Director of El Sistema - Somerville. Then EEO statement: The Somerville Public Schools does not discriminate... (boilerplate). Remove. We need to decide sections: About the role (position summary). Responsibilities (essential functions). Requirements (maybe combine qualifications and skills? The spec says we have separate headings for Qualifications and Skills. But we can combine if content thin? The instruction: Prefer a few substantive sections over many thin ones. So we could have sections: About the role, Responsibilities, Qualifications (including skills), Terms of Employment (maybe schedule, benefits, pay). However we have separate headings for Benefits, Pay, Schedule. We need to include a section only when posting has real, specific content for it. The posting includes Schedule (Part Time, up to 19 hrs per week, days/times). It includes Benefits: Non Benefits Eligible position. It does NOT include Pay (no salary). So we should not create Pay section because no specific pay info. Benefits: we have "Non Benefits Eligible position" which is specific content (though it's a statement that it's not benefits eligible). That is substantive; we should include Benefits section with that statement. Schedule: we have specifics, include Schedule section. We could also include a Requirements section for things like physical requirements? But maybe we can incorporate physical requirements into Responsibilities? Not exactly. Could create a Requirements section for qualifications (education, experience) and maybe physical requirements? But we have Qualifications and Skills headings separate. We could combine Qualifications and Skills into one section titled Qualifications (including skills). Or we could have two sections: Qualifications and Skills. But the instruction says prefer few substantive sections over many thin ones. So better to combine. Thus sections: About the role (position summary). Responsibilities (essential functions). Qualifications (including skills and education/experience). Benefits. Schedule. Possibly also Reporting Relationships? Could be part of About the role or Responsibilities? Might be its own section but not in list of allowed headings. The allowed headings are only those listed: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. So we cannot add Reporting Relationships as a heading; we could fold that into About the role or Responsibilities as prose. Similarly Physical Requirements could be folded into Responsibilities or Requirements? There is a Requirements heading allowed. We could use Requirements for physical requirements and maybe also for qualifications? But we already have Qualifications. Perhaps we use Requirements for physical requirements and maybe other mandatory requirements (like eligibility to work?). But we have qualifications already covering education/experience. The spec says we can use Requirements heading for any list of duties/requirements/benefits. So we could put physical requirements under Requirements. However we also have Qualifications and Skills separate. To avoid many thin sections, we could combine Qualifications and Skills into one Qualifications section, and put physical requirements under Requirements. That yields sections: About the role, Responsibilities, Qualifications, Requirements, Benefits, Schedule. That's six sections, maybe okay. But we could also merge Requirements into Qualifications if we think it's thin. However physical requirements are substantive; we could include them under Responsibilities? Not exactly responsibilities but could be considered job demands. The spec says we can use
- for any list of duties/requirements/benefits. So we could put physical requirements as a list under Responsibilities? Might be okay but better to have Requirements.
We need to avoid filler like "commensurate with experience". Not present.
Now we need to output HTML fragment only, no /, no markdown fences.
We'll produce:
About the role
Somerville Public Schools strives to create an inclusive and racially affirming environment that welcomes and values the diversity of our staff and students. We foster fairness, equity, and inclusion to create a workplace environment where everyone is treated with respect and dignity. We welcome and value different perspectives and experiences in our staff, recognizing the powerful impact that a diverse workforce has on all students. We are committed to supporting educators through a strong induction and mentorship program, educator-driven professional development, and opportunities for professional growth and advancement. As a district, we are also committed to supporting the whole child by promoting a trusting, mutually respectful and inspiring culture that values the individuality of our students and the professionalism of the field.
Responsibilities
- Develop and teach engaging group lessons that establish routines and encourage development of strong fundamental musical skills
- Incorporate a variety of strategies (movement, ear training, music reading, bowing/plucking) and activities (exercises, games, demonstration, listening, etc)
- Maintain excellent classroom management
- Adapt to the needs of students at various levels and with various learning styles
- Encourage peer teaching
- Collaborate closely with the administration and faculty to achieve program-wide learning goals
- Maintain a positive and nurturing classroom environment
- Set and maintain high standards for student behavior and music learning
- Enforce program rules and policies
Qualifications
- Excellent musicianship and artistry as a teacher/performer
- Strong understanding of viola pedagogy
- Strong commitment to El Sistema’s philosophy of social change through music
- Experience working with children grades 3rd‑8th from diverse ethnic and economic backgrounds
- Strong interpersonal and communication skills
- Self‑motivated and willing to collaborate in a team‑teaching environment
- At least 2 years of prior teaching experience preferred
- Bachelor’s or equivalent degree in Music Performance or Music Education
Requirements
- Mobility: Frequent walking, standing, and navigating stairs
- Lifting/Strength: Ability to lift, push, pull, or carry objects ranging from 10 to 30 lbs (e.g., books, supplies, equipment)
- Physical Dexterity: Bending, crouching, kneeling, stooping, and reaching to assist students
- Stationary Tasks: Remaining in a stationary position (sitting/standing) for long periods
Benefits
Non Benefits Eligible position
Schedule
Part‑time, up to 19 work hours per week; Monday, Tuesday, Thursday & Friday – 1:00 pm‑5:45 pm (School Year)
We need to ensure we didn't repeat job title. No mention of Pay. No mention of EEO. We removed duplicated lines. Ensure we didn't include any boilerplate like "The Somerville Public Schools does not discriminate...". Good. Check that we preserved all substantive info: Position summary captured. Responsibilities captured all bullet points. Qualifications captured all listed. Requirements captured physical demands. Benefits captured "Non Benefits Eligible position". Schedule captured part-time schedule. Reporting Relationships omitted but we could fold into About the role? Not required. The spec says preserve ALL substantive information; do NOT invent or summarize away detail. Reporting Relationships is substantive: "Position Reports to: The Director of El Sistema - Somerville". We omitted it. That would be losing substantive info. We need to include it somewhere. Where can we put? Not a heading allowed, but we can fold into About the role or Responsibilities as prose. Probably best to add a sentence in About the role or Responsibilities. Since it's about reporting line, maybe add to About the role after the summary. Let's add a sentence: "The position reports to the Director of El Sistema - Somerville." That preserves info. Also we might need to include "FLSA Classification: Non Exempt" and "Union Status: Non Union". Those are substantive. Where to put? Could be in About the role or Responsibilities? Could add to About the role as additional sentences. Or we could create a separate section? Not allowed headings besides those. Could add to About the role or Responsibilities. Probably About the role is fine. We also have "Position Type: Part Time" already captured in Schedule. Good. We need to ensure we didn't lose any substantive info: The position summary includes mention of supporting educators, induction, mentorship, professional development, growth, supporting whole child, trusting culture. We captured that. We also have "Essential Functions & Responsibilities The essential functions or responsibilities listed below are intended only as illustrations of the various types of work that may be performed. The omission of specific statements of duties does not exclude them from the position if the work is similar, related, or a logical assignment to the position". That's boilerplate-ish but it's part of the description. It's not a list of duties, it's a disclaimer. Should we keep? It's substantive? It's more of a generic statement. The instruction: Remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. This line is not exactly