Piano Education Lead - Full-time, Los Angeles (Online Education)

We need to output HTML fragment with sections: About the role? Actually we have "About us" and "About the job". According to rules: use

for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). We should map content to appropriate headings. We have: - About us (company description) could be "About the role"? Actually "About us" is company description, not role. Could be "About the role"? But we have "About the job". Could treat as "About the role". The instruction: Use

for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). So we can include headings that match content: About the role (maybe combine About us and About the job). Responsibilities: maybe "What’s the work look like?" and first 30 days. Requirements: the three requirements bullet list. Qualifications: maybe professional pianist etc. Skills: maybe sight-read, improvise, multiple styles, performing experience, video lesson creation, etc. Benefits: we have 401(k) 4% match, healthcare, 20 days paid leave, sick leave, parental leave. Pay: they said not listing salary; we should NOT create Pay section unless posting actually states them. They said "We normally include salary for jobs but we aren’t listing a salary for this one". So we should NOT include Pay section. Schedule: they said normal working hours Monday-Friday, studio at least 80% of time. That's schedule info, we can include Schedule section. Also relocation info maybe not needed. We must not repeat job title as heading. Do not put Job ID. Remove boilerplate like application instructions, how to apply, etc. Also remove duplicated lines, cookie/navigation/legal/EEO etc. There's no explicit EEO but there is "Not based in Los Angeles? We'll cover your costs to relocate...". That's not boilerplate; it's relevant. Also "Not in the US? Unfortunately this job is only available for people legally able to work in the US." That's also relevant. We must preserve all substantive information. So we need to include details about responsibilities, requirements, qualifications, skills, benefits, schedule, relocation, work eligibility, etc. We must not invent or summarize away detail. Must keep specifics. We need to output only HTML fragment, no /, no markdown fences. Thus produce something like:

About the role

Pickup Music is a leading music-education company based in Los Angeles that has been growing steadily since 2016. We are the leaders in structured, long form learning with over 50,000 members for guitar, bass, piano and drums. We are an independent, bootstrapped company led by musicians.

Responsibilities

• Prepare and teach piano lessons on camera.
• Produce other teachers to create lessons.
• Manage the community of piano learners.
• Write, produce and film the world’s best piano curriculum (deep work).
• Direct and produce talent, see classes through to publish.
• Onboarding, teach a course, start work on first learning pathway (first 30 days).

Requirements

• Professional pianist: sight‑read, improvise fluently, play multiple styles, extensive performing experience.
• Preference for jazz pianists over classical pianists.
• Passionate about creating video lessons to teach beginner to intermediate students.
• Excited to work with a fast‑growing music technology company to build something special that helps tens of thousands of people learn music.

Qualifications

Extensive performing experience, ability to sight‑read and improvise across styles, experience teaching beginner to intermediate students, experience creating video lessons.

Skills

• Sight‑reading.
• Fluent improvisation.
• Multiple musical styles (jazz preference).
• Video lesson production and scripting.
• Community management.
• Production direction (directing and producing talent).

Benefits

• 401(k) 4% match.
• Healthcare.
• 20 days paid leave.
• Sick leave.
• Parental leave.

Schedule

Full‑time, Monday to Friday. Studio presence at least 80% of the time; remaining pre‑ and post‑production work can be done remotely.

Relocation & Eligibility

If not based in Los Angeles, relocation costs within the US will be covered. The role is only open to individuals legally authorized to work in the US; visa sponsorship is not provided and the position is not remote.

