IT Coordinator, Alpha - $90,000/year USD

We need to produce HTML fragment with sections: headings

for sections like About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. Only include sections that have real specific content. We must not repeat job title as heading. No Job ID/requisition numbers as headings; fold minor metadata into short

or drop it. Remove boilerplate, navigation, legal, EEO, duplicated lines, application instructions. Preserve all substantive info. We need to parse the posting. Content: - LOCATION NOTE: This in-person role is located on our Chantilly, VA campus. (Location info) - Elite schools aren't built... (intro paragraph) - As our IT Coordinator, you'll be the linchpin... (intro) - This isn't about maintaining status quo... (intro) - What You Will Be Doing (list of bullet points) - Orchestrating compelling campus tours... - Executing a strategic communications approach... - Implementing and enforcing comprehensive safety protocols... - Directing facilities management... - Leveraging data analytics... - What You Won’t Be Doing (list of bullet points) - Developing educational content... - Following reactive protocols... - Delivering standardized... - Working in isolation... - IT Coordinator Key Responsibilities (paragraph) - Drive measurable enrollment growth while maintaining... - Basic Requirements (list) - Bachelor's Degree (field of study not specified) - Proven track record in admissions, enrollment management, or customer-facing roles within educational contexts - Superior communication capabilities across all mediums—written, verbal, and interpersonal - Exceptional emotional intelligence with demonstrated ability to establish credibility and trust - Proficiency in data-driven decision making and performance analytics - Self-directed work ethic with demonstrated initiative and accountability - Commitment to on-site presence at our Chantilly, VA campus - Authorization to work in the United States without sponsorship - About Alpha (paragraphs) - Join the team building school around student growth... - Alpha reimagines the school day... - Roles with real student impact... - Education work that pays like it matters... - A culture built for builders... - Alpha is where you can do the most meaningful work... - There is so much to cover... (maybe filler) - Working with us (paragraph) - This is a full-time, W2 employee position with immediate access to benefits (link) - All roles are year-long positions. - The compensation level for this role is $90,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-5629-US-Miami-ITCoordinator.001 (metadata) We need to include sections: maybe About the role (intro), Responsibilities (What You Will Be Doing + Key Responsibilities?), Requirements (Basic Requirements), Qualifications? Possibly combine Requirements and Qualifications. Skills? Could be derived from requirements. Benefits? There's mention of immediate access to benefits but not specifics; we should not create Benefits section unless posting actually states them. It says "immediate access to benefits" but no detail; that might be considered not specific enough? The rule: never create Pay/Schedule/Benefits sections unless the posting actually states them. It states compensation level $90,000 USD/year and payment period weekly. That's specific enough for Pay and Schedule. Benefits: only says immediate access to benefits, no detail; that might be too vague; better to omit Benefits section. Schedule: payment period weekly is schedule? Actually schedule could be work schedule; but they mention payment period weekly, not work schedule. The rule: Schedule section only if posting actually states them. It mentions payment period weekly, which is about pay frequency, not work schedule. Might still be considered schedule? The instruction: "never create Pay/Schedule/Benefits sections unless the posting actually states them." Pay: they state compensation level $90,000 USD/year. Schedule: they state payment period weekly (maybe considered schedule). Could include Schedule with weekly pay frequency. However typical schedule would be full-time, year-long positions. They also say "All roles are year-long positions." That's duration, not schedule. Could treat as Schedule? Might be okay to include Schedule with "Year-long positions, full-time". But we need to avoid filler. Let's include Pay and Schedule sections with the specific info. We also need About the role section: could combine intro paragraphs before "What You Will Be Doing". That includes location note, elite schools paragraph, As our IT Coordinator..., This isn't about maintaining status quo... That's substantive. Responsibilities: combine "What You Will Be Doing" bullet list and "IT Coordinator Key Responsibilities" paragraph. Requirements: Basic Requirements list. Qualifications: maybe not separate; we could omit Qualifications if not distinct. Skills: maybe not needed. We must not repeat job title as heading. So no

IT Coordinator

. Use headings like About the role, Responsibilities, Requirements, Pay, Schedule. We need to output only HTML fragment, no /. Use

for each section heading, then content:

for prose,

