Associate Director of Admissions, Alpha - $250,000/year USD

We need to output HTML fragment with sections: headings using

for section headings like About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We must include only sections that have real specific content. We need to extract content from posting. Let's parse posting: Title: Associate Director Of Admissions (but we must not repeat job title as heading). So we start with maybe a short paragraph for metadata? The instruction: do NOT put Job ID / requisition numbers as headings — fold minor metadata into a short

or drop it. So we can include a short

with location, maybe job code? But we can drop it. Probably include a short

with location and maybe note it's full-time on-site. Then sections: - About the role: we have description: "Alpha School students, on average, experience 2.4 to 2.6 times the academic growth..." etc. Also description of role: generating demand, etc. So we can put that under About the role. - Responsibilities: list from "What You Will Be Doing" bullet points. - Requirements: Basic Requirements list. - Qualifications: maybe Nice-to-have Requirements? Could be Skills? The instruction: use headings for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). We need to decide which sections have content. We have: - About the role: yes. - Responsibilities: yes (What You Will Be Doing). - Requirements: Basic Requirements. - Qualifications: maybe Nice-to-have Requirements could be under Qualifications or Skills. Could treat as Qualifications. - Skills: maybe we can extract from requirements: communication, AI tools, etc. But we could also put under Qualifications. - Benefits: posting mentions immediate access to benefits link, but no specifics. It says "immediate access to benefits (link)". No detail. Should we include Benefits section? The rule: never create Benefits section unless posting actually states them. It states "immediate access to benefits" but no specifics. That's vague but still states benefits exist. However we should not include placeholder like "not specified". It says immediate access to benefits, but no detail. Might be considered substantive enough? The instruction: "never emit a heading followed by filler/placeholder text (e.g. 'commensurate with experience', 'not specified', 'N/A', 'varies', 'TBD')". "immediate access to benefits" is not filler; it's a statement that benefits are provided immediately. Could be okay. But we might avoid Benefits section if we lack detail. However we could include a short

stating "Immediate access to benefits (health, retirement, etc.) via provided link." But we shouldn't invent. We can just note that benefits are provided immediately with link. That's not invented; it's from posting. So we can include Benefits section with a

that says "Immediate access to benefits (see link)." That's not filler. - Pay: posting says "The compensation level for this role is $250,000 USD/year. The payment period is weekly." That's specific. So we need Pay section. - Schedule: posting says "This role is fully on-site, not hybrid." Also "You work on-site at one campus (Palo Alto or San Rafael) five days a week". So schedule: full-time, on-site, five days a week. So we can include Schedule section. Now we need to avoid repeating job title as heading. So we start with maybe a short

containing location and note it's full-time on-site? But schedule will cover that. Could include a short

with job code? Might drop. We'll output:

Associate Director of Admissions – On‑site, full‑time (Palo Alto or San Rafael, CA).

Then sections:

About the role

... (prose)

We need to preserve all substantive information, not invent or summarize away detail. So we need to include the key points: Alpha claim, growth numbers, description of role, etc. Let's craft About the role paragraph: combine the initial description and role overview. From posting: "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. We need to keep that as prose. Now Responsibilities: list from "What You Will Be Doing". Items: - Generating your own qualified family demand 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. We'll put each as

inside

. Now Requirements: Basic Requirements 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. We'll put each as
• . Now Qualifications/Nice-to-have: we can treat as Qualifications. Nice-to-have Requirements: - 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. We'll put as
  under Qualifications. Now Benefits: we have "immediate access to benefits (https://support.crossover.com/article/7581-w2-benefits-u-s-paychex-paid-only)". Also "All roles are year-long positions." That's maybe more about contract length. But benefits: immediate access to benefits. We'll put a

  stating "Immediate access to benefits (see link)." Could also mention "All roles are year-long positions." That's not benefits but maybe schedule? We'll keep benefits simple. Pay: "$250,000 USD/year. The payment period is weekly." Schedule: "Fully on-site, five days a week at either Palo Alto or San Rafael campus." Also "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." We'll put schedule as

  stating full-time on-site, five days a week. Now ensure we don't repeat job title as heading. We already have a short

  maybe with title? We could avoid title entirely. But we need to convey role? The page already shows it per instruction. So we can omit title. We'll just start with a short

  about location and maybe note it's full-time on-site? But schedule covers that. Maybe we just start with About the role directly. However we need to include some minimal metadata? The instruction: "do NOT put Job ID / requisition numbers as headings — fold minor metadata into a short

  or drop it." So we can drop metadata entirely. So we can start directly with About the role heading. Thus output:

  About the role

  ... (the long paragraph)

  Responsibilities

  ...

  Requirements

  ...

  Qualifications

  ...

  Benefits

  Immediate access to benefits (see benefits details).

  Pay

  $250,000 USD per year, paid weekly.

  Schedule

  Full‑time, on‑site, five days per week at either the Palo Alto or San Rafael campus.

  We must ensure we don't include any extra text like markdown fences. Just HTML. Check for any repeated content: we must preserve all substantive information. Did we miss any? The posting also mentions "All roles are year-long positions." That's not benefits but maybe we could add to Benefits or Schedule? It's about contract length. Could be included in Benefits? Might be better to add a note in Benefits: "All roles are year‑long positions." But that's not a benefit per se.