Driver

We need to output HTML fragment with sections: Use

for 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 extract content. Given posting: Employment Type: Part time Shift: (blank? maybe not provided) Description: Position Purpose: Ensure safe and prompt transportation for PACE participants, including meal delivery and essential supplies. Maintain vehicle cleanliness and safety while promptly reporting any issues to the department leader. What You'll Do: Safely transport PACE participants, prioritizing their comfort and satisfaction. Adhere to schedules, adjusting for unforeseen changes and participant needs. Operate vehicles in compliance with regulations and safety standards. Provide physical assistance to participants as needed during boarding and disembarking. Handle biohazard materials with proper precautions. Maintain vehicle cleanliness and equipment functionality. Minimum Qualifications: High school diploma or equivalent; Associate's degree preferred. Valid driver's license with a clean record; CDL with passenger endorsement for larger vehicles. Minimum one year of experience with elderly or frail populations preferred. Position Highlights and Benefits: Comprehensive benefits including medical, dental, vision, and paid time off from day one. Access to Daily Pay for earned wages. Incentives available through Employee Referral program. Supportive, patient-centered environment. Extensive orientation and ongoing professional development opportunities. Ministry/Facility Information: Trinity Health PACE programs offer continuous, quality care for the elderly, enabling independent living at home. Seniors receive comprehensive care from interdisciplinary teams, fostering health improvement and community relationships. Guided by Gospel values, we serve with compassion and integrity, transforming lives within our communities. Our Commitment Rooted in our Mission and Core Values, we honor the dignity of every person and recognize the unique perspectives, experiences, and talents each colleague brings. By finding common ground and embracing our differences, we grow stronger together and deliver more compassionate, person-centered care. We are an Equal Opportunity Employer. All qualified applicants will receive consideration for employment without regard to race, color, religion, sex, sexual orientation, gender identity, national origin, disability, veteran status, or any other status protected by federal, state, or local law. We need to remove boilerplate: EEO, equal-opportunity, scam-warning, etc. Also remove duplicated lines. Remove "Ministry/Facility Information" maybe not needed? It's not a standard heading but could be considered "About the role" or "About the organization". The instruction: Use headings for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). So we need to map content to these headings. We have: - Position Purpose and What You'll Do => Responsibilities (or About the role?). "About the role" could be a brief description. But we have "Position Purpose" and "What You'll Do". That's responsibilities. So we can put under

Responsibilities

with

