Care Team Manager - Community Health
or drop it. Probably we can include a short paragraph summarizing location, work model, schedule, travel, vehicle required, reports to, positions supervised. But we must not create headings for those unless they are actual sections. The instruction: "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." So we can include a short
after the opening maybe. We need sections: About the role (maybe the introductory paragraph). Responsibilities (list of duties). Requirements (maybe "What You Bring — The Must-Haves" and "Valued Experience"? Actually "Qualifications & Position Requirements" is separate. We need to decide mapping. We have sections: About the role (intro). Responsibilities (Lead Your Team, Drive Market Performance, Leverage Technology, Stay Connected to Members). Requirements (maybe "What You Bring — The Must-Haves" and "Valued Experience"? Could be under Requirements). Qualifications (maybe "Qualifications & Position Requirements"). Skills (maybe not explicit; could be derived from "What Success Looks Like"? Might be better to put under Skills? But we need to only include sections when posting has real specific content. There's a "What Success Looks Like" which could be considered Responsibilities or maybe Skills? But we can treat as part of Responsibilities. We have Benefits listed. Pay range given. Schedule: "Work Schedule: Monday–Friday with occasional evenings and/or weekends". That's schedule info, we can include a Schedule section. We must not create sections with filler like "commensurate with experience". Not present. Thus sections: - About the role: intro paragraph(s) describing role and mission. - Responsibilities: bullet list of duties (Lead Your Team, Drive Market Performance, Leverage Technology, Stay Connected to Members). Could break into sub-bullets. - Requirements: "What You Bring — The Must-Haves" and maybe "Valued Experience". Could combine. - Qualifications: "Qualifications & Position Requirements" (age, availability, driver's license, background check, HIPAA, tech use, lift). Also maybe "Bachelor's degree..." is under Valued Experience but could be Qualifications. We'll decide. - Skills: maybe not needed; we could omit if no explicit skills list. But we have "Strong communication and relationship-building skills", "Experience using performance metrics and data", etc. Those are more requirements. Could put under Requirements. - Benefits: list. - Pay: include pay range. - Schedule: include schedule. We must not repeat job title. We need to output only HTML fragment, no /. 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.
Let's extract content.
Intro paragraph: "At Reema Health, we believe a personalized, community-based approach to care makes it easier for anyone to get what they need to improve their lives. We believe a relationship with a real person, someone who listens, meets members where they are, and understands the community's resources can ease those burdens. As a Care Team Manager, you’ll lead a team of Community Guides while overseeing Reema’s care delivery in your market. Each community guide manages a caseload of approximately 80-120 members, helping individuals overcome barriers to care and improve their health. Your role is to ensure your team has the coaching, tools, accountability and support they need to consistently deliver exceptional member experiences and outcomes. You’ll balance people leadership and operational ownership - developing your team, using data to drive performance, using technology to improve team efficiency and member outcomes, and building strong community partnerships. As a growing startup, our teams evolve quickly, so we’re looking for a leader who embraces change, inspires others to do the same, and builds a high-performing team that consistently delivers exceptional member outcomes. This role requires the ability to quickly learn and apply new information across multiple systems and workflows. While you'll receive comprehensive onboarding and support, success in this role comes from being comfortable navigating a fast learning curve and continuously building proficiency over time."
That's the About the role.
Now "What Success Looks Like" could be part of Responsibilities or maybe a separate section but we can incorporate into Responsibilities as bullet points.
But we have explicit sections: "Lead Your Team", "Drive Market Performance", "Leverage Technology", "Stay Connected to Members". Those are responsibilities.
Thus Responsibilities: list each heading with sub-bullets.
Let's extract each:
Lead Your Team:
- Hire, onboard, coach, and develop Community Guides
- Hold regular 1:1 meetings that provide coaching, feedback, recognition, and career development
- Foster an engaged, collaborative, and accountable team culture in a primarily remote environment
- Lead team meetings, case reviews, and ongoing learning opportunities
- Support Guides through complex member situations while reinforcing trauma-informed, member-centered care
- Monitor workloads and help Guides effectively manage their caseloads
- Partner with cross-functional teams to remove barriers and improve team effectiveness
Drive Market Performance:
- Lead the day-to-day operations of Reema's care delivery within your assigned market
- Monitor performance metrics, quality measures, documentation, and member outcomes
- Translate data into coaching, action plans, and operational improvements
- Hold the team accountable for key performance goals while helping each Guide understand how their work contributes to overall success
- Ensure compliance with HIPAA, documentation standards, and organizational policies
- Build and maintain relationships with healthcare providers, community organizations, and local partners
- Champion organizational change and help your team adapt to evolving priorities and new initiatives
Leverage Technology:
- Champion adoption of Reema's technology platform and operational tools
- Coach team members on documentation, workflows, and technology best practices
- Troubleshoot operational challenges and identify opportunities for process improvement
- Help create a culture where technology enables better member care and greater efficiency
Stay Connected to Members:
- While this is primarily a leadership role, you'll occasionally maintain a small member caseload to:
- Support operational needs
- Provide coverage when needed
- Stay connected to the member experience
- Better coach your team through real-world situations
Also note: "This Job responsibilities may grow and change as business needs evolve." Could be a note; we can include as a sentence in Responsibilities maybe.
Now Requirements: "What You Bring — The Must-Haves":
- 3+ years of leadership experience in healthcare, community-based services, care management, social work, behavioral health, or a related field
- Experience coaching and developing employees
- Strong communication and relationship-building skills
- Experience using performance metrics and data to improve team outcomes
- Comfortable learning and adopting new technology and helping others do the same
- Strong organizational, problem-solving, and prioritization skills
- Ability to thrive in a fast-paced, evolving startup environment
- Experience leading remote or field-based teams
"Valued Experience":
- Bachelor's degree in Social Work, Human Services, Psychology, Health Sciences, or a related field (or equivalent experience)
- Experience with care coordination, case management, population health, or social determinants of health
- Experience working with Medicaid, managed care organizations, or community-based healthcare programs
"This Role May Be a Great Fit If You ..." and "This Role Might NOT Be for You If…" are more cultural fit; could be included under Requirements or maybe separate but we can incorporate as bullet points under Requirements or maybe under a separate "Fit" but not required. We'll include them under Requirements as additional bullet points.
Now Qualifications & Position Requirements:
- 18 years of age or older
- Available to work Monday–Friday during core business hours.
- [If field-based:] Valid driver's license, insurance, and reliable transportation
- Offers contingent upon passing a pre-employment drug screening and background check
- Comply with federal, state, and local regulations regarding patient confidentiality and HIPAA
- Use technology-based tools and systems daily
- Lift and carry up to 25 lbs occasionally
We need to fold minor metadata like location, FLSA status etc into a short paragraph. We'll include a short
after the intro maybe: "Location: Texas. FLSA Status: Exempt. Job Status: Full Time. Work Model: Remote/Field Based. Work Schedule: Monday–Friday with occasional evenings and/or weekends. Vehicle Required: Yes - with valid insurance. Amount of Travel Required: Occasional travel throughout market. Positions Supervised: Community Guides. Reports To: Assistant Director of Care Team Operations."
But we also have Schedule section later; we might not need to repeat schedule in metadata. However schedule is also a section; we can include schedule details there. The metadata includes schedule; we could drop it from metadata and rely on Schedule section. But we need to include location etc. We'll include a short paragraph with location, FLSA, job status, work model, vehicle required, travel, positions supervised, reports to. We'll omit schedule from there because we have schedule section.
Now Benefits:
- Competitive Salary Package
- Medical, Dental, and Vision Insurance
- HSA and FSA Options
- 401(k) Retirement Savings with Company Match
- Employee Assistance Program
- Technology Stipend
- Mileage Reimbursement
- Accrued Paid Time Off
- Paid Family and Medical Leave
Pay: "The Pay Range For This Role Is 73,000 - 82,000 USD per year(Austin, TX)". We'll output as a paragraph.
Schedule: "Work Schedule: Monday–Friday with occasional evenings and/or weekends". We'll output as a paragraph.
Now we must not include boilerplate like EEO statement, etc. Remove that.
Now construct HTML.
We'll start with a short paragraph for metadata (location etc). Then
About the role
intro paragraph(s). Might need to split into multiple paragraphs? We can keep as one
but it's long; still okay.
Then
Responsibilities
with - for each major responsibility heading? The instruction: Use
- for any list of duties/requirements/benefits. So we need to list duties as list items. Could have nested lists? Probably we can just have top-level list items for each responsibility heading, and within each we can have sub-list using
- inside? That's still a list. We'll do nested lists.
Thus:
Responsibilities
- Lead Your Team
- Hire, onboard, coach, and develop Community Guides
- Hold regular 1:1 meetings that provide coaching, feedback, recognition, and career development
- Foster an engaged, collaborative, and accountable team culture in a primarily remote environment
- Lead team meetings, case reviews, and ongoing learning opportunities
- Support Guides through complex member situations while reinforcing trauma-informed, member-centered care
- Monitor workloads and help Guides effectively manage their caseloads
- Partner with cross-functional teams to remove barriers and improve team effectiveness
for prose. We need to preserve all substantive information; do not invent or summarize away detail. Let's extract content. Intro paragraph: "At Reema Health, we believe a personalized, community-based approach to care makes it easier for anyone to get what they need to improve their lives. We believe a relationship with a real person, someone who listens, meets members where they are, and understands the community's resources can ease those burdens. As a Care Team Manager, you’ll lead a team of Community Guides while overseeing Reema’s care delivery in your market. Each community guide manages a caseload of approximately 80-120 members, helping individuals overcome barriers to care and improve their health. Your role is to ensure your team has the coaching, tools, accountability and support they need to consistently deliver exceptional member experiences and outcomes. You’ll balance people leadership and operational ownership - developing your team, using data to drive performance, using technology to improve team efficiency and member outcomes, and building strong community partnerships. As a growing startup, our teams evolve quickly, so we’re looking for a leader who embraces change, inspires others to do the same, and builds a high-performing team that consistently delivers exceptional member outcomes. This role requires the ability to quickly learn and apply new information across multiple systems and workflows. While you'll receive comprehensive onboarding and support, success in this role comes from being comfortable navigating a fast learning curve and continuously building proficiency over time." That's the About the role. Now "What Success Looks Like" could be part of Responsibilities or maybe a separate section but we can incorporate into Responsibilities as bullet points. But we have explicit sections: "Lead Your Team", "Drive Market Performance", "Leverage Technology", "Stay Connected to Members". Those are responsibilities. Thus Responsibilities: list each heading with sub-bullets. Let's extract each: Lead Your Team: - Hire, onboard, coach, and develop Community Guides - Hold regular 1:1 meetings that provide coaching, feedback, recognition, and career development - Foster an engaged, collaborative, and accountable team culture in a primarily remote environment - Lead team meetings, case reviews, and ongoing learning opportunities - Support Guides through complex member situations while reinforcing trauma-informed, member-centered care - Monitor workloads and help Guides effectively manage their caseloads - Partner with cross-functional teams to remove barriers and improve team effectiveness Drive Market Performance: - Lead the day-to-day operations of Reema's care delivery within your assigned market - Monitor performance metrics, quality measures, documentation, and member outcomes - Translate data into coaching, action plans, and operational improvements - Hold the team accountable for key performance goals while helping each Guide understand how their work contributes to overall success - Ensure compliance with HIPAA, documentation standards, and organizational policies - Build and maintain relationships with healthcare providers, community organizations, and local partners - Champion organizational change and help your team adapt to evolving priorities and new initiatives Leverage Technology: - Champion adoption of Reema's technology platform and operational tools - Coach team members on documentation, workflows, and technology best practices - Troubleshoot operational challenges and identify opportunities for process improvement - Help create a culture where technology enables better member care and greater efficiency Stay Connected to Members: - While this is primarily a leadership role, you'll occasionally maintain a small member caseload to: - Support operational needs - Provide coverage when needed - Stay connected to the member experience - Better coach your team through real-world situations Also note: "This Job responsibilities may grow and change as business needs evolve." Could be a note; we can include as a sentence in Responsibilities maybe. Now Requirements: "What You Bring — The Must-Haves": - 3+ years of leadership experience in healthcare, community-based services, care management, social work, behavioral health, or a related field - Experience coaching and developing employees - Strong communication and relationship-building skills - Experience using performance metrics and data to improve team outcomes - Comfortable learning and adopting new technology and helping others do the same - Strong organizational, problem-solving, and prioritization skills - Ability to thrive in a fast-paced, evolving startup environment - Experience leading remote or field-based teams "Valued Experience": - Bachelor's degree in Social Work, Human Services, Psychology, Health Sciences, or a related field (or equivalent experience) - Experience with care coordination, case management, population health, or social determinants of health - Experience working with Medicaid, managed care organizations, or community-based healthcare programs "This Role May Be a Great Fit If You ..." and "This Role Might NOT Be for You If…" are more cultural fit; could be included under Requirements or maybe separate but we can incorporate as bullet points under Requirements or maybe under a separate "Fit" but not required. We'll include them under Requirements as additional bullet points. Now Qualifications & Position Requirements: - 18 years of age or older - Available to work Monday–Friday during core business hours. - [If field-based:] Valid driver's license, insurance, and reliable transportation - Offers contingent upon passing a pre-employment drug screening and background check - Comply with federal, state, and local regulations regarding patient confidentiality and HIPAA - Use technology-based tools and systems daily - Lift and carry up to 25 lbs occasionally We need to fold minor metadata like location, FLSA status etc into a short paragraph. We'll include a short
after the intro maybe: "Location: Texas. FLSA Status: Exempt. Job Status: Full Time. Work Model: Remote/Field Based. Work Schedule: Monday–Friday with occasional evenings and/or weekends. Vehicle Required: Yes - with valid insurance. Amount of Travel Required: Occasional travel throughout market. Positions Supervised: Community Guides. Reports To: Assistant Director of Care Team Operations." But we also have Schedule section later; we might not need to repeat schedule in metadata. However schedule is also a section; we can include schedule details there. The metadata includes schedule; we could drop it from metadata and rely on Schedule section. But we need to include location etc. We'll include a short paragraph with location, FLSA, job status, work model, vehicle required, travel, positions supervised, reports to. We'll omit schedule from there because we have schedule section. Now Benefits: - Competitive Salary Package - Medical, Dental, and Vision Insurance - HSA and FSA Options - 401(k) Retirement Savings with Company Match - Employee Assistance Program - Technology Stipend - Mileage Reimbursement - Accrued Paid Time Off - Paid Family and Medical Leave Pay: "The Pay Range For This Role Is 73,000 - 82,000 USD per year(Austin, TX)". We'll output as a paragraph. Schedule: "Work Schedule: Monday–Friday with occasional evenings and/or weekends". We'll output as a paragraph. Now we must not include boilerplate like EEO statement, etc. Remove that. Now construct HTML. We'll start with a short paragraph for metadata (location etc). Then
About the role
intro paragraph(s). Might need to split into multiple paragraphs? We can keep as one
but it's long; still okay. Then
Responsibilities
- with
- for each major responsibility heading? The instruction: Use
- for any list of duties/requirements/benefits. So we need to list duties as list items. Could have nested lists? Probably we can just have top-level list items for each responsibility heading, and within each we can have sub-list using
- inside? That's still a list. We'll do nested lists.
Thus:
Responsibilities
- Lead Your Team
- Hire, onboard, coach, and develop Community Guides
- Hold regular 1:1 meetings that provide coaching, feedback, recognition, and career development
- Foster an engaged, collaborative, and accountable team culture in a primarily remote environment
- Lead team meetings, case reviews, and ongoing learning opportunities
- Support Guides through complex member situations while reinforcing trauma-informed, member-centered care
- Monitor workloads and help Guides effectively manage their caseloads
- Partner with cross-functional teams to remove barriers and improve team effectiveness
- Lead Your Team
- inside? That's still a list. We'll do nested lists.
Thus:
- for any list of duties/requirements/benefits. So we need to list duties as list items. Could have nested lists? Probably we can just have top-level list items for each responsibility heading, and within each we can have sub-list using