Intern - Behavioral Health
Rincon Family Services · Chicago, IL · 4 wk ago
On-siteHealthcareVolunteer
We need to output HTML fragment with headings for sections: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. Only include sections that have real specific content. Must not repeat job title. Must not include Job ID etc. Must preserve all substantive info. Remove boilerplate.
We need to parse the description.
Job Title: Intern – Behavioral Health (already shown elsewhere, we don't repeat). Job Type: Internship. Job Location: Chicagoland Area Rincon - Building Spaces, Restoring Communities- Who We Are ... This is about the organization. So we can have an "About the role" maybe? Actually "About the role" could be description of role. The posting includes "Position Description – What The Role Entails". That's about the role. Also "Company Culture - Do Our Values Speak to You?" That's about organization values. Could be part of "About the role" or separate? The instruction: use headings for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). So we should map content to these headings.
We need to decide which sections have content.
- About the role: Could include overview of internship, purpose, what they will do generally. The "Position Description – What The Role Entails" plus maybe company culture. We'll put that under About the role.
- Responsibilities: The list of duties under "Areas Of Accountability - What You Will Be Doing" with subcategories: Departmental & Behavioral Health Support, Projects & Special Assignments, Client, Community & Team Communication, Documentation, Administrative & Organizational Support, Behavioral Health Learning & Professional Development. Those are responsibilities.
- Requirements: The section "Requirements The Knowledge and Expertise that Matters Most - What you bring to the Role:" includes bullet points: currently enrolled, area of study may vary, strong written and verbal communication, ability to work collaboratively, ability to maintain confidentiality, previous experience is a plus, specific qualifications may vary. Also maybe "Position Qualifications – What Is Required To Perform The Role" includes strong analytical and problem-solving skills, excellent communication skills, solid technical knowledge and attention to detail, proficiency with various operating systems, excellent understanding of network protocols and hardware components, degree in computer science or related field (recommended), relevant certification in IT support or equivalent professional experience. Wait that seems mismatched: This is a behavioral health internship but qualifications list IT skills. Possibly a copy-paste error. But we must preserve all substantive info; we cannot invent or summarize away detail. So we need to include both sets as requirements/qualifications? The headings: Requirements and Qualifications are separate. We need to decide what goes where. Typically Requirements are what you need to have; Qualifications are maybe preferred or required. The posting has two sections: "Requirements The Knowledge and Expertise that Matters Most - What you bring to the Role:" and "Position Qualifications – What Is Required To Perform The Role". We'll treat first as Requirements, second as Qualifications.
- Skills: Could be derived from requirements/qualifications but we might not have a separate skills section. The instruction: use headings for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). If we don't have specific skills content, we should not create a Skills section. However we could extract skills like communication, collaboration, confidentiality, analytical, problem-solving, technical knowledge, OS proficiency, network protocols, hardware, etc. But those are already in requirements/qualifications. Might be better to not create a Skills section to avoid duplication. The instruction: Prefer a few substantive sections over many thin ones. So we can omit Skills if not distinct.
- Benefits: There's a section "Rincon Rewards & Benefits- How We Value You" with bullet points: Professional Development Opportunities, Mentorship and hands-on learning opportunities, Exposure to nonprofit and community-based programs and services, Opportunities to develop professional and transferable workplace skills. Also maybe "Rincon’s Work Environment – What To Expect". That's about work environment, not benefits. But we can include benefits as those bullet points.
- Pay: No mention of pay/salary. So we should not create Pay section.
- Schedule: There's a line: "Schedule Schedule may vary depending on department and internship placement." That's specific content: schedule may vary. So we can include a Schedule section with that sentence.
We must not include boilerplate like cookie/navigation/legal/EEO etc. Not present.
We must not repeat job title.
We must not put Job ID/requisition numbers.
We must preserve all substantive information.
We need to output only HTML fragment, no /, no markdown fences.
We'll structure:
for sections: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. Only include sections that have real specific content. Must not repeat job title. Must not include Job ID etc. Must preserve all substantive info. Remove boilerplate.
We need to parse the description.
Job Title: Intern – Behavioral Health (already shown elsewhere, we don't repeat). Job Type: Internship. Job Location: Chicagoland Area Rincon - Building Spaces, Restoring Communities- Who We Are ... This is about the organization. So we can have an "About the role" maybe? Actually "About the role" could be description of role. The posting includes "Position Description – What The Role Entails". That's about the role. Also "Company Culture - Do Our Values Speak to You?" That's about organization values. Could be part of "About the role" or separate? The instruction: use headings for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). So we should map content to these headings.
We need to decide which sections have content.
- About the role: Could include overview of internship, purpose, what they will do generally. The "Position Description – What The Role Entails" plus maybe company culture. We'll put that under About the role.
- Responsibilities: The list of duties under "Areas Of Accountability - What You Will Be Doing" with subcategories: Departmental & Behavioral Health Support, Projects & Special Assignments, Client, Community & Team Communication, Documentation, Administrative & Organizational Support, Behavioral Health Learning & Professional Development. Those are responsibilities.
- Requirements: The section "Requirements The Knowledge and Expertise that Matters Most - What you bring to the Role:" includes bullet points: currently enrolled, area of study may vary, strong written and verbal communication, ability to work collaboratively, ability to maintain confidentiality, previous experience is a plus, specific qualifications may vary. Also maybe "Position Qualifications – What Is Required To Perform The Role" includes strong analytical and problem-solving skills, excellent communication skills, solid technical knowledge and attention to detail, proficiency with various operating systems, excellent understanding of network protocols and hardware components, degree in computer science or related field (recommended), relevant certification in IT support or equivalent professional experience. Wait that seems mismatched: This is a behavioral health internship but qualifications list IT skills. Possibly a copy-paste error. But we must preserve all substantive info; we cannot invent or summarize away detail. So we need to include both sets as requirements/qualifications? The headings: Requirements and Qualifications are separate. We need to decide what goes where. Typically Requirements are what you need to have; Qualifications are maybe preferred or required. The posting has two sections: "Requirements The Knowledge and Expertise that Matters Most - What you bring to the Role:" and "Position Qualifications – What Is Required To Perform The Role". We'll treat first as Requirements, second as Qualifications.
- Skills: Could be derived from requirements/qualifications but we might not have a separate skills section. The instruction: use headings for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). If we don't have specific skills content, we should not create a Skills section. However we could extract skills like communication, collaboration, confidentiality, analytical, problem-solving, technical knowledge, OS proficiency, network protocols, hardware, etc. But those are already in requirements/qualifications. Might be better to not create a Skills section to avoid duplication. The instruction: Prefer a few substantive sections over many thin ones. So we can omit Skills if not distinct.
- Benefits: There's a section "Rincon Rewards & Benefits- How We Value You" with bullet points: Professional Development Opportunities, Mentorship and hands-on learning opportunities, Exposure to nonprofit and community-based programs and services, Opportunities to develop professional and transferable workplace skills. Also maybe "Rincon’s Work Environment – What To Expect". That's about work environment, not benefits. But we can include benefits as those bullet points.
- Pay: No mention of pay/salary. So we should not create Pay section.
- Schedule: There's a line: "Schedule Schedule may vary depending on department and internship placement." That's specific content: schedule may vary. So we can include a Schedule section with that sentence.
We must not include boilerplate like cookie/navigation/legal/EEO etc. Not present.
We must not repeat job title.
We must not put Job ID/requisition numbers.
We must preserve all substantive information.
We need to output only HTML fragment, no /, no markdown fences.
We'll structure:
About the role
... content ...
Responsibilities
- ... each duty ...
and then
or
- . For About the role: we need to combine the position description and company culture and work environment. Let's craft a paragraph(s) that preserve all info. Position Description – What The Role Entails: The Intern will support Rincon Family Services through hands-on learning and meaningful participation in organizational activities, projects, and day-to-day operations. Interns may be placed within various departments based on organizational needs, educational background, interests, and available opportunities. This position is designed to provide students and emerging professionals with practical experience in a nonprofit community-based organization while developing professional, communication, organizational, and problem-solving skills. Interns will work under the guidance and supervision of assigned staff and may assist with projects, research, administrative activities, community programs, client services, or other department-specific responsibilities. Internship assignments may be available across a variety of our locations. Company Culture - Do Our Values Speak to You?: At Rincon, Our Commitment To Mutual Respect, Inclusivity, And Diversity Is Woven Into The Structure Of All That We Do. We Value Dedication- Embodying effective and transparent leadership and quality client care. Education – Preventative programming and clinical services based on industry standards, competence and outreach. Accountability – Consistent service delivery, measurable success, and sensible financial management. Advocacy – Empowerment, reduction of treatment stigma, and relationship building with partners. Compassion – Embracing culturally diverse communities and equality through sensitivity to individual needs. With these values in mind, we promote a culture that fosters professional development and agency success. Many of our employees span an extended tenure, and we pride ourselves on developing dedicated and supported team members.