Jobs · OTHR · Pennsylvania

Walk In Tuesday for Nursing and Dining Services

Masonic Villages of Pennsylvania · Elizabethtown, PA · 1 mo ago
OTHRFull-time
We need to output HTML fragment with sections: About the role? Actually the posting is about an onsite hiring event. We need to follow rules: use

for section headings (e.g., About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). Use
  • for any list of duties/requirements/benefits, and

    for prose. Do NOT repeat the job title as a heading (the page already shows it) and do NOT put Job ID / requisition numbers as headings — fold minor metadata into a short

    or drop it. Preserve ALL substantive information; do NOT invent or summarize away detail. Remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. IMPORTANT: include a section ONLY when the posting has real, specific content for it — never emit a heading followed by filler/placeholder text (e.g., "commensurate with experience", "not specified", "N/A", "varies", "TBD") and never create Pay/Schedule/Benefits sections unless the posting actually states them. Prefer a few substantive sections over many thin ones. Output ONLY the HTML fragment — no /, no markdown code fences. We need to decide what sections to include. The posting includes: event details (date, time, location), description of event, positions available (list), how to attend. There's no explicit responsibilities, requirements, qualifications, skills, benefits, pay, schedule (though schedule info is present for positions: e.g., shifts). But we should not create a Schedule section unless posting actually states them. The posting does state shift times for each position (e.g., "All shifts", "Part Time Day, Full Time Evenings and Part Time Evenings", etc.). That could be considered schedule information. However the rule says: never create Pay/Schedule/Benefits sections unless the posting actually states them. It does state schedule details for positions, but not overall job schedule. Might be okay to include a Schedule section with the shift details? But the instruction says "Prefer a few substantive sections over many thin ones." Could combine positions list under a section like "Positions Available". However the allowed headings are limited to those examples: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. It says use

    for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). It doesn't say we cannot use other headings, but likely they expect those headings. However we can also create other headings if needed? The instruction: "use

    for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." This suggests those are examples; we can use those headings when appropriate. If we don't have content for those, we should not create them. So we need to decide which sections we have substantive content for. We have event details: date, time, location, description. That could be "About the role"? Not exactly a role, but maybe "About the event". But the allowed headings include "About the role". Could we use "About the role" to describe the event? Might be stretching. Better to not create a heading if not matching. However we need to output something. Perhaps we can output just a

    with event details, then a

    for "Positions Available" (though not in list). But the instruction says use

    for section headings (e.g., About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). It doesn't forbid other headings, but suggests those are typical. Safer to stick to those headings only when we have content. We have schedule info for each position: could be placed under a Schedule section. But the schedule is varied per position; we could list them. That seems substantive. We have no explicit pay or benefits. So we should not create Pay or Benefits sections. We have no explicit responsibilities, requirements, qualifications, skills. So we should not create those. Thus we could have a single section: Schedule (with shift details). And maybe also a section: About the role (event description). But "About the role" might be okay to describe the event/hiring event. The posting includes description: "Masonic Village at Elizabethtown is hosting an onsite hiring event with open interviews for multiple positions in Nursing and Dining Services." That's about the event. Could be considered "About the role"? Not ideal but maybe acceptable. Alternatively we could output just a

    for event details and a

      for positions, without any headings. But the instruction says use

      for section headings (e.g., About the role, Responsibilities...). It doesn't say we must use headings, but if we have sections we should use

      . If we don't have sections, we can just output paragraphs and lists. However the instruction: "Use

      for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." This implies if we have a section heading, we should use

      . It doesn't require us to have headings. So we could output just a

      for event info, then a

        for positions, then maybe a

        for how to attend. That would be valid. But we need to preserve ALL substantive information. Let's extract: - Event: Onsite Hiring Event - Nursing and Dining Services Masonic Village at Elizabethtown - Date: Tuesday, September 22, 2026 - Time: 1:00 pm to 5:00 pm - Location: The Masonic Conference Center - Patton Campus 1244 Bainbridge Road Elizabethtown, PA 17022 - Additional note: Masonic Village at Elizabethtown is ideally located with just a 20 - 30 minute drive to Harrisburg and Lancaster - Join Our Team - Immediate Openings Available! - Masonic Village at Elizabethtown is hosting an onsite hiring event with open interviews for multiple positions in Nursing and Dining Services. - Walk-ins are welcome -bring a friend! - Positions Available - Nursing: - Nursing Assistant - CNA (Full Time, Part Time, PRN - All shifts!) - Licensed Practical Nurse - LPN (Part Time Day, Full Time Evenings and Part Time Evenings) - Registered Nurse - RN (Full Time Evenings and Full Time Nights) - Positions Available - Dining Services: - Busperson (Part Time Evenings) - Cook (Full Time Days/Evenings) - Cook's Helper (Part Time Days/Evenings) - Dining Attendant (Full Time Days and Part Time Evenings) - Kitchen Utility Worker/Dishwasher (Part Time Days/Evenings) - Server (Part Time Days or Part Time Evenings) - How To Attend: Simply come to the event during the scheduled time with your resume. No appointment necessary! - We are proud to be an equal opportunity employer. (EEO boilerplate - should be removed) We need to remove EEO/equal-opportunity boilerplate. So drop that line. Also remove duplicated lines? Not seeing duplicates. We should not include application instructions? The "How To Attend" is basically application instructions. The instruction says: "Remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions." So we should remove the "How To Attend" lines as they are application instructions. However we need to preserve ALL substantive information; but application instructions are to be removed. So we can drop that. Thus we keep event details, description, positions list, location note about drive to Harrisburg/Lancaster. We also have "Join Our Team - Immediate Openings Available!" which is substantive. We need to format with

        for prose,

        • for lists. We could structure:

          Onsite Hiring Event - Nursing and Dining Services Masonic Village at Elizabethtown

          Date: Tuesday, September 22, 2026

          Time: 1:00 pm to 5:00 pm

          Location: The Masonic Conference Center - Patton Campus 1244 Bainbridge Road Elizabethtown, PA 17022

          Masonic Village at Elizabethtown is ideally located with just a 20 - 30 minute drive to Harrisburg and Lancaster.

          Join Our Team - Immediate Openings Available! Masonic Village at Elizabethtown is hosting an onsite hiring event with open interviews for multiple positions in Nursing and Dining Services. Walk-ins are welcome - bring a friend!

          Positions Available

          • Nursing Assistant - CNA (Full Time, Part Time, PRN - All shifts!)
          • Licensed Practical Nurse - LPN (Part Time Day, Full Time Evenings and Part Time Evenings)
          • Registered Nurse - RN (Full Time Evenings and Full Time Nights)
          • Busperson (Part Time Evenings)
          • Cook (Full Time Days/Evenings)
          • Cook's Helper (Part Time Days/Evenings)
          • Dining Attendant (Full Time Days and Part Time Evenings)
          • Kitchen Utility Worker/Dishwasher (Part Time Days/Evenings)
          • Server (Part Time Days or Part Time Evenings)
          But we used a heading "Positions Available" which is not in the examples. Is that allowed? The instruction says use

          for section headings (e.g., About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). It doesn't explicitly forbid other headings, but suggests those are typical. However to be safe, we could avoid any heading and just output paragraphs and list. But then we lose semantic grouping. However 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 headings, but if we have a section heading we should use

          . If we don't want to risk using a non-standard heading, we could omit headings entirely. Then we just have paragraphs and a list. That would still be valid HTML fragment. But we need to preserve ALL substantive information. The list is substantive. We can put a

          introducing the list: "Positions Available:" then

            . That would be fine. Thus final HTML:

            Onsite Hiring Event - Nursing and Dining Services Masonic Village at Elizabethtown

            Date: Tuesday, September 22, 2026

            Time: 1:00 pm to 5:00 pm

            Location: The Masonic Conference Center - Patton Campus 1244 Bainbridge Road Elizabethtown, PA 17022

            Masonic Village at Elizabethtown is ideally located with just a 20 - 30 minute drive to Harrisburg and Lancaster.

            Join Our Team - Immediate Openings Available! Masonic Village at Elizabethtown is hosting an onsite hiring event with open interviews for multiple positions in Nursing and Dining Services. Walk-ins are welcome - bring a friend!

            Positions Available:

            • Nursing Assistant - CNA (Full Time, Part Time, PRN - All shifts!)
            • Licensed Practical Nurse - LPN (Part Time Day, Full Time Evenings and Part Time Evenings)
            • Registered Nurse - RN (Full Time

Similar jobs

Walk-In Wednesday

Centennial School DistrictWarminster, PA· 2 mo ago
OTHRapply on applitrack.com

Walk In Clinic Nurse

Outer Cape Health ServicesProvincetown, MA· 1 mo ago
Healthcareapply on paycomonline.net

Tuesdays

Office Pride of Cedar RapidsCedar Rapids, IA· 2 wk ago
OTHR$15/hrapply on office-pride-of-cedar-rapids.careerplug.com