Graduation Candidate Advocate

We need to output HTML fragment with sections: About the role? Actually they said use

for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). We must not repeat job title as heading. We need to include sections only if posting has real specific content. Let's parse content. We have: - About Acceleration Academies (intro). Could be "About the role"? Actually "About Acceleration Academies" is about organization. Could be "About the role"? The role description is under "The Role". Could treat as "About the role". We'll include a section with heading

About the role

and then paragraphs summarizing the role description. But we must preserve all substantive information, not invent or summarize away detail. We need to keep details. However we can combine paragraphs. We need to avoid filler like "commensurate with experience". Not present. We need sections: Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. Let's see what content maps: Responsibilities: Under "Key Responsibilities" with subpoints: Community Engagement and Advocacy, Recruitment and Canvassing, Enrollment, Retention and Attendance, Academics, Operations. We'll output a

• list. Requirements: Education: Bachelor's degree required. Experience: 1-3 years of relevant experience in educational support, case management, or working with at-risk youth. Qualifications: Preferred Qualifications: Willingness to obtain an Ohio substitute teaching license, familiarity with myINCITE, Slack, bilingual Spanish preferred, experience in non-traditional educational settings, comfort with project based and competency based learning approaches. Skills: Under "What We’re Looking For" includes Skills bullet list: Strong relationship building and excellent communication across differences..., ability to motivate others..., strong organization..., comfort taking charge..., sound judgment..., passion..., technology: advanced proficiency with Google Workspace and email, Zoom, ability to learn new systems quickly, proficiency with LMS and educational tech tools expected. We could separate Skills and maybe also include Technology as part of Skills. But we have a Skills section; we can include those bullet points. Benefits: Under "Why Join Us?" includes bullet list: Competitive Compensation: Starting at $18.00 an hour; Retirement Savings: 401(k) plan with up to a 4% company match; Comprehensive Insurance Coverage: list; Flexible Paid Time Off; Wellness Support; Employee Referral Incentives; Professional Development; Bonus Opportunities. Pay: The compensation is mentioned: Starting at $18.00 an hour. That's pay info. Should we create a Pay section? The instruction: "never create Pay/Schedule/Benefits sections unless the posting actually states them." Pay is stated: Starting at $18.00 an hour. So we can create a Pay section with that detail. However Benefits section also includes compensation as part of benefits; but we can still have Pay separate. However they said prefer a few substantive sections over many thin ones. Might combine Pay into Benefits? But they said include a section ONLY when posting has real, specific content for it. Pay is specific: $18.00 an hour. So we could include Pay section. Benefits also have many items. Could keep both. Schedule: Not mentioned explicitly. There's no schedule info like full-time, part-time, hours. So we should not create Schedule section. We also need to include Work Location maybe as a short paragraph? Not a heading. Could be included in About the role or a separate paragraph? The instruction: do NOT put Job ID / requisition numbers as headings — fold minor metadata into a short

  or drop it. Work location is minor metadata; we can include a short

  after About the role maybe. We must remove boilerplate: cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. At the end there is "Third-Party Agency & Recruiter Notice", "Equal Opportunity Employer", "Responsibilities All roles at Acceleration Academies include core responsibilities..." That seems like boilerplate; we should remove. Also "Ready to Make a Difference?" etc is maybe call to action; but that's application instruction? It says "If you’re passionate... we’d love to hear from you." That's application instruction; we should remove. We need to preserve all substantive information; we must not discard substantive content like the role description, responsibilities, requirements, qualifications, skills, benefits, pay. Let's craft HTML. Structure:

  About the role

  ... description of role ...

  Work Location: 4030 Reading Road, Cincinnati, OH 45229. This position is onsite at Cincinnati Acceleration Academy.

  Responsibilities

  • Community Engagement and Advocacy: Serve as a connector between students and community resources, identifying and securing support for students experiencing homelessness, emotional distress, and other urgent needs; build and maintain relationships and partnerships across the greater Cincinnati community; represent the academy at community events and initiatives; advocate for students by assisting in identifying solutions and connecting them to academy staff for academic and non-academic support.
  • Recruitment and Canvassing: Lead and contribute to canvassing efforts throughout the community to attract new students; communicate the mission, model, and measurement goals of Acceleration Academies clearly and confidently to anyone; support ongoing student recruitment efforts alongside the academy team.
  • Enrollment: Assist with the registration and enrollment process for new students; provide comprehensive support during student orientation to set the stage for success.
  • Retention and Attendance: Act as a case manager for a designated cohort of students, monitoring and documenting regular attendance; implement the Acceleration Academy Retention Protocol through proactive outreach such as texts, calls, and home visits; utilize technology tools for efficient daily monitoring and maintenance of student attendance and retention records.
  • Academics: Deliver one-on-one academic support and interventions to facilitate student learning and complement the work of center professionals; collaborate closely with the student support team to track learning pathways, monitor behavior, and implement transition plans, including incentive programs to bolster student achievement; utilize the Learning Management System and other technology resources to monitor and facilitate student progress and maintain up-to-date academic records, including attendance; engage in professional development activities to enhance academic support practices.
  • Operations: Provide daily operational support for the academy, such as answering phones and maintaining student records; participate actively in academy meetings and school or community events; step into academy and Graduation Candidate Advocate related tasks as needed on a small, closely connected team; perform additional duties as assigned to support the overall mission of the academy.

  Requirements

  • Education: Bachelor's degree required.
  • Experience: 1-3 years of relevant experience in educational support, case management, or working with at-risk youth.

  Qualifications

  • Willingness to obtain an Ohio substitute teaching license.
  • Familiarity with myINCITE, Slack, or similar platforms.
  • Bilingual skills, Spanish preferred.
  • Experience in non-traditional educational settings.
  • Comfort with project-based and competency-based learning approaches.

  Skills

  • Strong relationship building and excellent communication across differences in race, gender, orientation, need, mindset, and working style.
  • Ability to motivate others and inspire confidence.
  • Strong organization and executive function.
  • Comfort taking charge and making decisions with minimal supervision in a fast-paced environment.
  • Sound judgment in conflict resolution.
  • Passion: genuine commitment to supporting students who have disengaged from traditional schooling and a drive to help them succeed.
  • Technology: Advanced proficiency with Google Workspace and email is required, along with Zoom; ability to learn new systems quickly and pivot as priorities shift; proficiency with learning management systems and educational technology tools is expected.

  Benefits

  • Competitive Compensation: Starting at $18.00 an hour.
  • Retirement Savings: 401(k) plan with up to a 4% company match.
  • Comprehensive Insurance Coverage: Medical, Dental, Vision, FSA, Company Paid Life Insurance, Supplemental Life Insurance, Disability Insurance, Hospital Indemnity, Critical Illness, and Accident insurance options.
  • Flexible Paid Time Off: Encouraging a healthy work-life balance through adaptable FTO.
  • Wellness Support: Employer-paid financial wellness programs and access to mental health resources.
  • Employee Referral Incentives: Rewarding you for helping us build a talented team.
  • Professional Development: Certification reimbursement programs to invest in your growth.
  • Bonus Opportunities: Celebrating milestones and achievements with performance-based bonuses.

  Pay

  Starting at $18.00 an hour.

  We have duplicated compensation in Benefits and Pay; maybe we should not duplicate. The instruction: preserve ALL substantive information; do NOT invent or summarize away detail. Duplication is okay if it's in source? The source mentions compensation in Benefits list as "Competitive Compensation: Starting at $18.00 an hour." It also appears elsewhere? Not elsewhere. So we have it only once in Benefits. If we also create Pay section repeating same info, that's duplication but still preserving info. Might be considered redundant but not invented. However they said prefer a few substantive sections over many thin ones. Having both Benefits and Pay may be thin. Better to keep compensation only in Benefits and not create a separate Pay section. But they said never create Pay/Schedule/Benefits sections unless posting actually states them. It does state compensation, so we could have Pay section. However we already have Benefits section that includes compensation. Having both may be redundant but still okay. However they said prefer a few substantive sections over many thin ones. Having Pay as a separate thin section (just one line) might be considered thin. Better to incorporate compensation into Benefits and not create Pay section. But then we would not have a Pay section, which is okay because we still have the info in Benefits. The rule: "never create Pay/Schedule/Benefits sections unless the posting actually states them." It doesn't say we must create them if stated; it's just we shouldn't create them if not stated. So we can choose not to create Pay section if we already have the info elsewhere. That seems fine. Thus we will not include a separate Pay section. We also need to ensure we didn't include Schedule. Now check for any leftover boilerplate: We removed Equal Opportunity Employer, Third-Party Agency notice, Responsibilities All roles..., etc. Check if any duplicated lines: We have not included the "About Acceleration Academies" intro paragraph? We included About the role but not the intro about Acceleration Academies. Should we include that as part of About the role? The intro about Acceleration Academies is about organization, not role. Could be included as a short paragraph under About the role or maybe a separate section like "About the organization". But they only gave examples of headings: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. They didn't list About the organization. So we should incorporate that info into About the role section perhaps as a brief preamble. The instruction: "use

  for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." It doesn't forbid other headings, but they gave examples. Safer to stick to those headings. So we can put the Acceleration Academies description inside the About the role section as a paragraph