Tutor, Alpha - $100,000/year USD
for sections like About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. Use - for any list of duties/requirements/benefits, and
for prose. Do NOT repeat job title as heading. Do NOT put Job ID / requisition numbers as headings — fold minor metadata into short
or drop it. Preserve ALL substantive information; do NOT invent or summarize away detail. Remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. IMPORTANT: 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") and never create Pay/Schedule/Benefits sections unless the posting actually states them. Prefer a few substantive sections over many thin ones. Output ONLY the HTML fragment — no /, no markdown code fences.
We need to parse the posting.
Key content:
- Quote from Katie: "The sheer amount of time I get back from not having to make daily lesson plans and grade papers is huge." — Katie, Lead Guide, Alpha Denver
- "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. 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"
Then "What You Will Be Doing" bullet list:
- Leading one-hour life-skills workshops for K-8 cohorts on public speaking, focus, and giving and receiving feedback
- Running daily 1:1 and small-group motivation sessions that push every student to 100% of their weekly app goals, using Coachbot analytics and Alpha's incentive systems (school currency, leaderboards)
- Administering the Test2Pass mastery assessment for each life skill, then re-coaching any student who does not pass until they do
- Adapting the workshop playbook, and building new sessions when you find a gap, so the same material lands with a kindergartener and with an 8th grader
- Being both the adult who holds the standard and the adult your students choose to talk to
Then "What You Won’t Be Doing":
- Writing math and reading lesson plans, grading homework, or lecturing at a whiteboard; academic instruction lives in the apps
- Running standardized test prep or answering for a class-wide test score
- Handling parent conferences, emails, and complaints; campus leadership owns all parent-facing work
- Crowd-controlling 30 students at once; cohorts are small and behavior work here is 1:1 coaching
- Supervising kids at computers; motivation here is active and personal
Then "Tutor" (maybe heading? Actually "Tutor" appears as a label before "Key Responsibilities". Might be a heading but we should not repeat job title; "Tutor" is not the job title? The job title maybe "Tutor"? The posting says "Tutor" then "Key Responsibilities". We should not repeat the job title as a heading. The job title is maybe "Tutor"? Actually the posting says "Tutor" then "Key Responsibilities". The job title might be "Tutor". We should not repeat the job title as heading. So we should not output a heading "Tutor". Instead we can treat "Key Responsibilities" as a section heading? The instruction says use
for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). So we can map "What You Will Be Doing" to Responsibilities. "What You Won’t Be Doing" maybe also part of Responsibilities? Could be separate but we can combine? The instruction: Prefer a few substantive sections over many thin ones. So maybe we have sections: About the role (intro paragraph), Responsibilities (list of duties), Requirements (basic requirements + nice-to-have), Qualifications (maybe same as Requirements?), Skills (maybe not explicit), Benefits (maybe not explicit), Pay (we have compensation: $100,000 USD/year, weekly payment), Schedule (full-time, on-site). Also location info.
We need to include sections only if posting has real specific content.
Let's extract:
About the role: The introductory paragraph(s) describing role, mission, etc. Could be the first paragraph after quote? Actually the quote is from Katie. Then "Alpha is hiring..." etc. That's about the role. We'll put that in
maybe multiple paragraphs.
Responsibilities: The "What You Will Be Doing" list (bullet points). Also maybe "What You Won’t Be Doing" could be part of responsibilities but it's negative; we could include as part of responsibilities but maybe better to include as part of responsibilities as a list of what not to do? The instruction says use
- for any list of duties/requirements/benefits. So we can have two lists: duties and non-duties? But we could combine into one responsibilities section with subheadings? However we cannot add extra headings besides the allowed ones? The instruction says use
for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). It doesn't forbid other headings, but says use for section headings (e.g. those). Likely they expect only those headings. So we should not create custom headings like "What You Won’t Be Doing". Instead we could incorporate that into responsibilities as prose or list items prefixed with "Not..." but better to keep as list items under responsibilities? Could be separate bullet list but still under same heading Responsibilities. That's okay.
Requirements: Basic Requirements list (relocation support, location willingness, Bachelor's degree, 3 years experience, comfort with software, personal record of high achievement, stage presence, legal right to work). Also Nice-to-have Requirements list.
Qualifications: Might overlap with Requirements; but we could treat Requirements as qualifications. The instruction says we can have both Requirements and Qualifications sections if there is distinct content. But we might combine to avoid thin sections. However we have both basic and nice-to-have; we could put basic under Requirements, nice-to-have under Skills? Or Qualifications? The instruction says Skills section for skills. Nice-to-have includes youth athletics coaching, debate, drama, camp leadership, after-school program work where you were personally accountable for kids hitting a specific goal; experience teaching SEL or durable-skills curricula; a student you can name who went from resistant to engaged; daily use of generative AI tools. Those are more like skills/experience. Could go under Skills.
But we need to avoid filler sections. Let's decide:
- About the role: intro paragraph(s).
- Responsibilities: list of duties (What You Will Be Doing) plus maybe also list of what you won't be doing (as notes).
- Requirements: basic requirements (location willingness, Bachelor's degree, 3 years experience, comfort with software, personal record of high achievement, stage presence, legal right to work). Also relocation support? That's a benefit? Actually relocation support provided is mentioned under Basic Requirements: "Willing to work in person at an Alpha campus in Scottsdale, AZ; Oklahoma City or Tulsa, OK; Nashville, TN; or Austin, Dallas, or Plano, TX - relocation support provided". So relocation support is a benefit? Could be under Benefits. But we can keep it in Requirements as a note.
- Skills: nice-to-have requirements (youth athletics coaching, debate, drama, camp leadership, after-school program work where you were personally accountable for kids hitting a specific goal; experience teaching SEL or durable-skills curricula; a student you can name who went from resistant or checked out to fully engaged, and the specific thing you did; daily use of generative AI tools such as ChatGPT, Claude, or Gemini).
- Pay: compensation level $100,000 USD/year, payment period weekly.
- Schedule: full-time, on-site role.
- Benefits: maybe immediate access to benefits, W2 employee, year-long positions, link to benefits. Also maybe "All roles are year-long positions." That's a benefit? Could be under Benefits.
We need to avoid filler like "commensurate with experience". Not present.
We must not include Job ID / requisition numbers as headings; we have "Crossover Job Code: LJ-4415-US-Scottsda-Tutor.001". That's minor metadata; we should fold into a short
or drop it. Probably drop it.
We must remove boilerplate like "Working with us This is a 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. Consult www.crossover.com/help-and-faqs for more details on this topic." That's actually relevant for Pay, Benefits, Schedule. We'll extract.
We must remove duplicated lines.
Now craft HTML.
We'll start with
About the role
then ...
.
We need to preserve all substantive information. Let's compose About the role paragraph(s):
From the posting:
"The sheer amount of time I get back from not having to make daily lesson plans and grade papers is huge." — Katie, Lead Guide, Alpha Denver
"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
for prose. Do NOT repeat job title as heading. Do NOT put Job ID / requisition numbers as headings — fold minor metadata into short
or drop it. Preserve ALL substantive information; do NOT invent or summarize away detail. Remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. IMPORTANT: 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") and never create Pay/Schedule/Benefits sections unless the posting actually states them. Prefer a few substantive sections over many thin ones. Output ONLY the HTML fragment — no /, no markdown code fences. We need to parse the posting. Key content: - Quote from Katie: "The sheer amount of time I get back from not having to make daily lesson plans and grade papers is huge." — Katie, Lead Guide, Alpha Denver - "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. 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" Then "What You Will Be Doing" bullet list: - Leading one-hour life-skills workshops for K-8 cohorts on public speaking, focus, and giving and receiving feedback - Running daily 1:1 and small-group motivation sessions that push every student to 100% of their weekly app goals, using Coachbot analytics and Alpha's incentive systems (school currency, leaderboards) - Administering the Test2Pass mastery assessment for each life skill, then re-coaching any student who does not pass until they do - Adapting the workshop playbook, and building new sessions when you find a gap, so the same material lands with a kindergartener and with an 8th grader - Being both the adult who holds the standard and the adult your students choose to talk to Then "What You Won’t Be Doing": - Writing math and reading lesson plans, grading homework, or lecturing at a whiteboard; academic instruction lives in the apps - Running standardized test prep or answering for a class-wide test score - Handling parent conferences, emails, and complaints; campus leadership owns all parent-facing work - Crowd-controlling 30 students at once; cohorts are small and behavior work here is 1:1 coaching - Supervising kids at computers; motivation here is active and personal Then "Tutor" (maybe heading? Actually "Tutor" appears as a label before "Key Responsibilities". Might be a heading but we should not repeat job title; "Tutor" is not the job title? The job title maybe "Tutor"? The posting says "Tutor" then "Key Responsibilities". We should not repeat the job title as a heading. The job title is maybe "Tutor"? Actually the posting says "Tutor" then "Key Responsibilities". The job title might be "Tutor". We should not repeat the job title as heading. So we should not output a heading "Tutor". Instead we can treat "Key Responsibilities" as a section heading? The instruction says use
for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). So we can map "What You Will Be Doing" to Responsibilities. "What You Won’t Be Doing" maybe also part of Responsibilities? Could be separate but we can combine? The instruction: Prefer a few substantive sections over many thin ones. So maybe we have sections: About the role (intro paragraph), Responsibilities (list of duties), Requirements (basic requirements + nice-to-have), Qualifications (maybe same as Requirements?), Skills (maybe not explicit), Benefits (maybe not explicit), Pay (we have compensation: $100,000 USD/year, weekly payment), Schedule (full-time, on-site). Also location info. We need to include sections only if posting has real specific content. Let's extract: About the role: The introductory paragraph(s) describing role, mission, etc. Could be the first paragraph after quote? Actually the quote is from Katie. Then "Alpha is hiring..." etc. That's about the role. We'll put that in
maybe multiple paragraphs. Responsibilities: The "What You Will Be Doing" list (bullet points). Also maybe "What You Won’t Be Doing" could be part of responsibilities but it's negative; we could include as part of responsibilities but maybe better to include as part of responsibilities as a list of what not to do? The instruction says use
- for any list of duties/requirements/benefits. So we can have two lists: duties and non-duties? But we could combine into one responsibilities section with subheadings? However we cannot add extra headings besides the allowed ones? The instruction says use
for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). It doesn't forbid other headings, but says use
for section headings (e.g. those). Likely they expect only those headings. So we should not create custom headings like "What You Won’t Be Doing". Instead we could incorporate that into responsibilities as prose or list items prefixed with "Not..." but better to keep as list items under responsibilities? Could be separate bullet list but still under same heading Responsibilities. That's okay. Requirements: Basic Requirements list (relocation support, location willingness, Bachelor's degree, 3 years experience, comfort with software, personal record of high achievement, stage presence, legal right to work). Also Nice-to-have Requirements list. Qualifications: Might overlap with Requirements; but we could treat Requirements as qualifications. The instruction says we can have both Requirements and Qualifications sections if there is distinct content. But we might combine to avoid thin sections. However we have both basic and nice-to-have; we could put basic under Requirements, nice-to-have under Skills? Or Qualifications? The instruction says Skills section for skills. Nice-to-have includes youth athletics coaching, debate, drama, camp leadership, after-school program work where you were personally accountable for kids hitting a specific goal; experience teaching SEL or durable-skills curricula; a student you can name who went from resistant to engaged; daily use of generative AI tools. Those are more like skills/experience. Could go under Skills. But we need to avoid filler sections. Let's decide: - About the role: intro paragraph(s). - Responsibilities: list of duties (What You Will Be Doing) plus maybe also list of what you won't be doing (as notes). - Requirements: basic requirements (location willingness, Bachelor's degree, 3 years experience, comfort with software, personal record of high achievement, stage presence, legal right to work). Also relocation support? That's a benefit? Actually relocation support provided is mentioned under Basic Requirements: "Willing to work in person at an Alpha campus in Scottsdale, AZ; Oklahoma City or Tulsa, OK; Nashville, TN; or Austin, Dallas, or Plano, TX - relocation support provided". So relocation support is a benefit? Could be under Benefits. But we can keep it in Requirements as a note. - Skills: nice-to-have requirements (youth athletics coaching, debate, drama, camp leadership, after-school program work where you were personally accountable for kids hitting a specific goal; experience teaching SEL or durable-skills curricula; a student you can name who went from resistant or checked out to fully engaged, and the specific thing you did; daily use of generative AI tools such as ChatGPT, Claude, or Gemini). - Pay: compensation level $100,000 USD/year, payment period weekly. - Schedule: full-time, on-site role. - Benefits: maybe immediate access to benefits, W2 employee, year-long positions, link to benefits. Also maybe "All roles are year-long positions." That's a benefit? Could be under Benefits. We need to avoid filler like "commensurate with experience". Not present. We must not include Job ID / requisition numbers as headings; we have "Crossover Job Code: LJ-4415-US-Scottsda-Tutor.001". That's minor metadata; we should fold into a short
or drop it. Probably drop it. We must remove boilerplate like "Working with us This is a 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. Consult www.crossover.com/help-and-faqs for more details on this topic." That's actually relevant for Pay, Benefits, Schedule. We'll extract. We must remove duplicated lines. Now craft HTML. We'll start with
About the role
then...
. We need to preserve all substantive information. Let's compose About the role paragraph(s): From the posting: "The sheer amount of time I get back from not having to make daily lesson plans and grade papers is huge." — Katie, Lead Guide, Alpha Denver "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