Education Program Manager

We need to output HTML fragment with sections for headings: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. Use

for each heading. Use

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

  for prose. Do NOT repeat job title as heading. Do NOT include Job ID/requisition numbers. Remove boilerplate. Include only sections with real specific content. We need to parse the posting. First, "About Junior Achievement Of Southern Nevada" is description of organization. Could be "About the role"? Actually "About the role" heading is for summary of role. The posting includes "Position Summary". So we can put that under "About the role". Use

  About the role

  then

  with the position summary text. Next "Essential Functions" includes many duties; that's responsibilities. So

  Responsibilities

  then
  • each bullet. We need to extract bullet points from Essential Functions. Let's list them: - Oversee implementation, scheduling, and delivery of JASN's traditional K–12 programs in partnership with schools, educators, and the Education Coordinator - Lead coordination and execution of traditional program events, including JA Inspire and SWTBF - Manage program quality and quantity across assigned programs and events, ensuring consistent and effective implementation - Ensure adherence to JA USA program models and organizational quality standards, including documenting and submitting required program variances - Ensure appropriate school contracts, class registration forms, and other program documentation are completed and maintained - Coordinate ordering and timely delivery of program materials to participating schools - Become cross-trained across additional JASN education programs and support alternative delivery approaches, including after-school programs, summer camps, private-school partnerships, and collaborative agency programming - Supervise staff supporting traditional education programming, including coaching, scheduling support, performance feedback, and ongoing development - Develop and facilitate training for educators, school staff, volunteers, or other program stakeholders as needed - Evaluate training effectiveness and identify opportunities to strengthen participant preparation and program delivery - Provide staff with clear expectations, resources, and support necessary to execute programs effectively and consistently - Develop and implement strategies to engage and retain educators and schools, including classroom visits, newsletters, phone outreach, follow-up sessions, and other relationship-building activities - Cultivate and renew partnerships with teachers, schools, districts, and other educational stakeholders to sustain participation and identify opportunities for program growth - Develop and deliver presentations to prospective educators and schools that support strategic program expansion - Serve as a responsive and knowledgeable point of contact for educational partners throughout program planning and implementation - Represent JASN at school district functions, career fairs, education-related committees, and other community engagement opportunities - Coordinate collection of applicable pre- and post-assessments, teacher surveys, and other program evaluation measures - Use participant and stakeholder feedback to identify opportunities for continuous improvement - Develop post-program recap reports documenting successes, challenges, opportunities, and recommended improvements - Maintain accurate program, educator, and community-partner records within JASN's CRM - Develop program forecasts, progress reports, and other information requested by the Director of Community Engagement or executive leadership - Implement grant-funded program objectives and ensure required program and evaluation data are accurately tracked and reported - Represent JASN to schools, youth-serving organizations, corporate/community partners, and other external stakeholders and communicate the organization's mission and opportunities for engagement - Identify opportunities to expand traditional programming through strategic school, district, community, and organizational partnerships - Collaborate across JASN departments to support organizational priorities, program growth, and a consistent partner experience - Participate in education-related committees, meetings, events, and community outreach opportunities as appropriate That's a lot. We'll put them as
  • . Next "Required Qualifications" and "Desired Qualifications". Those can go under Requirements or Qualifications. The instruction: Use headings: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We need to decide where to put qualifications vs requirements vs skills. Typically "Required Qualifications" could go under Requirements. "Desired Qualifications" could go under Qualifications or Skills. But we have both headings; we need to include sections only if there is real specific content. We have required qualifications list; we have desired qualifications list. We could put required under Requirements, desired under Qualifications. Skills maybe we can extract from required/desired: e.g., Strong verbal and written communication skills, organizational, time-management, prioritization, proficiency with Microsoft Office, comfort using CRM/database, reliable transportation, etc. But we might just put skills under Skills heading if we have explicit skill list. The posting includes "Strong verbal and written communication skills, including demonstrated public-speaking or presentation experience", "Strong organizational, time-management, and prioritization skills", "Proficiency with Microsoft Office and comfort using CRM/database systems", "Reliable transportation, valid driver's license, and current automobile insurance". Those could be skills. However we also have "Desired Qualifications" includes experience supervising staff, implementing K-12 programming, building partnerships, facilitating training, using program data, managing grant-funded programs, supporting program expansion, experience with Blackbaud CRM. Those could be qualifications. We need to avoid duplication. Let's structure: - About the role: position summary paragraph. - Responsibilities: list of essential functions. - Requirements: required qualifications (bullet list). Could also include "Bachelor's degree or equivalent..." etc. - Qualifications: desired qualifications (bullet list). - Skills: maybe we can extract skill-based items from required qualifications that are skills: Strong verbal and written communication skills, Strong organizational, time-management, and prioritization skills, Proficiency with Microsoft Office and comfort using CRM/database systems, Reliable transportation, valid driver's license, current automobile insurance, Ability to work across office, school, event, and community environments and meet physical requirements, Ability to successfully complete required background checks. But some of those are more like requirements. Might be okay to put them under Skills. But we need to avoid filler like "commensurate with experience". Not present. Benefits: we have a detailed benefits list. So

    Benefits

    then
    • each benefit. Pay: we have compensation: salary range $45,000 to $50,000 annually. So

      Pay

      then

      with that. Schedule: The posting says "This is a full-time, in-person, exempt position." That's schedule info (full-time). So we can put

      Schedule

      then

      Full-time, in-person, exempt position.

      We must not include sections with placeholder text. All have real content. Now ensure we don't include boilerplate like "Our Commitment", "Additional Information". Those are EEO/legal boilerplate; we should remove them. Also remove "Junior Achievement of Nevada does not provide sponsorship..." etc. That's legal/visa info; remove. Also remove "About Junior Achievement Of Southern Nevada" maybe we could incorporate into About the role? But we already have position summary. The "About Junior Achievement Of Southern Nevada" paragraph is about organization; could be considered "About the role"? Actually it's about the organization, not the role. The instruction says use

      for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). So "About the role" likely expects a summary of the role, not the organization. However we have "Position Summary". That is suitable. The organization description could be omitted or maybe we could include it under About the role as extra context. But the instruction says "Do NOT repeat the job title as a heading (the page already shows it) and do NOT put Job ID / requisition numbers as headings — fold minor metadata into a short

      or drop it." It doesn't forbid including organization description. But we should preserve ALL substantive information; do NOT invent or summarize away detail. So we should keep the organization description somewhere. Where? Could be a paragraph before About the role? But we only allowed headings from list. Could we add a

      before first heading? The instruction says output ONLY the HTML fragment — no /, no markdown code fences. It didn't forbid extra paragraphs outside headings. It said use

      for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). Use

      • for any list of duties/requirements/benefits, and

        for prose. So we can have prose paragraphs not under a heading? It says use

        for prose. It doesn't say all prose must be under a heading. But they gave examples of headings. Probably they expect each section to have a heading. However we could include a brief intro paragraph about the organization under a heading like "About the role"? But that heading is for role, not organization. Might be okay to include organization description under About the role as part of role context. But risk of misrepresenting. Alternatively we could add a heading "About the organization" but not in allowed list. The instruction says use

        for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). The "e.g." suggests those are examples, not exclusive list. But they say "Prefer a few substantive sections over many thin ones." So we could add an "About the organization" section if we want, but better to stick to the given headings to be safe. We could incorporate the organization description into the About the role paragraph, merging with position summary. That would preserve the info. Let's do that: About the role paragraph includes both organization description and position summary. That would be substantive. Thus:

        About the role

        [organization description] [position summary]

        We need to ensure we don't lose any detail. Let's combine: Organization description: "Junior Achievement’s learning experiences promote transferable skills and competencies students need to take advantage of economic opportunity and achieve economic mobility. Our lessons use financial literacy, work readiness, and entrepreneurial concepts to emphasize the importance of continuing education and training beyond high school, especially in high-growth, high-demand fields. At the same time, our experiential learning approach ensures students gain the critical and creative thinking, collaboration, communication, and technical literacy skills needed to become lifelong learners to navigate “what’s next” in our ever-changing world." Position Summary: "The Education Program Manager leads the delivery, quality, and continued growth of Junior Achievement of Southern Nevada's traditional K–12 programming. Reporting to the Director of Community Engagement, this position oversees program implementation and special events, supervises staff supporting traditional education programs, and builds strong relationships with educators, schools, districts, volunteers, and community partners. The Education Program Manager ensures programs are delivered consistently with JA USA models and organizational quality standards while using feedback and program data to strengthen implementation and support continued participation and expansion. The position currently oversees programs including JA Our City, JA Our Region, JA More Than Money, JA It's My Future, JA Career Success, and JA Company Pop-Up, as well as events including JA Inspire and Swimming With The Big Fish (SWTBF). Program assignments may evolve based on organizational and community needs. The ideal candidate is an organized, collaborative, and relationship-oriented leader who enjoys supporting staff and educators, managing multiple programs simultaneously, and building partnerships that expand access to high-quality JA learning experiences. This individual will also become cross-trained across other JASN education programs and support alternative delivery models as organizational needs arise. This is a full-time, in-person, exempt position." We can combine them into one paragraph or two paragraphs. Use

        for prose; could have multiple

        inside the section. That's fine. Now Responsibilities: list as above. Requirements: Required Qualifications bullet list. Qualifications: Desired Qualifications bullet list. Skills: maybe we can extract skill-based items from Required Qualifications that are not already captured. But we might also include some from Required Qualifications that are skills: Strong verbal and written