Advocate
for section headings: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. Only include sections that have real specific content. We must not repeat job title as heading. Must not include Job ID etc. Remove boilerplate like EEO, etc. Must preserve all substantive info.
We need to parse the posting:
- Intro: Youth Advocate Programs, Inc. (YAP) is dedicated to empowering youth... Status: Part-Time Hourly FLSA Classification: Non-Exempt Summary of the Position: We are seeking a passionate and dedicated Advocate to join our dynamic team. The Advocate will work closely with at-risk youth to provide guidance, support and resources aimed at improving their overall well-being and helping them navigate life challenges. Hourly, Part Time position serving youth and families throughout Tattnall County are available. Applicant must be dependable, committed, and able to serve as a positive role model for youth in the community, school, and home settings.
- The Primary responsibilities of the Advocate are to initiate, organize, plan, develop and implement direct advocacy services to assigned participants and their families. Build trusting relationships with youth and their families Work with individualized support plans Provide support, mentoring, and advocacy Connect youth with community resources and services Monitor and assess progress and adjust support strategies as needed. Collaborate with other professionals and community organizations Maintain accurate records and documentation of services provide All service plans will be based on a strength-based approach using the wrap around model.
- This position offers flexible hours, competitive weekly pay, mileage and activity reimbursement.
- Qualifications/Requirements: High School Diploma or GED is required. Experience working with youth, especially those from at-risk backgrounds Knowledge of community resources and support services Ability to work with diverse populations of staff, children, and families in a collaborative and culturally sensitive manner. Provide quality documentation, progress notes, and submitted within required deadlines. Excellent verbal and written communication skills Ability to work independently and part of a team. Proficient in Microsoft Office Suite preferred. Position requires insured reliable transportation, valid driver's license, and current auto insurance coverage. Bilingual (English/Spanish Speaking) Applicants are a plus.
- Benefits Available: Voluntary Dental Voluntary Vision UNUM Supplemental Insurance Employee Assistance Program 403(b) Retirement Savings Plan Pet Insurance Direct Deposit Flexible Schedule, Weekly Pay Mileage and activity reimbursement
- Then: Join our supportive and collaborative work environment and make a meaningful impact in the lives of youth.
- Then EEO boilerplate to remove.
We need sections: About the role (maybe summary), Responsibilities, Requirements (maybe qualifications), Skills (maybe separate), Benefits, Pay, Schedule.
We must not create sections with filler like "commensurate with experience". We have specific content for Pay: "competitive weekly pay". Schedule: "flexible hours". Benefits: list.
We need to decide what goes where.
About the role: could be the introductory paragraph describing the role and mission.
Responsibilities: list of duties.
Requirements: maybe education and experience.
Skills: maybe communication, teamwork, Microsoft Office, bilingual, etc.
Benefits: list.
Pay: mention competitive weekly pay.
Schedule: flexible hours.
We must not repeat job title.
We need to output only HTML fragment, no /. Use for each section heading. Use - for any list of duties/requirements/benefits. Use
for prose.
We must preserve all substantive info; do not invent or summarize away detail. So we need to include all details from the posting, but we can group them.
Let's extract details:
Intro/mission: "Youth Advocate Programs, Inc. (YAP) is dedicated to empowering youth and fostering positive changes within our communities. We provide personalized support and advocacy to help youth people overcome challenges and achieve their full potential." Also "Status: Part-Time Hourly FLSA Classification: Non-Exempt". Might be considered metadata; we could fold into a short
or drop? The instruction: "do NOT put Job ID / requisition numbers as headings — fold minor metadata into a short
or drop it." So we can include status in a short paragraph maybe under About the role.
Summary of the Position: "We are seeking a passionate and dedicated Advocate to join our dynamic team. The Advocate will work closely with at-risk youth to provide guidance, support and resources aimed at improving their overall well-being and helping them navigate life challenges. Hourly, Part Time position serving youth and families throughout Tattnall County are available. Applicant must be dependable, committed, and able to serve as a positive role model for youth in the community, school, and home settings."
That's prose.
Responsibilities: list:
- initiate, organize, plan, develop and implement direct advocacy services to assigned participants and their families.
- Build trusting relationships with youth and their families
- Work with individualized support plans
- Provide support, mentoring, and advocacy
- Connect youth with community resources and services
- Monitor and assess progress and adjust support strategies as needed.
- Collaborate with other professionals and community organizations
- Maintain accurate records and documentation of services provide (typo: provide)
- All service plans will be based on a strength-based approach using the wrap around model.
We need to keep each as list items.
Qualifications/Requirements: list:
- High School Diploma or GED is required.
- Experience working with youth, especially those from at-risk backgrounds
- Knowledge of community resources and support services
- Ability to work with diverse populations of staff, children, and families in a collaborative and culturally sensitive manner.
- Provide quality documentation, progress notes, and submitted within required deadlines.
- Excellent verbal and written communication skills
- Ability to work independently and part of a team.
- Proficient in Microsoft Office Suite preferred.
- Position requires insured reliable transportation, valid driver's license, and current auto insurance coverage.
- Bilingual (English/Spanish Speaking) Applicants are a plus.
We could split into Requirements (education/experience) and Skills (communication, teamwork, etc). But we have headings: Requirements, Qualifications, Skills. The instruction says use those headings if content exists. We need to decide distribution.
Maybe:
- Requirements: Education (HS Diploma/GED), Experience, Knowledge of community resources, Ability to work with diverse populations, Documentation skills, Transportation requirements.
- Skills: Communication, Teamwork, Microsoft Office, Bilingual.
But we also have "Qualifications" heading; maybe we can combine Requirements and Qualifications? The instruction: "Use
for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." So we can have multiple of those. We need to include sections only when posting has real specific content. So we can include Requirements, Qualifications, Skills, Benefits, Pay, Schedule, About the role, Responsibilities.
We must not repeat content across sections unnecessarily, but we can split.
Let's decide:
About the role: mission statement + status + summary.
Responsibilities: list of duties.
Requirements: Education (HS Diploma/GED), Experience working with youth, Knowledge of community resources, Ability to work with diverse populations, Documentation skills, Transportation requirements (insured reliable transportation, valid driver's license, current auto insurance). Possibly also "Bilingual (English/Spanish Speaking) Applicants are a plus." could be a plus but maybe under Skills.
Qualifications: maybe "Proficient in Microsoft Office Suite preferred." plus maybe "Ability to work independently and part of a team." but that could be skill.
Skills: Communication (verbal/written), Teamwork, Microsoft Office, Bilingual.
But we need to avoid duplication. Let's think: The posting lumps many items under Qualifications/Requirements. We could treat that as Requirements section and not have separate Qualifications or Skills. However we have headings for Qualifications and Skills; we could still include them if we have content.
Better to follow typical structure: Requirements (education, experience, etc.), Skills (specific abilities), Qualifications (maybe certifications). But we have limited.
Let's assign:
- Requirements: HS Diploma/GED, Experience working with youth (especially at-risk), Knowledge of community resources, Ability to work with diverse populations, Documentation skills, Transportation requirements.
- Skills: Excellent verbal and written communication skills, Ability to work independently and part of a team, Proficient in Microsoft Office Suite preferred, Bilingual (English/Spanish Speaking) Applicants are a plus.
- Qualifications: maybe we could include "Position offers flexible hours, competitive weekly pay, mileage and activity reimbursement." but that's Benefits/Pay/Schedule. Not qualifications.
Alternatively, we could skip Qualifications heading if no distinct content. But we have "Qualifications/Requirements" heading in original; we could treat that as Requirements and not have separate Qualifications. The instruction says we can use those headings; we don't have to use all. So we can omit Qualifications if no specific content beyond what we already placed.
Thus sections: About the role, Responsibilities, Requirements, Skills, Benefits, Pay, Schedule.
Check if we have content for each:
About the role: mission + status + summary.
Responsibilities: list.
Requirements: list (education, experience, knowledge, ability to work diverse, documentation, transportation).
Skills: list (communication, teamwork, MS Office, bilingual).
Benefits: list (Voluntary Dental, Voluntary Vision, UNUM Supplemental Insurance, Employee Assistance Program, 403(b) Retirement Savings Plan, Pet Insurance, Direct Deposit, Flexible Schedule, Weekly Pay, Mileage and activity reimbursement). Note: Flexible Schedule and Weekly Pay also appear under Benefits but also we have separate Pay and Schedule sections. The instruction: "never create Pay/Schedule/Benefits sections unless the posting actually states them." The posting states benefits list includes Flexible Schedule, Weekly Pay, Mileage and activity reimbursement. So we could put those under Benefits, but also we have separate Pay and Schedule sections. To avoid duplication, we should not duplicate content. We could put Flexible Schedule and Weekly Pay under Benefits, and then not have separate Pay and Schedule sections (or we could have them but mention they are covered under Benefits). The instruction: "Prefer a few substantive sections over many thin ones." So maybe we combine Pay and Schedule into Benefits? But we have headings for Pay and Schedule; we could still include them if we have specific content. The posting explicitly mentions "competitive weekly pay" and "flexible hours". So we could have Pay: competitive weekly pay. Schedule: flexible hours. And Benefits: other benefits (dental, vision, insurance, retirement, pet insurance, direct deposit, mileage reimbursement). That avoids duplication.
Thus Benefits: Voluntary Dental, Voluntary Vision, UNUM Supplemental Insurance, Employee Assistance Program, 403(b) Retirement Savings Plan, Pet Insurance, Direct Deposit, Mileage and activity reimbursement.
Pay: competitive weekly pay.
Schedule: flexible hours.
Now ensure we preserve all substantive info: we have included everything.
Check we didn't miss: "All service plans will be based on a strength-based approach using the wrap around model." included in responsibilities.
"Applicant must be dependable, committed, and able to serve as a positive role model for youth in the community, school, and home settings." That's part of summary; we included in About the role.
"Hourly, Part Time position serving youth and families throughout Tattnall County are available." included.
"Status: Part-Time Hourly FLSA Classification: Non-Exempt" we could include in About the role as a short paragraph.
Now produce HTML.
We need to wrap each section: About the role
then
... maybe multiple paragraphs. For lists:
- ...
.
We must not include any extra text outside HTML.
Let's craft.
About the role paragraph(s):
First paragraph: mission statement.
Second paragraph: status and summary.
- for any list of duties/requirements/benefits. Use
for prose. We must preserve all substantive info; do not invent or summarize away detail. So we need to include all details from the posting, but we can group them. Let's extract details: Intro/mission: "Youth Advocate Programs, Inc. (YAP) is dedicated to empowering youth and fostering positive changes within our communities. We provide personalized support and advocacy to help youth people overcome challenges and achieve their full potential." Also "Status: Part-Time Hourly FLSA Classification: Non-Exempt". Might be considered metadata; we could fold into a short
or drop? The instruction: "do NOT put Job ID / requisition numbers as headings — fold minor metadata into a short
or drop it." So we can include status in a short paragraph maybe under About the role. Summary of the Position: "We are seeking a passionate and dedicated Advocate to join our dynamic team. The Advocate will work closely with at-risk youth to provide guidance, support and resources aimed at improving their overall well-being and helping them navigate life challenges. Hourly, Part Time position serving youth and families throughout Tattnall County are available. Applicant must be dependable, committed, and able to serve as a positive role model for youth in the community, school, and home settings." That's prose. Responsibilities: list: - initiate, organize, plan, develop and implement direct advocacy services to assigned participants and their families. - Build trusting relationships with youth and their families - Work with individualized support plans - Provide support, mentoring, and advocacy - Connect youth with community resources and services - Monitor and assess progress and adjust support strategies as needed. - Collaborate with other professionals and community organizations - Maintain accurate records and documentation of services provide (typo: provide) - All service plans will be based on a strength-based approach using the wrap around model. We need to keep each as list items. Qualifications/Requirements: list: - High School Diploma or GED is required. - Experience working with youth, especially those from at-risk backgrounds - Knowledge of community resources and support services - Ability to work with diverse populations of staff, children, and families in a collaborative and culturally sensitive manner. - Provide quality documentation, progress notes, and submitted within required deadlines. - Excellent verbal and written communication skills - Ability to work independently and part of a team. - Proficient in Microsoft Office Suite preferred. - Position requires insured reliable transportation, valid driver's license, and current auto insurance coverage. - Bilingual (English/Spanish Speaking) Applicants are a plus. We could split into Requirements (education/experience) and Skills (communication, teamwork, etc). But we have headings: Requirements, Qualifications, Skills. The instruction says use those headings if content exists. We need to decide distribution. Maybe: - Requirements: Education (HS Diploma/GED), Experience, Knowledge of community resources, Ability to work with diverse populations, Documentation skills, Transportation requirements. - Skills: Communication, Teamwork, Microsoft Office, Bilingual. But we also have "Qualifications" heading; maybe we can combine Requirements and Qualifications? The instruction: "Use
for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." So we can have multiple of those. We need to include sections only when posting has real specific content. So we can include Requirements, Qualifications, Skills, Benefits, Pay, Schedule, About the role, Responsibilities. We must not repeat content across sections unnecessarily, but we can split. Let's decide: About the role: mission statement + status + summary. Responsibilities: list of duties. Requirements: Education (HS Diploma/GED), Experience working with youth, Knowledge of community resources, Ability to work with diverse populations, Documentation skills, Transportation requirements (insured reliable transportation, valid driver's license, current auto insurance). Possibly also "Bilingual (English/Spanish Speaking) Applicants are a plus." could be a plus but maybe under Skills. Qualifications: maybe "Proficient in Microsoft Office Suite preferred." plus maybe "Ability to work independently and part of a team." but that could be skill. Skills: Communication (verbal/written), Teamwork, Microsoft Office, Bilingual. But we need to avoid duplication. Let's think: The posting lumps many items under Qualifications/Requirements. We could treat that as Requirements section and not have separate Qualifications or Skills. However we have headings for Qualifications and Skills; we could still include them if we have content. Better to follow typical structure: Requirements (education, experience, etc.), Skills (specific abilities), Qualifications (maybe certifications). But we have limited. Let's assign: - Requirements: HS Diploma/GED, Experience working with youth (especially at-risk), Knowledge of community resources, Ability to work with diverse populations, Documentation skills, Transportation requirements. - Skills: Excellent verbal and written communication skills, Ability to work independently and part of a team, Proficient in Microsoft Office Suite preferred, Bilingual (English/Spanish Speaking) Applicants are a plus. - Qualifications: maybe we could include "Position offers flexible hours, competitive weekly pay, mileage and activity reimbursement." but that's Benefits/Pay/Schedule. Not qualifications. Alternatively, we could skip Qualifications heading if no distinct content. But we have "Qualifications/Requirements" heading in original; we could treat that as Requirements and not have separate Qualifications. The instruction says we can use those headings; we don't have to use all. So we can omit Qualifications if no specific content beyond what we already placed. Thus sections: About the role, Responsibilities, Requirements, Skills, Benefits, Pay, Schedule. Check if we have content for each: About the role: mission + status + summary. Responsibilities: list. Requirements: list (education, experience, knowledge, ability to work diverse, documentation, transportation). Skills: list (communication, teamwork, MS Office, bilingual). Benefits: list (Voluntary Dental, Voluntary Vision, UNUM Supplemental Insurance, Employee Assistance Program, 403(b) Retirement Savings Plan, Pet Insurance, Direct Deposit, Flexible Schedule, Weekly Pay, Mileage and activity reimbursement). Note: Flexible Schedule and Weekly Pay also appear under Benefits but also we have separate Pay and Schedule sections. The instruction: "never create Pay/Schedule/Benefits sections unless the posting actually states them." The posting states benefits list includes Flexible Schedule, Weekly Pay, Mileage and activity reimbursement. So we could put those under Benefits, but also we have separate Pay and Schedule sections. To avoid duplication, we should not duplicate content. We could put Flexible Schedule and Weekly Pay under Benefits, and then not have separate Pay and Schedule sections (or we could have them but mention they are covered under Benefits). The instruction: "Prefer a few substantive sections over many thin ones." So maybe we combine Pay and Schedule into Benefits? But we have headings for Pay and Schedule; we could still include them if we have specific content. The posting explicitly mentions "competitive weekly pay" and "flexible hours". So we could have Pay: competitive weekly pay. Schedule: flexible hours. And Benefits: other benefits (dental, vision, insurance, retirement, pet insurance, direct deposit, mileage reimbursement). That avoids duplication. Thus Benefits: Voluntary Dental, Voluntary Vision, UNUM Supplemental Insurance, Employee Assistance Program, 403(b) Retirement Savings Plan, Pet Insurance, Direct Deposit, Mileage and activity reimbursement. Pay: competitive weekly pay. Schedule: flexible hours. Now ensure we preserve all substantive info: we have included everything. Check we didn't miss: "All service plans will be based on a strength-based approach using the wrap around model." included in responsibilities. "Applicant must be dependable, committed, and able to serve as a positive role model for youth in the community, school, and home settings." That's part of summary; we included in About the role. "Hourly, Part Time position serving youth and families throughout Tattnall County are available." included. "Status: Part-Time Hourly FLSA Classification: Non-Exempt" we could include in About the role as a short paragraph. Now produce HTML. We need to wrap each section:
About the role
then... maybe multiple paragraphs. For lists:
- ...