Director of Family Relations, Alpha - $200,000/year USD

We need to output HTML fragment with headings

for sections: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. Only include sections that have real specific content. Must not repeat job title as heading. Must not include Job ID etc. Must preserve all substantive info, remove boilerplate, navigation, legal, EEO, etc. Must not include filler like "commensurate with experience". Must not create Pay/Schedule/Benefits unless posting actually states them. The posting includes: "On-site (multiple cities - see Requirements) W2 Employee $200K/yr Relocation assistance available". So Pay: $200K/yr. Benefits: health coverage, etc. Schedule: On-site full-time, including early mornings, late afternoons, evening events 2–3x/month, occasional weekends. Also relocation assistance. We need sections: About the role (maybe a brief description). Responsibilities (list). Requirements (list). Qualifications? Might be overlapping with Requirements. The posting includes "Basic Requirements" and "Nice-to-have Requirements". Could treat Basic Requirements as Requirements, Nice-to-have as Qualifications or Skills. Also "Hands-on daily use of AI tools" etc. Could be Skills. We must not create sections with filler. So we need to decide which sections have substantive content. We have: - About the role: The initial paragraph describing role: "Alpha School students, on average, experience 2.4 to 2.6 times the academic growth..." then description of role, what you will be doing, etc. Could be About the role. - Responsibilities: The "What You Will Be Doing" bullet list (multiple paragraphs). Also "Your mandate is to build a campus..." maybe part of responsibilities. - Requirements: Basic Requirements list (live within commuting distance, on-site full-time, legally authorized, 5+ years experience, track record, independent ownership, willing to own school growth, clear communication, familiarity with independent/private/non-traditional education, hands-on daily use of AI tools, genuine conviction about AI-powered education). Also relocation assistance? That's benefit. - Qualifications: Nice-to-have Requirements list (established local network, private/independent school experience, experience as relationship owner alongside educators, launch/early-stage assignment, instinct for creating experiences, startup/early-stage experience). Could be Qualifications. - Skills: Could be derived from requirements like "Clear, concise communication", "Hands-on daily use of AI tools", "Familiarity with independent, private, or non-traditional education". But maybe we treat those as Skills. - Benefits: Health coverage, life/disability insurance, voluntary benefits, tax-advantaged FSA/HSA/commuter accounts, 401(k), paid time off, parental leave, one-time relocation allowance. - Pay: $200K/yr. - Schedule: On-site full-time, including early mornings, late afternoons, evening events 2–3x/month, occasional weekends. We must not include sections with filler like "commensurate with experience". Not present. We must output only HTML fragment, no markdown fences. We need to use

for each section heading. Use

