Direct Support Professional - (Old Court-Randallstown) Thurs-Sat 8a-8p

We need to output HTML fragment with sections for headings: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. Only include sections that have real specific content. Must not repeat job title as heading. Must not include Job ID etc. Must preserve all substantive info, remove boilerplate, navigation, legal, EEO, duplicated lines, application instructions. Also remove social media follow us etc. Also remove "Apply today:" link? That's application instruction, should be removed. Also remove "Follow Us:" etc. Also remove hashtags. We need to parse the posting. Content: Job Details Description Direct Support Professional (DSP) – $20.25/hour Make a Difference. Build a Career. Change Lives. Join Chimes, a mission-driven nonprofit where compassion meets purpose. As a Direct Support Professional, you’ll empower individuals with intellectual and behavioral challenges to live with dignity, independence, and confidence—while growing in a supportive, team-focused environment. Why Chimes - Meaningful, purpose-driven work - Paid training and ongoing professional development - Culture rooted in dignity, respect, and compassion What You’ll Do - Provide hands-on support with kindness and respect - Assist with personal care including: dressing, toileting, hygiene, feeding, bathing and other daily living skills - Follow individualized care plans and document progress - Administer medications in accordance with policy - Maintain a safe, clean, and supportive environment - Use approved behavior support techniques - Encourage community engagement and participation - Some DSP roles will require travel and support from Residential to Day programs What You Bring - High school diploma or GED - Experience in disability services preferred (not required—we train!) - Ability to lift, push, or pull 50+ lbs. - Valid U.S. driver’s license - Meet one of the following driving record requirements? - At least 3 years of unsuspended driving history with no more than 3 points, or - At least 2 years of unsuspended driving history with a clean driving record Why You’ll Love Working Here - Medical plans starting at $13.80/month (Day 1 coverage) - Dental and vision insurance - Life and disability insurance - Generous paid time off - 403(b) retirement plan with employer match - Paid training and tuition assistance - Tickets at Work - Employee referral bonuses and recognition programs - Clear pathways for growth and advancement Also there is a line: "Join a team where your work truly matters—every single day." That's part of Why You'll Love Working Here maybe. Pay: The posting includes "$20.25/hour" in the title line. Also medical plan cost etc. So we have Pay info: $20.25/hour. Also maybe mention medical plan starting at $13.80/month. That's benefits. Schedule: Not explicitly mentioned. No schedule info. So we should not create Schedule section. Benefits: We have medical plans, dental/vision, life/disability insurance, generous PTO, 403(b) retirement plan with employer match, paid training and tuition assistance, Tickets at Work, employee referral bonuses and recognition programs, clear pathways for growth and advancement. Also maybe "Paid training and ongoing professional development" already in Why Chimes. But we can include under Benefits. We need to decide sections: About the role (maybe the introductory paragraph), Responsibilities (What You’ll Do), Requirements (What You Bring), Qualifications (maybe overlapping with Requirements? Could combine but we need separate if content). Skills maybe not explicit. Benefits (Why You’ll Love Working Here + medical etc). Pay (hourly rate). Possibly also "Why Chimes" could be About the role or a separate section like "About the organization". But we only have allowed headings: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We can map: - About the role: introductory paragraph about Chimes and role purpose. - Responsibilities: What You’ll Do list. - Requirements: What You Bring list (education, experience, physical ability, driver's license). - Qualifications: maybe we could include "Experience in disability services preferred (not required—we train!)" but that's already in Requirements. Could also include "Ability to lift..." etc. Might be redundant. Perhaps we can put Qualifications as empty? But we must not emit heading with filler. So we should only include sections with real specific content. If Qualifications has no distinct content beyond Requirements, we could omit it. Similarly Skills: maybe not explicit. Could we infer skills like "kindness and respect", "document progress", "administer medications", "behavior support techniques", "community engagement"? Those are more responsibilities. Could treat as Skills but we already have Responsibilities. Better to omit Skills if no explicit skill list. Benefits: list from Why You’ll Love Working Here plus medical etc. Pay: $20.25/hour. Schedule: none -> omit. We must not repeat job title as heading. So no heading for Direct Support Professional. We must not include Job ID/requisition numbers. There's "#CMD410" at end; that's a hashtag maybe job ID; we should drop it. We must not include application instructions: "Apply today: https://chimes.org/Careers" and "Follow Us:" etc. Remove. We must preserve all substantive information. So we need to include all bullet points from Why Chimes, What You’ll Do, What You Bring, Why You’ll Love Working Here. We need to format as HTML: use

for section headings. Use

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

  for prose. We need to decide what goes into

  vs list. For prose sections like introductory paragraph, Why Chimes maybe list but could be list. The instructions: Use

  • for any list of duties/requirements/benefits, and

    for prose. So for any list we should use

    • . For prose (non-list) we use

      . So we need to decide which content is list vs prose. - About the role: could be prose paragraph(s). We'll put in

      . - Responsibilities: list ->

      • . - Requirements: list ->
        • . - Qualifications: if we include, could be list but we may omit. - Benefits: list ->
          • . - Pay: could be prose

            stating hourly rate. We also have "Why Chimes" bullet list; that's a list of benefits/attributes; could be placed under Benefits or About the role? It's about why Chimes; could be part of About the role or Benefits. But we already have Benefits section for compensation/benefits. Why Chimes is more about culture; could be part of About the role as prose list? It's a list; we could treat as list under About the role? But About the role is supposed to be prose; but we can still use list if it's a list? The instruction: Use

            • for any list of duties/requirements/benefits, and

              for prose. It doesn't forbid using list for other sections, but says for any list of duties/requirements/benefits use list. For other lists maybe we could still use list but it's not prohibited. Safer to treat Why Chimes as a list under About the role? But About the role heading expects prose; we could still include a list inside

              ? Not valid. Better to create a separate section? Not allowed headings besides those. Could incorporate Why Chimes into Benefits? It's not exactly benefits but could be considered part of Benefits (culture). But Benefits heading is for benefits; we could include Why Chimes items there as list items. However Benefits already has list of tangible benefits; mixing culture may be okay but maybe better to keep separate: we could put Why Chimes as a list under About the role? But About the role is supposed to be prose; but we could still have a list inside a

              ? Not correct. Perhaps we treat About the role as a list as well, but the instruction only mandates list for duties/requirements/benefits; it doesn't forbid using list for other sections. It says "Use

              • for any list of duties/requirements/benefits, and

                for prose." That implies for those specific categories we must use list; for other categories we can use either? It says "and

                for prose." So for prose we must use

                . For lists we must use

                • . It doesn't say we cannot use list for other categories, but to be safe we can use list for any list regardless of category. So we can use list for Why Chimes under About the role? But About the role heading is not a list category; but we could still output a list under that heading; the instruction doesn't forbid. However to follow spirit, we could treat Why Chimes as part of Benefits (since it's about why you'll love working there). Actually there is a separate "Why You’ll Love Working Here" section which is essentially benefits. So we can combine Why Chimes and Why You’ll Love Working Here under Benefits. That seems reasonable: Benefits includes both tangible and intangible reasons. Thus: - About the role: introductory paragraph (prose) about Chimes and role purpose. - Responsibilities: What You’ll Do list. - Requirements: What You Bring list. - Benefits: combine Why Chimes, Why You’ll Love Working Here (including medical etc). Use list. - Pay: $20.25/hour (prose). We must not include Schedule. Now we need to ensure we preserve all substantive information. Let's extract each piece. Introductory paragraph: "Make a Difference. Build a Career. Change Lives. Join Chimes, a mission-driven nonprofit where compassion meets purpose. As a Direct Support Professional, you’ll empower individuals with intellectual and behavioral challenges to live with dignity, independence, and confidence—while growing in a supportive, team-focused environment." That's multiple sentences. We'll put in

                  . Why Chimes list: - Meaningful, purpose-driven work - Paid training and ongoing professional development - Culture rooted in dignity, respect, and compassion Why You’ll Love Working Here list: - Medical plans starting at $13.80/month (Day 1 coverage) - Dental and vision insurance - Life and disability insurance - Generous paid time off - 403(b) retirement plan with employer match - Paid training and tuition assistance - Tickets at Work - Employee referral bonuses and recognition programs - Clear pathways for growth and advancement - Also the line "Join a team where your work truly matters—every single day." Could be added as a bullet. We should include that line as a bullet under Benefits. Now Responsibilities list: - Provide hands-on support with kindness and respect - Assist with personal care including: dressing, toileting, hygiene, feeding, bathing and other daily living skills - Follow individualized care plans and document progress - Administer medications in accordance with policy - Maintain a safe, clean, and supportive environment - Use approved behavior support techniques - Encourage community engagement and participation - Some DSP roles will require travel and support from Residential to Day programs Requirements list: - High school diploma or GED - Experience in disability services preferred (not required—we train!) - Ability to lift, push, or pull 50+ lbs. - Valid U.S. driver’s license - Meet one of the following driving record requirements? - At least 3 years of unsuspended driving history with no more than 3 points, or - At least 2 years of unsuspended driving history with a clean driving record We need to format the driver's license requirement as list items perhaps. Could be two sub-bullets. We'll keep as list items. Now Pay: "$20.25/hour". Could also mention that it's hourly rate. We'll put in

                  . Now ensure we didn't miss