CLINICIAN-SALARY

CHOR Youth & Family Services · Reading, PA · 1 mo ago

On-siteHealthcareFull-time

We need to output HTML fragment with sections: About the role? Actually we have sections: About The Children’s Home of Reading, Why Join Our Team? (but we need to follow headings list: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We should only include sections that have real specific content. The posting includes: About The Children’s Home of Reading (organization description) – could map to "About the role"? Actually "About the role" is about the job, not organization. There's a "What You’ll Do" section (responsibilities). There's "Who We’re Looking For" (qualities). There's "Qualifications Required:" (qualifications). There's "Why Join Our Team?" includes benefits, career growth, meaningful work. There's "Schedule • Full-Time / Exempt • This position is based across two work locations...". There's also "Physical Requirements". There's "DailyPay Available" mention. There's "Competitive Pay & Benefits" bullet list. We need to map to allowed headings: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We should not repeat job title as heading. We should not include Job ID etc. We need to decide which sections to include based on content. - About the role: Could include a brief description of the role? The posting has "Build a Career with Purpose CLINICIAN Clinician – ORR Program Bethlehem and Doylestown, PA Full-Time DailyPay Available". Then a paragraph about looking for more than a job. That could be considered "About the role". We'll include that as prose. - Responsibilities: The "What You’ll Do As a Clinician, you will:" bullet list. Use

. - Requirements: Could be the "Who We’re Looking For" list of traits? Or maybe "Physical Requirements". But Requirements heading likely for mandatory requirements like age, degree, licensure, etc. The posting has "Qualifications Required:" with many bullet points. That could be under Qualifications heading. But we have both Requirements and Qualifications headings allowed. We need to decide which to use. The posting has "Qualifications Required:" which is clearly qualifications. So we can put that under Qualifications. Requirements could be things like "Must be at least 21 years of age", "Master’s or doctorate degree", etc. Actually those are also qualifications. But we can split: Requirements could be the mandatory prerequisites (age, degree, licensure, background check, immunity proof, training, code of conduct). Qualifications could be the desired traits (compassionate, dependable, etc). However the posting has "Who We’re Looking For" list of traits (compassionate, dependable, patient, team-oriented, service-focused, professional, positive, committed to helping others). That could be under Skills? Or maybe under Requirements? The heading list includes Skills. So we could put those traits under Skills. Then Requirements could be the mandatory qualifications (age, degree, licensure, etc). Qualifications could be the "Qualifications Required:" list? But that seems overlapping. Let's think: The posting has a section titled "Qualifications Required:" with bullet points. That is definitely qualifications. So we will use Qualifications heading for that. Then we need a Requirements heading: maybe we can put the "Must be at least 21 years of age..." etc as Requirements. But those are also in the Qualifications Required list. Actually the Qualifications Required list includes those items. So we could just use Qualifications for that and not have a separate Requirements. But we need to decide if we should include Requirements heading at all. The instruction: "Prefer a few substantive sections over many thin ones." So we can omit Requirements if its content would be thin or duplicate. We could combine Requirements into Qualifications. But we have both headings allowed; we can choose to include only Qualifications and skip Requirements if it would be thin. However we have also "Who We’re Looking For" traits which could be Skills. So we can have Skills heading for those traits. Benefits: The posting has "Why Join Our Team?💰 Competitive Pay & Benefits • Competitive Compensation • DailyPay – Access Your Earned Wages Before Payday • Medical, Dental & Vision Insurance • 401(k) Retirement Plan • Paid Time Off • Employee Assistance Program • Wellness Programs • Employee Referral Bonuses • Company-Paid Training". Also career growth and meaningful work sections. We can put Benefits heading with those bullet points (compensation, DailyPay, insurance, 401k, PTO, EAP, wellness, referral bonuses, company-paid training). Also maybe career growth could be under Benefits? But there is also a separate heading for Pay. Pay heading could include "Competitive Compensation" and maybe DailyPay? But DailyPay is a benefit. The instruction: "never create Pay/Schedule/Benefits sections unless the posting actually states them." The posting states competitive compensation, DailyPay, etc. So we can have Pay section for compensation details (maybe just "Competitive Compensation" and "DailyPay – Access Your Earned Wages Before Payday"). Benefits section for the rest (medical, dental, vision, 401k, PTO, EAP, wellness, referral bonuses, company-paid training). Schedule: The posting has "Schedule • Full-Time / Exempt • This position is based across two work locations, Bethlehem and Doylestown. The employee will be required to report to and work from both offices as necessary and assigned." So we can include Schedule heading with that. We also have Physical Requirements but not a heading allowed; we could maybe include under Requirements? But we don't have a heading for Physical Requirements. Could we put it under Requirements? Since we are not using Requirements heading, maybe we can omit Physical Requirements or incorporate into Schedule? Better to omit if not covered by allowed headings. However we must preserve ALL substantive information; we cannot drop Physical Requirements if it's substantive. But we can incorporate it into a section like "Requirements" if we decide to include that heading. Since we have a Requirements heading allowed, we could use it for Physical Requirements and maybe also for age, degree, etc? But we already used Qualifications for the qualifications list. We could use Requirements for the physical requirements and maybe also for the mandatory pre-service training etc? But those are also in Qualifications Required. Hmm. We need to preserve all substantive information. Let's list all substantive info blocks: - Intro paragraph about purpose, looking for more than a job. - About The Children’s Home of Reading (organization description). - Why Join Our Team? with sub-sections: Competitive Pay & Benefits, Career Growth & Development, Meaningful Work That Matters. - What You’ll Do As a Clinician, you will: (responsibilities bullet list). - Who We’re Looking For (traits list). - Qualifications Required: (bullet list of mandatory qualifications). - Schedule • Full-Time / Exempt • location info. - Physical Requirements bullet. - Apply Today motivational paragraph. - About Our Organization (similar to earlier? Actually repeats The Children’s Home of Reading is part of Inperium family...). - Equal Opportunity Employer boilerplate (to be removed). We need to remove boilerplate: EEO, equal-opportunity, scam-warning, duplicated lines, application instructions, cookie/navigation/legal. So we remove the Equal Opportunity Employer paragraph and maybe the "About Our Organization" if it's duplicate of earlier? The earlier "About The Children’s Home of Reading" is similar but not identical; the later "About Our Organization" mentions Inperium family and Apis Services. That's substantive? It provides info about employment administered through Apis Services, Inc. That could be considered metadata but not required heading. Could be placed in a short p under maybe "About the role"? But we already have About The Children’s Home of Reading. We could combine or keep both? 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 fold minor metadata into a short p. The "About Our Organization" could be considered minor metadata; we could include as a short p under maybe "About the role" or just drop? It's not duplicate exactly; it's about the organization being part of Inperium and employment administered via Apis Services. That's somewhat relevant but maybe minor. We could include as a short p after the About The Children’s Home of Reading paragraph. We need to preserve ALL substantive information; we should not drop important info like the organization description, the benefits, responsibilities, qualifications, schedule, physical requirements. The Equal Opportunity Employer boilerplate can be removed. Now decide headings: - About the role: Could include the intro paragraph about purpose and looking for more than a job, plus maybe the About The Children’s Home of Reading description? Actually "About the role" is about the job, not organization. But we have no other heading for organization description. Could we put organization description under About the role? It's not exactly role but could be considered context. The instruction: "Use
for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." So they gave examples; we can use those headings as we see fit. We could use About the role to include both the intro and organization description. Or we could create a separate heading like "About the organization" but not allowed. So we fold it into About the role. - Responsibilities: the "What You’ll Do" bullet list. - Requirements: Could be the "Physical Requirements" plus maybe the "Schedule"? But Schedule is separate heading. We'll use Requirements for Physical Requirements (and maybe also the mandatory pre-service training etc? but those are in Qualifications). We'll keep Requirements for Physical Requirements only. - Qualifications: the "Qualifications Required:" bullet list. - Skills: the "Who We’re Looking For" traits list. - Benefits: the benefits list from Competitive Pay & Benefits (excluding compensation maybe). We'll separate Pay and Benefits. - Pay: the compensation details: Competitive Compensation, DailyPay. - Schedule: the schedule bullet. We also have Career Growth & Development and Meaningful Work That Matters under Why Join Our Team. Those could be considered part of Benefits? Or maybe we could add a separate section but not allowed headings. We could fold them into Benefits as additional bullet points (career growth opportunities, meaningful work). That would preserve that info. Thus Benefits heading will include: Competitive Compensation? Actually we moved compensation to Pay. So Benefits will include: DailyPay – Access Your Earned Wages Before Payday, Medical, Dental & Vision Insurance, 401(k) Retirement Plan, Paid Time Off, Employee Assistance Program, Wellness Programs, Employee Referral Bonuses, Company-Paid Training, Career Growth & Development (Paid Training Programs, Professional Development Opportunities, Certification Opportunities, Leadership Development Programs, Career Advancement Opportunities, Opportunities Across Multiple Service Lines), Meaningful Work That Matters (Make a Difference Every Day, Support Individuals and Families, Build Meaningful Relationships, Strengthen Communities, Join a Mission-Driven Organization). We'll keep them as bullet points. Now we need to ensure we don't include filler like "commensurate with experience". Not present. Now produce HTML fragment: start with
About the role
then
... intro + organization description + maybe Apis Services note.
Then
Responsibilities
- ... each bullet. Then
  Requirements
  - ... physical requirements bullets. Then
    Qualifications
    - ... qualifications required bullets. Then
      Skills
      - ... who we’re looking for traits. Then
        Benefits
        
        ... benefits bullets. Then
        Pay
        
        ... compensation bullets. Then
        Schedule

CLINICIAN-SALARY

About the role

Responsibilities

Requirements

Qualifications

Skills

Benefits

Pay

Schedule

Similar jobs