Jobs · Healthcare · Wisconsin

EMT AEMT Paramedic PART TIME

Lifestar Emergency Medical Services, LLC · West Bend, WI · 1 mo ago
On-siteHealthcarePart-time
We need to output HTML fragment with sections: About the role? The description includes "What is Lifestar hiring for?" and "Who is Lifestar?" and "Why should you apply?" and "Requirements" and "Must Have Skills". Also "Paid in-house training" is a benefit? It's listed under description bullet. Also "Ability to set your own schedule" and "Ability to work at any of our locations". Those could be benefits or schedule. We need sections only if posting has real specific content. We have: - About the role: maybe "What is Lifestar hiring for?" includes part-time EMT, AEMT, Paramedic positions, locations, license requirements, age, 24 hours per month, schedule flexibility, work any location, paid in-house training. That's role description. - About the company: "Who is Lifestar?" includes family owned, founded 1995, service seven communities, small family atmosphere, largest total 911 square mile coverage, responds to approx 5,500 calls, operates at Critical Care Paramedic Level, offers paid in-house trainings, encourages growth, employees respected. - Why should you apply? includes bullet list: Exceptional patient care standards, Family culture, Focus on growth and training, Hire/promote from within first, Employee social events, Community event participation, Standby events. - Requirements: list of license, driver's license, age, under 21 no violations, 19+. - Must Have Skills: list of skills. - Benefits? The posting mentions "Paid in-house training", "Ability to set your own schedule", "Ability to work at any of our locations". Those could be benefits or schedule. There's no explicit Pay or Schedule section besides those. The instruction: include a section ONLY when posting has real specific content for it. So we could have a Benefits section with those items. Or we could incorporate them under About the role or Why should you apply? But they are more like benefits. The instruction says prefer a few substantive sections over many thin ones. We could combine schedule and location flexibility under a "Schedule and Location" section? But they said use headings like About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. So we can use Benefits for paid in-house training, schedule flexibility, location flexibility. Or we could use Schedule for ability to set own schedule. But we have both schedule and location. Could create a Benefits section with those three items. Pay not mentioned, so omit Pay section. Schedule not separate if we put in Benefits. We must not repeat job title as heading. No Job ID. Remove boilerplate. We need to output only HTML fragment, using

