Director of Community Engagement, Alpha - $400,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:
- Intro: "the Great Educational Equalizer" — Philosopher Johnathan Bi, on Alpha School Alpha is hiring. ... (some narrative). This is basically description of role.
- Then "What You Will Be Doing" bullet list (actually sentences). Then "What You Won’t Be Doing" bullet list.
- Then "Director Of Community Engagement" (maybe title). Then "Key Responsibilities" (maybe a sentence). Then "Basic Requirements" bullet list. Then "Nice-to-have Requirements" bullet list.
- Then "About Alpha" paragraph.
- Then "Working with us" paragraph: full-time W2 employee position with immediate access to benefits (link). All roles are year-long positions. The compensation level for this role is $400,000 USD/year. The payment period is weekly. Consult www.crossover.com/help-and-faqs for more details on this topic. Crossover Job Code: LJ-5465-US-LasVegas-DirectorofComm.001
We need to extract substantive info.
We need sections: maybe "About the role", "Responsibilities", "Requirements", "Qualifications", "Skills", "Benefits", "Pay", "Schedule". But we only include sections if there is real specific content.
We have:
- About the role: could be the introductory narrative (the Great Educational Equalizer etc). Could be "About Alpha" also.
- Responsibilities: the "What You Will Be Doing" list and maybe "Key Responsibilities". Also "What You Won’t Be Doing" could be considered responsibilities but it's negative; maybe we can include as part of responsibilities or separate? The instruction: Use
for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). So we can choose headings that match content.
We need to decide which sections to include.
We have content for:
- About the role: we have description of role (the narrative). Also "About Alpha" could be separate but maybe we combine.
- Responsibilities: "What You Will Be Doing" bullet list (list of duties). Also "Key Responsibilities" short sentence.
- Requirements: "Basic Requirements" bullet list.
- Qualifications: maybe "Nice-to-have Requirements" could be qualifications? Or we could treat as "Qualifications" (preferred). Or we could have separate "Skills" maybe not needed.
- Benefits: mention "immediate access to benefits" but no specifics; not specific enough? It says immediate access to benefits (link). That's somewhat specific but not details. The instruction says never create Benefits section unless posting actually states them. It does state "immediate access to benefits". That's a statement, albeit vague. Should we include? Probably yes, as it's a benefit statement. But we need to avoid filler like "commensurate with experience". This is not filler. So we can include Benefits section with that statement.
- Pay: compensation level $400,000 USD/year, payment period weekly. That's specific. So include Pay section.
- Schedule: full-time, W2 employee position, year-long positions, includes evening and weekend community events (2 to 4 per month). Also mention on-site full-time. So we have schedule info: full-time, on-site, evening/weekend events. So we can include Schedule section.
Thus we can include sections: About the role, Responsibilities, Requirements, Qualifications (nice-to-have), Benefits, Pay, Schedule.
We need to avoid repeating job title as heading. The job title is "Director Of Community Engagement". We should not use that as heading.
We need to preserve all substantive information, not invent or summarize away detail. So we need to keep details like "7+ years leading high-stakes relationships in private or independent K-12 education, fundraising or major gifts, enterprise sales, client success, or private wealth management", etc.
We need to format lists with - . For prose, use
.
We need to remove boilerplate: cookie/navigation/legal/EEO/equal-opportunity/scam-warning, duplicated lines, application instructions. There's no explicit EEO etc. There's a link to benefits and a link to FAQs. Those are not boilerplate? The link to benefits is part of Working with us; we can keep the link? Probably we can keep the URL as part of the sentence. The instruction: remove application instructions. There's "Hit the Apply button if you found this interesting and want to learn more." That's application instruction; we should remove that. Also "We look forward to meeting you!" maybe also application instruction? It's a closing line; maybe we can keep as it's not instruction but it's fluff. Safer to remove? The instruction says remove application instructions. The closing line is not an instruction but could be considered boilerplate. I'd remove "Hit the Apply button..." and "We look forward to meeting you!" as they are not substantive. Also "There is so much to cover for this exciting role, and space here is limited." That's filler; remove.
Also "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." That's substantive about Alpha.
We need to preserve all substantive info; we must not invent or summarize away detail. So we need to keep the details exactly as given, but we can rephrase? The instruction says preserve ALL substantive information; do NOT invent or summarize away detail. It doesn't forbid rephrasing, but summarizing away detail is not allowed. Safer to keep the exact sentences, maybe just restructure into HTML.
We need to output only HTML fragment.
Let's extract sections.
**About the role**: Could combine the opening narrative and maybe "About Alpha". Let's decide: We'll have a section "About the role" containing the descriptive paragraphs that talk about the role purpose, what the job is about, the environment, etc. Then maybe another section "About Alpha" but we don't have that heading in allowed list; we could use "About the role" for role description and "About Alpha" could be considered "About the role"? Not exactly. The allowed headings include "About the role". There's no "About the company". But we could put Alpha description under "About the role" or maybe under "Responsibilities"? Better to put under "About the role" as it's about the role context. However the instruction says use headings e.g. About the role, Responsibilities, etc. So we can use About the role for role description, and maybe we can also include a separate section "About Alpha" but not in list; maybe we should not create a heading not in list. So we should stick to the given headings. So we can put Alpha description under "About the role" as well, or maybe under "Responsibilities"? I'd put under "About the role" a blend: the opening narrative about the role and the description of Alpha.
But we need to avoid duplication. Let's parse the text:
Opening: ""the Great Educational Equalizer" — Philosopher Johnathan Bi, on Alpha School Alpha is hiring. You went into private school leadership to shape how children learn, not to run capital campaigns and referee parent committees. There is a version of this job where the academic model is protected for you, operations is handled centrally, and you spend your week on what you are best at: winning over the families who matter most, turning them into advocates, and being the voice of authority when the conversation gets hard. You will own the parent side of Alpha in one metro — Miami, San Francisco, or Los Angeles. Your measure is enrollment and advocacy: prospective ultra-high-net-worth families who convert, current UHNW families who re-enroll, refer, and publicly champion 2 Hour Learning, and a local community where Alpha is top of mind. Roughly half your week is outward-facing — community partnerships, info sessions, and 1:1 conversations with sophisticated parents who have read every AI skeptic and want to know why the model actually works. The rest of the seat is the escalation line. When an Associate Dean of Parents reaches the edge of what they can resolve — a board family threatening to pull their kids, a campus quietly softening the model to keep a vocal parent happy — it comes to you. You retain the family, and you keep the model intact. Both. Then you document the precedent so the Associate Dean network can handle it next time without you. If you have run a private or independent K-12 school, or you have spent a career earning the trust of UHNW families in another industry, and you have been waiting for the job where judgment and persuasion are the actual deliverables, this is it."
That's a lot of role description.
Then "What You Will Be Doing" list.
Then "What You Won’t Be Doing" list.
Then "Director Of Community Engagement" (maybe title). Then "Key Responsibilities" sentence: "Build a metro where Alpha families are 2 Hour Learning’s loudest advocates — and where no parent crisis is resolved by compromising the model."
Then "Basic Requirements" list.
Then "Nice-to-have Requirements" list.
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."
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 $400,000 USD/year. The payment period is weekly. Consult www.crossover.com/help-and-faqs for more details on this topic. Crossover Job Code: LJ-5465-US-LasVegas-DirectorofComm.001"
Then maybe some filler after that: "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'll remove those.
Now we need to decide sections.
**About the role**: Could include the opening narrative (the Great Educational Equalizer ...) plus maybe the "About Alpha" paragraph? But the About Alpha paragraph is more about the organization, not the role. However we don't have a separate heading for About the company. Could we put it under "About the role
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: - Intro: "the Great Educational Equalizer" — Philosopher Johnathan Bi, on Alpha School Alpha is hiring. ... (some narrative). This is basically description of role. - Then "What You Will Be Doing" bullet list (actually sentences). Then "What You Won’t Be Doing" bullet list. - Then "Director Of Community Engagement" (maybe title). Then "Key Responsibilities" (maybe a sentence). Then "Basic Requirements" bullet list. Then "Nice-to-have Requirements" bullet list. - Then "About Alpha" paragraph. - Then "Working with us" paragraph: full-time W2 employee position with immediate access to benefits (link). All roles are year-long positions. The compensation level for this role is $400,000 USD/year. The payment period is weekly. Consult www.crossover.com/help-and-faqs for more details on this topic. Crossover Job Code: LJ-5465-US-LasVegas-DirectorofComm.001 We need to extract substantive info. We need sections: maybe "About the role", "Responsibilities", "Requirements", "Qualifications", "Skills", "Benefits", "Pay", "Schedule". But we only include sections if there is real specific content. We have: - About the role: could be the introductory narrative (the Great Educational Equalizer etc). Could be "About Alpha" also. - Responsibilities: the "What You Will Be Doing" list and maybe "Key Responsibilities". Also "What You Won’t Be Doing" could be considered responsibilities but it's negative; maybe we can include as part of responsibilities or separate? The instruction: Use
for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). So we can choose headings that match content.
We need to decide which sections to include.
We have content for:
- About the role: we have description of role (the narrative). Also "About Alpha" could be separate but maybe we combine.
- Responsibilities: "What You Will Be Doing" bullet list (list of duties). Also "Key Responsibilities" short sentence.
- Requirements: "Basic Requirements" bullet list.
- Qualifications: maybe "Nice-to-have Requirements" could be qualifications? Or we could treat as "Qualifications" (preferred). Or we could have separate "Skills" maybe not needed.
- Benefits: mention "immediate access to benefits" but no specifics; not specific enough? It says immediate access to benefits (link). That's somewhat specific but not details. The instruction says never create Benefits section unless posting actually states them. It does state "immediate access to benefits". That's a statement, albeit vague. Should we include? Probably yes, as it's a benefit statement. But we need to avoid filler like "commensurate with experience". This is not filler. So we can include Benefits section with that statement.
- Pay: compensation level $400,000 USD/year, payment period weekly. That's specific. So include Pay section.
- Schedule: full-time, W2 employee position, year-long positions, includes evening and weekend community events (2 to 4 per month). Also mention on-site full-time. So we have schedule info: full-time, on-site, evening/weekend events. So we can include Schedule section.
Thus we can include sections: About the role, Responsibilities, Requirements, Qualifications (nice-to-have), Benefits, Pay, Schedule.
We need to avoid repeating job title as heading. The job title is "Director Of Community Engagement". We should not use that as heading.
We need to preserve all substantive information, not invent or summarize away detail. So we need to keep details like "7+ years leading high-stakes relationships in private or independent K-12 education, fundraising or major gifts, enterprise sales, client success, or private wealth management", etc.
We need to format lists with - . For prose, use
.
We need to remove boilerplate: cookie/navigation/legal/EEO/equal-opportunity/scam-warning, duplicated lines, application instructions. There's no explicit EEO etc. There's a link to benefits and a link to FAQs. Those are not boilerplate? The link to benefits is part of Working with us; we can keep the link? Probably we can keep the URL as part of the sentence. The instruction: remove application instructions. There's "Hit the Apply button if you found this interesting and want to learn more." That's application instruction; we should remove that. Also "We look forward to meeting you!" maybe also application instruction? It's a closing line; maybe we can keep as it's not instruction but it's fluff. Safer to remove? The instruction says remove application instructions. The closing line is not an instruction but could be considered boilerplate. I'd remove "Hit the Apply button..." and "We look forward to meeting you!" as they are not substantive. Also "There is so much to cover for this exciting role, and space here is limited." That's filler; remove.
Also "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." That's substantive about Alpha.
We need to preserve all substantive info; we must not invent or summarize away detail. So we need to keep the details exactly as given, but we can rephrase? The instruction says preserve ALL substantive information; do NOT invent or summarize away detail. It doesn't forbid rephrasing, but summarizing away detail is not allowed. Safer to keep the exact sentences, maybe just restructure into HTML.
We need to output only HTML fragment.
Let's extract sections.
**About the role**: Could combine the opening narrative and maybe "About Alpha". Let's decide: We'll have a section "About the role" containing the descriptive paragraphs that talk about the role purpose, what the job is about, the environment, etc. Then maybe another section "About Alpha" but we don't have that heading in allowed list; we could use "About the role" for role description and "About Alpha" could be considered "About the role"? Not exactly. The allowed headings include "About the role". There's no "About the company". But we could put Alpha description under "About the role" or maybe under "Responsibilities"? Better to put under "About the role" as it's about the role context. However the instruction says use headings e.g. About the role, Responsibilities, etc. So we can use About the role for role description, and maybe we can also include a separate section "About Alpha" but not in list; maybe we should not create a heading not in list. So we should stick to the given headings. So we can put Alpha description under "About the role" as well, or maybe under "Responsibilities"? I'd put under "About the role" a blend: the opening narrative about the role and the description of Alpha.
But we need to avoid duplication. Let's parse the text:
Opening: ""the Great Educational Equalizer" — Philosopher Johnathan Bi, on Alpha School Alpha is hiring. You went into private school leadership to shape how children learn, not to run capital campaigns and referee parent committees. There is a version of this job where the academic model is protected for you, operations is handled centrally, and you spend your week on what you are best at: winning over the families who matter most, turning them into advocates, and being the voice of authority when the conversation gets hard. You will own the parent side of Alpha in one metro — Miami, San Francisco, or Los Angeles. Your measure is enrollment and advocacy: prospective ultra-high-net-worth families who convert, current UHNW families who re-enroll, refer, and publicly champion 2 Hour Learning, and a local community where Alpha is top of mind. Roughly half your week is outward-facing — community partnerships, info sessions, and 1:1 conversations with sophisticated parents who have read every AI skeptic and want to know why the model actually works. The rest of the seat is the escalation line. When an Associate Dean of Parents reaches the edge of what they can resolve — a board family threatening to pull their kids, a campus quietly softening the model to keep a vocal parent happy — it comes to you. You retain the family, and you keep the model intact. Both. Then you document the precedent so the Associate Dean network can handle it next time without you. If you have run a private or independent K-12 school, or you have spent a career earning the trust of UHNW families in another industry, and you have been waiting for the job where judgment and persuasion are the actual deliverables, this is it."
That's a lot of role description.
Then "What You Will Be Doing" list.
Then "What You Won’t Be Doing" list.
Then "Director Of Community Engagement" (maybe title). Then "Key Responsibilities" sentence: "Build a metro where Alpha families are 2 Hour Learning’s loudest advocates — and where no parent crisis is resolved by compromising the model."
Then "Basic Requirements" list.
Then "Nice-to-have Requirements" list.
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."
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 $400,000 USD/year. The payment period is weekly. Consult www.crossover.com/help-and-faqs for more details on this topic. Crossover Job Code: LJ-5465-US-LasVegas-DirectorofComm.001"
Then maybe some filler after that: "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'll remove those.
Now we need to decide sections.
**About the role**: Could include the opening narrative (the Great Educational Equalizer ...) plus maybe the "About Alpha" paragraph? But the About Alpha paragraph is more about the organization, not the role. However we don't have a separate heading for About the company. Could we put it under "About the role
. We need to remove boilerplate: cookie/navigation/legal/EEO/equal-opportunity/scam-warning, duplicated lines, application instructions. There's no explicit EEO etc. There's a link to benefits and a link to FAQs. Those are not boilerplate? The link to benefits is part of Working with us; we can keep the link? Probably we can keep the URL as part of the sentence. The instruction: remove application instructions. There's "Hit the Apply button if you found this interesting and want to learn more." That's application instruction; we should remove that. Also "We look forward to meeting you!" maybe also application instruction? It's a closing line; maybe we can keep as it's not instruction but it's fluff. Safer to remove? The instruction says remove application instructions. The closing line is not an instruction but could be considered boilerplate. I'd remove "Hit the Apply button..." and "We look forward to meeting you!" as they are not substantive. Also "There is so much to cover for this exciting role, and space here is limited." That's filler; remove. Also "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." That's substantive about Alpha. We need to preserve all substantive info; we must not invent or summarize away detail. So we need to keep the details exactly as given, but we can rephrase? The instruction says preserve ALL substantive information; do NOT invent or summarize away detail. It doesn't forbid rephrasing, but summarizing away detail is not allowed. Safer to keep the exact sentences, maybe just restructure into HTML. We need to output only HTML fragment. Let's extract sections. **About the role**: Could combine the opening narrative and maybe "About Alpha". Let's decide: We'll have a section "About the role" containing the descriptive paragraphs that talk about the role purpose, what the job is about, the environment, etc. Then maybe another section "About Alpha" but we don't have that heading in allowed list; we could use "About the role" for role description and "About Alpha" could be considered "About the role"? Not exactly. The allowed headings include "About the role". There's no "About the company". But we could put Alpha description under "About the role" or maybe under "Responsibilities"? Better to put under "About the role" as it's about the role context. However the instruction says use headings e.g. About the role, Responsibilities, etc. So we can use About the role for role description, and maybe we can also include a separate section "About Alpha" but not in list; maybe we should not create a heading not in list. So we should stick to the given headings. So we can put Alpha description under "About the role" as well, or maybe under "Responsibilities"? I'd put under "About the role" a blend: the opening narrative about the role and the description of Alpha. But we need to avoid duplication. Let's parse the text: Opening: ""the Great Educational Equalizer" — Philosopher Johnathan Bi, on Alpha School Alpha is hiring. You went into private school leadership to shape how children learn, not to run capital campaigns and referee parent committees. There is a version of this job where the academic model is protected for you, operations is handled centrally, and you spend your week on what you are best at: winning over the families who matter most, turning them into advocates, and being the voice of authority when the conversation gets hard. You will own the parent side of Alpha in one metro — Miami, San Francisco, or Los Angeles. Your measure is enrollment and advocacy: prospective ultra-high-net-worth families who convert, current UHNW families who re-enroll, refer, and publicly champion 2 Hour Learning, and a local community where Alpha is top of mind. Roughly half your week is outward-facing — community partnerships, info sessions, and 1:1 conversations with sophisticated parents who have read every AI skeptic and want to know why the model actually works. The rest of the seat is the escalation line. When an Associate Dean of Parents reaches the edge of what they can resolve — a board family threatening to pull their kids, a campus quietly softening the model to keep a vocal parent happy — it comes to you. You retain the family, and you keep the model intact. Both. Then you document the precedent so the Associate Dean network can handle it next time without you. If you have run a private or independent K-12 school, or you have spent a career earning the trust of UHNW families in another industry, and you have been waiting for the job where judgment and persuasion are the actual deliverables, this is it." That's a lot of role description. Then "What You Will Be Doing" list. Then "What You Won’t Be Doing" list. Then "Director Of Community Engagement" (maybe title). Then "Key Responsibilities" sentence: "Build a metro where Alpha families are 2 Hour Learning’s loudest advocates — and where no parent crisis is resolved by compromising the model." Then "Basic Requirements" list. Then "Nice-to-have Requirements" list. 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." 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 $400,000 USD/year. The payment period is weekly. Consult www.crossover.com/help-and-faqs for more details on this topic. Crossover Job Code: LJ-5465-US-LasVegas-DirectorofComm.001" Then maybe some filler after that: "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'll remove those. Now we need to decide sections. **About the role**: Could include the opening narrative (the Great Educational Equalizer ...) plus maybe the "About Alpha" paragraph? But the About Alpha paragraph is more about the organization, not the role. However we don't have a separate heading for About the company. Could we put it under "About the role