Sous Chef - Dining Services at the University of North Georgia - Dahlonega
Aramark · Dahlonega, GA · 1 mo ago
On-siteManagementFull-time
We need to output HTML fragment with sections: About the role, Responsibilities, Requirements (or Qualifications), maybe Skills, Benefits, Pay, Schedule only if present. The posting includes: Job Description (intro), Job Responsibilities (list), Qualifications (list), Education (maybe not present), About Aramark (company info). Also mention "Previous supervisor experience...", "Experience as a cook...", etc. Also "Food safety certification required". Also "This role may have physical demands...". Also "This role may also require uniforms and/or usage of PPE." Also "At Aramark, developing new skills...". Also "In order to meet our commitments, job duties may change...". Also "About Aramark" sections.
We need to remove boilerplate: cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, application instructions. The EEO statement is present: "At Aramark, we believe that every employee should enjoy equal employment opportunity...". That's boilerplate; we should remove it. Also duplicated lines: "About Aramark" appears twice with similar content; we need to keep substantive info but not duplicate. We'll keep one About Aramark section with meaningful content (mission, purpose, etc). Remove the EEO statement.
We need headings: for section headings: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We need to include sections only when posting has real specific content.
We have About the role: maybe the introductory paragraph "The Lead Cook is responsible for cooking and preparing food...". That's about the role. So we can have
for section headings: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We need to include sections only when posting has real specific content.
We have About the role: maybe the introductory paragraph "The Lead Cook is responsible for cooking and preparing food...". That's about the role. So we can have About the role
with
containing that description. Responsibilities: we have a list of responsibilities under "Job Responsibilities". We'll output
Responsibilities
with- each item.
Qualifications: we have "Qualifications" section with bullet list. Also "Education" maybe not present; we can ignore.
Skills: maybe we can extract skills from qualifications: "Proven knowledge of the basic principles of food preparation, various cooking methods, and food safety regulations such as proper food handling, sanitation, and storage", "Demonstrates basic math and counting skills", "Demonstrates effective interpersonal and communication skills, both written and verbal". Also "Previous supervisor experience in a related role preferred", "Experience as a cook or related role required", "Ability to work independently with limited supervision required", "Food safety certification required". These could go under Qualifications or Skills. The instruction says we can have Skills section if there is real specific content. We could put those under Qualifications (makes sense). But we could also separate Skills. However we need to avoid many thin sections. Better to combine qualifications and skills into one Qualifications section. The instruction says we can have Qualifications heading. So we will put all qualification-related content under
Qualifications
. That includes experience, supervisor, ability to work independently, knowledge, math, communication, certification, physical demands, uniform/PPE maybe? Physical demands could be part of qualifications or maybe separate but we can include in Qualifications as note. We should not create Benefits, Pay, Schedule sections because not present. We also have "At Aramark, developing new skills and doing what it takes to get the job done make a positive impact for our employees and for our customers. In order to meet our commitments, job duties may change or new ones may be assigned without formal notice." This is more about company culture; could go under About the role or maybe a separate About Aramark section. We have About Aramark section with mission etc. We'll put that underAbout Aramark
? But allowed headings list includes About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. Not About Aramark. However we could treat About Aramark as part of About the role? The instruction says use those headings for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). It doesn't forbid other headings, but says "Usefor section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." The e.g. suggests those are examples; we could still use other headings if needed, but better to stick to those. However we have substantive content about Aramark mission etc. Could we put that under About the role? Possibly combine: About the role could include description of role and company overview. But the instruction says "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." It doesn't forbid adding other headings like About Aramark. But to be safe, we could include About Aramark as a paragraph under About the role or maybe as a separate section with heading About Aramark (though not in list). The instruction says "Use
for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." The e.g. implies those are typical but not exhaustive. However they also say "Prefer a few substantive sections over many thin ones." So we could combine About Aramark info into About the role section to avoid extra heading. Thus we will have:
About the role
... (intro + company mission etc)
Responsibilities
- ...
Qualifications
- ...