d'Lite Line Cook

We need to output HTML fragment with sections only if there is real specific content. Use

for section headings: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We need to decide which sections have content. From posting: - POSITION OVERVIEW: description about role. Could be "About the role". So we can have

About the role

with paragraph(s) summarizing the overview. - Responsibilities: list of duties. So

Responsibilities

with

• items. - Requirements: list of requirements (knowledge, skills, education + experience). So

  Requirements

  with
  . - Qualifications: maybe same as requirements? The posting includes "Requirements KNOWLEDGE, SKILLS, EDUCATION + EXPERIENCE REQUIRED FOR THE JOB:" then bullet list. Also later "Frequency PHYSICAL DEMANDS:" etc. Could treat as Qualifications? But we have both Requirements and Qualifications sections. We need to decide if we have distinct content for Qualifications. The posting does not separate qualifications separate from requirements; it's all under Requirements. So we could either put everything under Requirements and skip Qualifications, or we could split: Requirements (knowledge, skills, education + experience) and Qualifications (certifications, physical demands?). However the instruction: "Prefer a few substantive sections over many thin ones." So better to combine into one Requirements section and omit Qualifications if no distinct content. - Skills: maybe we could extract skills from responsibilities? But we already have responsibilities. Could create Skills section but might be thin. Better to omit. - Benefits: posting mentions "competitive compensation package, an opportunity to thrive..." but not specific benefits like health insurance etc. It says "competitive compensation package" but not details. The rule: never create Benefits section unless posting actually states them. It mentions competitive compensation package but not specific benefits. Might be considered vague. Probably we should not create Benefits section because no concrete benefits listed. - Pay: posting says Salary: Competitive (but not specific). Also "competitive compensation package". Not specific number or range. According to rule: never create Pay/Schedule/Benefits sections unless posting actually states them. It says Salary: Competitive (not specific). That's not a specific amount, so we should not create Pay section. - Schedule: posting includes "Regular and predictable attendance: The scheduled working hours for this position range from Sunday – Saturday from 5:30am to 5:30pm and shifts range from 4 to 8 hours in length." That's specific schedule info. So we can create Schedule section with that paragraph. Thus sections: About the role, Responsibilities, Requirements, Schedule. We need to preserve all substantive information, not invent or summarize away detail. Must not repeat job title as heading. Must not include Job ID etc. Must remove boilerplate like applicant declaration? The applicant declaration at end: "I have read the responsibilities..." That's boilerplate/application instruction? It's like a statement. Probably we should remove it as it's application instruction/boilerplate. Also remove "Location: Scottsdale, AZ Employment Type: Part-Time Salary: Competitive Job Description" maybe we keep location? The instruction: do not put Job ID/requisition numbers as headings — fold minor metadata into a short

  or drop it. Location and employment type could be minor metadata; we could include in a short

  under About the role or separate? Probably we can include location and employment type in a short paragraph after the overview. But we must preserve all substantive information; location and employment type are substantive. So we should include them somewhere. Could add a

  with "Location: Scottsdale, AZ. Employment Type: Part-Time." Or incorporate into About the role. We must not repeat job title as heading. The job title is Line Cook; we shouldn't make a heading for it. We need to output only HTML fragment, no /, no markdown fences. Let's craft:

  About the role

  Location: Scottsdale, AZ. Employment Type: Part-Time. The Line Cook is a team member of the Back of House responsible for superior customer satisfaction through food assembly with accuracy and efficiency, ensuring core values are carried out through execution. The Line Cook reports to the Shift Leader or General Manager, must complete General Team Member Training Certification and Line Cook Training Certification, and is expected to maintain professional dress, speech, and behavior while communicating effectively in English.

  But we need to preserve all details from POSITION OVERVIEW: many sentences. Let's capture them. POSITION OVERVIEW text: "The Line Cook is a team member of the Back of House. The Line Cook is responsible and accountable for superior customer satisfaction through food assembly with accuracy and efficiency, and ensuring that core values are carried out through execution. The Line Cook is expected to be a role model for the company culture, and always exhibit the highest standards in overall guest experience, by delivering the best food and service, in the cleanest, most friendly and safest dining environment. The Line Cook reports directly to the assigned Shift Leader [SL] and/or General Manager [GM]. The Line Cook is accountable for executing the policies, procedures and direction provided by the SL and/or GM. The Line Cook is required to complete and meet the requirements of the General Team Member Training Certification and the Line Cook Training Certification. It is preferred that the Line Cook be able to speak and write in the English language in order to best communicate with our customers, vendors, and leadership, and must maintain professional dress, speech, and behavior at all times." We should keep that as prose, maybe split into paragraphs but okay. Then Responsibilities: list many items. We'll create
  • for each bullet. Let's extract responsibilities lines: - Superior customer service through fast, efficient, accurate, and proper food production all completed to company standards - Continuously test all food products for taste, appearance, consistency to assure that all company food standards and procedures are being followed - Clean and maintain the kitchen on a regular basis, including proper timely maintenance on all machines and equipment - Superior knowledge of entire food menu, ingredients, modifications, cook times, assembly order - Proper protocol and management of ticket orders, table number groupings - Proper presentation and/or preparation of food for dine-in or to-go - Become familiar with new menu items and their preparation, cook times and assembly - Supports the Back of House team by ensuring that prep is completed, coolers are stocked, equipment is clean, and ready for service at all times with a friendly, positive attitude aligning with company core values - Completes position Primary and Secondary Responsibilities as well as Daily Duties at a superior level - Maintains a calm demeanor during periods of high volume or unusual events to keep store operating to standard and to set positive examples for rest of team - Assist with the par/inventory/order of food supply - Coordinate food service with other departments as necessary - Maintaining accurate temperatures on all cooling equipment, maintain waste sheet, temp logs - Maintains kitchen to high standard and follows sanitation guidelines compliant with Health Department and company standards - At times, performs work of other team members as needed - Keeps company passwords and intellectual property confidential - Demonstrates a positive, helpful attitude as well as presenting professional conduct and appearance at all times - Use, implementation, and adherence to all company policies, procedures, systems and processes - Regular and predictable attendance: The scheduled working hours for this position range from Sunday – Saturday from 5:30am to 5:30pm and shifts range from 4 to 8 hours in length. Note: The last bullet about attendance is also schedule; but we already have schedule section. Might duplicate. We could keep it in responsibilities but also schedule. However we should avoid duplication? The instruction: Preserve ALL substantive information; do NOT invent or summarize away detail. Duplication is okay if it's in original. But we might move attendance to schedule section and remove from responsibilities to avoid redundancy. However the responsibilities list includes that line; if we remove it, we are omitting substantive information. Better to keep it in responsibilities and also have schedule section? That would duplicate. The instruction says do not invent or summarize away detail; duplication is not prohibited but might be considered redundant. However we could keep it only in schedule section and remove from responsibilities to avoid duplication while still preserving the info (since it's still present). But we would be removing it from responsibilities list, which is part of the original responsibilities. That would be omitting detail. So we need to keep it somewhere; we could keep it in responsibilities and not have a separate schedule section, but we have schedule info separate from responsibilities? The schedule info is also present in responsibilities; we could still have schedule section but we would be duplicating. The instruction does not forbid duplication, but says "Prefer a few substantive sections over many thin ones." Duplication would create thin sections maybe. Better to keep schedule info only in responsibilities and not create schedule section. However the schedule info is also a distinct piece; but we can keep it within responsibilities. The rule: "never create Pay/Schedule/Benefits sections unless the posting actually states them." It does state schedule (the attendance line). So we could create schedule section with that line, but then we would be duplicating if we also keep it in responsibilities. To avoid duplication, we could remove it from responsibilities list. But that would be removing content from responsibilities. However we could keep responsibilities list without that line, and still have the schedule section with that line. The responsibilities list would be missing that line, which is part of the original responsibilities. That would be omitting detail. So we need to keep it somewhere; we could keep it in both places, but that's duplication. The instruction does not explicitly forbid duplication, but says "Preserve ALL substantive information; do NOT invent or summarize away detail." Duplication preserves all info (none lost) but adds extra. It's not prohibited. However they also say "Prefer a few substantive sections over many thin ones." Duplication creates extra section (schedule) which might be thin if only that line. But schedule section would have that line plus maybe we could add other schedule details if any. There's only that line. So schedule section would be thin. Better to not create schedule section and keep the line within responsibilities. Then we are not creating a schedule section, which is okay because we are not required to create it; we only create if posting actually states them, but we can choose not to? The rule: "never create Pay/Schedule/Benefits sections unless the posting actually states them." It does not say we must create them if they exist; it says we must not create them unless they exist. So we can optionally create them if we want, but we should prefer few sections. So we can omit schedule section. Thus sections: About the role, Responsibilities, Requirements. Now we need to extract Requirements list. Requirements block: "KNOWLEDGE, SKILLS, EDUCATION + EXPERIENCE REQUIRED FOR THE JOB: 18+ years of age Prefer high school graduate 1 yr of food preparation and/or kitchen experience Demonstrate cooking skills, ability to follow established protocol and recipes Dependable, honest, trustworthy, possesses integrity Positive attitude and great personal drive Courteous and enthusiastic Willingness and ability to learn in a fast-paced sales environment Exceptional communication skills Exceptional guest services skills Basic math skills and computer skills Prefer ability to handle multiple projects simultaneously and efficiently Successful completion of General Team Member Training Certification Successful completion of Line Cook Training Certification Ability to learn and maintain knowledge of company’s products and procedures Availability to work on weekends Reliable transportation" Also there is "Frequency PHYSICAL DEMANDS:" etc. That could be considered part of Requirements? It's physical demands. Could be included under Requirements as well. But we might treat as part of Requirements (maybe as a sublist). However we already have many items; adding physical demands may be okay. Physical demands section: "Frequency PHYSICAL DEMANDS: Never = 0% Rarely = 1 – 1