Piano Teacher Store 028

We need to output HTML fragment with sections: About the role? Actually we need to use headings for sections like About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We must include only sections that have real specific content. Let's parse the posting. Content: - Intro paragraph about Music & Arts, mission, etc. Could be "About the role"? Actually "What You'll Do" is responsibilities. - "What You'll Do:" bullet list: Teach music lessons..., Build positive relationships..., Partner with store teams..., Share your musical expertise... - "Minimum Requirements:" list: Bachelor’s Degree in Music Education, Music Performance, or equivalent experience. 2 years of music teaching experience. - "Preferred Qualifications:" list: Advanced degrees (Master’s or Doctoral) in Music. Professional teaching memberships or certifications. 8+ years of teaching experience, especially with multiple instruments (list many instruments). - "About Music & Arts": description of company history, mission, etc. - "Why Music & Arts?" includes benefits: gig leave, robust benefits and perks, including 401K plus company match, employee discount program, and more. - There's also a statement about pay ranges not reflective, etc. That's pay info but says not necessarily reflective, etc. It says "The pay range(s) listed are provided in compliance with state specific laws. Pay ranges may be different in other locations." However no actual pay range numbers given. So we cannot create Pay section because no specific pay range. The instruction: never create Pay/Schedule/Benefits sections unless the posting actually states them. Benefits: they mention robust benefits and perks, including 401K plus company match, employee discount program, and more. That's specific enough? It mentions specific benefits: 401K plus company match, employee discount program. So we can include Benefits section. - Schedule: not mentioned. - Skills: not explicitly listed; maybe we could infer but we shouldn't invent. So no Skills section. - Qualifications: we have Minimum Requirements and Preferred Qualifications. Could combine into Requirements and Qualifications sections. The instruction: use headings for Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We have Requirements (minimum) and Qualifications (preferred). We'll output those. - About the role: maybe we can have an "About the role" section summarizing the role description? But we already have Responsibilities. The intro paragraph about mission could be considered "About the role"? However the instruction: "use

for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." So we can include About the role if there is real specific content. The intro paragraph about Music & Arts providing tools and support, etc. That's more about the company, not the role. But we could treat that as About the role? Might be better to have About the role summarizing the role: "As a Music Teacher, you will create an engaging, supportive, and safe learning environment where students thrive." That's from responsibilities. But we already have Responsibilities section with bullet list. So About the role could be a short paragraph describing the role overall. The posting includes: "We are looking for educators who are not only skilled musicians but also dedicated to empowering learners." That's about the role. Also "We believe that private lessons are the building blocks..." That's about the role. So we can include About the role. - Responsibilities: we have bullet list under "What You'll Do:". - Requirements: Minimum Requirements. - Qualifications: Preferred Qualifications. - Benefits: from Why Music & Arts? includes gig leave, 401K plus company match, employee discount program. - Pay: not specific, so omit. - Schedule: not mentioned, omit. - Skills: not mentioned, omit. We must preserve all substantive information; do not invent or summarize away detail. So we need to keep the list of instruments in Preferred Qualifications exactly as given. We need to remove boilerplate: cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. At the end there is EEO statement and accommodation request. That's boilerplate; we should remove it. Also remove lines like "The job posting is not necessarily reflective of actual compensation..." that's pay disclaimer; but we are omitting Pay section anyway, but we might still need to keep that statement? It's about pay, but we are not including Pay section; however the instruction says preserve ALL substantive information; do NOT invent or summarize away detail. If we omit the Pay section, we are omitting that statement. But is that substantive? It's a disclaimer about pay. Since we are not including Pay section because no specific pay range, but the disclaimer is still about pay. The instruction: "never create Pay/Schedule/Benefits sections unless the posting actually states them." It doesn't say we must include pay disclaimer if we omit Pay section. However "Preserve ALL substantive information" suggests we should keep that disclaimer somewhere. But where? Could we include it as a paragraph under Benefits? Not appropriate. Could we include a general note? The instruction says we should not create Pay section unless posting actually states them. The posting does state something about pay (disclaimer). But it's not a specific pay range. The instruction about Pay section: "never create Pay/Schedule/Benefits sections unless the posting actually states them." It doesn't forbid including a Pay section with a disclaimer if there is any pay-related statement. However they also say "Prefer a few substantive sections over many thin ones." And "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')". The disclaimer is not filler? It's a statement about pay ranges not being reflective. It's somewhat vague but still specific. However it's not a concrete pay range. The instruction says never emit a heading followed by filler/placeholder text like "commensurate with experience", "not specified", etc. The disclaimer is not exactly those but it's still vague. Safer to omit Pay section entirely, as there is no specific pay range. The disclaimer might be considered boilerplate? It's a legal disclaimer about pay. Might be considered boilerplate? The instruction says remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate. This is a legal disclaimer about pay, could be considered legal boilerplate. So we can remove it. Thus we will omit Pay section. Now we need to output only HTML fragment, no /, no markdown. We'll produce something like:

