Clinic Success Manager

We need to output HTML fragment with sections: 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. Must not include Job ID etc. Remove boilerplate like EEO, legal, etc. Must preserve all substantive info. We need to parse the posting. Let's extract sections: - About the role: The first paragraph: "Ensure Integrity. Enhance Satisfaction. Elicit Positivity. Bloomwell Autism Therapy is looking for a charismatic and driven leader to join our team as the Clinic Success Manager. The Clinic Success Manager ensures that everyone—the teammates, the patients and the parents—at a clinic is successful. They are responsible for all non-clinical aspects of the clinic and for creating an efficient, productive and fun environment for our teammates and patients. This role is the second-in-command at the clinic and is the Clinical Director’s right hand. They are a team that works together to make sure the clinic as a whole is successful." That's about the role. - How We Support Our Teammates: This is benefits/compensation: includes competitive compensation, PTO, training, career potential, benefits list, recognition, perks. So Benefits section. - How You Will Nurture Your Clinic: This is responsibilities/duties list: many bullet-like sentences. So Responsibilities. - What You Need To Have: requirements/qualifications: degree, experience, etc. So Requirements/Qualifications/Skills. - Who We Are: maybe About the company, but not required heading; could be omitted or could be part of About the role? The instruction says use headings for sections like About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We can include About the role (we have). Responsibilities (we have). Requirements (maybe combine qualifications and skills). Benefits (we have). Pay: we have mention of "Competitive compensation with growth opportunities!" but not specific numbers. The instruction says: never create Pay/Schedule/Benefits sections unless the posting actually states them. It does state "Competitive compensation with growth opportunities!" That's a statement about pay, albeit vague. Should we include Pay? It says "Competitive compensation with growth opportunities!" That's a statement about compensation. It's not a specific number but it's still stating something about pay. The rule: "never create Pay/Schedule/Benefits sections unless the posting actually states them." It does state compensation, albeit generic. So we could include a Pay section with that sentence. However also we have Benefits section already covering many benefits; Pay could be separate short sentence. Schedule: The posting includes "Ability to work 7:00am-3:00pm Monday - Friday and occasionally on the evenings or weekends for a community event". That's schedule info. So we can include Schedule section. Thus we will have sections: About the role, Responsibilities, Requirements (maybe combine qualifications and skills), Benefits, Pay, Schedule. We must not create sections with filler like "commensurate with experience". We have actual content. We need to use

for section headings. Use

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

  for prose. We need to preserve all substantive information; do not invent or summarize away detail. So we need to keep all details from each section. Let's extract details precisely. About the role paragraph: We'll keep as is. Responsibilities: list from "How You Will Nurture Your Clinic". Let's extract each bullet: - Scheduling new patient assessments and family tours - Handling new patient onboarding and scheduling - Monitoring patient and teammate attendance - Ensuring consistent and timely session note conversion - Leading the clinic's morale committee by supporting in the organization of off-site team building activities, happy hours, and other teammate engagement activities - Supporting the CD in budget oversight, teammate hiring, new-hire training, and teammate performance management initiatives - Planning community-focused events, caregiver/patient events and team building events each quarter - Managing the clinic’s schedule for ongoing schedules, callouts, and coverage needs - Ensuring proper maintenance of the facility, technology, and therapy materials to support seamless service delivery - Conducting regular team meetings to communicate goals, updates, and performance insights - Assisting in hiring, training, and onboarding new staff to ensure a strong team foundation - Providing coaching and mentorship to staff, promoting professional growth and development - Tracking clinic revenue, expenses, and financial performance in collaboration with leadership We need to keep each as