• for any list of duties/requirements/benefits. Use

  for prose. We must not repeat job title as heading. The job title is "Director Of Family Relations". Not to be used as heading. We must not put Job ID/requisition numbers as headings; we can drop them. We must remove cookie/navigation/legal/EEO etc. The posting includes some legal text at end: "Working with us This is a full-time, W2 employee position...". That includes compensation details, but we already captured pay and benefits. The line "All roles are year-long positions." Might be considered metadata; could be omitted? It's substantive? It's about duration. Might be considered part of schedule? Not exactly. Could be included in a short paragraph under About the role? Might be considered boilerplate? It's not navigation/legal/EEO. It's about role duration. Might be okay to keep as prose. But we need to preserve ALL substantive information. So we should include that it's a year-long position. Where to put? Could be under About the role or maybe under Schedule? Probably under About the role as a note. Also "The payment period is weekly." That's pay detail. Also "Consult www.crossover.com/help-and-faqs for more details on this topic." That's a link; maybe considered boilerplate? It's a reference; could be omitted as it's application instruction? It's not application instruction but a reference. Might be considered navigation? Probably safe to drop. Also "Crossover Job Code: LJ-5598-US-LasVegas-DirectorofFami.001" drop. Also "Hit the Apply button if you found this interesting and want to learn more." That's application instruction; drop. Also "We look forward to meeting you!" drop. Also "There is so much to cover for this exciting role, and space here is limited." drop. Also "About Alpha Join the team building school around student growth..." That's about company; could be About the role? Actually it's about Alpha. Could be included under About the role as a brief description. We need to ensure we don't include any filler like "commensurate with experience". Not present. Now craft HTML. Structure:

  About the role

  ... prose describing role, including the Forbes quote, description of Alpha model, year-long position, etc.

  Responsibilities

  • Own the relationship with every family on campus, and lead the hard conversations.
  • Find the real concern, deliver a clear decision, hold it, and follow through until it stays resolved.
  • Defend Alpha's model through screen-time worries, skeptical relatives, and moments of doubt.
  • Operate as the parent-facing co-leader alongside your Guides. Align before and after sensitive conversations, protect the coaching relationship they hold with students, take family issues off their plate, and make sure families always know who owns what.
  • Make the real-time calls in ambiguous student and family situations, and route child-safety, legal, and high-risk matters through the correct escalation path immediately.
  • Build the community: campus traditions, parent networks, and local partnerships, each with a defined outcome behind it, plus the trusted parent champions who become the campus's most credible voice.
  • Own the growth contribution your campus phase calls for, against outcomes agreed up front and tracked as the campus changes. At a launch or under-enrolled campus, that means developing local demand and personally owning admissions follow-through to enrollment. At a mature campus it means retention, referrals, and clean handoffs to admissions.
  Maybe also include "You won't do it alone, and you won't do it around the Guides who mentor these students." but that's covered.

  Requirements

  • Live within commuting distance of one of these campuses, or relocate within 60 days: Boca Raton, FL; Burlington, VT; Jackson Hole, WY; Las Vegas, NV; Palm Beach, FL; Park City, UT; Tulsa, OK
  • On-site full-time, including early mornings, late afternoons, evening events 2–3x/month, and occasional weekends
  • Legally authorized to work in the U.S. without sponsorship
  • 5+ years personally owning high-trust relationships with families, clients, donors, or members, where your judgment and follow-through changed retention or advocacy
  • A track record of holding firm decisions with demanding stakeholders without losing the relationship
  • Independent ownership of an ambiguous relationship, community, or growth outcome, with results you can point to as your own
  • Willing to own school growth and admissions follow-through when your campus phase calls for it
  • Clear, concise communication that earns confidence quickly with affluent, high-expectation families
  • Familiarity with independent, private, or non-traditional education
  • Hands-on daily use of AI tools, and genuine conviction about AI-powered education
  Note: The on-site full-time schedule appears also in Requirements; but we also have Schedule section. Might duplicate. Could keep schedule in Requirements and also have Schedule section? Might be redundant. Better to put schedule in Schedule section, and not duplicate in Requirements. However the requirement list includes "On-site full-time, including early mornings, late afternoons, evening events 2–3x/month, and occasional weekends". That's essentially schedule. We could keep it under Requirements as a requirement, and also have Schedule section? Might be duplication. The instruction: "Prefer a few substantive sections over many thin ones." So we could combine schedule into Requirements, and not have separate Schedule section unless there is additional schedule info beyond that. The posting also mentions "On-site (multiple cities - see Requirements) W2 Employee $200K/yr Relocation assistance available". That's covered. So we could omit Schedule section. But the instruction says to use headings for sections like Schedule if posting actually states them. It does state schedule details. So we could include Schedule section with those details, and not duplicate in Requirements. However the requirement list also includes that schedule as a requirement; but we could keep it only under Schedule and not under Requirements. However the requirement list also includes many other items; we could keep the schedule item out of Requirements to avoid duplication. Let's see if the requirement list includes any other schedule-related items: It includes "On-site full-time, including early mornings, late afternoons, evening events 2–3x/month, and occasional weekends". That's purely schedule. So we can move that to Schedule section and remove from Requirements. Thus Requirements will not include that line. Now Benefits section: list benefits. Pay section: $200K/yr, weekly payment period, W2 employee, relocation assistance (maybe also benefit). Relocation assistance is mentioned under Benefits? It says "A one-time relocation allowance." under Benefits. Also earlier "Relocation assistance available". So we can include relocation allowance in Benefits. Pay: $200K/yr, weekly payment period. Now Qualifications/Nice-to-have: we can call it Qualifications. Skills: maybe we can combine some skills like "Clear, concise communication", "Hands-on daily use of AI tools", "Familiarity with independent, private, or non-traditional education". But those are already in Requirements. Could move them to Skills. However we already have Requirements covering many items; we could keep Requirements as the mandatory requirements, and Skills as desired skills. But the posting doesn't separate skills vs qualifications; it's just "Nice-to-have Requirements". So we can treat Nice-to-have as Qualifications. Thus sections: About the role, Responsibilities, Requirements, Qualifications, Benefits, Pay. Possibly Schedule omitted as we moved schedule to Requirements? But we removed schedule from Requirements; we need Schedule section. Let's add Schedule section with the schedule details. Thus sections: About the role, Responsibilities, Requirements, Skills? Actually we have Requirements (mandatory), Qualifications (nice-to-have), Benefits, Pay, Schedule. We need to ensure we don't create sections with filler. All have content. Now craft HTML. We must not include markdown fences. Let's write. About the role paragraph: combine initial Forbes quote, description of Alpha model, year-long position, W2 employee, etc. We need to preserve all substantive info: The Forbes quote: "Alpha School students, on average, experience 2.4 to 2.6 times the academic growth of traditional school students" — Forbes. Also description: "Alpha is hiring. On-site (multiple cities - see Requirements) W2 Employee $200K/yr Relocation assistance available Most schools have someone whose job is keeping parents happy. Alpha needs someone parents trust. That is a different job and a harder one: you