Residential Coordinator - Group Home
for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). So we need to decide which sections to include based on content.
We have:
- Salary: Starting at $17.00/Hour => Pay section.
- Schedule: Monday – Friday, 8:00AM-4:00PM with flexibility. (Friday shifts are required as well as 1 shift in the homes each week.) => Schedule section.
- Benefits: list: Medical, Dental & Vision Insurance; Short-Term & Long-Term Disability; Competitive Wages & Paid Training; Career Growth Opportunities; Paid Weekly PTO with Vesting; Paid Holidays; 403(b) Retirement Plan with Match; Tuition Assistance Program.
- Responsibilities: many bullet-like sentences: assisting to onboard new hires, ensuring compliance, scheduling staff for medical appointments, provide direct support as needed, assist in implementing PCISPs, respond to crises, ensure accurate documentation, collaborate with other departments, representing agency at surveys, maintaining adherence, providing direct support and programming, maintaining info/data/documentation, working with Quality Compliance Administrator, ensuring timely completion of reports, promoting safety/housekeeping, preventive maintenance, training newly hired staff on CBTs, providing for health safety wellbeing, protecting rights, HIPAA, administrative support, coordinating schedules, ensuring compliance, assisting with documentation and reporting.
We can group responsibilities into a - .
- Requirements: Education and Experience: high school diploma or GED; valid driver's license, adequate automobile insurance, meet agency insurability requirements. Knowledge: learn basic principles of teaching (instruction provided), good basic mathematical computation and English Language writing knowledge. Physical Requirements: ability to walk, bend, stoop, stand extended periods; assist in lifting/transferring individuals; wear required PPE. Safety and Compliance: follow safe and universal precaution practices; know first aid, health & safety measures or build competence by post-hire training.
We could also include Qualifications and Skills sections: The "Ideal Experience, Background & Skills" includes experience providing support, experience with accredited agency, organizational, communication, leadership skills, ability to assess crisis, general knowledge of word processing/spreadsheet, ability to manage time, adaptive/flexible, certification in CPR, First Aid, behavioral interventions, medication administration (or ability to obtain). That could go under Skills or Qualifications. The instruction says we can have Qualifications and Skills sections. We need to decide which to include based on content. We have both experience and skills. Could combine into Skills section. Or we could have Qualifications (certifications) and Skills (others). But we should avoid thin sections. Perhaps we can have a single "Skills" section that includes all those items. Or we could have "Qualifications" for certifications and "Skills" for others. But we need to avoid creating sections with filler. We have substantive content for both.
Let's think: The posting includes "Ideal Experience, Background & Skills" which lists experience and skills. Then later "As a Residential Coordinator, You’ll Spend Your Days..." which is more responsibilities. Then "Why Work With Us" includes purpose-driven work, professional growth, inclusive environment (these could be part of Benefits or separate but we already have Benefits). Could be omitted as they are more like selling points but still substantive. However instruction: Prefer a few substantive sections over many thin ones. Could combine "Why Work With Us" into Benefits or maybe omit. But we already have Benefits section with list; we could add a short paragraph about purpose-driven work etc as a
under Benefits? But we should not invent sections. The instruction: include a section ONLY when the posting has real, specific content for it — never emit a heading followed by filler/placeholder text. So we can include Benefits as we have specific list. The "Why Work With Us" could be considered part of Benefits or maybe we could add a section "About the organization" but we already have "Who Are". Actually we have "Who We Are" which is about the organization. That could be "About the role"? Not exactly. The heading "About the role" is suggested but we could use "Who We Are" as content for About the role? The instruction says use
for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). It doesn't forbid using other headings, but we should follow the examples. Likely they expect those headings. So we should map content to those headings.
Thus:
- About the role: Could be the "Who We Are" paragraph plus maybe the mission statement? Actually "Who We Are" describes the organization, not the role. But we could still put it under About the role as overview. Or we could put a brief summary of the role: "As a Residential Coordinator supporting both Upland and Hartford City Group Homes, you will play a key administrative role in Community Living..." That is more about the role. So we can combine both.
- Responsibilities: list of duties.
- Requirements: education, experience, knowledge, physical, safety/compliance.
- Qualifications: maybe certifications? Could include CPR, First Aid, behavioral interventions, medication administration (or ability to obtain). Also maybe experience with accredited agency? But that is more experience.
- Skills: organizational, communication, leadership, crisis assessment, time management, adaptability, word processing/spreadsheet, etc.
- Benefits: list.
- Pay: salary.
- Schedule: hours.
We need to avoid duplication. Ensure we preserve all substantive info.
Let's extract each piece.
First, location: Upland, IN. Not needed for any section; could be omitted as minor metadata? The instruction: do NOT put Job ID / requisition numbers as headings — fold minor metadata into a short
or drop it. Location is minor metadata; we could include in a short
at top maybe. But we are to output only HTML fragment; we could include a
with location and maybe salary? But salary has its own section. Location could be a short
before sections. However instruction: "fold minor metadata into a short
or drop it." So we can add a
for location. But we also have schedule, pay etc. We'll include a
for location maybe.
But we must not repeat job title. No job title appears in the snippet except maybe "Residential Coordinator". The page already shows it, so we should not repeat as heading. We can still mention it in prose.
Now, let's craft sections.
We'll start with a
for location: "Location: Upland, IN". Could also include "Full-Time". But full-time is implied by schedule.
Better to include location
under Benefits? But we should not invent sections. The instruction: include a section ONLY when the posting has real, specific content for it — never emit a heading followed by filler/placeholder text. So we can include Benefits as we have specific list. The "Why Work With Us" could be considered part of Benefits or maybe we could add a section "About the organization" but we already have "Who Are". Actually we have "Who We Are" which is about the organization. That could be "About the role"? Not exactly. The heading "About the role" is suggested but we could use "Who We Are" as content for About the role? The instruction says use
for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). It doesn't forbid using other headings, but we should follow the examples. Likely they expect those headings. So we should map content to those headings. Thus: - About the role: Could be the "Who We Are" paragraph plus maybe the mission statement? Actually "Who We Are" describes the organization, not the role. But we could still put it under About the role as overview. Or we could put a brief summary of the role: "As a Residential Coordinator supporting both Upland and Hartford City Group Homes, you will play a key administrative role in Community Living..." That is more about the role. So we can combine both. - Responsibilities: list of duties. - Requirements: education, experience, knowledge, physical, safety/compliance. - Qualifications: maybe certifications? Could include CPR, First Aid, behavioral interventions, medication administration (or ability to obtain). Also maybe experience with accredited agency? But that is more experience. - Skills: organizational, communication, leadership, crisis assessment, time management, adaptability, word processing/spreadsheet, etc. - Benefits: list. - Pay: salary. - Schedule: hours. We need to avoid duplication. Ensure we preserve all substantive info. Let's extract each piece. First, location: Upland, IN. Not needed for any section; could be omitted as minor metadata? The instruction: do NOT put Job ID / requisition numbers as headings — fold minor metadata into a short
or drop it. Location is minor metadata; we could include in a short
at top maybe. But we are to output only HTML fragment; we could include a
with location and maybe salary? But salary has its own section. Location could be a short
before sections. However instruction: "fold minor metadata into a short
or drop it." So we can add a
for location. But we also have schedule, pay etc. We'll include a
for location maybe. But we must not repeat job title. No job title appears in the snippet except maybe "Residential Coordinator". The page already shows it, so we should not repeat as heading. We can still mention it in prose. Now, let's craft sections. We'll start with a
for location: "Location: Upland, IN". Could also include "Full-Time". But full-time is implied by schedule. Better to include location