Jobs · Wyoming

Deli Clerk

Sprouts Healthy Communities Foundation · Cheyenne, WY · 1 mo ago
Part-time
We need to output HTML fragment with headings

for sections: About the role? Actually we have Overview, Job Description, Overview Of Responsibilities, Qualifications, Benefits, Eligibility Requirements, Get Paid Every Day!, Why Sprouts, etc. We need to include sections only when posting has real specific content. We must not repeat job title as heading. Use

for section headings like About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. But we can adapt headings to match content: maybe "Overview", "Responsibilities", "Qualifications", "Benefits", "Eligibility Requirements", "DailyPay", "Why Sprouts". However guidelines: Use

for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). It suggests we should use those standard headings if applicable. But we can also use other headings? It says use

for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). Likely they expect we use those headings when content matches. We have responsibilities, qualifications, benefits. Also we have overview (maybe "About the role"). We have eligibility requirements (maybe part of qualifications). We have DailyPay (maybe part of benefits/pay). We have Why Sprouts (maybe about company). We should include sections only when there is real specific content. We need to preserve all substantive information; do not invent or summarize away detail. Remove boilerplate etc. We need to output only HTML fragment, no /, no markdown fences. We need to use
  • for any list of duties/requirements/benefits, and

    for prose. We need to not repeat job title as heading. We need to not put Job ID/requisition numbers as headings. We need to remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. We need to preserve all substantive information. Let's parse the posting. Overview Job Description: "If you’d be excited to work in a professional kitchen preparing and cooking meals, consider applying for the position of Deli Clerk. As one of the fastest growing natural foods retailers, we’re seeking team members who are excited to share their passion for food." Overview Of Responsibilities: list of responsibilities. Qualifications: list. Benefits: list. Eligibility Requirements: list (bonus based on performance, affordable benefit coverage, HSA, FSA, short-term disability, paid parental leave, paid holidays). Get Paid Every Day! description of DailyPay. Why Sprouts: description. We need to decide sections. Potential sections: - About the role (overview) - Responsibilities - Qualifications - Benefits - Eligibility Requirements (maybe part of benefits but it's separate) - DailyPay (maybe under Pay) - Why Sprouts (maybe about company) But guidelines: Prefer a few substantive sections over many thin ones. So we could combine some. We could have:

    About the role

    with overview paragraph.

    Responsibilities

    with
      list.

      Qualifications

      with
        list.

        Benefits and Compensation

        maybe combine Benefits, Eligibility Requirements, DailyPay. But we need to use headings from list: Benefits, Pay, Schedule. We have benefits content, we have pay info (DailyPay). We don't have schedule specifics beyond flexible schedule mentioned in qualifications. Could include schedule under Qualifications? But we could add a Schedule section if we have content: qualifications mention flexible schedule that changes as business changes, including nights, weekends and holidays. That's schedule info. So we could create a Schedule section. Thus sections: About the role, Responsibilities, Qualifications, Benefits, Pay, Schedule. We need to ensure we only include sections when posting has real specific content. All have content. Now we need to extract content precisely, preserving all substantive information, not inventing or summarizing away detail. We must not include boilerplate like "The above statements are intended to describe the general nature..." etc. Also remove "Eligibility Requirements May Apply For The Following Benefits" maybe it's part of benefits but we need to keep the list. We need to remove duplicated lines, application instructions, etc. Let's extract each piece. About the role: "If you’d be excited to work in a professional kitchen preparing and cooking meals, consider applying for the position of Deli Clerk. As one of the fastest growing natural foods retailers, we’re seeking team members who are excited to share their passion for food." That's the overview. Responsibilities: The list after "Overview Of Responsibilities At Sprouts Farmers Market, the Deli Clerk is responsible for:" then bullet-like sentences separated by line breaks. Let's capture each: - Assisting customers in making healthy food choices by preparing “fresh and easy meals” - Providing a high level of customer service and ensuring that Deli items are properly prepared, packaged, and presented, always ensuring cleanliness of the Deli department area - Filling, maintaining, and rotating products and displays - Preparing special orders and party trays - Operating meat and cheese slicers, ovens, microwaves, cutting tools, scales, and other deli equipment following company standards and procedures - Maintaining a clean, safe, and sanitary deli area and equipment including cleaning shelves and products, keeping floors free of spills, removing hazardous debris from floor, and sweeping - Receiving, inspecting, and logging products for accuracy of shipment, temperature, and quality Also there is a sentence: "If you thrive in a fast-paced environment, we want to hear from you!" That's more of a call to action, maybe not a responsibility. Could be omitted as boilerplate? It's not a responsibility but it's part of posting. Might be considered fluff. But we need to preserve all substantive information; it's not boilerplate. Could include as a paragraph after responsibilities? Might be considered application encouragement. Might be okay to keep as a paragraph under responsibilities? But guidelines: remove duplicated lines, application instructions. This is not application instruction but a encouragement. Might keep as a short paragraph. Qualifications: list after "Qualifications To be a Deli Clerk at Sprouts Farmers Market you must:" then bullet-like sentences separated by semicolons or line breaks. Let's extract each: - Be at least 18 years of age and have a high school diploma or equivalent and experience working in grocery, restaurant, or related field; or an acceptable combination of education and experience. - Be dependable and reliable - Have and show an outgoing, friendly behavior with a positive attitude and the ability to interact with our customers - Have the ability to work a flexible schedule that changes as the business changes, including nights, weekends and holidays. - Have good communication skills; and the ability to take direction and participate in a team environment - Be able to answer phones and take special orders - Must be able to lift/carry product horizontally/vertically weighing up to 70 lbs., from 4” to 60”, for a distance up to 20 feet without mechanical assistance for up to 4 hours - Must be able to stand for up to 4 hour continuously, for a total of 8 hours per shift. - Perform general housekeeping in the department; clean and sanitize work area (including tables, floor, walls, cases, cooler, freezer, etc.). - Operate a slicer, wrapping and cooking equipment; assisting in maintaining all equipment in safe working condition. - Adhere to all safety, health, and Weights and Measures regulations; achieve and maintain a Food Handlers permit - Be able to work in different temperature environments (cooler and freezer). - Other related duties as assigned. Also there is a line: "Have good communication skills; and the ability to take direction and participate in a team environment" maybe duplicate? It's fine. Benefits: after "Benefits In addition to a rewarding career, Sprouts offers a comprehensive program to help support you and your family. These programs include:" then list: - Competitive pay - Sick time plan that you can use to support you or your immediate families health - Vacation accrual plan - Opportunities for career growth - 15% discount for you and one other family member in your household on all purchases made at Sprouts - Flexible schedules - Employee Assistance Program (EAP) - 401(K) Retirement savings plan with a generous company match - Company paid life insurance - Contests and appreciation events throughout the year full of prizes, food and fun! Then "Eligibility Requirements May Apply For The Following Benefits" then list: - Bonus based on company and/or individual performance - Affordable benefit coverage, including medical, dental and vision - Health Savings Account with company match - Pre-tax Flexible Spending Accounts for healthcare and dependent care - Company paid short-term disability coverage - Paid parental leave for both mothers and fathers - Paid holidays We could combine Benefits and Eligibility Requirements under Benefits section, but we need to preserve all info. Could make two subsections? But we only allow

        headings; we could have Benefits heading and then include both lists as
          . Might be okay. Pay: we have DailyPay description. Also "Competitive pay" already in benefits. But we could have Pay section covering Competitive pay and DailyPay. However guidelines: prefer few substantive sections over many thin ones. Could combine Pay and Benefits into one Benefits section? But we have separate headings suggestions. Might be okay to have Benefits and Pay separate. Schedule: we have flexible schedule mentioned in qualifications. Also maybe schedule info elsewhere? Not much else. Could create Schedule section with that point. Now we need to ensure we don't include boilerplate like "The above statements are intended to describe the general nature..." etc. Also remove "Get Paid Every Day! Sprouts Farmers Market offers DailyPay - if you’re hired as an eligible employee, you’ll be able to transfer the money you’ve already earned at no extra cost, and get it the next business day, for free. We offer DailyPay so you don’t have to wait for payday to access the money you’ve already worked for. With DailyPay, you can see how much you’ve made every day and you can transfer your money any time before payday. You can learn more by visiting https://www.dailypay.com/partners/sprouts-farmers-market/." That's substantive about DailyPay; we should keep it but maybe condense? We must preserve all substantive information; we cannot summarize away detail. So we need to keep the description but we can keep as paragraph(s). It's not boilerplate; it's a benefit description. "Why Sprouts Grow with us! ..." That's also substantive about company culture; we could include as a section maybe "About Sprouts" but not in standard headings. Could we include as a paragraph under About the role? Might be okay but it's separate. Could create a section "Why Sprouts" but not in standard list; guidelines say use

          for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). It doesn't forbid other headings, but suggests using those. Safer to stick to those headings. So we could incorporate the "Why Sprouts" content into About the role or Benefits? It's about company culture, maybe fit under About the role. We'll add a paragraph after overview. Now we need to remove duplicated lines, application instructions, legal boilerplate, etc. Also remove "EEO/equal-opportunity/scam-warning". There's a statement: "Sprouts will consider for employment qualified applicants with criminal histories in a manner consistent with the requirements of the Fair Chance in Hiring Ordinance. California Residents: We collect information in accordance with California law, please see here for more information." That's legal boilerplate;

Similar jobs

Deli Clerk

Sprouts Healthy Communities FoundationPalm Harbor, FL· 1 mo ago
Manufacturingapply on jobs.sprouts.com

Deli Clerk

Associated Food StoresSalt Lake City, UT· 2 mo ago
Managementapply on de.jobsyn.org

Deli Clerk

SafewayLakewood, WA· 2 mo ago
Manufacturingapply on eofd.fa.us6.oraclecloud.com

Deli Clerk

Jewel-OscoLake Zurich, IL· 2 mo ago
Managementapply on eofd.fa.us6.oraclecloud.com

Deli Clerk

KrogerLake Charles, LA· 2 mo ago
Manufacturingapply on eluq.fa.us2.oraclecloud.com

Deli Clerk

SafewayAlexandria, VA· 3 mo ago
Manufacturingapply on eofd.fa.us6.oraclecloud.com