We must ensure we didn't include any boilerplate like "How to apply". We removed that. Also we removed duplicated lines like "About us" repeated. We kept substance. Check for any mention of salary: we omitted Pay section. Good. Check for any mention of "We normally include salary for jobs but we aren’t listing a salary for this one as we are open to applications of all experience levels." That's about pay but we are not creating Pay section. Should we include that info somewhere? The rule: "never create Pay/Schedule/Benefits sections unless the posting actually states them." It does state that they aren't listing salary. But we are not creating a Pay section; we could mention that salary is not disclosed in a paragraph maybe under About the role? However the rule says "Prefer a few substantive sections over many thin ones." It might be okay to include a note about salary not being listed in the About the role paragraph. But we must not invent or summarize away detail. The detail is that they aren't listing salary. Should we include that? Possibly we can add a sentence: "Salary is not disclosed in the posting; the company is open to discussing compensation based on experience." That's preserving the detail. However the rule says "never create Pay/Schedule/Benefits sections unless the posting actually states them." It doesn't forbid mentioning pay info elsewhere. So we could add a sentence in About the role or maybe a separate note. But we must avoid creating a Pay section. So we can add a short paragraph under About the role: "The posting does not list a specific salary; compensation will be discussed based on experience." That's preserving detail. Similarly, we might want to include the note about "We offer a 401(k) 4% match, healthcare, 20 days paid leave, sick leave, and parental leave." Already in Benefits. Also note about "We don’t expect you to hit the ground running. We’ll be coaching you through how to produce a class at Pickup Music." That's part of responsibilities or maybe a note. Could add to responsibilities. Also "We’ll be coaching you through how to produce a class at Pickup Music. You’ll learn from our other producers and we’ll iterate quickly from user feedback." Could be responsibilities. Also "Not based in Los Angeles? We’ll cover your costs to relocate to LA from within the US. Not in the US? Unfortunately this job is only available for people legally able to work in the US. We are not sponsoring visas for this role, and it is not a remote job." Already captured. Also "We offer a 401(k) 4% match, healthcare, 20 days paid leave, sick leave, and parental leave." Already. Also "What’s the work look like? At Pickup Music, we respect and allow time for our team members to shut out the noise, and focus on their deep, meaningful work. For you, this deep work will be primarily writing, producing and filming the world’s best piano curriculum." Already. Also "Here’s what your first 30 days will look like: Week 1: onboarding, where you can meet the team, learn our product and plan your first class with me. Week 2: teach a course, with another producer producing you, so you can see what it’s like to do a class end-to-end. Week 3: start work on your first learning pathway." Already. Also "Day to day, you’ll be working with our head of education and production teams. As well as being on camera, you will direct and produce talent and see classes through to publish." Already. Also "We don’t expect you to hit the ground running. We’ll be coaching you through how to produce a class at Pickup Music. You’ll learn from our other producers and we’ll iterate quickly from user feedback." Add. Also "Not based in Los Angeles? We’ll cover your costs to relocate to LA from within the US. Not in the US? Unfortunately this job is only available for people legally able to work in the US. We are not sponsoring visas for this role, and it is not a remote job." Already. Also "How to apply" etc removed. Also "The interview process will follow these steps: ..." That's application instructions; we should remove as per rule: remove application instructions. So we should omit that. Also "We’ll ask for three references to call including two people who have directly managed you and one person you have managed." That's also part of application process; remove. Thus final HTML includes sections: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Schedule, Relocation & Eligibility (maybe we could incorporate into About the role or Schedule? But it's substantive; we can keep as its own heading? The allowed headings list includes About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. It does not list Relocation & Eligibility. However we can still use

for any section heading? The instruction: "Use

for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." It gives examples but not exclusive. It says use

for section headings (e.g. those). Likely we should stick to those headings; but we can also create other headings if needed? The instruction 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; but we could also use other headings if needed? It says "Use

for section headings (e.g. ...)" which suggests we should use h3 for any section headings, and the examples are typical ones. It doesn't forbid other headings, but to be safe we could map relocation info under About the role or Schedule. However it's distinct enough to maybe be part of About the role (company location). Could add a paragraph under About the role about location and relocation. Similarly, eligibility (US work authorization) could be part of About the role. Thus we can avoid extra heading. Let's restructure: - About the role: includes company description, location, schedule, relocation, eligibility, salary not disclosed. - Responsibilities: as above. - Requirements: as above. - Qualifications: maybe combine with Requirements? But we can keep Qualifications separate. - Skills: as above. - Benefits: as above. We must not create Pay section. We must not create Schedule section separately if we included schedule in About the role. But the rule says "Prefer a few substantive sections over many thin ones." So maybe we keep Schedule separate? It's up to us. The examples include Schedule as a possible heading. Since we have schedule info, we could make a Schedule section. That's fine. Thus we will have sections: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Schedule. We'll embed location/rel