Head of Admissions, Alpha - $250,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 a 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 and extract sections.
The posting includes:
- Intro paragraph about Alpha School growth claim, description of job.
- Then "What You Will Be Doing" bullet list.
- Then "What You Won’t Be Doing" bullet list.
- Then "Head Of Admissions" maybe title? Actually "Head Of Admissions" is the role title.
- Then "Key Responsibilities" bullet (just one line? Actually "Grow enrollment at one Bay Area campus with families who will thrive in the Alpha model.") That's a responsibility.
- Then "Basic Requirements" bullet list.
- Then "Nice-to-have Requirements" bullet list.
- Then "About Alpha" paragraph.
- Then "Working with us" paragraph about full-time, W2 employee, benefits link, year-long positions, compensation $250,000 USD/year, payment period weekly, Crossover Job Code.
We need to produce sections: maybe "About the role", "Responsibilities", "Requirements", "Qualifications", "Skills", "Benefits", "Pay", "Schedule". But we should only include sections that have real specific content.
We have:
- About the role: we can combine intro description and maybe "About Alpha" as about the role? The instructions: use
for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). So we can decide which sections to include.
We have content for:
- About the role: description of job, mission, etc. Could be "About the role" heading.
- Responsibilities: "What You Will Be Doing" list, plus maybe "Key Responsibilities". Also "What You Won’t Be Doing" could be under responsibilities? Might be separate but we can combine.
- Requirements: "Basic Requirements" list.
- Qualifications: maybe "Nice-to-have Requirements" could be under Qualifications or Skills? Could be "Qualifications" for required, and "Nice-to-have" as "Preferred Qualifications". But we have only allowed headings: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We could map:
- Requirements: Basic Requirements (mandatory)
- Qualifications: Nice-to-have Requirements (preferred)
- Skills: maybe we can extract skills from responsibilities? But we could also omit if not specific.
- Benefits: we have benefits mention: immediate access to benefits (link). Also "All roles are year-long positions." That's maybe schedule? Actually schedule: work on-site five days a week, visible at drop-off, pick-up, evening events. That's schedule info.
- Pay: compensation $250,000 USD/year, payment period weekly.
- Schedule: work on-site at one campus five days a week, visible at drop-off, pick-up, evening events.
We need to ensure we don't create sections with filler like "not specified". We have actual content for Pay, Benefits, Schedule.
We need to avoid repeating job title as heading. So we won't put "Head Of Admissions" as heading.
We need to not put Job ID as heading; we can fold minor metadata into a short
or drop it. The Job Code: "Crossover Job Code: LJ-5811-US-SanRafae-HeadofAdmissio.010". We can drop it or include in a short p maybe under About the role? Probably drop.
We need to remove boilerplate like application instructions ("Hit the Apply button if you found this interesting...").
We need to preserve all substantive information.
Let's extract substantive content:
Intro paragraph:
"Alpha School students, on average, experience 2.4 to 2.6 times the academic growth of traditional school students" — Forbes Alpha is hiring. In the Bay Area, the strongest admissions people don't sell. They manage a waitlist, staff a committee, and protect a reputation built long before they arrived. This job is the reverse. In your market, almost no family has heard of us yet. You go find them. Alpha is a K-12 private school built on a claim we can prove: students complete core academics in two hours a day, learn faster than national benchmarks, and spend their afternoons on real skills rather than busywork. Bay Area parents are the hardest audience for that claim and the best one. Founders, engineers, physicians, and investors will not accept a warm tour and a mission statement. They will ask for the data, push on the trade-offs, and compare us to Nueva, Castilleja, Harker, Marin Country Day, and Branson in the same breath. Welcome that conversation. Be clear about what this is. It is a sales job with a mandate for selectivity. You generate your own demand: preschool and feeder-school relationships, community partnerships, local events, and referrals from families you have already earned. You carry a growth number. You also tell a family "no" when the model is wrong for their child, in a market where saying "no" to a well-connected parent carries consequences. Both halves are the job. One misaligned family in a small cohort costs more than an empty seat. Year one, you are the founding local face of a campus with a fledgling local brand, and most of your week happens outside the building. As the campus fills, the work changes. You stop chasing first conversations and become the leader parents ask for by name, with support under you and a playbook other campuses copy. You work on-site at one campus (Palo Alto or San Rafael) five days a week, visible at drop-off, pick-up, and evening events. If you have Bay Area connections and want the whole-family journey, apply today.
That's a lot of prose. We'll keep it as
under About the role.
Then "What You Will Be Doing" bullet list:
- Building your own qualified family pipeline through preschool and feeder-school relationships, community partnerships, referrals, and local events.
- Owning every stage yourself: first inquiry, needs-assessment conversation, campus tour, student shadow day, enrollment decision, and onboarding.
- Leading tours, open houses, and information sessions where you defend an AI-powered learning model to analytical, skeptical parents.
- Holding 7 or more active family relationships at different stages, each with a tracked status and next action in HubSpot and our SIS (student information system).
- Reporting weekly on pipeline health and conversion quality, and rewriting the local admissions playbook, FAQs, and SOPs as you learn what works in your market.
That's responsibilities.
Then "What You Won’t Be Doing" bullet list:
- Sorting a waitlist. There is no inherited demand here.
- Routing decisions through an admissions committee or layered approvals.
- Working a script or a quota-first call list.
- Handing a family off between four coordinators, an events team, and a front desk.
- Managing a large team or spending your week in internal meetings.
These are also responsibilities (what not to do). Could be included under Responsibilities as well.
Then "Head Of Admissions" maybe just title.
Then "Key Responsibilities": "Grow enrollment at one Bay Area campus with families who will thrive in the Alpha model." That's a responsibility.
Then "Basic Requirements" bullet list:
- 3+ years in premium client-facing roles where an individual or family was the buyer at $25K+ per client or $2K+ per month. You can name the employer and price point; business-to-business or enterprise sales alone do not qualify.
- Personal ownership of an end-to-end client, admissions, or enrollment journey: application, needs assessment, offer, decision, and onboarding. What you did, not what your team did.
- A measurable growth or customer-acquisition number you owned, including how you generated leads and built local partnerships to hit it.
- 7 or more concurrent client or family relationships at different stages, tracked in a named CRM or database.
- A concrete example of recommending against your own product because it was not the right fit.
- Hands-on use of AI tools in a client-facing workflow, such as meeting preparation, personalized outreach, conversation summaries, or follow-up.
- Experience personally leading in-person tours, presentations, meetings, or hosted experiences for high-net-worth clients, senior executives, or similarly demanding audiences.
- Strong written and verbal communication with executive presence: you can uncover needs, explain complex concepts simply, handle objections, and lead high-stakes decision conversations.
- Experience managing thoughtful, multi-touch client relationships over several weeks, including staying engaged with prospects who do not immediately commit.
- You live in or will relocate within 60 days to Palo Alto, CA, or San Rafael, CA (Marin County). This role is fully on-site, not hybrid.
- Authorized to work in the United States without visa sponsorship.
Then "Nice-to-have Requirements" bullet list:
- An existing network among Peninsula or Marin families, with relationships at local private preschools or feeder schools.
- Admissions or enrollment experience at a selective independent K-12 school, or a program with more applicants than seats.
- Background in luxury hospitality, private client services, concierge medicine, private wealth, membership clubs, or high-end residential real estate.
Then "About Alpha" paragraph:
"Join the team building school around student growth Alpha reimagines the school day around faster learning, stronger mentorship, and more time for students to build real-world skills. Roles with real student impact: Alpha hires teachers (guides), operators, admissions experts, school & curriculum leaders, and remote team members. Education work that pays like it matters: Alpha offers six-figure roles for people ready to help build a radically better school experience. A culture built for builders: Alpha is fast-moving, ambitious, and student focused. It’s for people who want to improve the system, not maintain it. Alpha is where you can do the most meaningful work of your career. There is so much to cover for this exciting role, and space here is limited. Hit the Apply button if you found this interesting and want to learn more. We look forward to meeting you!"
We need to remove application instructions like "Hit the Apply button...". So we should cut that sentence. Also "We look forward to meeting you!" maybe okay but it's somewhat boilerplate; but it's not a legal/EEO. Might keep? The instruction says remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. "Hit the Apply button..." is application instruction, remove. "We look forward to meeting you!" maybe not application instruction but could be considered boilerplate; but it's not explicitly prohibited. Safer to keep? Might be considered filler but not disallowed. We'll keep it.
Then "Working with us" paragraph:
"This is a full-time, W2 employee position with immediate access to benefits (https://support.crossover.com/article/7581-w2-benefits-u-s-paychex-paid-only). All roles are year-long positions. The compensation level for this role is $250,000 USD/year. The payment period is weekly.
for prose. Do NOT repeat job title as heading. Do NOT put Job ID / requisition numbers as headings — fold minor metadata into a 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 and extract sections. The posting includes: - Intro paragraph about Alpha School growth claim, description of job. - Then "What You Will Be Doing" bullet list. - Then "What You Won’t Be Doing" bullet list. - Then "Head Of Admissions" maybe title? Actually "Head Of Admissions" is the role title. - Then "Key Responsibilities" bullet (just one line? Actually "Grow enrollment at one Bay Area campus with families who will thrive in the Alpha model.") That's a responsibility. - Then "Basic Requirements" bullet list. - Then "Nice-to-have Requirements" bullet list. - Then "About Alpha" paragraph. - Then "Working with us" paragraph about full-time, W2 employee, benefits link, year-long positions, compensation $250,000 USD/year, payment period weekly, Crossover Job Code. We need to produce sections: maybe "About the role", "Responsibilities", "Requirements", "Qualifications", "Skills", "Benefits", "Pay", "Schedule". But we should only include sections that have real specific content. We have: - About the role: we can combine intro description and maybe "About Alpha" as about the role? The instructions: use
for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). So we can decide which sections to include. We have content for: - About the role: description of job, mission, etc. Could be "About the role" heading. - Responsibilities: "What You Will Be Doing" list, plus maybe "Key Responsibilities". Also "What You Won’t Be Doing" could be under responsibilities? Might be separate but we can combine. - Requirements: "Basic Requirements" list. - Qualifications: maybe "Nice-to-have Requirements" could be under Qualifications or Skills? Could be "Qualifications" for required, and "Nice-to-have" as "Preferred Qualifications". But we have only allowed headings: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We could map: - Requirements: Basic Requirements (mandatory) - Qualifications: Nice-to-have Requirements (preferred) - Skills: maybe we can extract skills from responsibilities? But we could also omit if not specific. - Benefits: we have benefits mention: immediate access to benefits (link). Also "All roles are year-long positions." That's maybe schedule? Actually schedule: work on-site five days a week, visible at drop-off, pick-up, evening events. That's schedule info. - Pay: compensation $250,000 USD/year, payment period weekly. - Schedule: work on-site at one campus five days a week, visible at drop-off, pick-up, evening events. We need to ensure we don't create sections with filler like "not specified". We have actual content for Pay, Benefits, Schedule. We need to avoid repeating job title as heading. So we won't put "Head Of Admissions" as heading. We need to not put Job ID as heading; we can fold minor metadata into a short
or drop it. The Job Code: "Crossover Job Code: LJ-5811-US-SanRafae-HeadofAdmissio.010". We can drop it or include in a short p maybe under About the role? Probably drop. We need to remove boilerplate like application instructions ("Hit the Apply button if you found this interesting..."). We need to preserve all substantive information. Let's extract substantive content: Intro paragraph: "Alpha School students, on average, experience 2.4 to 2.6 times the academic growth of traditional school students" — Forbes Alpha is hiring. In the Bay Area, the strongest admissions people don't sell. They manage a waitlist, staff a committee, and protect a reputation built long before they arrived. This job is the reverse. In your market, almost no family has heard of us yet. You go find them. Alpha is a K-12 private school built on a claim we can prove: students complete core academics in two hours a day, learn faster than national benchmarks, and spend their afternoons on real skills rather than busywork. Bay Area parents are the hardest audience for that claim and the best one. Founders, engineers, physicians, and investors will not accept a warm tour and a mission statement. They will ask for the data, push on the trade-offs, and compare us to Nueva, Castilleja, Harker, Marin Country Day, and Branson in the same breath. Welcome that conversation. Be clear about what this is. It is a sales job with a mandate for selectivity. You generate your own demand: preschool and feeder-school relationships, community partnerships, local events, and referrals from families you have already earned. You carry a growth number. You also tell a family "no" when the model is wrong for their child, in a market where saying "no" to a well-connected parent carries consequences. Both halves are the job. One misaligned family in a small cohort costs more than an empty seat. Year one, you are the founding local face of a campus with a fledgling local brand, and most of your week happens outside the building. As the campus fills, the work changes. You stop chasing first conversations and become the leader parents ask for by name, with support under you and a playbook other campuses copy. You work on-site at one campus (Palo Alto or San Rafael) five days a week, visible at drop-off, pick-up, and evening events. If you have Bay Area connections and want the whole-family journey, apply today. That's a lot of prose. We'll keep it as
under About the role. Then "What You Will Be Doing" bullet list: - Building your own qualified family pipeline through preschool and feeder-school relationships, community partnerships, referrals, and local events. - Owning every stage yourself: first inquiry, needs-assessment conversation, campus tour, student shadow day, enrollment decision, and onboarding. - Leading tours, open houses, and information sessions where you defend an AI-powered learning model to analytical, skeptical parents. - Holding 7 or more active family relationships at different stages, each with a tracked status and next action in HubSpot and our SIS (student information system). - Reporting weekly on pipeline health and conversion quality, and rewriting the local admissions playbook, FAQs, and SOPs as you learn what works in your market. That's responsibilities. Then "What You Won’t Be Doing" bullet list: - Sorting a waitlist. There is no inherited demand here. - Routing decisions through an admissions committee or layered approvals. - Working a script or a quota-first call list. - Handing a family off between four coordinators, an events team, and a front desk. - Managing a large team or spending your week in internal meetings. These are also responsibilities (what not to do). Could be included under Responsibilities as well. Then "Head Of Admissions" maybe just title. Then "Key Responsibilities": "Grow enrollment at one Bay Area campus with families who will thrive in the Alpha model." That's a responsibility. Then "Basic Requirements" bullet list: - 3+ years in premium client-facing roles where an individual or family was the buyer at $25K+ per client or $2K+ per month. You can name the employer and price point; business-to-business or enterprise sales alone do not qualify. - Personal ownership of an end-to-end client, admissions, or enrollment journey: application, needs assessment, offer, decision, and onboarding. What you did, not what your team did. - A measurable growth or customer-acquisition number you owned, including how you generated leads and built local partnerships to hit it. - 7 or more concurrent client or family relationships at different stages, tracked in a named CRM or database. - A concrete example of recommending against your own product because it was not the right fit. - Hands-on use of AI tools in a client-facing workflow, such as meeting preparation, personalized outreach, conversation summaries, or follow-up. - Experience personally leading in-person tours, presentations, meetings, or hosted experiences for high-net-worth clients, senior executives, or similarly demanding audiences. - Strong written and verbal communication with executive presence: you can uncover needs, explain complex concepts simply, handle objections, and lead high-stakes decision conversations. - Experience managing thoughtful, multi-touch client relationships over several weeks, including staying engaged with prospects who do not immediately commit. - You live in or will relocate within 60 days to Palo Alto, CA, or San Rafael, CA (Marin County). This role is fully on-site, not hybrid. - Authorized to work in the United States without visa sponsorship. Then "Nice-to-have Requirements" bullet list: - An existing network among Peninsula or Marin families, with relationships at local private preschools or feeder schools. - Admissions or enrollment experience at a selective independent K-12 school, or a program with more applicants than seats. - Background in luxury hospitality, private client services, concierge medicine, private wealth, membership clubs, or high-end residential real estate. Then "About Alpha" paragraph: "Join the team building school around student growth Alpha reimagines the school day around faster learning, stronger mentorship, and more time for students to build real-world skills. Roles with real student impact: Alpha hires teachers (guides), operators, admissions experts, school & curriculum leaders, and remote team members. Education work that pays like it matters: Alpha offers six-figure roles for people ready to help build a radically better school experience. A culture built for builders: Alpha is fast-moving, ambitious, and student focused. It’s for people who want to improve the system, not maintain it. Alpha is where you can do the most meaningful work of your career. There is so much to cover for this exciting role, and space here is limited. Hit the Apply button if you found this interesting and want to learn more. We look forward to meeting you!" We need to remove application instructions like "Hit the Apply button...". So we should cut that sentence. Also "We look forward to meeting you!" maybe okay but it's somewhat boilerplate; but it's not a legal/EEO. Might keep? The instruction says remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. "Hit the Apply button..." is application instruction, remove. "We look forward to meeting you!" maybe not application instruction but could be considered boilerplate; but it's not explicitly prohibited. Safer to keep? Might be considered filler but not disallowed. We'll keep it. Then "Working with us" paragraph: "This is a full-time, W2 employee position with immediate access to benefits (https://support.crossover.com/article/7581-w2-benefits-u-s-paychex-paid-only). All roles are year-long positions. The compensation level for this role is $250,000 USD/year. The payment period is weekly.