Youth Mentor, Alpha - $100,000/year USD

We need to output HTML fragment with sections: headings

for sections like About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. Only include sections that have real specific content. We must not repeat job title as heading. Must not include Job ID etc. Remove boilerplate, navigation, legal, EEO, etc. Must preserve all substantive info. We need to parse the posting. Key info: - Quote at top: not needed? It's part of description but maybe not needed as heading. Could be part of About the role? Might be considered intro. We can include as

before sections. - The posting includes description: "Alpha is hiring. The most supportive thing you can do..." etc. That's about role. - Then "What You Will Be Doing" list. - Then "What You Won’t Be Doing" list. - Then "Youth Mentor" heading? Actually "Youth Mentor" appears as a title? Might be role name. - Then "Key Responsibilities" bullet. - Then "Basic Requirements" list. - Then "Nice-to-have Requirements" list. - Then "About Alpha" paragraph. - Then "Working with us": full-time, W2 employee position with immediate access to benefits (link). All roles are year-long positions. The compensation level for this role is $100,000 USD/year. The payment period is weekly. Also mention Crossover Job Code (should be dropped as minor metadata). Also mention relocation support provided. - Also list of locations: Scottsdale, AZ; Oklahoma City and Tulsa, OK; Nashville, TN; and Austin, Dallas, and Plano, TX. - Also mention "If you're interested in another Alpha campus, apply anyway and tell us your preferred location—we'll consider you for the appropriate opening." That's application instruction? Might be considered boilerplate? It's about location preference; maybe keep as part of location info. - Also mention "If you have coached youth sports, run a cabin at camp, or tutored a kid who wanted to quit, the last step before an offer is a full day on campus coaching real Alpha students. If that day is the part you want most, apply today." That's also application instruction? Might be considered call to action; we should drop application instructions per instruction: "Remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions." So we should drop sentences that are explicitly about applying (e.g., "If you're interested... apply anyway", "If that day is the part you want most, apply today.", "Hit the Apply button if you found this interesting..."). - Also drop the link to benefits? It's a URL; maybe keep as part of benefits description? It's a link; we could keep as plain text? Probably we can keep the mention of benefits but not the URL? The instruction: preserve ALL substantive information; do NOT invent or summarize away detail. The link is substantive? It's a reference to benefits details. Might be considered minor metadata? It's a URL; maybe we can keep as plain text but it's not heading. Could be considered part of Benefits section. - Also "Crossover Job Code: LJ-4415-US-Pearland-YouthMentor.003" is minor metadata; drop. - Also "All roles are year-long positions." That's schedule? Could be part of Schedule section? It's about duration. Could be considered schedule info (full-time, year-long). We have Pay and Schedule sections only if posting actually states them. Pay: "$100,000 USD/year" and "payment period is weekly". So we need Pay section. Schedule: "full-time, on-site role", "year-long positions". Also maybe mention "full-time, W2 employee position". So we can create Schedule section with full-time, on-site, year-long. - Benefits: "immediate access to benefits (link)". Also maybe mention relocation support provided. So Benefits section. - Responsibilities: we have "What You Will Be Doing" list, also "Key Responsibilities" bullet, also "What You Won’t Be Doing" list (maybe as responsibilities negative). We should combine into Responsibilities section with