• items. - Minimum Qualifications => Requirements or Qualifications. We have "Minimum Qualifications". Could be Requirements. We'll use

  Requirements

  (or Qualifications). The instruction list includes both Requirements and Qualifications. We need to decide. Since we have "Minimum Qualifications", we could use

  Qualifications

  . But also we have no separate "Requirements". We'll choose Qualifications. - Position Highlights and Benefits => Benefits. So

  Benefits

  with list. - Pay: Not explicitly stated except "Access to Daily Pay for earned wages." That's a pay-related benefit but not a specific pay rate. The instruction says: never create Pay/Schedule/Benefits sections unless the posting actually states them. It says "Access to Daily Pay for earned wages." That is a pay feature. Should we include a Pay section? It mentions pay but not a rate. The instruction says: never create Pay/Schedule/Benefits sections unless the posting actually states them. It does state something about pay (Access to Daily Pay). So we could include a Pay section with that detail. However they also said: Prefer a few substantive sections over many thin ones. Could combine Pay into Benefits? But Benefits already includes benefits; pay is separate. The instruction list includes Benefits as a possible heading. It says "never create Pay/Schedule/Benefits sections unless the posting actually states them." So we can create Pay section if there is pay info. There is "Access to Daily Pay for earned wages." That's a pay feature. So we can include Pay section with that line. - Schedule: Not given. Shift: blank. So we should not create Schedule section. - Skills: Not explicitly listed. Could infer from responsibilities but not explicit. So we should not create Skills section unless there is explicit content. Not present. - About the role: Could be the Position Purpose summary. But we already used Responsibilities for that. Could we also have About the role with a brief paragraph? The instruction: Use

  for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). It doesn't forbid using both About the role and Responsibilities. But we should avoid thin sections. We have Position Purpose and What You'll Do; that is substantive. Could be placed under About the role as a paragraph, and Responsibilities as a list? But the content is similar. Better to have one section: Responsibilities (or About the role). Which heading is more appropriate? The content is about what you'll do, so Responsibilities fits. We'll use Responsibilities. Thus sections: Responsibilities, Qualifications, Benefits, Pay. We need to output HTML fragment only, no /. Use

  for each heading, then content:

  for prose,

  • for lists. We need to preserve ALL substantive information; do not invent or summarize away detail. So we need to include all details from the posting, but we can format as lists. Let's extract details: Responsibilities (from Position Purpose and What You'll Do): - Ensure safe and prompt transportation for PACE participants, including meal delivery and essential supplies. - Maintain vehicle cleanliness and safety while promptly reporting any issues to the department leader. - Safely transport PACE participants, prioritizing their comfort and satisfaction. - Adhere to schedules, adjusting for unforeseen changes and participant needs. - Operate vehicles in compliance with regulations and safety standards. - Provide physical assistance to participants as needed during boarding and disembarking. - Handle biohazard materials with proper precautions. - Maintain vehicle cleanliness and equipment functionality. Note: Some duplicates: "Maintain vehicle cleanliness and safety" appears in Position Purpose and also later "Maintain vehicle cleanliness and equipment functionality." We should keep both but avoid duplicate lines? The instruction: Remove duplicated lines. So we need to deduplicate identical lines. The two lines are not identical: one says "Maintain vehicle cleanliness and safety while promptly reporting any issues to the department leader." The other says "Maintain vehicle cleanliness and equipment functionality." They are different. Keep both. Qualifications (Minimum Qualifications): - High school diploma or equivalent. - Associate's degree preferred. - Valid driver's license with a clean record. - CDL with passenger endorsement for larger vehicles. - Minimum one year of experience with elderly or frail populations preferred. Benefits (Position Highlights and Benefits): - Comprehensive benefits including medical, dental, vision, and paid time off from day one. - Access to Daily Pay for earned wages. - Incentives available through Employee Referral program. - Supportive, patient-centered environment. - Extensive orientation and ongoing professional development opportunities. Pay: We have "Access to Daily Pay for earned wages." Already listed under Benefits. But we might move it to Pay section to avoid duplication? The instruction says preserve ALL substantive information; we can include it in both sections? That would duplicate. Better to not duplicate. Since Pay section is separate, we could put that line there and not duplicate in Benefits. However Benefits also includes other benefits. The line about Daily Pay is a pay feature; we could keep it under Pay and not repeat in Benefits. But the Benefits section originally includes that line; we need to preserve all info, but we can relocate it. The instruction: "Prefer a few substantive sections over many thin ones." Having both Benefits and Pay might be thin if Pay only has one line. But we have to include Pay if posting states it. It does state "Access to Daily Pay for earned wages." So we need a Pay section. We could keep Benefits without that line, but then we lose that info from Benefits section. However we still have it in Pay section, so info is preserved overall. That's acceptable. Thus Benefits list will exclude the Daily Pay line. Benefits: - Comprehensive benefits including medical, dental, vision, and paid time off from day one. - Incentives available through Employee Referral program. - Supportive, patient-centered environment. - Extensive orientation and ongoing professional development opportunities. Pay: - Access to Daily Pay for earned wages. Now we need to ensure we didn't include boilerplate: Remove EEO etc. Also remove "Ministry/Facility Information" and "Our Commitment" etc. That's boilerplate? It's descriptive of organization but not a standard heading; could be considered "About the role" but we already have Responsibilities. The instruction: Remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. The Ministry/Facility Information and Our Commitment are not exactly legal boilerplate but could be considered organizational description. However they are not explicitly listed as headings we should use. We could incorporate them under About the role? But we already used Responsibilities. The instruction says we should only include sections when posting has real, specific content for it. The Ministry/Facility Information is specific content about the organization. Could be placed under About the role. But we have no About the role section yet. We could add About the role with that description. However we must avoid thin sections. The Ministry/Facility Information paragraph is substantive. So we could add an About the role section with that paragraph. Then we would have sections: About the role, Responsibilities, Qualifications, Benefits, Pay. That's five sections. Might be okay. But we need to check if we are duplicating content: The About the role would contain the Ministry/Facility Information and maybe also the Position Purpose? But we already used Position Purpose in Responsibilities. To avoid duplication, we could put the organization description in About the role, and keep Responsibilities as the list of duties. That seems reasonable. Thus: About the role:

    Trinity Health PACE programs offer continuous, quality care for the elderly, enabling independent living at home. Seniors receive comprehensive care from interdisciplinary teams, fostering health improvement and community relationships. Guided by Gospel values, we serve with compassion and integrity, transforming lives within our communities. Our Commitment Rooted in our Mission and Core Values, we honor the dignity of every person and recognize the unique perspectives, experiences, and talents each colleague brings. By finding common ground and embracing our differences, we grow stronger together and deliver more compassionate, person-centered care.

    We need to ensure we removed the EEO line at the end: "We are an Equal Opportunity Employer..." That's boilerplate; remove. Now Responsibilities: list as above. Qualifications: list. Benefits: list (excluding Daily Pay). Pay: list with Daily Pay. Check for any other info: Employment Type: Part time, Shift: (blank). Not included as heading; could be folded into a short

    or dropped. The instruction: do NOT put Job ID / requisition numbers as headings — fold minor metadata into a short

    or drop it. Employment Type and Shift are minor metadata. We could include a short paragraph at the top maybe under a heading? But we shouldn't create a heading for them. Could add a

    before sections: "Employment Type: Part time." But the instruction says fold minor metadata into a short

    or drop it. So we can include a

    at