Lobby Receptionist, Security, Full Time, Day
Valley Health System · Paramus, NJ · 1 mo ago
Administrative$18.82–$23.53/hrFull-time
We need to output HTML fragment with sections: About the role? The posting has "Position Summary". That could be considered About the role. Use for section headings. Use
for section headings. Use - for any list of duties/requirements/benefits. Use
for prose.
We need to preserve all substantive info, remove boilerplate (EEO, etc). Also remove navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. So we should drop the EEO statement.
We need sections only when posting has real specific content. We have:
- Position Summary (summary)
- Education
- Experience
- Skills
- Job Location (maybe not a heading? Could be part of About the role? But we can treat as a separate section maybe "Job Location". However the instruction says use headings for section headings like About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. It doesn't list Job Location as a heading. So we should not create a heading for Job Location unless it's one of those. Probably we should embed location in a paragraph under About the role or maybe not create a heading. Since they said "Use
for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." So we can use those headings if content exists. Job Location is not listed, so we should not create a heading for it; we can include location in a paragraph under About the role or maybe just in a
without heading.
Similarly "Shift Day" maybe part of schedule? There's schedule info: "Shift Day". That's schedule. So we can create a Schedule section with that content.
Benefits: there is a list of benefits. So we create Benefits section with
- .
Pay: there is Pay Range: $18.82 - $23.53 per hour. So we create Pay section.
Responsibilities: The Position Summary includes duties: greet, direct, provide helpful information. That's responsibilities. Could be under Responsibilities heading. But we also have Position Summary. The instruction says use headings like About the role, Responsibilities, etc. We could choose either About the role or Responsibilities. Since we have a Position Summary, we could treat that as About the role. Or we could treat as Responsibilities. The summary is about greeting etc. I'd choose About the role for the summary paragraph. Then we could also have Responsibilities if there are more detailed duties, but not needed. We'll keep About the role.
Education: we can put under Qualifications or Requirements? Education is a qualification. Could be under Qualifications. But we have a heading "Qualifications". We'll put Education under Qualifications.
Experience: also under Qualifications or Requirements. We'll put under Qualifications as well.
Skills: we have Skills heading.
Thus sections: About the role (position summary), Qualifications (education + experience), Skills, Benefits, Pay, Schedule.
We need to ensure we don't create sections with filler like "commensurate with experience". Not present.
We need to preserve all substantive info: include the exact text for each.
Let's extract:
Position Summary: "To greet, direct, and provide helpful information to patients, visitors, physicians, and employees."
Education: "High school diploma or equivalent is required."
Experience: "Computer experience preferred."
Skills: list:
- Ability to read, write, and speak clear and fluent English.
- Ability to communicate effectively (orally and in writing) and interact with patients, family members, visitors, physicians, sales representatives, and members of the general public.
- Ability to handle frequent interruptions, adapt to changes in workload and work schedule, and remain composed during interruptions and changes.
- Ability to set priorities and solve problems.
- Ability to respond quickly to emergency requests.
Job Location: "The Valley Hospital-Paramus" (maybe also "Shift Day (United States of America)"? Actually "Job Location The Valley Hospital-Paramus Shift Day (United States of America)". So location includes shift day? Might be two separate lines: Job Location The Valley Hospital-Paramus Shift Day (United States of America). We'll treat location as "The Valley Hospital-Paramus" and schedule as "Shift Day". The "(United States of America)" maybe redundant. We'll include location in About the role paragraph? Or we can add a short p: "Location: The Valley Hospital-Paramus." But we shouldn't create a heading for location. We'll just include in a paragraph after About the role maybe.
Benefits list: need to parse:
"Medical/Prescription, Dental & Vision Discount Program (Full Time/Part Time Employees)Group Term Life Insurance and AD&D(Full Time Employees)Flexible Spending Accounts and Commuter Benefit PlansSupplemental Voluntary Benefits ( e.g. Short-term and Long-term Disability, Whole Life Insurance, Legal Support, etc.)6 Paid Holidays, Paid Time Off (varies), Wellness Time Off, Extended IllnessRetirement PlanTuition Assistance Employee Assistance Program (EAP)Valley Health LifeStyles Fitness Center Membership DiscountDay Care Discounts for Various Daycare Facilities"
This is a bit messy due to missing spaces. We need to preserve all substantive information; we should not invent or summarize away detail. We need to output as list items preserving the text as given, but we can add spaces for readability? The instruction: "Preserve ALL substantive information; do NOT invent or summarize away detail." It doesn't forbid minor formatting adjustments like adding spaces for readability, but we should be careful not to change meaning. The original text seems to have missing spaces between items due to OCR. We could try to insert spaces where logically needed, but that might be considered inventing detail. Safer to keep the exact string as given, but it's hard to read. However we can split into list items based on apparent delimiters: maybe each benefit separated by a capital letter after a closing parenthesis? But that's risky.
Better to keep the benefits as a single paragraph? But the instruction says use
- for any list of duties/requirements/benefits. So we need to make a list. We could keep each benefit as a list item, but we need to separate them correctly. Let's try to parse:
Original: "Medical/Prescription, Dental & Vision Discount Program (Full Time/Part Time Employees)Group Term Life Insurance and AD&D(Full Time Employees)Flexible Spending Accounts and Commuter Benefit PlansSupplemental Voluntary Benefits ( e.g. Short-term and Long-term Disability, Whole Life Insurance, Legal Support, etc.)6 Paid Holidays, Paid Time Off (varies), Wellness Time Off, Extended IllnessRetirement PlanTuition Assistance Employee Assistance Program (EAP)Valley Health LifeStyles Fitness Center Membership DiscountDay Care Discounts for Various Daycare Facilities"
We can see patterns: after each benefit there is a parenthesis with eligibility, then next benefit starts with a capital letter (Group, Flexible, Supplemental, 6, Retirement, Tuition, Valley, Day). The "6 Paid Holidays" starts with a number.
Thus we can split before each capital letter that follows a closing parenthesis or before a number at start? But we risk mis-splitting inside parentheses like "( e.g. Short-term and Long-term Disability, Whole Life Insurance, Legal Support, etc.)" includes lower-case after e.g. but that's inside parentheses.
Simplify: We could keep the benefits as a single
but that violates instruction to use
- for any list. However maybe we can treat the whole benefits string as a single list item? That would be a list with one item, which is still a list. But the instruction says "Use
- for any list of duties/requirements/benefits". If we have a list, we should use
- . If we have a single block, we could still use
- with one item. That satisfies.
Thus we can output:
- Medical/Prescription, Dental & Vision Discount Program (Full Time/Part Time Employees)Group Term Life Insurance and AD&D(Full Time Employees)Flexible Spending Accounts and Commuter Benefit PlansSupplemental Voluntary Benefits ( e.g. Short-term and Long-term Disability, Whole Life Insurance, Legal Support, etc.)6 Paid Holidays, Paid Time Off (varies), Wellness Time Off, Extended IllnessRetirement PlanTuition Assistance Employee Assistance Program (EAP)Valley Health LifeStyles Fitness Center Membership DiscountDay Care Discounts for Various Daycare Facilities
That preserves all info.
Similarly for Skills we have multiple sentences; we can make a list.
Education and Experience could be list items under Qualifications.
Pay: we have "Pay Range: $18.82 - $23.53 (per hour)". Also there is a paragraph about salary: "Joining Valley Health System means becoming part of a dedicated team that values the highest quality of care in a supportive environment. In our commitment to high performance and reliability, we encourage and recognize exceptional individual performance through our industry leading compensation practices including a starting salary and benefits in accordance with your role, experience, education, and licensure. Actual individual salaries vary depending on these factors. The salary listed does not include other forms of compensation or benefits." That's prose about pay. We should preserve that as well. So Pay section could have a with that prose, then a
- for the range? Or we could just put the range in a
. The instruction: use
- for any list of duties/requirements/benefits. Pay is not a list, it's a range. So we can use
.
Schedule: we have "Shift Day". Also maybe "Shift Day (United States of America)"? Actually the location line includes shift day. We'll treat schedule as "Shift Day". We'll put in
.
Now About the role: we have Position Summary sentence. Could also include location? We'll keep location separate maybe as a
after About the role.
Let's craft HTML:
About the role
To greet, direct, and provide helpful information to patients, visitors, physicians, and employees.
Location: The Valley Hospital-Paramus.
Qualifications
- High school diploma or equivalent is required.
- Computer experience preferred.
Skills
- Ability to read, write, and speak clear and fluent English.
- Ability to communicate effectively (orally and in writing) and interact with patients, family members, visitors, physicians, sales representatives, and members of the general public.
- Ability to handle frequent interruptions, adapt to changes in workload and work schedule, and remain composed during interruptions and changes.
- Ability to set priorities and solve problems.
- Ability to respond quickly to emergency requests.
Benefits
- Medical/Prescription, Dental & Vision Discount Program (Full Time/Part Time Employees)Group Term Life Insurance and AD&D(Full Time Employees)Flexible Spending Accounts and Commuter Benefit PlansSupplemental Voluntary Benefits ( e.g. Short-term and Long-term Disability, Whole Life Insurance, Legal Support, etc.)6 Paid Holidays, Paid Time Off (varies), Wellness Time Off, Extended IllnessRetirement PlanTuition Assistance Employee Assistance Program (EAP)Valley Health LifeStyles Fitness Center Membership DiscountDay Care Discounts for Various Daycare Facilities
Pay
Joining Valley Health System means becoming part of a dedicated team that values the highest quality of care in a supportive environment. In our commitment to high performance and reliability, we encourage and recognize exceptional individual performance through our industry leading compensation practices including a starting salary and benefits in accordance with your role, experience,
for prose. We need to preserve all substantive info, remove boilerplate (EEO, etc). Also remove navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. So we should drop the EEO statement. We need sections only when posting has real specific content. We have: - Position Summary (summary) - Education - Experience - Skills - Job Location (maybe not a heading? Could be part of About the role? But we can treat as a separate section maybe "Job Location". However the instruction says use headings for section headings like About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. It doesn't list Job Location as a heading. So we should not create a heading for Job Location unless it's one of those. Probably we should embed location in a paragraph under About the role or maybe not create a heading. Since they said "Use
for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." So we can use those headings if content exists. Job Location is not listed, so we should not create a heading for it; we can include location in a paragraph under About the role or maybe just in a
without heading. Similarly "Shift Day" maybe part of schedule? There's schedule info: "Shift Day". That's schedule. So we can create a Schedule section with that content. Benefits: there is a list of benefits. So we create Benefits section with
- .
Pay: there is Pay Range: $18.82 - $23.53 per hour. So we create Pay section.
Responsibilities: The Position Summary includes duties: greet, direct, provide helpful information. That's responsibilities. Could be under Responsibilities heading. But we also have Position Summary. The instruction says use headings like About the role, Responsibilities, etc. We could choose either About the role or Responsibilities. Since we have a Position Summary, we could treat that as About the role. Or we could treat as Responsibilities. The summary is about greeting etc. I'd choose About the role for the summary paragraph. Then we could also have Responsibilities if there are more detailed duties, but not needed. We'll keep About the role.
Education: we can put under Qualifications or Requirements? Education is a qualification. Could be under Qualifications. But we have a heading "Qualifications". We'll put Education under Qualifications.
Experience: also under Qualifications or Requirements. We'll put under Qualifications as well.
Skills: we have Skills heading.
Thus sections: About the role (position summary), Qualifications (education + experience), Skills, Benefits, Pay, Schedule.
We need to ensure we don't create sections with filler like "commensurate with experience". Not present.
We need to preserve all substantive info: include the exact text for each.
Let's extract:
Position Summary: "To greet, direct, and provide helpful information to patients, visitors, physicians, and employees."
Education: "High school diploma or equivalent is required."
Experience: "Computer experience preferred."
Skills: list:
- Ability to read, write, and speak clear and fluent English.
- Ability to communicate effectively (orally and in writing) and interact with patients, family members, visitors, physicians, sales representatives, and members of the general public.
- Ability to handle frequent interruptions, adapt to changes in workload and work schedule, and remain composed during interruptions and changes.
- Ability to set priorities and solve problems.
- Ability to respond quickly to emergency requests.
Job Location: "The Valley Hospital-Paramus" (maybe also "Shift Day (United States of America)"? Actually "Job Location The Valley Hospital-Paramus Shift Day (United States of America)". So location includes shift day? Might be two separate lines: Job Location The Valley Hospital-Paramus Shift Day (United States of America). We'll treat location as "The Valley Hospital-Paramus" and schedule as "Shift Day". The "(United States of America)" maybe redundant. We'll include location in About the role paragraph? Or we can add a short p: "Location: The Valley Hospital-Paramus." But we shouldn't create a heading for location. We'll just include in a paragraph after About the role maybe.
Benefits list: need to parse:
"Medical/Prescription, Dental & Vision Discount Program (Full Time/Part Time Employees)Group Term Life Insurance and AD&D(Full Time Employees)Flexible Spending Accounts and Commuter Benefit PlansSupplemental Voluntary Benefits ( e.g. Short-term and Long-term Disability, Whole Life Insurance, Legal Support, etc.)6 Paid Holidays, Paid Time Off (varies), Wellness Time Off, Extended IllnessRetirement PlanTuition Assistance Employee Assistance Program (EAP)Valley Health LifeStyles Fitness Center Membership DiscountDay Care Discounts for Various Daycare Facilities"
This is a bit messy due to missing spaces. We need to preserve all substantive information; we should not invent or summarize away detail. We need to output as list items preserving the text as given, but we can add spaces for readability? The instruction: "Preserve ALL substantive information; do NOT invent or summarize away detail." It doesn't forbid minor formatting adjustments like adding spaces for readability, but we should be careful not to change meaning. The original text seems to have missing spaces between items due to OCR. We could try to insert spaces where logically needed, but that might be considered inventing detail. Safer to keep the exact string as given, but it's hard to read. However we can split into list items based on apparent delimiters: maybe each benefit separated by a capital letter after a closing parenthesis? But that's risky.
Better to keep the benefits as a single paragraph? But the instruction says use
- for any list of duties/requirements/benefits. So we need to make a list. We could keep each benefit as a list item, but we need to separate them correctly. Let's try to parse:
Original: "Medical/Prescription, Dental & Vision Discount Program (Full Time/Part Time Employees)Group Term Life Insurance and AD&D(Full Time Employees)Flexible Spending Accounts and Commuter Benefit PlansSupplemental Voluntary Benefits ( e.g. Short-term and Long-term Disability, Whole Life Insurance, Legal Support, etc.)6 Paid Holidays, Paid Time Off (varies), Wellness Time Off, Extended IllnessRetirement PlanTuition Assistance Employee Assistance Program (EAP)Valley Health LifeStyles Fitness Center Membership DiscountDay Care Discounts for Various Daycare Facilities"
We can see patterns: after each benefit there is a parenthesis with eligibility, then next benefit starts with a capital letter (Group, Flexible, Supplemental, 6, Retirement, Tuition, Valley, Day). The "6 Paid Holidays" starts with a number.
Thus we can split before each capital letter that follows a closing parenthesis or before a number at start? But we risk mis-splitting inside parentheses like "( e.g. Short-term and Long-term Disability, Whole Life Insurance, Legal Support, etc.)" includes lower-case after e.g. but that's inside parentheses.
Simplify: We could keep the benefits as a single
but that violates instruction to use
- for any list. However maybe we can treat the whole benefits string as a single list item? That would be a list with one item, which is still a list. But the instruction says "Use
- for any list of duties/requirements/benefits". If we have a list, we should use
- . If we have a single block, we could still use
- with one item. That satisfies.
Thus we can output:
- Medical/Prescription, Dental & Vision Discount Program (Full Time/Part Time Employees)Group Term Life Insurance and AD&D(Full Time Employees)Flexible Spending Accounts and Commuter Benefit PlansSupplemental Voluntary Benefits ( e.g. Short-term and Long-term Disability, Whole Life Insurance, Legal Support, etc.)6 Paid Holidays, Paid Time Off (varies), Wellness Time Off, Extended IllnessRetirement PlanTuition Assistance Employee Assistance Program (EAP)Valley Health LifeStyles Fitness Center Membership DiscountDay Care Discounts for Various Daycare Facilities
with that prose, then a
- for the range? Or we could just put the range in a
. The instruction: use
- for any list of duties/requirements/benefits. Pay is not a list, it's a range. So we can use
. Schedule: we have "Shift Day". Also maybe "Shift Day (United States of America)"? Actually the location line includes shift day. We'll treat schedule as "Shift Day". We'll put in
. Now About the role: we have Position Summary sentence. Could also include location? We'll keep location separate maybe as a
after About the role. Let's craft HTML:
About the role
To greet, direct, and provide helpful information to patients, visitors, physicians, and employees.
Location: The Valley Hospital-Paramus.
Qualifications
- High school diploma or equivalent is required.
- Computer experience preferred.
Skills
- Ability to read, write, and speak clear and fluent English.
- Ability to communicate effectively (orally and in writing) and interact with patients, family members, visitors, physicians, sales representatives, and members of the general public.
- Ability to handle frequent interruptions, adapt to changes in workload and work schedule, and remain composed during interruptions and changes.
- Ability to set priorities and solve problems.
- Ability to respond quickly to emergency requests.
Benefits
- Medical/Prescription, Dental & Vision Discount Program (Full Time/Part Time Employees)Group Term Life Insurance and AD&D(Full Time Employees)Flexible Spending Accounts and Commuter Benefit PlansSupplemental Voluntary Benefits ( e.g. Short-term and Long-term Disability, Whole Life Insurance, Legal Support, etc.)6 Paid Holidays, Paid Time Off (varies), Wellness Time Off, Extended IllnessRetirement PlanTuition Assistance Employee Assistance Program (EAP)Valley Health LifeStyles Fitness Center Membership DiscountDay Care Discounts for Various Daycare Facilities
Pay
Joining Valley Health System means becoming part of a dedicated team that values the highest quality of care in a supportive environment. In our commitment to high performance and reliability, we encourage and recognize exceptional individual performance through our industry leading compensation practices including a starting salary and benefits in accordance with your role, experience,
- for any list of duties/requirements/benefits. Pay is not a list, it's a range. So we can use
- with one item. That satisfies.
Thus we can output:
- . If we have a single block, we could still use
- for any list of duties/requirements/benefits". If we have a list, we should use
- for any list. However maybe we can treat the whole benefits string as a single list item? That would be a list with one item, which is still a list. But the instruction says "Use
- for any list of duties/requirements/benefits. So we need to make a list. We could keep each benefit as a list item, but we need to separate them correctly. Let's try to parse:
Original: "Medical/Prescription, Dental & Vision Discount Program (Full Time/Part Time Employees)Group Term Life Insurance and AD&D(Full Time Employees)Flexible Spending Accounts and Commuter Benefit PlansSupplemental Voluntary Benefits ( e.g. Short-term and Long-term Disability, Whole Life Insurance, Legal Support, etc.)6 Paid Holidays, Paid Time Off (varies), Wellness Time Off, Extended IllnessRetirement PlanTuition Assistance Employee Assistance Program (EAP)Valley Health LifeStyles Fitness Center Membership DiscountDay Care Discounts for Various Daycare Facilities"
We can see patterns: after each benefit there is a parenthesis with eligibility, then next benefit starts with a capital letter (Group, Flexible, Supplemental, 6, Retirement, Tuition, Valley, Day). The "6 Paid Holidays" starts with a number.
Thus we can split before each capital letter that follows a closing parenthesis or before a number at start? But we risk mis-splitting inside parentheses like "( e.g. Short-term and Long-term Disability, Whole Life Insurance, Legal Support, etc.)" includes lower-case after e.g. but that's inside parentheses.
Simplify: We could keep the benefits as a single