• for lists. We must preserve all substantive information; do not invent or summarize away detail. So we need to keep all bullet points exactly as given (maybe slight rephrase? Should preserve meaning). We'll copy the bullet points. Let's extract bullet points: What You Will Be Doing: - Orchestrating compelling campus tours that convert prospects by demonstrating how Alpha's commitments translate to tangible student outcomes - Executing a strategic communications approach that guides families through the admissions journey with personalized, timely engagement - Implementing and enforcing comprehensive safety protocols that protect our students and build parent confidence - Directing facilities management with precision—anticipating needs, managing vendor relationships, and ensuring operational continuity - Leveraging data analytics to optimize both enrollment metrics and operational efficiency What You Won’t Be Doing: - Developing educational content or classroom instruction—your domain is creating the environment where exceptional teaching happens - Following reactive protocols that address problems after they emerge—we expect proactive leadership - Delivering standardized, impersonal admissions experiences that fail to address each family's unique concerns - Working in isolation—your success depends on effective collaboration across all stakeholders IT Coordinator Key Responsibilities: - Drive measurable enrollment growth while maintaining an operationally flawless campus environment that empowers our educational team to focus exclusively on delivering superior learning outcomes. That's a single sentence; could be a

  or

  • . Since it's a responsibility, we can put as

    . Basic Requirements list: - Bachelor's Degree (field of study not specified) - Proven track record in admissions, enrollment management, or customer-facing roles within educational contexts - Superior communication capabilities across all mediums—written, verbal, and interpersonal - Exceptional emotional intelligence with demonstrated ability to establish credibility and trust - Proficiency in data-driven decision making and performance analytics - Self-directed work ethic with demonstrated initiative and accountability - Commitment to on-site presence at our Chantilly, VA campus - Authorization to work in the United States without sponsorship Note: "Bachelor's Degree (field of study not specified)" includes "(field of study not specified)" which is placeholder-like; but it's actual text. The rule: 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. This is about headings with filler text; but here it's inside a list item; it's okay to keep it as it's part of the requirement. We should keep it. Now About the role section: combine location note and intro paragraphs. Location note: "LOCATION NOTE: This in-person role is located on our Chantilly, VA campus." Could be a

    . Then intro: "Elite schools aren't built on academic excellence alone. They're built by operational maestros who make excellence possible. At Alpha, you'll be the linchpin that drives both growth and operational integrity. As our IT Coordinator, you'll master the dual arts of enrollment expansion and campus management—creating the foundation that enables our educational mission to thrive. This isn't about maintaining status quo; it's about building systems that scale with our ambitious growth while maintaining the exceptional experience that families expect from a premium educational institution." We'll combine into one or two paragraphs. Now Pay section: compensation level $90,000 USD/year. Schedule section: payment period weekly; also All roles are year-long positions; full-time, W2 employee position. Could include: "This is a full-time, W2 employee position. All roles are year-long positions. The payment period is weekly." We should not include application instructions like "Hit the Apply button". Remove that. Also remove "Working with us" heading? It's a heading but we can treat as part of Pay/Schedule? Actually "Working with us" is a heading in the original; we can incorporate its content into Pay/Schedule or maybe a separate section like "Employment Details". But we only have allowed headings list; we could create a section like "Employment Details" but not in list. Better to fold into Pay/Schedule. We must not include duplicated lines, boilerplate like "Consult www.crossover.com/help-and-faqs for more details on this topic." That's maybe okay to keep as a link? It's not boilerplate? It's a reference; could keep as

    with link. But it's not essential; but we can keep as it's substantive info about where to find more details. However it's not a list; we can keep as a

    . Also "Crossover Job Code: LJ-5629-US-Miami-ITCoordinator.001" is metadata; we can fold into a short

    or drop. Probably drop as minor metadata. Now produce HTML. Structure:

    About the role

    LOCATION NOTE: This in-person role is located on our Chantilly, VA campus.

    Elite schools aren't built on academic excellence alone. They're built by operational maestros who make excellence possible. At Alpha, you'll be the linchpin that drives both growth and operational integrity. As our IT Coordinator, you'll master the dual arts of enrollment expansion and campus management—creating the foundation that enables our educational mission to thrive. This isn't about maintaining status quo; it's about building systems that scale with our ambitious growth while maintaining the exceptional experience that families expect from a premium educational institution.

    Responsibilities

    • Orchestrating compelling campus tours that convert prospects by demonstrating how Alpha's commitments translate to tangible student outcomes
    • Executing a strategic communications approach that guides families through the admissions journey with personalized, timely engagement
    • Implementing and enforcing comprehensive safety protocols that protect our students and build parent confidence
    • Directing facilities management with precision—anticipating needs, managing vendor relationships, and ensuring operational continuity
    • Leveraging data analytics to optimize both enrollment metrics and operational efficiency

    Drive measurable enrollment growth while maintaining an operationally flawless campus environment that empowers our educational team to focus exclusively on delivering superior learning outcomes.

    What You Won’t Be Doing

    ... but we might not need a separate heading for "What You Won’t Be Doing". Could incorporate into Responsibilities? But it's substantive; we could make a section "What You Won’t Be Doing". However allowed headings list does not include that; but we can still use

    for any section heading? The instruction: use

    for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). It gives examples but not exclusive list. It says "use

    for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." So we can use other headings as long as they are

    .