for section headings,
  • for lists,

    for prose. We must preserve all substantive information. Let's extract details. From description: "What is Lifestar hiring for? Are you looking for a part time EMT, AEMT, or Paramedic position? We are looking for part time EMTs, AEMTs, and Paramedics at all of our locations. Candidates must have a Wisconsin EMT, AEMT, EMT-P or CCEMT-P license, a valid Wisconsin Driver License with clean driving record, and be 19 years of age or older. Required to work at least 24 hours each month Ability to set your own schedule Ability to work at any of our locations Paid in-house training" So we need to capture: part-time EMT, AEMT, Paramedic positions at all locations; required license; valid WI driver license clean record; age 19+; work at least 24 hours each month; ability to set own schedule; ability to work at any location; paid in-house training. "Who is Lifestar?" paragraph: family owned, private ambulance company founded 1995; expanded to service seven communities in Wisconsin; strive to keep small family-owned atmosphere; one of the largest total 911 square mile coverage areas in WI; responds to approx 5,500 911 and 911-equivalent calls annually; operates at a Critical Care Paramedic Level; offer multitude of paid in-house trainings and encourage employees to grow and learn; employees are respected and appreciated members of our family. "Why should you apply?" bullet list: Exceptional patient care standards; Family culture that appreciates and supports YOU; Focus on your growth and training; We hire and promote from within FIRST; Employee Social events! Cook-outs, picnics, bowling parties, Brewer games; Community Event Participation: Senior Fairs, Community Fund Raisers, Parades and Festivals; Standby Events: Races, Community Sporting Events, County Fairs. "Requirements" list: Current Wisconsin EMT, AEMT, EMT-P or CCEMT-P license; Valid Driver's License with relatively clean driving record; Drivers under 21 years of age must have no violations on their driving record; Must be 19 years of age or older. "Must Have Skills": Exceptional customer service; The ability to communicate easily with patients, family members, nursing staff, and doctors; The drive to grow as a provider; Strong leadership skills with the desire to mentor other providers. We need to decide sections. Potential sections: - About the role (h3) containing description of role: part-time positions, license, driver license, age, 24 hrs/month, schedule flexibility, location flexibility, paid in-house training. - About the company (maybe "About Lifestar" but heading must be from list: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. There's no "About the company". Could use "About the role" for role description, and maybe "Qualifications" for company? But Qualifications is for candidate qualifications. Better to use "About the role" for role description, and maybe "Requirements" for requirements, "Skills" for skills, "Benefits" for benefits (paid training, schedule flexibility, location flexibility). The "Why should you apply?" could be part of Benefits or maybe we could add a section "About the role" includes why apply? But better to have a section "Why should you apply?" but not in allowed headings. The instruction says use

    for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). It says e.g., meaning those are examples, but we should prefer those headings. It doesn't forbid other headings, but says use those for section headings. Likely they want us to use those specific headings only. So we must map content to those headings. Thus we need to decide which of those headings we have content for. - About the role: we have role description. - Responsibilities: we could list duties? Not explicitly given. The posting doesn't list specific duties like "respond to emergencies", "provide patient care". It mentions "Exceptional patient care standards" but that's more of a benefit. Could treat as responsibilities? Might be thin. Better to omit Responsibilities if no specific content. - Requirements: we have explicit Requirements list. - Qualifications: could overlap with Requirements; but we have Must Have Skills separate. Qualifications could be license, driver license, age, etc. But we already have Requirements for those. Qualifications could be something like "Current Wisconsin EMT license" etc. But to avoid duplication, we could put license etc under Requirements, and maybe Qualifications for "Ability to set own schedule"? Not sure. - Skills: we have Must Have Skills list. - Benefits: we have paid in-house training, ability to set own schedule, ability to work at any location. Also maybe employee social events, community participation, standby events? Those are more "Why should you apply?" but could be benefits. However they are more like perks. Could include them under Benefits as well. - Pay: not specified, omit. - Schedule: we have ability to set own schedule, but we already put schedule flexibility in Benefits. Could also make a Schedule section with that detail. But we should avoid thin sections. If we put schedule in Benefits, we might not need separate Schedule. Thus we could have sections: About the role, Requirements, Skills, Benefits. Possibly also Qualifications if we want to separate license etc from Requirements? But Requirements already covers license, driver license, age, under 21 no violations, 24 hrs/month. That's basically qualifications. So we can keep Requirements and maybe not need Qualifications. But we must preserve all substantive information. If we put license etc under Requirements, that's fine. The "Must Have Skills" goes under Skills. The "Why should you apply?" items (employee social events, community participation, standby events) could go under Benefits as well. Also "Exceptional patient care standards" maybe under Benefits or About the role? It's a standard they uphold; could be part of About the role (they emphasize exceptional patient care). But we can include it under Benefits as a perk? It's more of a standard. Might be okay to put under Benefits as "Exceptional patient care standards". However the instruction: prefer a few substantive sections over many thin ones. So we could combine many items into Benefits. Let's craft:

    About the role

    We are looking for part‑time EMTs, AEMTs, and Paramedics at all of our locations. Candidates must hold a Wisconsin EMT, AEMT, EMT‑P or CCEMT‑P license, have a valid Wisconsin driver’s license with a clean driving record, and be 19 years of age or older. The position requires a minimum of 24 hours of work each month, offers the ability to set your own schedule, to work at any of our locations, and includes paid in‑house training.

    That captures role description.

    Requirements

    • Current Wisconsin EMT, AEMT, EMT‑P or CCEMT‑P license
    • Valid Driver's License with a relatively clean driving record
    • Drivers under 21 years of age must have no violations on their driving record
    • Must be 19 years of age or older

    Skills

    • Exceptional customer service
    • The ability to communicate easily with patients, family members, nursing staff, and doctors
    • The drive to grow as a provider
    • Strong leadership skills with the desire to mentor other providers

    Benefits

    • Paid in‑house training
    • Ability to set your own schedule
    • Ability to work at any of our locations
    • Exceptional patient care standards
    • Family‑focused culture that appreciates and supports you
    • Focus on your growth and training; hire and promote from within first
    • Employee social events (cook‑outs, picnics, bowling parties, Brewer games)
    • Community event participation (Senior Fairs, fundraisers, parades, festivals)
    • Standby event coverage (races, community sporting events, county fairs)
    We have preserved all info: company description? We missed the "Who is Lifestar?" details: founded 1995, family owned, seven communities, small family atmosphere, largest 911 sq mile coverage, 5,500 calls annually, Critical Care Paramedic Level, paid in-house trainings (already in benefits), encourage growth, employees respected. Some of those are covered partially but we lost some specifics: founded 1995, seven communities, small family atmosphere, largest coverage area, 5,500 calls, Critical Care Paramedic Level. We need to preserve those. Where to put them? Could be under About the role? Or maybe a separate section "About the company" but not allowed heading. Could we put them under Benefits? They are not benefits exactly. Could we create a section "About the role" and include company info there? The About the role section currently focuses

Similar jobs