Project Search Skills Trainer
employU · Port St Lucie, FL · 4 wk ago
Human Resources$50k/yrVolunteer
We need to output HTML fragment with sections: use for section headings like About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We must only include sections when posting has real specific content. We need to parse the description.
The posting includes:
- Description: culture EPIC, values statement, flexible schedule, paid weekly, working in community, making difference, great team, work/life balance. Also mentions full-time benefits list, part-time benefits list. So we have Benefits content.
- Responsibilities: The "ESSENTIAL FUNCTIONS" list is responsibilities.
- Requirements: There's a "Requirements" heading then "ESSENTIAL FUNCTIONS" (but that's responsibilities). Actually after "Requirements" heading they list essential functions. Then "Position Qualifications" then "Skills & Abilities" then "Education:" etc. Then "Other Requirements:" then "PHYSICAL DEMANDS AND WORKING ENVIRONMENT". So we need to separate.
We need sections: About the role (maybe from description intro), Responsibilities (essential functions), Requirements (maybe education/experience/computer skills/other requirements), Qualifications (maybe position qualifications?), Skills (skills & abilities), Benefits (full-time/part-time benefits), Pay (not mentioned), Schedule (maybe mention flexible schedule, paid weekly, typical hours 8-4 M-F occasional weekend). So we can include Schedule.
We must not repeat job title as heading. No Job ID.
We must not include boilerplate like EEO etc. Not present.
We must not include sections with placeholder/filler like "commensurate with experience". Not present.
We must preserve all substantive info.
We need to output only HTML fragment, no /, no markdown fences.
We'll create sections:
for section headings like About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We must only include sections when posting has real specific content. We need to parse the description.
The posting includes:
- Description: culture EPIC, values statement, flexible schedule, paid weekly, working in community, making difference, great team, work/life balance. Also mentions full-time benefits list, part-time benefits list. So we have Benefits content.
- Responsibilities: The "ESSENTIAL FUNCTIONS" list is responsibilities.
- Requirements: There's a "Requirements" heading then "ESSENTIAL FUNCTIONS" (but that's responsibilities). Actually after "Requirements" heading they list essential functions. Then "Position Qualifications" then "Skills & Abilities" then "Education:" etc. Then "Other Requirements:" then "PHYSICAL DEMANDS AND WORKING ENVIRONMENT". So we need to separate.
We need sections: About the role (maybe from description intro), Responsibilities (essential functions), Requirements (maybe education/experience/computer skills/other requirements), Qualifications (maybe position qualifications?), Skills (skills & abilities), Benefits (full-time/part-time benefits), Pay (not mentioned), Schedule (maybe mention flexible schedule, paid weekly, typical hours 8-4 M-F occasional weekend). So we can include Schedule.
We must not repeat job title as heading. No Job ID.
We must not include boilerplate like EEO etc. Not present.
We must not include sections with placeholder/filler like "commensurate with experience". Not present.
We must preserve all substantive info.
We need to output only HTML fragment, no /, no markdown fences.
We'll create sections:
About the role
with paragraph(s) describing culture, values, flexible schedule, paid weekly, community impact, growth opportunities.
Responsibilities
with - list of essential functions (the long list). Must preserve all bullet points.
Requirements
maybe combine education, experience, computer skills, other requirements (background check, transportation, etc). Could also include physical demands? Might be separate but we can include under Requirements or maybe a separate section "Physical Demands". But we only have headings list: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We can map:
- Requirements: education, experience, computer skills, other requirements (background check, transportation, etc). Also maybe "Position Qualifications" could be considered Requirements? But we have separate Qualifications heading. The posting has "Position Qualifications" then "Skills & Abilities". So we can map:
Qualifications
for Position Qualifications (competency statements list). Actually "Position Qualifications Competency Statement(s) Job Knowledge Training Skills Interpersonal Skills Relationship Building Business Development Communication Problem Solving/Analysis Organizational Skills Detail Oriented Time Management Ability to maintain cooperative working relationships and demonstrates sensitivity and respect for a diverse population." That's a list of competencies.
Skills
for Skills & Abilities (Education, Experience, Computer Skills, Other Requirements? Actually Other Requirements maybe separate but could go under Skills? Might be better to put Other Requirements under Requirements. But we already used Requirements for education/experience etc. Let's think.
We need to avoid duplication. Let's parse sections:
From posting:
Description (first paragraph about culture, values, flexible schedule, paid weekly, community impact, growth).
Then "Looking for meaningful work..." etc.
Then "Our team works within the disability community..." etc.
Then "Because we are always expanding..." etc.
Then "Full-time employees are offered: ..." list benefits.
Then "Part-time employees may be offered: ..." list benefits.
Then "Want to get a glimpse..." video link (we should drop as per instruction: remove application instructions? Video link maybe not boilerplate but it's promotional; could be considered part of description? Might keep as part of About the role? It's a link to video; we could keep as part of About the role paragraph? But instruction: remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. Video link is not exactly those; it's optional media. Might keep but could be considered not essential. Safer to drop? The instruction says remove application instructions. Video link is not application instruction. It's just a link to video. Could keep but not required. I'd keep it as part of About the role maybe as a link.
Then "Requirements ESSENTIAL FUNCTIONS" heading then list of essential functions.
Then "Position Qualifications Competency Statement(s) Job Knowledge Training Skills Interpersonal Skills Relationship Building Business Development Communication Problem Solving/Analysis Organizational Skills Detail Oriented Time Management Ability to maintain cooperative working relationships and demonstrates sensitivity and respect for a diverse population."
Then "Skills & Abilities Education: BA Degree ... Experience: Individuals without a BA Degree ... Computer Skills: Proficient with Microsoft Suite ... Other Requirements: Position typically works 8:00 am—4:00 pm, M-F, with occasional weekend work Ability to pass a level 2 background check. Must have reliable transportation, a valid driver’s license, auto registration, auto insurance minimum coverage of bodily injury $50,000 per person/$100,000 per accident. Ideal candidates will have experience and knowledge of the business community as well as providing support to individuals with disabilities. Must be creative, passionate and be successful in job placement. Participates in professional development in the following areas: systematic instruction, learning work skills, training techniques and strategies and other appropriate training. Must have own computer, printer, smartphone with data plan, and high-speed internet connection."
Then "PHYSICAL DEMANDS AND WORKING ENVIRONMENT ..." which we could include under Requirements or maybe a separate section but not in allowed headings. Could fold into Requirements or maybe under Skills? Probably under Requirements as "Other Requirements" includes work hours, background check, transportation etc. Physical demands could be part of Requirements as well.
We need to include Schedule section: we have flexible schedule, paid weekly, typical hours 8-4 M-F occasional weekend. So we can put that in Schedule.
Pay section: not mentioned, so omit.
Benefits section: we have full-time and part-time benefits list.
Thus sections:
About the role: include culture, values, flexible schedule, paid weekly, community impact, growth opportunities, maybe video link.
Responsibilities: essential functions list.
Requirements: maybe combine education, experience, computer skills, other requirements (background check, transportation, etc), physical demands? But we also have Qualifications and Skills sections.
We need to decide mapping to avoid missing content.
Let's assign:
- About the role: description paragraph(s).
- Responsibilities: essential functions.
- Qualifications: Position Qualifications competency statements.
- Skills: Skills & Abilities (Education, Experience, Computer Skills, Other Requirements? Actually Other Requirements includes work hours, background check, transportation, etc. Could be part of Skills? Might be better to put Other Requirements under Requirements, but we already used Requirements for something else. Let's think: The headings list includes Requirements, Qualifications, Skills. So we can allocate:
Requirements: Education, Experience, Computer Skills, Other Requirements (background check, transportation, etc), Physical Demands.
Qualifications: Position Qualifications competency statements.
Skills: maybe not needed if we put everything else elsewhere. But we have Skills & Abilities heading in posting; we could map that to Skills section. However Skills & Abilities includes Education, Experience, Computer Skills, Other Requirements. That's overlapping with Requirements. To avoid duplication, we could treat Skills & Abilities as Skills section, and Requirements as something else like "Requirements" maybe just the essential functions? But we already used Responsibilities for essential functions. Hmm.
Alternative: Use Requirements for the "Requirements" heading that appears before essential functions? Actually the posting says "Requirements ESSENTIAL FUNCTIONS". So the heading "Requirements" is followed by essential functions. So we could map that to Responsibilities (makes sense). Then after that we have "Position Qualifications" then "Skills & Abilities". So we could map:
- Responsibilities: essential functions (under Requirements heading).
- Qualifications: Position Qualifications.
- Skills: Skills & Abilities.
- Benefits: benefits.
- Schedule: schedule info (flexible schedule, paid weekly, typical hours).
- About the role: introductory description.
Thus we don't need a separate Requirements section; we already used Responsibilities for the essential functions. The heading "Requirements" in posting is misnamed but we treat as responsibilities.
Thus we will not emit a Requirements heading (since we already used Responsibilities). But the instruction says use for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). It doesn't say we must use all; we can omit sections lacking content. So we can omit Requirements if we think its content is covered elsewhere. However the posting's "Requirements" heading is actually essential functions; we already used Responsibilities for that. So we can omit Requirements heading.
Thus final sections: About the role, Responsibilities, Qualifications, Skills, Benefits, Schedule.
Check if we have any content for Pay: none, omit.
Now we need to extract content precisely.
About the role: combine paragraphs:
"At employU, our culture is EPIC. It’s not just a buzzword; it’s how we show up every day for our team and the community we serve. employU Values Statement — EPIC Empowerment – We give every person the tools, support, and confidence to chart their own career path. Passion – Energy and enthusiasm drive us to exceed expectations and change lives. Integrity – Honesty, transparency, and ethical decision-making guide everything we do. Commitment – We invest in long-term partnerships with clients, employers, and one another to ensure shared success. Looking for meaningful work with a team that lives its values? You’ll fit right in at employU. Join our team! A flexible schedule, paid weekly, working in the community, making a difference, being surrounded by a great team, and maintaining work/life balance—this is what you can expect working at employU. Our team works within the disability community to empower our customers with the knowledge, connections, and confidence required to achieve independence by establishing a sustainable career. Because we are always expanding, there is always an opportunity for growth for those seeking career advancement."
Also include video link maybe: "Want to get a glimpse into the employU atmosphere? Watch this video: https://youtu.be/K6Hf9jusJlA". We could keep as a link within paragraph.
We'll output as
... maybe multiple
but we can combine.
Responsibilities: list of essential functions. Need to preserve each bullet as
- . The list is long; we need to copy each sentence starting with a verb. Let's extract:
- Reviews potential Project Search candidates with the committee and conducts interviews using the agreed upon rubric in the selection process.
- Assists with the coordination of hospital tours for incoming interns, parents, and teachers to highlight the program to potential candidates.
- Organizes annual student/parent orientation and graduation sessions with all stakeholders.
- Prepares and conducts employment planning meetings with each intern, parent, supervisor and Project Search Team.
- Leads the Project Search assessments conducted at the beginning of each cohort and submits them for billing in the CRM.
- Ensures all client referrals are in place in regard to: vocational assessments, OJT rotations, and their placement upon completion of the Project SEARCH year.
- Assesses student skills to create an accurate skills profile of the intern and internships that will allow the team to make meaningful matches for each student/intern.
- Works with business liaison, department manager/mentors, instructors, and fellow skills trainers to develop internship sites, write job descriptions, task lists, job analysis and plan for necessary modifications for the internships and competitive jobs.
- Works with manager/mentors and co-workers to educate on disability awareness and training techniques to reinforce employability skills and assists interns to
Requirements
maybe combine education, experience, computer skills, other requirements (background check, transportation, etc). Could also include physical demands? Might be separate but we can include under Requirements or maybe a separate section "Physical Demands". But we only have headings list: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We can map: - Requirements: education, experience, computer skills, other requirements (background check, transportation, etc). Also maybe "Position Qualifications" could be considered Requirements? But we have separate Qualifications heading. The posting has "Position Qualifications" then "Skills & Abilities". So we can map:Qualifications
for Position Qualifications (competency statements list). Actually "Position Qualifications Competency Statement(s) Job Knowledge Training Skills Interpersonal Skills Relationship Building Business Development Communication Problem Solving/Analysis Organizational Skills Detail Oriented Time Management Ability to maintain cooperative working relationships and demonstrates sensitivity and respect for a diverse population." That's a list of competencies.Skills
for Skills & Abilities (Education, Experience, Computer Skills, Other Requirements? Actually Other Requirements maybe separate but could go under Skills? Might be better to put Other Requirements under Requirements. But we already used Requirements for education/experience etc. Let's think. We need to avoid duplication. Let's parse sections: From posting: Description (first paragraph about culture, values, flexible schedule, paid weekly, community impact, growth). Then "Looking for meaningful work..." etc. Then "Our team works within the disability community..." etc. Then "Because we are always expanding..." etc. Then "Full-time employees are offered: ..." list benefits. Then "Part-time employees may be offered: ..." list benefits. Then "Want to get a glimpse..." video link (we should drop as per instruction: remove application instructions? Video link maybe not boilerplate but it's promotional; could be considered part of description? Might keep as part of About the role? It's a link to video; we could keep as part of About the role paragraph? But instruction: remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. Video link is not exactly those; it's optional media. Might keep but could be considered not essential. Safer to drop? The instruction says remove application instructions. Video link is not application instruction. It's just a link to video. Could keep but not required. I'd keep it as part of About the role maybe as a link. Then "Requirements ESSENTIAL FUNCTIONS" heading then list of essential functions. Then "Position Qualifications Competency Statement(s) Job Knowledge Training Skills Interpersonal Skills Relationship Building Business Development Communication Problem Solving/Analysis Organizational Skills Detail Oriented Time Management Ability to maintain cooperative working relationships and demonstrates sensitivity and respect for a diverse population." Then "Skills & Abilities Education: BA Degree ... Experience: Individuals without a BA Degree ... Computer Skills: Proficient with Microsoft Suite ... Other Requirements: Position typically works 8:00 am—4:00 pm, M-F, with occasional weekend work Ability to pass a level 2 background check. Must have reliable transportation, a valid driver’s license, auto registration, auto insurance minimum coverage of bodily injury $50,000 per person/$100,000 per accident. Ideal candidates will have experience and knowledge of the business community as well as providing support to individuals with disabilities. Must be creative, passionate and be successful in job placement. Participates in professional development in the following areas: systematic instruction, learning work skills, training techniques and strategies and other appropriate training. Must have own computer, printer, smartphone with data plan, and high-speed internet connection." Then "PHYSICAL DEMANDS AND WORKING ENVIRONMENT ..." which we could include under Requirements or maybe a separate section but not in allowed headings. Could fold into Requirements or maybe under Skills? Probably under Requirements as "Other Requirements" includes work hours, background check, transportation etc. Physical demands could be part of Requirements as well. We need to include Schedule section: we have flexible schedule, paid weekly, typical hours 8-4 M-F occasional weekend. So we can put that in Schedule. Pay section: not mentioned, so omit. Benefits section: we have full-time and part-time benefits list. Thus sections: About the role: include culture, values, flexible schedule, paid weekly, community impact, growth opportunities, maybe video link. Responsibilities: essential functions list. Requirements: maybe combine education, experience, computer skills, other requirements (background check, transportation, etc), physical demands? But we also have Qualifications and Skills sections. We need to decide mapping to avoid missing content. Let's assign: - About the role: description paragraph(s). - Responsibilities: essential functions. - Qualifications: Position Qualifications competency statements. - Skills: Skills & Abilities (Education, Experience, Computer Skills, Other Requirements? Actually Other Requirements includes work hours, background check, transportation, etc. Could be part of Skills? Might be better to put Other Requirements under Requirements, but we already used Requirements for something else. Let's think: The headings list includes Requirements, Qualifications, Skills. So we can allocate: Requirements: Education, Experience, Computer Skills, Other Requirements (background check, transportation, etc), Physical Demands. Qualifications: Position Qualifications competency statements. Skills: maybe not needed if we put everything else elsewhere. But we have Skills & Abilities heading in posting; we could map that to Skills section. However Skills & Abilities includes Education, Experience, Computer Skills, Other Requirements. That's overlapping with Requirements. To avoid duplication, we could treat Skills & Abilities as Skills section, and Requirements as something else like "Requirements" maybe just the essential functions? But we already used Responsibilities for essential functions. Hmm. Alternative: Use Requirements for the "Requirements" heading that appears before essential functions? Actually the posting says "Requirements ESSENTIAL FUNCTIONS". So the heading "Requirements" is followed by essential functions. So we could map that to Responsibilities (makes sense). Then after that we have "Position Qualifications" then "Skills & Abilities". So we could map: - Responsibilities: essential functions (under Requirements heading). - Qualifications: Position Qualifications. - Skills: Skills & Abilities. - Benefits: benefits. - Schedule: schedule info (flexible schedule, paid weekly, typical hours). - About the role: introductory description. Thus we don't need a separate Requirements section; we already used Responsibilities for the essential functions. The heading "Requirements" in posting is misnamed but we treat as responsibilities. Thus we will not emit a Requirements heading (since we already used Responsibilities). But the instruction says usefor section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). It doesn't say we must use all; we can omit sections lacking content. So we can omit Requirements if we think its content is covered elsewhere. However the posting's "Requirements" heading is actually essential functions; we already used Responsibilities for that. So we can omit Requirements heading. Thus final sections: About the role, Responsibilities, Qualifications, Skills, Benefits, Schedule. Check if we have any content for Pay: none, omit. Now we need to extract content precisely. About the role: combine paragraphs: "At employU, our culture is EPIC. It’s not just a buzzword; it’s how we show up every day for our team and the community we serve. employU Values Statement — EPIC Empowerment – We give every person the tools, support, and confidence to chart their own career path. Passion – Energy and enthusiasm drive us to exceed expectations and change lives. Integrity – Honesty, transparency, and ethical decision-making guide everything we do. Commitment – We invest in long-term partnerships with clients, employers, and one another to ensure shared success. Looking for meaningful work with a team that lives its values? You’ll fit right in at employU. Join our team! A flexible schedule, paid weekly, working in the community, making a difference, being surrounded by a great team, and maintaining work/life balance—this is what you can expect working at employU. Our team works within the disability community to empower our customers with the knowledge, connections, and confidence required to achieve independence by establishing a sustainable career. Because we are always expanding, there is always an opportunity for growth for those seeking career advancement." Also include video link maybe: "Want to get a glimpse into the employU atmosphere? Watch this video: https://youtu.be/K6Hf9jusJlA". We could keep as a link within paragraph. We'll output as
... maybe multiple
but we can combine. Responsibilities: list of essential functions. Need to preserve each bullet as