Career Pathways Manager
Boys and Girls Clubs of Boston · Boston, MA · 4 wk ago
On-siteHuman Resources$55k–$66k/yrFull-time
We need to output HTML fragment with sections: headings for sections like About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We need to include only sections with real content. The posting includes: Position Overview (maybe About the role). Essential Duties and Responsibilities (Responsibilities). Qualifications (Required, Preferred). Also Salary & Benefits (Pay and Benefits). Travel maybe not needed. General BGCB Expectations maybe not needed as separate heading? Could be part of Requirements? But we can include as part of Requirements or Skills? The instructions: Use headings for those specific labels. We should map content accordingly.
We have:
- About the role: Position Overview paragraph.
- Responsibilities: ESSENTIAL DUTIES And RESPONSIBILITIES (multiple bullet-like sentences). We need to put in
for sections like About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We need to include only sections with real content. The posting includes: Position Overview (maybe About the role). Essential Duties and Responsibilities (Responsibilities). Qualifications (Required, Preferred). Also Salary & Benefits (Pay and Benefits). Travel maybe not needed. General BGCB Expectations maybe not needed as separate heading? Could be part of Requirements? But we can include as part of Requirements or Skills? The instructions: Use headings for those specific labels. We should map content accordingly.
We have:
- About the role: Position Overview paragraph.
- Responsibilities: ESSENTIAL DUTIES And RESPONSIBILITIES (multiple bullet-like sentences). We need to put in - . The content includes several paragraphs each starting with a bold heading? Actually they have headings like "Commitment to Excellence in Workforce Readiness, Career Development, and Teen Engagement", then bullet sentences. We can treat each bullet as list item. We'll need to extract list items.
Let's parse the responsibilities section:
"Commitment to Excellence in Workforce Readiness, Career Development, and Teen Engagement In partnership with the Ready to Work team and other Club staff, facilitate workforce readiness programming that includes skill development, career exploration, industry-recognized certifications, and high-quality work-based learning experiences.Provide individual and group career coaching to help teen members identify interests, develop career goals and plans, and prepare for employment and future opportunities.Lead and coordinate teen outreach, recruitment, and enrollment into Ready to Work programming.Support intern success through ongoing coaching, performance feedback, professional development, and encouragement around future education and career goals.Contribute to the planning and delivery of Ready to Work University curriculum, workshops, and events."
That's a paragraph with multiple sentences; we could split each sentence as list item? The instruction: Use
- for any list of duties/requirements/benefits. The posting does not explicitly use bullet list but we can treat each duty as list item. We'll split by sentences after the heading.
Similarly "Employer Partnerships and Work-Based Learning Develop and maintain productive relationships with employers and workforce partners that support teen employment and career-development opportunities.Identify and assess new employer and community partnerships that expand workforce readiness and work-based learning opportunities for teens.Coordinate and oversee school-year and summer internship opportunities, including systems and processes that support teen participation and effective Club and employer engagement.Maintain positive and productive relationships with teens, families, employers, schools, Club staff, community organizations, and other workforce partners."
"Program Operations, Evaluation, and Continuous Improvement Evaluate workforce readiness programming and use participant feedback, outcomes, and program data to strengthen delivery and improve teen experiences.Identify gaps in workforce readiness programming, resources, and service delivery and collaborate with appropriate staff and partners to address them.Maintain current knowledge of effective practices and trends in youth workforce readiness, career development, leadership, life skills, and youth development.Support accurate and timely payroll-related processes and documentation for on-site Club interns.Meet annual Ready to Work Program Standards and related program goals, reporting, and documentation requirements."
"Staff Support, Training, Communication, and Collaboration Provide workforce readiness guidance, technical assistance, and training to Club staff as appropriate.Collaborate with Club leadership, the Ready to Work team, and youth development staff to integrate career readiness, leadership, and life-skills development throughout the teen experience."
We'll create list items for each sentence.
Now Qualifications: Required and Preferred.
We need sections: Requirements, Qualifications, Skills? The instruction says use headings for: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We can combine Requirements and Qualifications maybe but better to separate: Requirements could be required experience, Qualifications could be preferred? Or we could put required under Requirements and preferred under Qualifications. Skills maybe separate but we could include skills under Qualifications or Requirements. However we should not create empty sections. Let's see content:
Qualifications Required: list of items.
Preferred Or Ideal: list.
We could put Required under Requirements heading, Preferred under Qualifications heading. Skills maybe not needed separately; we could omit Skills heading if no specific skills list beyond those already covered. But we have some skills like "Strong interpersonal, relationship-building, and communication skills." etc. Those are under Required. Could put them under Skills heading. But we already have Required list includes those. To avoid duplication, maybe we put Required under Requirements, Preferred under Qualifications, and Skills omitted.
But we need to follow instruction: Use headings for those labels only when posting has real specific content. We have content for Requirements (required experience). We have content for Qualifications (preferred). We have content for Skills? Could extract skills like "Strong interpersonal, relationship-building, and communication skills." etc. But those are already in Required. Might be redundant. Safer to omit Skills heading.
Pay and Benefits: Salary & Benefits section includes salary range and mention of competitive benefits. So we can have Pay heading with salary range, Benefits heading with benefits description.
Schedule: Not explicitly mentioned; there is "Flexibility to work Club hours, including evenings and occasional weekends, as seasons and service needs change." That's schedule info. So we can include Schedule heading with that sentence.
Travel: Not a standard heading; we can ignore.
Now we need to preserve all substantive information. Let's extract.
About the role: Position Overview paragraph: "The Teen Career Pathways Manager leads the implementation of BGCB’s youth workforce readiness strategy at the Club and prepares teen members for employment, career exploration, and future educational and career opportunities. The position provides career coaching, job-readiness programming, case management, work-based learning opportunities, and life-skills development while ensuring teens and families receive clear and consistent information about Ready to Work opportunities. The Teen Career Pathways Program Manager works closely with Club leadership, the Ready to Work team, employers, schools, and community partners to connect teens to meaningful career-development and employment experiences."
We'll put that in
.
Responsibilities: We'll create
with list items for each duty sentence.
Let's extract sentences:
From first block:
1. In partnership with the Ready to Work team and other Club staff, facilitate workforce readiness programming that includes skill development, career exploration, industry-recognized certifications, and high-quality work-based learning experiences.
2. Provide individual and group career coaching to help teen members identify interests, develop career goals and plans, and prepare for employment and future opportunities.
3. Lead and coordinate teen outreach, recruitment, and enrollment into Ready to Work programming.
4. Support intern success through ongoing coaching, performance feedback, professional development, and encouragement around future education and career goals.
5. Contribute to the planning and delivery of Ready to Work University curriculum, workshops, and events.
Second block:
6. Develop and maintain productive relationships with employers and workforce partners that support teen employment and career-development opportunities.
7. Identify and assess new employer and community partnerships that expand workforce readiness and work-based learning opportunities for teens.
8. Coordinate and oversee school-year and summer internship opportunities, including systems and processes that support teen participation and effective Club and employer engagement.
9. Maintain positive and productive relationships with teens, families, employers, schools, Club staff, community organizations, and other workforce partners.
Third block:
10. Evaluate workforce readiness programming and use participant feedback, outcomes, and program data to strengthen delivery and improve teen experiences.
11. Identify gaps in workforce readiness programming, resources, and service delivery and collaborate with appropriate staff and partners to address them.
12. Maintain current knowledge of effective practices and trends in youth workforce readiness, career development, leadership, life skills, and youth development.
13. Support accurate and timely payroll-related processes and documentation for on-site Club interns.
14. Meet annual Ready to Work Program Standards and related program goals, reporting, and documentation requirements.
Fourth block:
15. Provide workforce readiness guidance, technical assistance, and training to Club staff as appropriate.
16. Collaborate with Club leadership, the Ready to Work team, and youth development staff to integrate career readiness, leadership, and life-skills development throughout the teen experience.
Now Requirements (Required Experience):
List items:
- Experience developing and delivering workforce readiness, career development, youth development, or related programming and support services for teens.
- Knowledge of career readiness, career exploration, life-skills development, leadership, and youth development practices for teens.
- At least one year of supervisory, program leadership, or internship/work-based learning coordination experience.
- Strong interpersonal, relationship-building, and communication skills.
- Ability to coach and engage teens around career planning, employment preparation, and professional development.
- Must be or become CPR/First Aid certified.
- Ability to work effectively with teens and families from a variety of backgrounds.
- Ability to work independently and collaboratively as part of a team.
- Flexibility to work Club hours, including evenings and occasional weekends, as seasons and service needs change.
- Valid driver’s license.
Now Qualifications (Preferred Or Ideal):
- Bachelor’s degree in education, youth development, human services, workforce development, counseling, business, or a related field; equivalent relevant education and experience considered.
- Proficiency with Microsoft Office and web-based systems.
- Experience coordinating youth internships, employment programs, or other work-based learning opportunities.
- Experience developing employer, school, or community partnerships that support youth career development.
Now Pay: Salary range: "$55,255.20/year - $66,120.60/year - commensurate with experience". We should include that as Pay heading.
Benefits: "along with competitive benefits and a great work environment". That's benefits description.
Schedule: "Flexibility to work Club hours, including evenings and occasional weekends, as seasons and service needs change." Already in Requirements but we can also put under Schedule. However we might duplicate. The instruction: Preserve ALL substantive information; do NOT invent or summarize away detail. Duplication is okay if it's present in posting? It appears in Requirements as flexibility. We could keep it only under Requirements and not duplicate under Schedule, but then Schedule heading would be empty. Better to put schedule info under Schedule heading and maybe remove from Requirements? But that would remove info from Requirements. However the requirement includes that flexibility; we could keep it in both places? The instruction says preserve ALL substantive information; duplication is not prohibited but might be considered redundant. Safer to keep it only once, maybe under Requirements (as it's a requirement). Then we would not have Schedule section because we would have no specific schedule content besides that. But the instruction says include a section ONLY when the posting has real, specific content for it. If we move the flexibility to Schedule, we still have content for Schedule, but we would lose it from Requirements unless we duplicate. Could we keep it in both? That would preserve info but duplicate. Not prohibited but might be considered unnecessary. I'd rather keep it under Requirements and not create Schedule section, because the posting does not have a separate schedule section; it's just a line within qualifications. The instruction says use headings for Schedule only when posting has real specific content for it. It does have that line, but it's embedded. I'd argue it's still specific content for schedule. So we could create Schedule heading with that sentence, and also keep it in Requirements? Might be okay but could be seen as duplication. I'd choose to include Schedule heading with that sentence, and keep it also in Requirements? Might be okay but risk of being considered filler? Not sure.
Better to follow typical parsing: extract schedule info to Schedule heading, and remove from Requirements to avoid duplication. But then we lose that requirement from Requirements section. However the requirement is still present in the original posting; we need to preserve ALL substantive information. If we remove it from Requirements, we are not preserving it there. But we could keep it in both places; that preserves it. Duplication is not prohibited. I'll keep it in both.
Now Benefits: we have "along with competitive benefits and a great work environment". That's vague but it's benefits. We'll put that under Benefits.
Now we need to output HTML fragment only, no /. Use for each section heading.
Let's craft:
About the role
- for any list of duties/requirements/benefits. The posting does not explicitly use bullet list but we can treat each duty as list item. We'll split by sentences after the heading.
Similarly "Employer Partnerships and Work-Based Learning Develop and maintain productive relationships with employers and workforce partners that support teen employment and career-development opportunities.Identify and assess new employer and community partnerships that expand workforce readiness and work-based learning opportunities for teens.Coordinate and oversee school-year and summer internship opportunities, including systems and processes that support teen participation and effective Club and employer engagement.Maintain positive and productive relationships with teens, families, employers, schools, Club staff, community organizations, and other workforce partners."
"Program Operations, Evaluation, and Continuous Improvement Evaluate workforce readiness programming and use participant feedback, outcomes, and program data to strengthen delivery and improve teen experiences.Identify gaps in workforce readiness programming, resources, and service delivery and collaborate with appropriate staff and partners to address them.Maintain current knowledge of effective practices and trends in youth workforce readiness, career development, leadership, life skills, and youth development.Support accurate and timely payroll-related processes and documentation for on-site Club interns.Meet annual Ready to Work Program Standards and related program goals, reporting, and documentation requirements."
"Staff Support, Training, Communication, and Collaboration Provide workforce readiness guidance, technical assistance, and training to Club staff as appropriate.Collaborate with Club leadership, the Ready to Work team, and youth development staff to integrate career readiness, leadership, and life-skills development throughout the teen experience."
We'll create list items for each sentence.
Now Qualifications: Required and Preferred.
We need sections: Requirements, Qualifications, Skills? The instruction says use headings for: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We can combine Requirements and Qualifications maybe but better to separate: Requirements could be required experience, Qualifications could be preferred? Or we could put required under Requirements and preferred under Qualifications. Skills maybe separate but we could include skills under Qualifications or Requirements. However we should not create empty sections. Let's see content:
Qualifications Required: list of items.
Preferred Or Ideal: list.
We could put Required under Requirements heading, Preferred under Qualifications heading. Skills maybe not needed separately; we could omit Skills heading if no specific skills list beyond those already covered. But we have some skills like "Strong interpersonal, relationship-building, and communication skills." etc. Those are under Required. Could put them under Skills heading. But we already have Required list includes those. To avoid duplication, maybe we put Required under Requirements, Preferred under Qualifications, and Skills omitted.
But we need to follow instruction: Use headings for those labels only when posting has real specific content. We have content for Requirements (required experience). We have content for Qualifications (preferred). We have content for Skills? Could extract skills like "Strong interpersonal, relationship-building, and communication skills." etc. But those are already in Required. Might be redundant. Safer to omit Skills heading.
Pay and Benefits: Salary & Benefits section includes salary range and mention of competitive benefits. So we can have Pay heading with salary range, Benefits heading with benefits description.
Schedule: Not explicitly mentioned; there is "Flexibility to work Club hours, including evenings and occasional weekends, as seasons and service needs change." That's schedule info. So we can include Schedule heading with that sentence.
Travel: Not a standard heading; we can ignore.
Now we need to preserve all substantive information. Let's extract.
About the role: Position Overview paragraph: "The Teen Career Pathways Manager leads the implementation of BGCB’s youth workforce readiness strategy at the Club and prepares teen members for employment, career exploration, and future educational and career opportunities. The position provides career coaching, job-readiness programming, case management, work-based learning opportunities, and life-skills development while ensuring teens and families receive clear and consistent information about Ready to Work opportunities. The Teen Career Pathways Program Manager works closely with Club leadership, the Ready to Work team, employers, schools, and community partners to connect teens to meaningful career-development and employment experiences."
We'll put that in
. Responsibilities: We'll create
- with list items for each duty sentence.
Let's extract sentences:
From first block:
1. In partnership with the Ready to Work team and other Club staff, facilitate workforce readiness programming that includes skill development, career exploration, industry-recognized certifications, and high-quality work-based learning experiences.
2. Provide individual and group career coaching to help teen members identify interests, develop career goals and plans, and prepare for employment and future opportunities.
3. Lead and coordinate teen outreach, recruitment, and enrollment into Ready to Work programming.
4. Support intern success through ongoing coaching, performance feedback, professional development, and encouragement around future education and career goals.
5. Contribute to the planning and delivery of Ready to Work University curriculum, workshops, and events.
Second block:
6. Develop and maintain productive relationships with employers and workforce partners that support teen employment and career-development opportunities.
7. Identify and assess new employer and community partnerships that expand workforce readiness and work-based learning opportunities for teens.
8. Coordinate and oversee school-year and summer internship opportunities, including systems and processes that support teen participation and effective Club and employer engagement.
9. Maintain positive and productive relationships with teens, families, employers, schools, Club staff, community organizations, and other workforce partners.
Third block:
10. Evaluate workforce readiness programming and use participant feedback, outcomes, and program data to strengthen delivery and improve teen experiences.
11. Identify gaps in workforce readiness programming, resources, and service delivery and collaborate with appropriate staff and partners to address them.
12. Maintain current knowledge of effective practices and trends in youth workforce readiness, career development, leadership, life skills, and youth development.
13. Support accurate and timely payroll-related processes and documentation for on-site Club interns.
14. Meet annual Ready to Work Program Standards and related program goals, reporting, and documentation requirements.
Fourth block:
15. Provide workforce readiness guidance, technical assistance, and training to Club staff as appropriate.
16. Collaborate with Club leadership, the Ready to Work team, and youth development staff to integrate career readiness, leadership, and life-skills development throughout the teen experience.
Now Requirements (Required Experience):
List items:
- Experience developing and delivering workforce readiness, career development, youth development, or related programming and support services for teens.
- Knowledge of career readiness, career exploration, life-skills development, leadership, and youth development practices for teens.
- At least one year of supervisory, program leadership, or internship/work-based learning coordination experience.
- Strong interpersonal, relationship-building, and communication skills.
- Ability to coach and engage teens around career planning, employment preparation, and professional development.
- Must be or become CPR/First Aid certified.
- Ability to work effectively with teens and families from a variety of backgrounds.
- Ability to work independently and collaboratively as part of a team.
- Flexibility to work Club hours, including evenings and occasional weekends, as seasons and service needs change.
- Valid driver’s license.
Now Qualifications (Preferred Or Ideal):
- Bachelor’s degree in education, youth development, human services, workforce development, counseling, business, or a related field; equivalent relevant education and experience considered.
- Proficiency with Microsoft Office and web-based systems.
- Experience coordinating youth internships, employment programs, or other work-based learning opportunities.
- Experience developing employer, school, or community partnerships that support youth career development.
Now Pay: Salary range: "$55,255.20/year - $66,120.60/year - commensurate with experience". We should include that as Pay heading.
Benefits: "along with competitive benefits and a great work environment". That's benefits description.
Schedule: "Flexibility to work Club hours, including evenings and occasional weekends, as seasons and service needs change." Already in Requirements but we can also put under Schedule. However we might duplicate. The instruction: Preserve ALL substantive information; do NOT invent or summarize away detail. Duplication is okay if it's present in posting? It appears in Requirements as flexibility. We could keep it only under Requirements and not duplicate under Schedule, but then Schedule heading would be empty. Better to put schedule info under Schedule heading and maybe remove from Requirements? But that would remove info from Requirements. However the requirement includes that flexibility; we could keep it in both places? The instruction says preserve ALL substantive information; duplication is not prohibited but might be considered redundant. Safer to keep it only once, maybe under Requirements (as it's a requirement). Then we would not have Schedule section because we would have no specific schedule content besides that. But the instruction says include a section ONLY when the posting has real, specific content for it. If we move the flexibility to Schedule, we still have content for Schedule, but we would lose it from Requirements unless we duplicate. Could we keep it in both? That would preserve info but duplicate. Not prohibited but might be considered unnecessary. I'd rather keep it under Requirements and not create Schedule section, because the posting does not have a separate schedule section; it's just a line within qualifications. The instruction says use headings for Schedule only when posting has real specific content for it. It does have that line, but it's embedded. I'd argue it's still specific content for schedule. So we could create Schedule heading with that sentence, and also keep it in Requirements? Might be okay but could be seen as duplication. I'd choose to include Schedule heading with that sentence, and keep it also in Requirements? Might be okay but risk of being considered filler? Not sure.
Better to follow typical parsing: extract schedule info to Schedule heading, and remove from Requirements to avoid duplication. But then we lose that requirement from Requirements section. However the requirement is still present in the original posting; we need to preserve ALL substantive information. If we remove it from Requirements, we are not preserving it there. But we could keep it in both places; that preserves it. Duplication is not prohibited. I'll keep it in both.
Now Benefits: we have "along with competitive benefits and a great work environment". That's vague but it's benefits. We'll put that under Benefits.
Now we need to output HTML fragment only, no /. Use
for each section heading. Let's craft:
About the role