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

We need to output HTML fragment with sections: About the role? Actually we need to use headings for sections like About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We must include only sections that have real specific content. Let's parse the posting. Key info: - Title: Director Of Family Relations (but we must not repeat job title as heading). So we will not include heading for title. - About the role: The description includes many paragraphs about role, responsibilities, etc. Could be "About the role" section summarizing role. - Responsibilities: There's a "What You Will Be Doing" list (bullet points). Also "What You Won’t Be Doing". Could be responsibilities. - Requirements: Basic Requirements list (live within commuting distance, on-site full-time, legally authorized, 5+ years experience, etc.) - Qualifications: maybe "Nice-to-have Requirements" could be qualifications or preferred qualifications. - Skills: maybe "Clear, concise communication..." etc. Could be skills. - Benefits: "Benefits and other compensation:" list includes health coverage, PTO, relocation allowance. - Pay: "$200,000 USD/year" and "payment period is weekly". Also "W2 Employee". So we have pay info. - Schedule: "On-site full-time, including early mornings, late afternoons, evening events 2–3x/month, and occasional weekends". That's schedule. We must not include boilerplate like EEO, legal, application instructions, cookie/navigation, etc. Also remove duplicated lines. We must not create sections with filler like "commensurate with experience". We have actual content. We need to output only HTML fragment, no /, no markdown fences. We'll structure:

About the role

... prose summarizing role ...

Responsibilities

• ... each bullet ...

We need to capture responsibilities from "What You Will Be Doing" and maybe also "What You Won’t Be Doing" as responsibilities (what not to do). Could combine. Let's extract bullet points from "What You Will Be Doing": - 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. - This is also where you 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. Telling those two apart on the spot is the judgment this job turns on. - 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. Also "What You Won’t Be Doing" list: - Passing concerns along to someone else. You are a decision-maker, not a liaison, and "I'll raise it with the team" is not an answer families should hear from you. - Keeping the peace by saying yes, softening a standard, bending the model, or treating parent concerns as a ticket queue rather than as relationships that need boundaries. - Escalating every ambiguous situation to avoid owning the call, or at the other extreme, sitting on something that genuinely belongs with campus leadership, safety, or legal. - Taking over the mentoring and coaching decisions that belong to your Guides, or leaving Guides to absorb parent issues you should have resolved. - Routine school administration, desk work, or waiting for a playbook, an established process, or a full team before you act. We could include these as responsibilities (what you will do) and maybe also as "What you won't be doing" could be part of responsibilities or separate section? The instruction says use headings for sections like About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We could put "What you won't be doing" under Responsibilities as notes, or maybe under a separate section but not in list. Since we only have those headings, we can include them in Responsibilities as bullet points (maybe label as "What you will not do"). But we need to preserve all substantive information. So we should include both. We can create two

lists under Responsibilities: one for "What you will be doing" and another for "What you won't be doing". Or combine. Better: Under Responsibilities, we can have a

intro then two

lists with headings? But 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 inside? It says use

for section headings (list). Likely they expect only those headings as sections. We can still have

inside sections. Adding extra headings like

might be okay but not specified. Safer to avoid extra headings; we can just have paragraphs and lists. Thus under Responsibilities we can have a paragraph summarizing, then two lists: maybe preceded by a short sentence like "What you will be doing:" then list, then "What you won't be doing:" then list. That's fine. Now Requirements: Basic Requirements list: - 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 We could also include "W2 Employee" maybe under Pay or Schedule? It's employment type. Could be under Pay or maybe a separate section but not needed. Now Qualifications/Nice-to-have Requirements: "Nice-to-have Requirements Exceptional candidates will have at least one of the following:" list: - An established local network in the campus city, whether school, civic, faith, business, or community, that you can activate quickly - Private or independent school experience with a track record of family retention and community depth, not just enrollment numbers - Experience as the relationship owner alongside educators or other professionals, where you held the family, and they held the craft, and neither of you undermined the other - A launch or early-stage assignment where you personally built local demand and saw it through to committed families - An instinct for creating experiences (events, moments, environments) where people feel they belong to something worth protecting - Startup or early-stage experience where you built from nothing and stayed grounded when things changed quickly We could put these under Qualifications. Skills: maybe we can extract skills from requirements: clear concise communication, hands-on daily use of AI tools, etc. But we already have those in Requirements. Could still have a Skills section summarizing: communication, AI tools, relationship management, decision-making, community building, growth ownership. But we must not invent or summarize away detail; we can list skills that are explicitly mentioned. The posting mentions "Clear, concise communication", "Hands-on daily use of AI tools", "Familiarity with independent, private, or non-traditional education". Also "Independent ownership of ambiguous relationship...". Could treat those as skills. But we already have them in Requirements; maybe better to put them under Skills and keep Requirements focused on experience/eligibility. However the instruction says prefer a few substantive sections over many thin ones. We could combine Requirements and Qualifications into one section? But they ask to use those headings if content exists. We have content for Requirements (basic) and Qualifications (nice-to-have). We'll include both. Skills: maybe we can extract from "Clear, concise communication that earns confidence quickly with affluent, high-expectation families" and "Hands-on daily use of AI tools, and genuine conviction about AI-powered education". Also "Ability to make real-time calls in ambiguous situations". But that's more responsibility. Might be thin. Could skip Skills if not enough distinct content. But we have some explicit skill mentions. Let's include Skills section with those bullet points. Benefits: we have list. Pay: "$200,000 USD/year", "payment period is weekly", "W2 Employee". Also "Relocation assistance available" (mentioned earlier). Also "A one-time relocation allowance." That's under benefits actually. So Pay section: salary and pay frequency. Schedule: "On-site full-time, including early mornings, late afternoons, evening events 2–3x/month, and occasional weekends". Also maybe "including early mornings, late afternoons, evening events 2–3x/month, and occasional weekends". That's schedule. Now we need to remove boilerplate: lines like "Hit the Apply button if you found this interesting and want to learn more." etc. Also "Working with us This is a full-time, W2 employee position with immediate access to benefits (link)... All roles are year-long positions." That's somewhat duplicate of pay/benefits but we already captured pay and benefits. We can ignore the link and year-long positions maybe not needed. Also "Crossover Job Code: LJ-5598-US-Tulsa-DirectorofFami" is metadata to drop. Now produce HTML. We'll need to ensure proper nesting:

About the role

...

Responsibilities

... maybe intro

...

What you won't be doing:

...
etc. Make sure no extra text outside tags. Let's craft the About the role paragraph: summarizing the role: Director of Family Relations, parent-facing co-leader with Guides, owning trust, retention, advocacy, community, growth contribution, handling hard decisions, etc. Use info from posting. We'll write:

As the Director of Family Relations, you serve as the parent-facing co‑leader alongside the student Guides, owning the trust, retention, and advocacy of every family while protecting the Guides’ coaching authority. You lead hard conversations, make real‑time judgments on ambiguous student and family issues, build campus community through traditions, parent networks and local partnerships, and own the growth contribution appropriate to your campus’s phase — driving admissions at launch or under‑enrolled campuses and focusing on retention, referrals and community depth at mature campuses.

That captures substance. Now Responsibilities: We'll have a short intro maybe:

Your core duties include:

then list. But we need to avoid filler. We'll just have
directly after heading? Might be okay. We'll include a brief

before