Cook - Late Night Shift
for section headings, - for any list of duties/requirements/benefits, and
for prose.
We need to decide what goes into lists vs prose.
We should convert lists where appropriate: e.g., responsibilities list (essential functions) can be
- . Benefits list can be
- . Qualities list can be
- . Requirements list can be
- . Pay maybe prose. Schedule maybe prose.
We must not repeat job title. No headings for Job ID.
We must remove boilerplate: cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, application instructions. The posting includes "EOE" at end; that's EEO boilerplate, should be removed. Also "Raising Cane’s appreciates & values individuality. EOE" - remove that line.
Also "Locations may vary" maybe minor metadata; could be included in schedule or benefits? It's not essential; but we can keep as prose maybe under Schedule or Benefits? It's not a benefit. Might be considered minor metadata; we could drop it. The instruction: "Do NOT put Job ID / requisition numbers as headings — fold minor metadata into a short
or drop it." So "Locations may vary" is minor metadata; we can drop it or fold into a short p. Probably drop.
Also "*", "**", "***" footnotes: we can ignore them or keep as part of text? Probably keep the substance but remove the footnote markers. Eg "Paid Time Off*" -> just "Paid Time Off". "Closed for all major holidays**" -> "Closed for all major holidays". "Additional $1 per hour after 10pm***" -> "Additional $1 per hour after 10pm". "Must satisfy hours requirement per year**" -> "Must satisfy hours requirement per year". We'll keep the substance.
Now let's extract content.
**About the role** (prose):
- As a Cook at Raising Cane’s, you will set the pace of the Restaurant by ensuring all of the food we serve meets our high standards.
- Working in the Kitchen at Raising Cane’s is a fun and fast paced environment. Crank up the music and have some fun while you are working hard to prepare the highest quality chicken finger meals for our customers to enjoy.
- Starting out in the back of the house at Raising Cane’s can lead to many promotional opportunities for Cooks to grow their career by moving into advanced roles like Bird Specialist or Certified Trainer.
- We are looking to immediately hire entry level and experienced Cooks who can thrive in an upbeat and fast-paced food service environment.
- We are hiring immediately for Cooks that can work all shifts: opening shifts, closing shifts and everything in between.
- Whether you have previous experience as a customer service associate, retail team member, cashier, restaurant server, kitchen lead, cook, prep cook, drive-thru cashier or any other restaurant or service-oriented role - we have a position for you.
- We offer competitive pay and benefits for all positions.
- Even if you don’t have previous Restaurant experience, this position is entry-level (yes, that's no experience required) and we provide paid training for every new Restaurant Cook on the team.
- We will make sure you are prepared to grow your Restaurant career with us.
- Within your first year of working in the Restaurant, you can earn up to an extra $1.50 per hour in pay increases through additional training, certifications, and performance evaluations!
- If you want to be at Restaurant that is a FUN place to work, that values your growth and provides opportunities to impact your community, we want you on our team.
That's a lot; could be split into About the role and maybe Responsibilities. But we need to follow instruction: prefer a few substantive sections over many thin ones. So we could combine many of these into About the role (description) and Responsibilities (essential functions). Qualities (skills) separate. Requirements separate. Benefits separate. Pay separate. Schedule separate.
Let's decide:
**About the role**: general overview: setting pace, ensuring food standards, fun fast paced environment, promotional opportunities, hiring entry/experienced, work all shifts, various backgrounds, competitive pay/benefits, entry-level no experience required, paid training, career growth, extra pay increase, fun place to work, values growth, community impact.
**Responsibilities**: essential functions list (lift/carry up to 50 lbs, kneel/bend/twist/stoop, ascend/descend stairs, reach/grasp objects, excellent verbal/written communication, show up on time, cleaning tables/floors/other areas, taking orders and processing payments, follow safety procedures, ability to multitask). Also maybe "Provide all Customers with quick and friendly service" could be responsibility. But that is also under additional requirements. We'll keep it under Requirements maybe.
**Requirements**: additional requirements: Must be 16 years of age or older, Provide all Customers with quick and friendly service, Work together as a team, assisting other Crewmembers in completion of tasks and assignments to ensure continuity of service, Work under pressure and at a fast pace, Align with Raising Cane’s culture by balancing Working Hard and Having Fun, Take initiative, Comply with Company policies. (We'll drop EOE.)
**Qualifications**: Qualities of awesome Canes Restaurant Cook: Team player, Excellent communicator, Happy, Courteous and Enthusiastic, Hard working and attentive, Responsible and dependable, Authentic and genuine, Takes pride in doing a good job.
**Skills**: Could be the essential functions that are skills? But we already used essential functions for responsibilities. Maybe we can treat essential functions as responsibilities, and skills as things like verbal/written communication, multitasking, ability to show up on time, etc. But that overlaps. To avoid thin sections, we could merge Skills into Responsibilities or Qualifications. However the instruction says use sections only when posting has real specific content. It doesn't forbid overlapping but we should avoid thin sections. So maybe we omit Skills section and put those under Responsibilities.
**Ben
for prose. We need to decide what goes into lists vs prose. We should convert lists where appropriate: e.g., responsibilities list (essential functions) can be
- . Benefits list can be
- . Qualities list can be
- . Requirements list can be
- . Pay maybe prose. Schedule maybe prose.
We must not repeat job title. No headings for Job ID.
We must remove boilerplate: cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, application instructions. The posting includes "EOE" at end; that's EEO boilerplate, should be removed. Also "Raising Cane’s appreciates & values individuality. EOE" - remove that line.
Also "Locations may vary" maybe minor metadata; could be included in schedule or benefits? It's not essential; but we can keep as prose maybe under Schedule or Benefits? It's not a benefit. Might be considered minor metadata; we could drop it. The instruction: "Do NOT put Job ID / requisition numbers as headings — fold minor metadata into a short
or drop it." So "Locations may vary" is minor metadata; we can drop it or fold into a short p. Probably drop. Also "*", "**", "***" footnotes: we can ignore them or keep as part of text? Probably keep the substance but remove the footnote markers. Eg "Paid Time Off*" -> just "Paid Time Off". "Closed for all major holidays**" -> "Closed for all major holidays". "Additional $1 per hour after 10pm***" -> "Additional $1 per hour after 10pm". "Must satisfy hours requirement per year**" -> "Must satisfy hours requirement per year". We'll keep the substance. Now let's extract content. **About the role** (prose): - As a Cook at Raising Cane’s, you will set the pace of the Restaurant by ensuring all of the food we serve meets our high standards. - Working in the Kitchen at Raising Cane’s is a fun and fast paced environment. Crank up the music and have some fun while you are working hard to prepare the highest quality chicken finger meals for our customers to enjoy. - Starting out in the back of the house at Raising Cane’s can lead to many promotional opportunities for Cooks to grow their career by moving into advanced roles like Bird Specialist or Certified Trainer. - We are looking to immediately hire entry level and experienced Cooks who can thrive in an upbeat and fast-paced food service environment. - We are hiring immediately for Cooks that can work all shifts: opening shifts, closing shifts and everything in between. - Whether you have previous experience as a customer service associate, retail team member, cashier, restaurant server, kitchen lead, cook, prep cook, drive-thru cashier or any other restaurant or service-oriented role - we have a position for you. - We offer competitive pay and benefits for all positions. - Even if you don’t have previous Restaurant experience, this position is entry-level (yes, that's no experience required) and we provide paid training for every new Restaurant Cook on the team. - We will make sure you are prepared to grow your Restaurant career with us. - Within your first year of working in the Restaurant, you can earn up to an extra $1.50 per hour in pay increases through additional training, certifications, and performance evaluations! - If you want to be at Restaurant that is a FUN place to work, that values your growth and provides opportunities to impact your community, we want you on our team. That's a lot; could be split into About the role and maybe Responsibilities. But we need to follow instruction: prefer a few substantive sections over many thin ones. So we could combine many of these into About the role (description) and Responsibilities (essential functions). Qualities (skills) separate. Requirements separate. Benefits separate. Pay separate. Schedule separate. Let's decide: **About the role**: general overview: setting pace, ensuring food standards, fun fast paced environment, promotional opportunities, hiring entry/experienced, work all shifts, various backgrounds, competitive pay/benefits, entry-level no experience required, paid training, career growth, extra pay increase, fun place to work, values growth, community impact. **Responsibilities**: essential functions list (lift/carry up to 50 lbs, kneel/bend/twist/stoop, ascend/descend stairs, reach/grasp objects, excellent verbal/written communication, show up on time, cleaning tables/floors/other areas, taking orders and processing payments, follow safety procedures, ability to multitask). Also maybe "Provide all Customers with quick and friendly service" could be responsibility. But that is also under additional requirements. We'll keep it under Requirements maybe. **Requirements**: additional requirements: Must be 16 years of age or older, Provide all Customers with quick and friendly service, Work together as a team, assisting other Crewmembers in completion of tasks and assignments to ensure continuity of service, Work under pressure and at a fast pace, Align with Raising Cane’s culture by balancing Working Hard and Having Fun, Take initiative, Comply with Company policies. (We'll drop EOE.) **Qualifications**: Qualities of awesome Canes Restaurant Cook: Team player, Excellent communicator, Happy, Courteous and Enthusiastic, Hard working and attentive, Responsible and dependable, Authentic and genuine, Takes pride in doing a good job. **Skills**: Could be the essential functions that are skills? But we already used essential functions for responsibilities. Maybe we can treat essential functions as responsibilities, and skills as things like verbal/written communication, multitasking, ability to show up on time, etc. But that overlaps. To avoid thin sections, we could merge Skills into Responsibilities or Qualifications. However the instruction says use sections only when posting has real specific content. It doesn't forbid overlapping but we should avoid thin sections. So maybe we omit Skills section and put those under Responsibilities. **Ben
- . Pay maybe prose. Schedule maybe prose.
We must not repeat job title. No headings for Job ID.
We must remove boilerplate: cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, application instructions. The posting includes "EOE" at end; that's EEO boilerplate, should be removed. Also "Raising Cane’s appreciates & values individuality. EOE" - remove that line.
Also "Locations may vary" maybe minor metadata; could be included in schedule or benefits? It's not essential; but we can keep as prose maybe under Schedule or Benefits? It's not a benefit. Might be considered minor metadata; we could drop it. The instruction: "Do NOT put Job ID / requisition numbers as headings — fold minor metadata into a short
- . Requirements list can be
- . Qualities list can be