• . Should we separate "What You Won’t Be Doing"? Could be part of responsibilities but maybe better as separate section? The instruction: prefer a few substantive sections over many thin ones. Could combine both doing and not doing under Responsibilities. Or we could have Responsibilities and maybe "What You Won’t Be Doing" as a subsection? But we only have headings list; we could create a section "Responsibilities" and include both doing and not doing as items, maybe with note. But we need to preserve all substantive info; we can include both as list items, maybe prefix with "Will:" and "Will not:". - Requirements: we have Basic Requirements and Nice-to-have Requirements. Could combine into Requirements section with required and preferred. Or separate into Requirements and Qualifications? The headings list includes Requirements, Qualifications, Skills. We need to decide. The posting has "Basic Requirements" and "Nice-to-have Requirements". Also "Key Responsibilities". Also "Youth Mentor". Also "About Alpha". Also "Working with us". So we can map: - About the role: maybe intro paragraph(s) describing role, mission, quote. - Responsibilities: combine What You Will Be Doing, What You Won’t Be Doing, Key Responsibilities. - Requirements: Basic Requirements (must have). Could also include Nice-to-have as "Preferred Qualifications" maybe under Qualifications. - Skills: maybe list of skills like "Stage presence strong enough to hold a room of 12-year-olds for an hour without raising your voice", "Comfortable letting adaptive learning software deliver the academic instruction while you own motivation and life-skills coaching", "Personal record of high achievement", etc. Could be part of Requirements. - Benefits: immediate access to benefits, relocation support provided. - Pay: $100,000 USD/year, weekly payment. - Schedule: full-time, on-site, year-long. We must not create sections with filler like "commensurate with experience". We have actual specifics. We must not repeat job title as heading. The job title is likely "Youth Mentor". We should not use that as heading. We must not put Job ID/requisition numbers as headings. We must output only HTML fragment, no /, no markdown. Let's craft. First, maybe an introductory

  with the quote and description? The quote is from Braden, Head Guide, Alpha Austin. Could be included as

  with quote. Then maybe a

  summarizing the role: "Alpha is hiring..." etc. But we must preserve all substantive info; we can include the descriptive paragraphs as

  before sections. We need to decide where to put the quote. Could be a ? Not in allowed tags; only

  ,

  • ,

    . So we can put quote inside

    with maybe italic? Not needed. We'll produce:

    “We are never going to lower the standard for any kid — instead we're going to raise the support to help them get there.” — Braden, Head Guide, Alpha Austin

    Alpha is hiring. The most supportive thing you can do for a student who hits 99% of their weekly goal is refuse to call it done. Not because you are indifferent, but because you believe they can clear the bar, and lowering it is the real failure. You are not a teacher. At Alpha, students learn academics through AI-powered adaptive learning apps. No lectures. No textbooks. No whiteboard. Motivation and life skills, the two things schools normally squeeze into the margins, are the whole job here. Picture a Tuesday. Half your day you run one-hour workshops for a K-8 cohort on public speaking, focus, and how to give and receive real feedback. The other half you sit with those same students one-on-one or in small groups, read their Coachbot analytics, and push each of them to 100% of their weekly app goals, using school currency, leaderboards, and the relationship you have built with them to break through resistance. Your quarter comes down to three numbers: every student in your cohort hits their weekly app goals, every student passes the Test2Pass mastery check for each workshop, and 90% or more say they love you. Missing one of the three is missing the job. The payoff is the day a student who spent September insisting they were bad at math asks you to raise their goal. This is a full-time, on-site role at one of Alpha's campuses. We recruit nationally, so job boards may display this opportunity in nearby cities that do not have a campus yet. Current openings for this salary tier are available in Scottsdale, AZ; Oklahoma City and Tulsa, OK; Nashville, TN; and Austin, Dallas, and Plano, TX. If you're interested in another Alpha campus, apply anyway and tell us your preferred location—we'll consider you for the appropriate opening.

    But we need to drop application instruction sentences: "If you're interested in another Alpha campus, apply anyway and tell us your preferred location—we'll consider you for the appropriate opening." That's application instruction; drop. Also "If you have coached youth sports, run a cabin at camp, or tutored a kid who wanted to quit, the last step before an offer is a full day on campus coaching real Alpha students. If that day is the part you want most, apply today." Drop. Also "Hit the Apply button if you found this interesting and want to learn more. We look forward to meeting you!" Drop. Thus we need to remove those sentences. We also need to drop the link to benefits? It's not application instruction; it's benefits info. Keep but maybe as plain text. We also need to drop "Crossover Job Code: ..." as minor metadata. Now after intro, we create sections. Section About the role? Actually we already have intro describing role. Could treat that as About the role. But we already used intro paragraphs; we could make a heading

    About the role

    and then put the descriptive paragraphs inside. However the instruction: "use

    for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." So we should use those headings. The intro could be under About the role. Thus we will have:

    About the role

    “We are never going to lower the standard for any kid — instead we're going to raise the support to help them get there.” — Braden, Head Guide, Alpha Austin

    Alpha is hiring. The most supportive thing you can do for a student who hits 99% of their weekly goal is refuse to call it done. Not because you are indifferent, but because you believe they can clear the bar, and lowering it is the real failure. You are not a teacher. At Alpha, students learn academics through AI-powered adaptive learning apps. No lectures. No textbooks. No whiteboard. Motivation and life skills, the two things schools normally squeeze into the margins, are the whole job here. Picture a Tuesday. Half your day you run one-hour workshops for a K-8 cohort on public speaking, focus, and how to give and receive real feedback. The other half you sit with those same students one-on-one or in small groups, read their Coachbot analytics, and push each of them to 100% of their weekly app goals, using school currency, leaderboards, and the relationship you have built with them to break through resistance. Your quarter comes down to three numbers: every student in your cohort hits their weekly app goals, every student passes the Test2Pass mastery check for each workshop, and 90% or more say they love you. Missing one of the three is missing the job. The payoff is the day a student who spent September insisting they were bad at math asks you to raise their goal. This is a full-time, on-site role at one of Alpha's campuses. We recruit nationally, so job boards may display this opportunity in