Remote LPC Associate - Fee For Service

We need to output HTML fragment with sections: About the role, Responsibilities? The posting includes "About the Role" with bullet points. Also "Compensation" with pay info. "How We Support You" maybe not a required heading but could be considered "Benefits"? Actually there is a "Benefits" section later. Also "Our Community". We need to include sections only when posting has real specific content. Use

for section headings: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We need to map content. First, "About the job" paragraph: description of company. Could be placed under maybe "About the role"? Actually there is "About the job" then "About the Role". We should not repeat job title. We can include an

for the company overview maybe under a generic heading? But we only have allowed headings. Could we put it under "About the role"? The instruction: use

for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). So we can have those headings if content exists. We need to decide which sections to include. We have content: - About the role: includes description of role, bullet list of qualifications etc. So we can put that under

About the role

with

prose and maybe

for list. - Responsibilities: The posting does not explicitly list responsibilities separate from qualifications; but we could infer responsibilities: provide telehealth sessions, treat depression/anxiety, conduct intakes, diagnosing, etc. However we should not invent. The posting includes bullet points like "Graduate or Post-graduate work experience in a counseling setting treating depression and anxiety is required" etc. Those are more qualifications/experience. There's no explicit responsibilities list. Might be better to not create Responsibilities section if no explicit content. But we could treat the bullet list as responsibilities? The instruction: "Use
• for any list of duties/requirements/benefits". So we can put the bullet list under either Requirements or Responsibilities. The posting includes "About the Role" with bullet list of qualifications. Could treat as Requirements. So we can have a Requirements section. - Qualifications: maybe similar to Requirements. But we need to avoid duplication. We could have Requirements for the bullet list, and Qualifications for licensure etc? Actually the bullet list includes licensure, education, experience. That's qualifications. So maybe we put them under Requirements. Qualifications could be empty; better not to include. - Skills: maybe "Confident working with modern clinical technology, including telehealth and EHR tools" and "good teammate". Could be skills. We could create Skills section with those. - Benefits: there is a Benefits section with list. So include

  Benefits

  with
  . - Pay: there is "Compensation Up to $75,000 based on licensure type, session volume, and bonus opportunities." Also mention full-time clinicians eligible for health insurance etc (but that's benefits). So we can have Pay section with that sentence. - Schedule: there is "Consistently available to clients for a minimum of 25 sessions with 30 hours of availability weekly" and later "flexible scheduling available seven days a week from 7 a.m. to 10 p.m. ET." So we can include Schedule section. - Also there is "How We Support You" describing admin support, orientation, training, caseload within 90 days. Could be considered part of Benefits or maybe a separate section like "Support". Not in allowed headings; we could incorporate into Benefits or maybe under About the role? Probably better to add as a paragraph under About the role or maybe under Benefits? But Benefits already defined; we could add a separate section like "Support" but not allowed headings. The instruction says use those headings for section headings; we can still have other headings? It says use

  for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). It implies we should use those headings for sections; we could also have other headings but better to stick to those. We could incorporate "How We Support You" content into Benefits or About the role. - "Our Community" could be part of Benefits or maybe a separate section like "Community". Not in list; maybe we can incorporate into Benefits or About the role. We need to preserve all substantive information. So we need to ensure we don't lose any info. Let's extract all substantive info: Company overview: Thriveworks is a mental health care company founded by clinicians in 2008, still led by them. 340+ locations, nationwide hybrid care model, serve over 175,000 clients annually through >1.7 million sessions, growing. Partner with health systems and primary care providers. Clinician-led organization built to support clinicians with tools, community, stability. About the Role: hiring licensed clinicians to provide compassionate, evidence-based care to >175,000 clients across country. You may be a good fit if you’re: - Approved by the board as a LPC - Must be seeking independent licensure and living in Connecticut - Graduate of an approved 60-credit hour program - Graduate or Post-graduate work experience in a counseling setting treating depression and anxiety is required - Graduate or Post-graduate work experience independently conducting intakes and diagnosing (preferred) according to the current DSM-5 under a licensed supervisor. - Consistently available to clients for a minimum of 25 sessions with 30 hours of availability weekly - A behavioral health generalist who is open to treating a variety of clients, including couples and children - Invested in helping your clients achieve measurable progress - Confident working with modern clinical technology, including telehealth and EHR tools - A good teammate — we’re building a clinical community and value positive contributors Compensation: Up to $75,000 based on licensure type, session volume, and bonus opportunities. Full-time clinicians are eligible for health insurance, student loan repayment assistance, paid time off, and other employer-sponsored benefits. How We Support You: We handle administrative work (credentialing, billing, scheduling, marketing) so you can focus on care, plus paid orientation and training to get you started. You'll build a full caseload within 90 days of credentialing, with flexible scheduling available seven days a week from 7 a.m. to 10 p.m. ET. Benefits: As a W2 employee, you'll be eligible to receive: - Guaranteed bi-weekly pay for completed sessions - FREE group and individual clinical supervision provided - Medical, dental, and vision coverage - 401(k) with employer matching - Paid time off - Short- and long-term disability insurance - Company-paid life and AD&D insurance - CEU reimbursement and free in-house training - Student loan repayment assistance Our Community: Being a clinician can feel isolating, especially in a telehealth world. We're built to make sure it doesn't. You'll have access to live clinical support, monthly case consultations, and a vibrant online and in-person community of more than 2,700 licensed providers. All clinical leadership is promoted from within, so the people supporting you have been exactly where you are. Then scam warning, EEO, etc which we remove. We need to output HTML fragment with sections. We need to decide which headings to use. Potential sections: - About the role (h3) containing company overview and role description? Could split: maybe we put company overview in a paragraph before About the role heading? But we need to preserve all info. Could include a

  before any heading? The instruction: "Output ONLY the HTML fragment — no /, no markdown code fences." It doesn't forbid having stray

  before headings. But they said use

  for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). It doesn't say we cannot have other elements outside those headings. However they said "Prefer a few substantive sections over many thin ones." So we could have a leading

  for company overview, then

  About the role

  with the role specifics, then maybe

  Requirements

  for the bullet list (or we could embed bullet list under About the role). But we need to avoid duplication. Better: Use About the role section to include both company overview and role description? The company overview is about the job, not exactly about the role but could be considered part of About the role. However the posting has separate "About the job" and "About the Role". We could combine them under About the role heading. Then we need Requirements: maybe the bullet list of qualifications (education, licensure, experience). Could be under Requirements. Skills: maybe "Confident working with modern clinical technology..." and "good teammate". Could be under Skills. Pay: compensation sentence. Benefits: the benefits list. Schedule: availability and flexible scheduling. We also have "How We Support You" content: admin support, orientation, training, caseload within 90 days, flexible scheduling (already covered in Schedule). Could be placed under Benefits or About the role. Perhaps we can add a paragraph under About the role after the bullet list: "We handle the administrative work..." etc. Our Community: could be placed under Benefits or maybe a separate section like "Community" but not in allowed headings. Could incorporate into Benefits as another bullet? But it's not a benefit per se; it's community support. Could be placed under About the role as well. We need to ensure we don't miss any info: admin support, orientation/training, caseload within 90 days, flexible scheduling (already in Schedule), live clinical support, monthly case consultations, community of 2,700 providers, clinical leadership promoted from within. We could add a section "Support" but not allowed. Maybe we can add a paragraph under Benefits titled "Additional support" but that would be a heading not in list. Better to incorporate into Benefits as extra bullet points? But Benefits list already defined; we could add extra
  • items under Benefits for those support items, but they are not benefits exactly but could be considered support. However the instruction: "Use
    • for any list of duties/requirements/benefits". So we can use
      for benefits list; we can add those support items as
      • under Benefits if we want. But the Benefits heading already has a list; we can extend it. Alternatively, we could create a section "How We Support You" using

        but not in allowed list; risk of being considered not following instruction. Safer to stick to allowed headings. Thus we will place all remaining prose under About the role or Benefits. Let's design:

        About the role

        Thriveworks is a mental health care company founded by clinicians in 2008 and still led by them today. With 340+ locations and a nationwide hybrid care model, we serve over 175,000 clients annually through more than 1.7 million sessions, and we're growing. In addition to working directly with clients, we partner with health systems and primary care providers because we believe mental health is inseparable from physical health. As a clinician-led organization, we're built to support the people who do this work with the tools, community, and stability you need to build a career that lasts.

        We’re hiring licensed clinicians to provide compassionate, evidence-based care to our more than 175,000 clients across the country. You may be a good fit for this role if you’re:

        • Approved by the board as a LPC
        • Must be seeking independent licensure and living in Connecticut
        • Graduate of an approved 60-credit hour program