Direct Support Professional 2 (DSP 2)
Bridgewell · Lynnfield, MA · 3 wk ago
OTHRInternship
We need to output HTML fragment with sections: headings for sections like About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. Only include sections if posting has real specific content. We must not repeat job title. Must not include Job ID etc. Remove boilerplate. Preserve all substantive info.
We need to parse the posting.
Content:
- Intro paragraph about Bridgewell mission etc. Could be "About the role" or maybe "About Bridgewell". The instruction: use headings for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). So we can create sections: About the role (maybe summary), Responsibilities (Essential Duties And Responsibilities), Requirements (Required Education/Experience), Skills (Required Skills/Knowledge), Benefits (Bridgewell Offers...), Pay (The pay range listed...), Schedule (Schedule: Monday - Friday...). Also maybe Qualifications? Could combine Requirements and Qualifications but we have both. The posting has "Required Education/Experience" and "Required Skills/Knowledge". Also "Physical Demands". Could be part of Requirements or Qualifications. We'll decide.
We need to avoid filler sections like "Pay" if not specific. The posting includes: "The pay range listed for this position is the hourly rate range the organization reasonably and in good faith expects to pay for this position at this time. Actual compensation is determined based on several factors..." No actual numbers given. That's vague, not a specific range. According to instruction: never emit a heading followed by filler/placeholder text (e.g. "commensurate with experience", "not specified", "N/A", "varies", "TBD"). So we should NOT include Pay section because it's not specific. So omit Pay.
Schedule: they gave specific schedule: Monday - Friday 6:00 AM - 9:00 AM, Thursday 5:00 PM - 8:00 PM (18 hours). That's specific. So include Schedule.
Benefits: they list health benefits, paid time off, collaborative environment, training opportunities, additional compensation for on-call rotations, professional development. That's specific enough. So include Benefits.
About the role: we have mission and summary. Could be "About the role" or "Summary". We'll use About the role.
Responsibilities: Essential Duties And Responsibilities.
Requirements: Required Education/Experience.
Skills: Required Skills/Knowledge.
Qualifications: maybe combine with Requirements? But we have both Education/Experience and Skills/Knowledge separate. Could treat Skills as Qualifications? But instruction list includes Qualifications as a possible heading. We could have Qualifications (maybe combine Education/Experience and Skills). However we already have Skills heading. To avoid duplication, we could have Requirements (Education/Experience) and Qualifications (Skills/Knowledge). But they said use headings for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). So we can have both Requirements and Qualifications and Skills. But we need to avoid thin sections. Let's see content:
- Required Education/Experience: specific.
- Required Skills/Knowledge: specific.
- Physical Demands: also specific but could be part of Requirements or Qualifications. Could be its own section but not in list; we could incorporate into Requirements or Qualifications.
We could make: