Parent Relations Director, 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 where posting has real specific content. We must not repeat job title as heading. Must not include Job ID etc. Must preserve all substantive info, not invent or summarize away detail. Remove boilerplate, navigation, legal, EEO, etc. Also remove application instructions. Must not include filler like "commensurate with experience". Must not create Pay/Schedule/Benefits sections unless posting actually states them. The posting includes Benefits and other compensation: health coverage etc. Also includes compensation level $200,000 USD/year, payment period weekly. Also mentions Working with us: full-time, W2 employee position with immediate access to benefits, all roles year-long positions. Also mentions schedule? It says On-site full-time, including early mornings, late afternoons, evening events 2–3x/month, and occasional weekends. That's schedule info. So we can have Benefits, Pay, Schedule sections. We need sections: About the role (maybe a brief description). Responsibilities (What You Will Be Doing). Requirements (Basic Requirements). Qualifications? Could combine Requirements and Qualifications? The posting has Basic Requirements and Nice-to-have Requirements (which could be Qualifications). Also Skills? Could be part of Requirements. We'll follow instruction: use headings for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). We'll include only those with real content. We need About the role: we can summarize the role description from the intro: "Alpha School students...". Must preserve all substantive info, not invent or summarize away detail. But we can paraphrase? The instruction: "Preserve ALL substantive information; do NOT invent or summarize away detail." That suggests we should not omit details, but we can rephrase? It says do NOT summarize away detail. So we need to keep details, maybe as bullet points? But we can keep prose that includes details. We'll include a paragraph that captures the role description but not omit details. However we must not invent. We'll try to keep the essence but not lose details. Might be okay to have a concise paragraph that still includes key points: relationship owner, hard conversations, parent-facing co-leader with Guides, decision-making, community building, growth contribution depending on campus phase. That's basically the responsibilities. But we already have Responsibilities section for What You Will Be Doing. So About the role could be a brief overview: "Alpha is hiring a Parent Relations Director to own family relationships, lead hard conversations, partner with Guides, manage community, and drive growth according to campus stage." That seems okay and not inventing. Responsibilities: list bullet points from "What You Will Be Doing" and also "Key Responsibilities". We'll combine. Requirements: Basic Requirements list. Qualifications: Nice-to-have Requirements. Skills: maybe we can extract communication, AI tools familiarity, etc. Could be part of Requirements but we can make a Skills section: "Clear, concise communication... Familiarity with independent, private, or non-traditional education... Hands-on daily use of AI tools". We'll put those. Benefits: list health coverage etc. Pay: compensation $200,000/year, weekly payment. Schedule: On-site full-time, early mornings, late afternoons, evening events 2–3x/month, occasional weekends. We must not include boilerplate like "Working with us This is a full-time, W2 employee position..." but we already used schedule and benefits. The part about W2 employee position immediate access to benefits is somewhat redundant with benefits; we can incorporate into Benefits maybe. But we should not repeat. We'll keep schedule and pay. We must not include navigation, legal, EEO, etc. The posting includes "About Alpha", "Join the team building school around student growth", etc. That's about company; we could include in About the role? Might be considered boilerplate? It's descriptive of Alpha, not directly about role. Might be okay to include in About the role? But instruction: remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. "About Alpha" is not boilerplate; it's company description. Could be included in About the role? Might be okay but we need to avoid duplication. We'll keep About the role focusing on role, not company. Could add a short "About Alpha" section? Not in allowed headings list. So we skip. We must output only HTML fragment, no /, no markdown fences. Let's craft:

About the role

Alpha is hiring a Parent Relations Director to own the relationship with every family on campus, lead hard conversations, partner with Guides as the parent‑facing co‑leader, make real‑time judgments in ambiguous situations, build community traditions and parent networks, and drive the growth contribution appropriate to the campus’s stage (launch/under‑enrolled vs. mature).

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 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 ensure families know who owns what.
• Make real‑time calls in ambiguous student and family situations; 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, plus trusted parent champions who become the campus’s most credible voice.
• Own the growth contribution your campus phase calls for: at a launch or under‑enrolled campus, develop local demand and personally own admissions follow‑through to enrollment; at a mature campus, focus on retention, referrals, and clean handoffs to admissions.

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–3×/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.

Qualifications

• Established local network in the campus city (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.
• 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.

Skills

• 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.

Benefits

• Health coverage (medical, dental, vision)
• Life and disability insurance
• Voluntary benefits
• Tax‑advantaged FSA, HSA, and commuter accounts
• 401(k)
• Paid time off and parental leave
• One‑time relocation allowance

Pay

$200,000 USD per year, paid weekly.

Schedule

On‑site full‑time, including early mornings, late afternoons, evening events 2–3×/month, and occasional weekends.

Check for any duplicated content: We have communication etc repeated in Requirements and Skills; that's okay but maybe we should avoid duplication? The instruction: remove duplicated lines. Having same bullet in two sections could be considered duplicated. We could adjust: maybe keep communication only in Requirements, and Skills could focus on AI tools and education familiarity. But we already have those in Requirements. Let's adjust Skills to be distinct: maybe "Ability to build trust and navigate high‑expectation family dynamics", "Experience with community‑building initiatives", "Strategic thinking for growth initiatives". However we must not invent details. We can derive from posting: "Clear, concise communication that earns confidence quickly with affluent, high‑expectation families" is in Requirements. "Familiarity with independent, private, or non‑traditional education" also in Requirements. "Hands‑on daily use of AI tools, and genuine conviction about AI‑powered education" also in Requirements. So Skills section would be duplicate if we list same. Perhaps we can omit Skills section entirely, as the posting doesn't have a separate skills list beyond those already in Requirements. The instruction: include a section ONLY when the posting has real, specific content for it. Since there is no distinct skills list separate from requirements, we should not create a Skills section. So we drop Skills. Similarly, About the role we created; is there real specific content? The posting includes a description of the role in the intro paragraphs. That's specific enough. We'll keep. Now check for any boilerplate we inadvertently kept: "Working with us This is a full-time, W2 employee position with immediate access to benefits..." We didn't include that. Good. We kept "All roles are year-long positions." Not included; maybe that's schedule? Not needed. Could be considered part of schedule? It's about duration, not schedule. Not required to include. We'll omit. Now ensure we didn't miss any substantive info: The posting mentions "Compensation level for this role is $200,000 USD/year. The payment period is weekly." We have Pay. Benefits: we listed. Schedule: we have. Also mention "Nice-to-have Requirements" we turned into Qualifications. Check for any other specifics: "Alpha isn't a traditional school. Students finish core academics in two hours a day using AI-powered apps, then spend the rest of their time on public speaking, critical thinking, and real-world projects. No lectures. No busywork. Top 1% results nationwide. The families who choose it are paying