About the role

At Music & Arts, we provide the tools and support for you to focus on what matters most: teaching and inspiring students. With robust benefits, a commitment to innovation, and opportunities to grow your career, you’ll find a rewarding and impactful role here. We are looking for educators who are not only skilled musicians but also dedicated to empowering learners. We believe that private lessons are the building blocks to a lifelong relationship with music. Our strong commitment to music education is fundamental to our business, and we work hard to find instructors who are experts in their instrument. We take care of all the administrative work so you can do what you do best: inspire learning and creating the next generation of musicians!

Responsibilities

• Teach music lessons to students of varying ages and skill levels.
• Build positive relationships with students and parents through regular communication, goal-setting, and progress updates.
• Partner with store teams to schedule lessons and encourage student retention.
• Share your musical expertise to inspire students and foster their growth.

Requirements

• Bachelor’s Degree in Music Education, Music Performance, or equivalent experience.
• 2 years of music teaching experience.

Qualifications

• Advanced degrees (Master’s or Doctoral) in Music.
• Professional teaching memberships or certifications.
• 8+ years of teaching experience, especially with multiple instruments (banjo, baritone, bass clarinet, bass guitar, bassoon, cello, clarinet, flute, French horn, guitar, mandolin, oboe, percussion, piano, piccolo, saxophone, string bass, trombone, trumpet, tuba, ukulele, viola, violin, and voice).

Benefits

• Gig leave – take time off to share your music with the world and return to your job after your tour.
• 401K plus company match.
• Employee discount program.
• Robust benefits and perks (as described).

We need to ensure we didn't miss any substantive info: The "Why Music & Arts?" also mentions "robust benefits and perks, including 401K plus company match, employee discount program, and more." We captured gig leave, 401K, employee discount. The "and more" is vague; we could include a line "Robust benefits and perks" but that's vague. Might be okay to include as a bullet: "Robust benefits and perks". However that's somewhat generic but it's from the posting. It's not filler like "varies". It's a statement. We'll include it. Also we included the introductory paragraph under About the role. Did we miss any other substantive content? The "About Music & Arts" section includes history etc. That's substantive but not about the role. Should we include that? Possibly as "About Music & Arts" but not in the prescribed headings. The instruction only gave examples of headings but didn't forbid other headings? It says "use

for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." It implies we should use those headings for sections. It didn't say we cannot add other headings, but we should follow the pattern. The "About Music & Arts" is company description; could be considered "About the role"? Not exactly. But we could incorporate that into About the role section? The About the role we already used intro paragraph about mission and support. The company history might be considered extra but not required. The instruction: "Preserve ALL substantive information". If we omit the company history, we lose substantive info. So we need to include it somewhere. Perhaps we can add an "About Music & Arts" section with heading

About Music & Arts

. The instruction didn't forbid other headings; it gave examples. It said use

for section headings (e.g. About the role, Responsibilities...). It didn't say we cannot use other headings. So we can add About Music & Arts. Thus we will include About Music & Arts section with the history paragraph. Let's capture that paragraph: "About Music & Arts Music & Arts embodies the world of creativity and music by encouraging our teammates to find their own individual sound. We strive to create lifelong musicians and make a difference in the world by enabling musicians and non-musicians alike to experience the almost indescribable happiness that comes from playing an instrument. We believe in putting our customers first, engaging with respect and integrity and fulfilling our mission with passion. The first Music & Arts was located in a small house in Bethesda, MD and run by founder Benjamin O'Brien. When Music & Arts opened its doors in 1952, we offered printed music, music lessons, dance lessons, and art supplies. Ben decided shortly after opening his business that he wanted to focus on music to better serve his customers -- a decision that remains intact to this day. Since the 1990's, Music & Arts has expanded nationwide through organic growth and a series of acquisitions and mergers with other music dealers. In 2