Dining Room Server
The Arbor Company · Peachtree City, GA · 1 mo ago
On-siteManagementFull-time
We need to output HTML fragment with headings inside
for sections: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. Only include sections that have real specific content. Remove boilerplate, EEO, etc. Also remove duplicated lines, navigation, cookie, etc. We need to parse the posting. Content: "Are you ready to love your job again? Join The Arbor Company and discover a work family where you are treated with respect. We are recognized by our team members as a Great Place To Work® and we are honored to be one of only 20 companies on Fortune Magazine’s “Best Workplaces in Aging Services" list. Arbor People feel the love every day because we provide:" Then a list of benefits: - Free Meal for Each Work Shift - Employee Assistance Program – Wellness Resources for You and Your Family - Competitive Pay Rates - Paid Time Off for Full Time and Part Time Staff, Plus the Ability to Turn Your PTO Into Cash - Options To Get Paid on Your Own Schedule - Certified Great Place to Work - Pathways For Growth Opportunities - Diversity, Equity and Inclusion Training - Tuition Assistance - Student Loan Repayment Assistance - Access To Emergency Financial Assistance - Access To Health, Dental, Vision Insurance - 401K with Employer Matching Contributions Then: "As a Server at The Arbor Company, your work matters. Here's why:" Then bullet points (maybe not bullet but sentences): - You will deliver restaurant style dining services with a hospitality focus - Your cheerful energy brings a smile to residents during each meal service - You help residents who have special requests - You work as team to keep the dining room clean and inviting Then: "You’ll be great on this team because you have:" Then bullet points: - Must be able to pass a level 2 background check - Ability to maintain positive resident relations through a courteous, cooperative and understanding manner Then: "Our people and our residents are at the center of our universe. We can’t wait to meet you!" Then EEO boilerplate to remove. Thus we need sections: - About the role: maybe the introductory paragraph about company and role? Could be "About the role" includes description of role and company? The posting includes "Are you ready to love your job again? Join The Arbor Company..." That's more about company culture. Could be "About the role" includes description of role? But we have separate sections for Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We need to map content. Responsibilities: The bullet points after "As a Server at The Arbor Company, your work matters. Here's why:" are responsibilities. Requirements: The bullet points after "You’ll be great on this team because you have:" are requirements (background check, ability to maintain positive resident relations). Could also be qualifications. Qualifications: maybe same as requirements? But we need to avoid duplication. The instruction: "Prefer a few substantive sections over many thin ones." So we could combine Requirements and Qualifications into one section? But we have to use headings exactly as given if we include them. We can decide to include only sections that have content. Could include "Responsibilities" and "Requirements" and "Benefits". Possibly also "About the role" for introductory paragraph. Pay: The posting mentions "Competitive Pay Rates" under benefits list. That's a benefit, not a specific pay amount. The rule: never create Pay/Schedule/Benefits sections unless the posting actually states them. It does state "Competitive Pay Rates" but that's vague. However it's still stating pay rates (competitive). Is that enough? The rule says: 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. "Competitive Pay Rates" is somewhat vague but it's a statement about pay. It's not a specific number, but it's still stating something about pay. The rule about filler text includes "commensurate with experience", "not specified", etc. "Competitive Pay Rates" is not exactly filler but it's vague. However it's still a statement about pay. I'd lean to include Pay section with that line. Schedule: The posting mentions "Options To Get Paid on Your Own Schedule" under benefits. That's about pay schedule, not work schedule. There's no mention of work schedule (like shifts, full-time/part-time). There's mention of Paid Time Off for Full Time and Part Time Staff. That indicates full/part time but not schedule details. The rule: never create Schedule section unless posting actually states them. It does not state specific schedule (e.g., "Monday-Friday, 8am-5pm"). So we should not include Schedule. Benefits: we have many benefits listed. So include Benefits section. About the role: we have introductory paragraph about company culture and role? Could be "About the role" includes description of role and company. We'll include that. Requirements: we have bullet points about background check and ability to maintain positive resident relations. That's requirements. Qualifications: maybe we could combine with Requirements, but we have separate headings. If we include both, we might duplicate content. Better to include only Requirements and maybe Qualifications if we have distinct content. There's no explicit qualifications like education, experience. So we could omit Qualifications. Skills: we have no explicit skills list besides maybe "cheerful energy", "teamwork". Those are more responsibilities. Could put under Skills? But we have responsibilities already. Might be thin. Better to omit Skills. Thus sections: About the role, Responsibilities, Requirements, Benefits, Pay. Check if any content duplicated: The introductory paragraph includes "Arbor People feel the love every day because we provide:" then list of benefits. That list is also benefits. We should not duplicate the list in About the role; we can keep the intro paragraph as About the role (excluding the list). Then Benefits section will have the list. Let's extract About the role text: "Are you ready to love your job again? Join The Arbor Company and discover a work family where you are treated with respect. We are recognized by our team members as a Great Place To Work® and we are honored to be one of only 20 companies on Fortune Magazine’s “Best Workplaces in Aging Services" list." That's it. The sentence "Arbor People feel the love every day because we provide:" leads into list; we exclude that sentence? It's part of intro but leads to list. Could include it as part of About the role but then we would duplicate list. Better to include that sentence as part of About the role but not include the list. However the sentence says "Arbor People feel the love every day because we provide:" which is incomplete without list. Might be odd but acceptable. Could we rephrase? We must preserve ALL substantive information; we cannot invent or summarize away detail. We cannot omit the phrase "Arbor People feel the love every day because we provide:" because it's substantive? It's a lead-in to the list; but if we omit it, we lose that sentence. The rule: Preserve ALL substantive information; do NOT invent or summarize away detail. So we need to keep that sentence. However if we keep it, we must not then list the benefits again in Benefits section? Actually we need to list the benefits somewhere. The sentence is just a lead-in; the list is the benefits. So we can keep the sentence in About the role, and then Benefits section will list the benefits. That's fine; we are not duplicating the list, just the lead-in sentence. Thus About the role: include the two sentences: "Are you ready to love your job again? Join The Arbor Company and discover a work family where you are treated with respect. We are recognized by our team members as a Great Place To Work® and we are honored to be one of only 20 companies on Fortune Magazine’s “Best Workplaces in Aging Services" list. Arbor People feel the love every day because we provide:" (maybe end with colon). That's okay. Now Responsibilities: bullet points: - You will deliver restaurant style dining services with a hospitality focus - Your cheerful energy brings a smile to residents during each meal service - You help residents who have special requests - You work as team to keep the dining room clean and inviting We need to wrap each in
- .
Requirements: bullet points:
- Must be able to pass a level 2 background check
- Ability to maintain positive resident relations through a courteous, cooperative and understanding manner
Benefits: list all benefits:
- Free Meal for Each Work Shift
- Employee Assistance Program – Wellness Resources for You and Your Family
- Competitive Pay Rates
- Paid Time Off for Full Time and Part Time Staff, Plus the Ability to Turn Your PTO Into Cash
- Options To Get Paid on Your Own Schedule
- Certified Great Place to Work
- Pathways For Growth Opportunities
- Diversity, Equity and Inclusion Training
- Tuition Assistance
- Student Loan Repayment Assistance
- Access To Emergency Financial Assistance
- Access To Health, Dental, Vision Insurance
- 401K with Employer Matching Contributions
Pay: we have "Competitive Pay Rates" already in benefits. But we could also create Pay section with that line. However that would duplicate content. The rule: Preserve ALL substantive information; do NOT invent or summarize away detail. If we put it only in Benefits, we still preserve it. Creating a separate Pay section would duplicate the same line, which is not prohibited but could be considered duplication. The instruction says remove duplicated lines. So we should not duplicate. Therefore we should not create a separate Pay section if the pay info is already captured elsewhere. However the rule about Pay section: "never create Pay/Schedule/Benefits sections unless the posting actually states them." It does state competitive pay rates, but we already have it in Benefits. If we omit Pay section, we still have the info in Benefits. That's fine. The instruction: "Prefer a few substantive sections over many thin ones." So we can omit Pay section.
Thus sections: About the role, Responsibilities, Requirements, Benefits.
Check if any other content: "Our people and our residents are at the center of our universe. We can’t wait to meet you!" That's a closing statement. Could be part of About the role or maybe a separate section? Not fitting any heading. Could be included in About the role as extra sentence. It's substantive; we should preserve it. Where to put? Could add to About the role after the lead-in sentence. That would be okay.
Thus About the role will contain:
"Are you ready to love your job again? Join The Arbor Company and discover a work family where you are treated with respect. We are recognized by our team members as a Great Place To Work® and we are honored to be one of only 20 companies on Fortune Magazine’s “Best Workplaces in Aging Services" list. Arbor People feel the love every day because we provide: Our people and our residents are at the center of our universe. We can’t wait to meet you!"
But note the phrase "Arbor People feel the love every day because we provide:" then we have the list of benefits after. If we put "Our people and our residents are at the center of our universe. We can’t wait to meet you!" after the colon, it reads weird: "because we provide: Our people and our residents..." Might be okay but maybe better to keep the colon and then list benefits separately. Actually the original text: "Arbor People feel the love every day because we provide:" then line break then list. Then later after list: "As a Server at The Arbor Company, your work matters..." Then later: "Our people and our residents are at the center of our universe. We can’t wait to meet you!" So the closing sentence is after the list and after responsibilities etc. So we can keep it as a separate sentence after the list, maybe in About the role after the list? But we are not putting list in About