Enrollment Manager - Part-Time

We need to output HTML fragment with sections: headings

for each section that has content. Use

• for lists. Use

  for prose. No job title heading. No Job ID etc. Remove boilerplate. Preserve all substantive info. Let's parse the posting. Content: - Intro paragraph: "At Love to Code Academy, we're on a mission to cultivate character through technology. As our Enrollment Manager, you'll play a pivotal role in sharing our story and connecting with families who are eager to see their children thrive in coding, robotics, and esports. Our environment is one where teamwork, persistence, and leadership are nurtured, with technology as the backdrop. We're committed to helping students not just learn skills, but also build the traits that will serve them for a lifetime. In this part-time role, you'll have the opportunity to engage with families, guide them through our enrollment process, and help them understand the profound impact our programs can have. Working 15–20 hours per week, primarily after-school and occasionally on weekends, you'll be instrumental in welcoming new students to our academy. Join us at Love to Code Academy, where you'll be part of a team dedicated to shaping future leaders." - Compensation: "$21 - $26 hourly + Bonus" - Qualifications: "Who you are: Experience in community engagement, with a knack for building and nurturing relationships. Ability to communicate effectively and warmly with diverse groups, including parents, community leaders, and influencers. Proven track record of organizing and attending events, with a focus on generating interest and participation. Strong organizational skills to manage schedules, track enrollment processes, and report outcomes. Comfortable working independently, with the initiative to proactively schedule and attend networking events. Familiarity with the education sector, particularly in technology or extracurricular programs, is a plus. Ability to work flexible hours, including after-school and occasional weekends, to meet with families and attend events." - Why this role matters: paragraph. - Responsibilities: two sub-sections: Community & Awareness (~6–8 hrs/week) and Enrollment Conversion (~8–10 hrs/week). Each has bullet points. We need to decide sections: maybe About the role (intro), Responsibilities, Qualifications, Benefits? There's compensation (pay) and maybe schedule? The posting mentions working 15–20 hours per week, primarily after-school and occasionally on weekends. That's schedule info. Also compensation: $21 - $26 hourly + Bonus. So we can have Pay and Schedule sections. Benefits? Not mentioned besides bonus. Could include Bonus in Pay. No explicit benefits like health etc. So we may not create Benefits section unless there is content. The instruction: "Prefer a few substantive sections over many thin ones." So we can combine Pay and Schedule maybe into one? But they said use headings for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). So we can create sections for About the role (intro), Responsibilities, Qualifications, Pay, Schedule. Possibly also "Why this role matters" could be part of About the role. Could incorporate into About the role paragraph. We must not repeat job title as heading. So we will not have heading "Enrollment Manager". Use About the role heading. We need to preserve all substantive info. Let's extract. Intro paragraph includes mission, role description, part-time hours, etc. Also includes "Join us at Love to Code Academy, where you'll be part of a team dedicated to shaping future leaders." That's fine. Compensation: "$21 - $26 hourly + Bonus". We'll put under Pay heading. Schedule: "Working 15–20 hours per week, primarily after-school and occasionally on weekends". Also mention flexible hours in qualifications. We'll put under Schedule heading. Qualifications: list of bullet points. Responsibilities: two sub-sections with bullet points. We'll combine under Responsibilities heading with subheadings? The instruction only says use

  for section headings. Could we use

  for sub-sections? Possibly but they said section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). So sub-sections maybe not needed as separate headings; we can just list bullet points under Responsibilities. However we have two categories with hour breakdowns. We could keep them as separate

  sub-sections like "Community & Awareness" and "Enrollment Conversion". But those are not in the list of example headings but they are still headings. The instruction: "use

  for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." It says e.g., not exclusive. So we can use other headings as needed. But we should avoid creating thin sections. However these are substantive. We'll produce:

  About the role

  ...

  Responsibilities

  Community & Awareness (~6–8 hrs/week)

  ...

  Enrollment Conversion (~8–10 hrs/week)

  ...
  But they said use

  for section headings. Using

  might be okay but not specified. Safer to use

  for each subsection? Could cause many headings but still okay. However they said prefer a few substantive sections over many thin ones. Having many subheadings may be thin. Maybe we keep Responsibilities as one section with paragraphs describing each area, using

  for prose and

  for lists. Could embed the hour breakdown inside the prose. Let's craft:

  Responsibilities

  Community & Awareness (~6–8 hrs/week):

  • Attend 4-6 community/networking lunches per month with local leaders — chambers of commerce, service clubs, scouting organizations — representing the academy with warmth and clarity, with the goal of generating trial visits and referrals from those relationships.
  • Build relationships with 4-6 local parent bloggers/influencers per month through 1:1 lunches, opening new audiences and generating authentic word of mouth that converts into trial signups.
  • Proactively schedule the next month's lunches and events in the gaps between meetings, so the pipeline of new relationships never runs dry.

  Enrollment Conversion (~8–10 hrs/week):

  • Run trial classes and birthday events as the front door of the enrollment journey — greeting families, capturing contact info, and setting expectations for next steps on-site.
  • Own the full trial-to-enrollment pipeline end to end: track every family from first visit through follow-up to a clear enrolled-or-declined outcome, and report monthly trial-to-enrollment conversion rate.
  That seems fine. Qualifications: list.

  Qualifications

  • Experience in community engagement, with a knack for building and nurturing relationships.
  • Ability to communicate effectively and warmly with diverse groups, including parents, community leaders, and influencers.
  • Proven track record of organizing and attending events, with a focus on generating interest and participation.
  • Strong organizational skills to manage schedules, track enrollment processes, and report outcomes.
  • Comfortable working independently, with the initiative to proactively schedule and attend networking events.
  • Familiarity with the education sector, particularly in technology or extracurricular programs, is a plus.
  • Ability to work flexible hours, including after-school and occasional weekends, to meet with families and attend events.
  Pay:

  Pay

  $21 - $26 hourly + Bonus

  Schedule:

  Schedule

  15–20 hours per week, primarily after-school and occasionally on weekends.

  We might also include "Why this role matters" paragraph inside About the role. Let's craft About the role paragraph combining intro and why it matters. About the role paragraph: "At Love to Code Academy, we're on a mission to cultivate character through technology. As our Enrollment Manager, you'll play a pivotal role in sharing our story and connecting with families who are eager to see their children thrive in coding, robotics, and esports. Our environment is one where teamwork, persistence, and leadership are nurtured, with technology as the backdrop. We're committed to helping students not just learn skills, but also build the traits that will serve them for a lifetime. In this part-time role, you'll have the opportunity to engage with families, guide them through our enrollment process, and help them understand the profound impact our programs can have. Working 15–20 hours per week, primarily after-school and occasionally on weekends, you'll be instrumental in welcoming new students to our academy. Join us at Love to Code Academy, where you'll be part of a team dedicated to shaping future leaders. Parents rarely enroll because they want their child to learn to code. They enroll because they want their child to grow. You'll be the person who helps them see that growth is exactly what we offer — and gives their child the chance to experience it firsthand." But note we moved schedule to separate Schedule section; we might not want to duplicate schedule info in About the role. However we need to preserve all substantive info; we can keep schedule in About the role and also have Schedule section? That would duplicate. Better to keep schedule only in Schedule section and remove from About the role to avoid duplication. But we must preserve all info; we can keep schedule in Schedule section and not repeat. However the About the role paragraph originally includes schedule; we can rephrase to omit schedule but still keep meaning. Let's keep About the role without schedule details, and schedule in its own section. Thus About the role paragraph: "At Love to Code Academy, we're on a mission to cultivate character through technology. As our Enrollment Manager, you'll play a pivotal role in sharing our story and connecting with families who are eager to see their children thrive in coding, robotics, and esports. Our environment is one where teamwork, persistence, and leadership are nurtured, with technology as the backdrop. We're committed to helping students not just learn skills, but also build the traits that will serve them for a lifetime. In this part-time role, you'll have the opportunity to engage with families, guide them through our enrollment process, and help them understand the profound impact our programs can have. Join us at Love to Code Academy, where you'll be part of a team dedicated to shaping future leaders. Parents rarely enroll because they want their child to learn to code. They enroll because they want their child to grow. You'll be the person who helps them see that growth is exactly what we offer — and gives their child the chance to experience it firsthand." Now schedule section: "Working 15–20 hours per week, primarily after-school and occasionally on weekends." Pay section: "$21 - $26 hourly + Bonus" Now ensure we didn't miss any info: The "Why this role matters" paragraph is incorporated. The bullet points under responsibilities are included. Qualifications list included. No mention of benefits besides bonus; we included bonus in Pay. No other benefits. Check for any other info: "Ability to work flexible hours, including after-school and occasional weekends, to meet with families and attend events." That's in qualifications; we kept. Now produce HTML fragment. We must not include or . Just the fragment. Let's write:

  About the role

  At Love to Code Academy, we're on a mission to cultivate character through technology. As our Enrollment Manager, you'll play a pivotal role in sharing our story and connecting with families who are eager to see their children thrive in coding, robotics, and esports. Our environment is one where