• . Requirements/Qualifications/Skills: from "What You Need To Have". Let's extract: - A 4-year degree from an accredited university required - At least 2+ years of experience working in a healthcare environment strongly preferred - Experience working in the ABA industry strongly preferred - Excellent attention to detail skills - Impeccable interpersonal skills as you will be interacting daily with families and teammates - At least 1 year experience managing or handling oversight of a large team of hourly employees - Ability to work 7:00am-3:00pm Monday - Friday and occasionally on the evenings or weekends for a community event Note: The last bullet about schedule also appears in schedule section; but we might duplicate. However we should not duplicate content? The instruction: preserve ALL substantive information; do not invent or summarize away detail. If the same info appears in two places, we might need to include it both places? Probably we should keep it where it appears; but we could also note schedule in Schedule section and not duplicate in Requirements. However the requirement list includes that ability; it's part of qualifications. The schedule section also includes same info. To avoid duplication, we could keep it only in Schedule section and not in Requirements. But the requirement list includes it; if we remove it, we lose that detail from requirements. However we could keep it in both places; duplication is allowed as preserving info. The instruction didn't forbid duplication. It said preserve ALL substantive information; do not invent or summarize away detail. Duplication preserves detail. So we can keep it in both. But we might want to avoid redundancy but it's okay. Benefits: from "How We Support Our Teammates". Let's extract: - Competitive compensation with growth opportunities! - Ample PTO- 4 weeks of PTO are accrued throughout the year! - Ongoing Training and Development – We provide ongoing personal and professional development through our Boost program - Unlimited Career Potential –We offer clear professional milestones to build your career - Unmatched Benefits – We offer all our teammates a 401(k) plan with match, free short-term disability insurance, free life Insurance, access to mental health support, and more. - Teammate Recognition through our partnership with Bonusly - Holistic Perks Program: We provide thoughtful perks that focus on the whole individual such as: ClassPass membership, university program tuition discount, childcare subsidy and more. We need to keep each as
• under Benefits. Pay: we have "Competitive compensation with growth opportunities!" Already in Benefits list; but we could also have a Pay section with that sentence. However that would duplicate. Perhaps better to put Pay section with that sentence, and Benefits section without that line (or keep it there but also in Pay). The instruction: "Prefer a few substantive sections over many thin ones." Having both Pay and Benefits may be thin if Pay only has one line. But we have schedule also maybe one line. However we could combine Pay into Benefits? But the instruction says use headings for Benefits, Pay, Schedule separately if they have content. Since we have compensation statement, we could make Pay section with that line. Benefits section then would exclude that line (maybe we keep other benefits). That seems reasonable. Thus Benefits section will exclude the compensation line. Pay section:

  Competitive compensation with growth opportunities!

  Schedule section: we have schedule info: Ability to work 7:00am-3:00pm Monday - Friday and occasionally on the evenings or weekends for a community event. Also maybe mention "occasionally on the evenings or weekends for a community event". We'll keep as

  . Now About the role: we have paragraph. Responsibilities: list. Requirements: we need to include degree, healthcare experience, ABA experience, attention to detail, interpersonal skills, managing oversight of large team. We'll put those as

• . We'll also include maybe "Ability to work 7:00am-3:00pm Monday - Friday and occasionally on the evenings or weekends for a community event" but we already have schedule; we can keep it there as well but maybe not needed. We'll keep it in Requirements as well to preserve info. But we can also note it's duplicated; it's okay. Qualifications/Skills: The instruction separate headings for Qualifications and Skills. We could split: Qualifications: degree, experience; Skills: attention to detail, interpersonal skills, managing oversight. But we can also combine into Requirements section. However the instruction says use headings for those sections if they have real content. We have content for both. So we could have Qualifications and Skills separate. Let's decide: We'll have sections: About the role, Responsibilities, Qualifications, Skills, Benefits, Pay, Schedule. We'll not have a generic Requirements heading. Thus: - Qualifications: degree, healthcare experience, ABA experience, managing oversight of large team (maybe also years). Actually managing oversight is more skill/experience. We'll put: "At least 1 year experience managing or handling oversight of a large team of hourly employees" under Qualifications or Skills? It's experience. We'll put under Qualifications. - Skills: Excellent attention to detail skills, Impeccable interpersonal skills as you will be interacting daily with families and teammates. We also have "Ability to work 7:00am-3:00pm Monday - Friday and occasionally on the evenings or weekends for a community event" which is schedule; we already have schedule section. Now we need to ensure we don't include boilerplate like "We Value Diversity, Equity, Inclusion and Belonging." That's in "We Value Diversity..." paragraph; that's not a heading we need; we can omit as it's not under specified headings. It's not required to keep? The instruction: Preserve ALL substantive information; do NOT invent or summarize away detail. Remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. The diversity statement is not boilerplate; it's part of "We Value Diversity, Equity, Inclusion and Belonging." It's substantive about company values. Should we keep it? It's not under any of the headings we are using; but we could include it under About the role? Not really. The instruction says we should output only HTML fragment with those headings; we can include other content as paragraphs not under headings? 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. It didn't say we cannot have other sections; but we should prefer few substantive sections. The diversity statement could be placed under About the role as extra paragraph. However About the role already has a paragraph; we could add another paragraph after it about the company values. That would preserve info. Similarly "Who We Are" paragraph about Bloomwell ABA mission etc. That's also substantive. Could be added under About the role as extra paragraph. Thus we can have About the role section containing multiple paragraphs: the initial description, plus "Who We Are" description, plus "We Live By" values, plus "We Value Diversity..." paragraph. That would preserve all. But we must not include boilerplate like Privacy Policy, Terms & Conditions, etc. Those we must remove. Thus we will extract all substantive paragraphs except those that are legal/boilerplate. Let's list substantive paragraphs from the posting: 1. "Ensure Integrity. Enhance