LINE COOK

We need to output HTML fragment with headings

for sections: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. Only include sections that have real specific content. We must not repeat job title. Must not include Job ID etc. Must preserve all substantive info, not invent or summarize away detail. Remove boilerplate: location, employment type, salary line? Actually location and employment type and salary are metadata; they may be folded into a short

or dropped. The instruction: "Do NOT put Job ID / requisition numbers as headings — fold minor metadata into a short

or drop it." So location, employment type, salary can be placed in a short

maybe under an "About the role" section? But we need to decide sections. We have content: POSITION OVERVIEW paragraph (describes role). That's about the role. Then "REWARD FOR MEETING OUR HIGH STANDARDS?" paragraph about compensation package, opportunity to thrive, etc. That could be Benefits? It mentions competitive compensation package, opportunity to thrive, etc. Not specific benefits like health insurance, etc. So maybe we can treat that as Benefits? But we should only create Benefits section if posting actually states them. It says "competitive compensation package, an opportunity to thrive in a challenging, enriching and rewarding environment, with the opportunity to grow with us as we begin a period of exciting growth. The Line Cook will be empowered to work with the team and be provided the tools to do so." That's vague but still some content. Could be considered Benefits. However the instruction: "Prefer a few substantive sections over many thin ones." So maybe combine overview and reward into About the role? But we need headings for sections only when posting has real specific content. The overview is definitely role description. The reward paragraph is more about benefits/opportunities. Could be a Benefits section. Responsibilities: a big list. Requirements: includes knowledge, skills, education + experience required. Also includes physical demands etc. Could be Requirements section. Qualifications: maybe separate? The posting has "Requirements KNOWLEDGE, SKILLS, EDUCATION + EXPERIENCE REQUIRED FOR THE JOB:" then list. Then later "Frequency PHYSICAL DEMANDS:" etc. That could be part of Requirements or Qualifications. Since we have both Requirements and Qualifications headings allowed, we could split: Requirements = knowledge, skills, education + experience; Qualifications = physical demands? But physical demands are more like requirements too. However we need to avoid thin sections. Might be better to have one Requirements section that includes both the list and physical demands. The instruction: "Prefer a few substantive sections over many thin ones." So we can combine. Skills: maybe we can extract skills from requirements list (communication, guest service, math, computer, multitasking). But we already have them in requirements; making a separate Skills section would be thin. Better to not create Skills unless distinct. Pay: posting says "Salary: Competitive" and "competitive compensation package". No specific numbers. According to rule: never create Pay/Schedule/Benefits sections unless posting actually states them. It does state "competitive compensation package" but not specific pay. 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" is vague but it's stated. However it's still placeholder-like. Might be considered not specific enough. Safer to 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 a Schedule section. Benefits: we have reward paragraph; could be Benefits. It's not just filler; mentions competitive compensation package, opportunity to thrive, growth, empowerment, tools. That's substantive enough? Might be okay. Thus sections: About the role (position overview), Responsibilities, Requirements (including knowledge, skills, education, experience, physical demands), Benefits (reward paragraph), Schedule. We must not repeat job title as heading. Use

for each section heading. We need to use

• for any list of duties/requirements/benefits. For prose use

  . We need to preserve all substantive information; do not invent or summarize away detail. So we must keep the details from the posting. We need to remove boilerplate: location, employment type, salary line, applicant declaration? The applicant declaration at end: "I have read the responsibilities..." That's boilerplate? It's like a statement; maybe we can drop as it's application instruction? It's not exactly instruction but it's a declaration. Likely we can drop as it's not substantive job description. Also remove "Location: Scottsdale, AZ Employment Type: Part-Time Salary: Competitive". Also remove "Job Description" heading? Not needed. We need to keep all substantive content: position overview paragraph, reward paragraph, responsibilities list (each bullet), requirements list (including knowledge, skills, education + experience), physical demands details, schedule paragraph. We must not lose any details. Let's extract. Position Overview paragraph: "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." Reward paragraph: "In return for the Line Cook’s skills and dedicated effort, the Line Cook will receive a competitive compensation package, an opportunity to thrive in a challenging, enriching and rewarding environment, with the opportunity to grow with us as we begin a period of exciting growth. The Line Cook will be empowered to work with the team and be provided the tools to do so." Responsibilities: list items (each sentence seems a bullet). Let's capture each: - 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. Wait the last bullet about attendance is actually schedule; but it's included in responsibilities list. However we have schedule section separate; we might want to move that to schedule. But the instruction: preserve all substantive information; we can keep it in responsibilities but also schedule. However duplication might be okay but we should avoid duplication? Not explicitly forbidden but better to not duplicate. The attendance line is more schedule; we can treat it as schedule section and remove from responsibilities to avoid duplication. However the responsibilities list originally includes that line; if we remove it, we are omitting substantive info. Better to keep it in responsibilities and also have schedule section? That would duplicate. The instruction: "Preserve ALL substantive information; do NOT invent or summarize away detail." Duplication is not inventing or summarizing away; it's preserving. It might be okay but could be considered redundant. However we could keep it only in schedule and remove from responsibilities to avoid duplication while still preserving info (since it's moved). That's preserving the info, just relocated. That seems acceptable. Thus responsibilities list will exclude the attendance line. Now Requirements: list items from "KNOWLEDGE, SKILLS, EDUCATION + EXPERIENCE REQUIRED FOR THE JOB:" then list: - 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 Then after that there is "Frequency PHYSICAL DEMANDS:" with a table. We need to preserve that info. We can represent as a list or maybe a

  with each line. The table includes categories: LIFTING + CARRYING: Weight Frequency Objects ... etc. Also Sitting, Standing, Walking, Bending, Squatting, Kneeling, Crawling, Climbing, Reaching, Grasping. We need to keep all details. We can format as a
  with each line as
  • . Or we could keep as

    with line breaks? Better to use

    • for list. Thus Requirements section will contain two lists: one for knowledge/skills/experience, another for physical demands. Or we could combine into one list but that would be messy. We'll have two
      under Requirements. Now Benefits section: reward paragraph. Schedule section: the attendance line (regular and predictable attendance...). We must not include any boilerplate like "Applicant Declaration". Also remove "Location: Scottsdale, AZ Employment Type: Part-Time Salary: Competitive". Also remove "Job Description" heading. Now produce HTML fragment. Structure:

      About the role

      ...position overview...

      Responsibilities

      • ... each responsibility ...
      ...

      Requirements

      Knowledge, skills, education + experience:

      • ... each ...
      ...