Jobs · Customer Service · Pennsylvania

Full Time - Cashier - Closing

Lowe's Companies, Inc. · Monaca, PA · 4 wk ago
Customer Service$83/hrFull-time
We need to output HTML fragment with sections only if real specific content. Must not include boilerplate like EEO, navigation, legal, etc. Must not repeat job title as heading. Must use

for section headings: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. Use
  • for any list of duties/requirements/benefits. Use

    for prose. We need to extract substantive info from posting. Let's parse: - Opening: "Your Impact at Lowe's As a Lowe's cashier, you'll ensure every customer exits Lowe's on a high note. Your work helps our stores positively serve our customers and communities by providing a quick, friendly checkout experience and helping customers get the best value for their money." That's prose about role. - "How We Support You Whether you need a part-time position or a place to plant yourself and grow, Lowe's is ready to support your goals. As a Lowe's associate, you'll gain access to many benefits beyond competitive pay and flexible schedules. Make your well-being a priority with multiple top-tier health insurance options. Explore educational opportunities with Lowe's tuition assistance program. Take charge of your financial future with a company-matching 401(k) and optional Employee Stock Purchase Program. Gain extra savings with a 10% Associate Discount. Learn new trade skills with our Track to the Trades program. For information about our benefit programs and eligibility, please visit https://talent.lowes.com/us/en/benefits." That's benefits info. - "Your Day at Lowe's Whether you're answering customer questions or assisting with payments and exchanges, your job as a cashier is to ensure every customer leaves our stores satisfied. While most of your time will be spent at the register, you may be expected to engage in other activities as needed, such as helping other departments, stocking shelves, or moving carts. If you enjoy helping customers and solving problems in a fast-paced environment, this is the perfect role for you." That's description. - "Key Responsibilities Deliver a fast, friendly, and professional checkout experienceProactively assist customers in the self-checkout areaScan and bag items accurately and efficientlyManage a cash register, payments, and exchangesAnswer customer questionsHelp maintain a clean, safe workstationComplete other duties as assigned" That's a list of responsibilities. - "Minimum Qualifications Reading, writing, and performing basic arithmetic (addition and subtraction)Ability to stand and sit for prolonged periods of timeExperience using a computer, including inputting, accessing, modifying, or outputting informationMinimally lift 10lbs unassisted or over 15lbs with or without accommodationObtain sales-related licensure or registration if required by law in your state" That's qualifications. - "Preferred Qualifications Retail and/or customer service experienceBilingual skills" - "Lowe's commitment to growth and teamwork extends to the community as well. To better equip our stores and serve our communities, we strongly encourage bilingual, military, and veteran talent to apply and join our team." That's maybe a note but not required. - "Travel Requirements This role does not require regular travel; however, this role may need to travel occasionally to meetings, training, or to support neighboring stores." Travel info. - "Working Conditions Environmental factors vary by location. You may be working in both inside and outside weather conditions. Exposure to varying climates, including extreme heat or cold, wet, damp, humid, windy, or drafty conditions, is possible. You may be exposed to constant or intermittent noises in addition to moving or shaking objects and equipment. Lifting methods vary based on role, weight, and volume. Associates must follow guidelines, limiting single lifts to 75 pounds. Team lifts are used minimally starting at 75 pounds or when needed. Powered equipment should be used as required, with proper training or assistance from a trained coworker." Working conditions. - "About Lowe’s Lowe’s Companies, Inc. (NYSE: LOW) is a FORTUNE® 50 home improvement company serving approximately 16 million customer transactions a week in the United States. With total fiscal year 2024 sales of more than $83 billion, Lowe’s operates over 1,700 home improvement stores and employs approximately 300,000 associates. Based in Mooresville, N.C., Lowe’s supports the communities it serves through programs focused on creating safe, affordable housing, improving community spaces, helping to develop the next generation of skilled trade experts and providing disaster relief to communities in need. For more information, visit Lowes.com." Then duplicate about Lowe's again with FY2025 sales $86B, 530 branches and 130 distribution centers. That's also about company. We need to decide which sections to include: About the role (maybe "Your Impact at Lowe's" and "Your Day at Lowe's" could be combined as About the role). Responsibilities (Key Responsibilities). Requirements (Minimum Qualifications). Qualifications (Preferred Qualifications). Skills maybe not separate; but we could include Skills if there is specific skill list; but we have bilingual skills etc. Could treat as Skills. Benefits: we have benefits described (health insurance, tuition assistance, 401(k), ESPP, 10% discount, Track to the Trades). That's specific. Pay: posting mentions "competitive pay" but no specific rate; also "Starting rate of pay may vary based on factors..." That's vague; we should not create Pay section unless posting actually states them. It says "competitive pay" but no numbers; also "Starting rate of pay may vary..." That's not specific. According to rule: 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. Since pay is not specific (just says competitive pay, may vary), we should NOT create a Pay section. Schedule: posting mentions part-time or full-time? It says "Whether you need a part-time position or a place to plant yourself and grow". No specific schedule details. So we should not create Schedule section. Benefits: we have specific benefits listed, so we can create Benefits section. Now we need to avoid boilerplate: EEO, legal, navigation, cookie, duplicated lines, application instructions. Also we should not include the "For information about our benefit programs and eligibility, please visit ..." maybe that's okay as part of benefits but it's a link; we can keep as prose. We also need to avoid repeating "About Lowe’s" duplicated; we can include a short paragraph about company maybe under About the role? Actually About the role is about the role, not company. There's no explicit "About the company" heading in allowed list; but we could put company info under About the role? The allowed headings are About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. So we should not add a heading for company overview. However we could incorporate company info into About the role as prose? The rule: Use

    for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). It doesn't forbid other headings? It says use those for section headings. Likely we should only use those headings. So we should not add a heading for company overview. But we could include company info as part of About the role? Might be odd but permissible. However the instruction: "Prefer a few substantive sections over many thin ones." So we could have About the role (including impact, day, maybe company overview). Responsibilities, Requirements, Qualifications, Skills, Benefits. We need to decide what goes where. About the role: combine "Your Impact at Lowe's" and "Your Day at Lowe's" plus maybe brief company overview? But we can keep company overview as a short paragraph under About the role? Might be okay. Responsibilities: list from Key Responsibilities. Requirements: Minimum Qualifications. Qualifications: Preferred Qualifications. Skills: maybe bilingual skills etc. Could also include computer experience etc but that's already in Requirements. We could put bilingual skills under Skills. Benefits: list of benefits. We must not include duplicated lines like the repeated About Lowe's sections. We'll include only one concise company overview. We must not include Travel Requirements, Working Conditions, etc because they are not in allowed headings; but we could possibly include them under About the role? However they are not about role but working conditions. The instruction says to include a section ONLY when the posting has real, specific content for it — never emit a heading followed by filler/placeholder text. It doesn't forbid adding other headings not in the list, but the list is given as examples; but they say "Use

    for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." This suggests we should limit to those headings. So we should not create headings for Travel Requirements or Working Conditions. We could incorporate that info into About the role as prose? Might be okay but it's not directly about role. However we could omit them entirely? The rule says "Preserve ALL substantive information; do NOT invent or summarize away detail." So we must keep all substantive info. If we omit Travel Requirements and Working Conditions, we lose substantive info. But we could embed them under About the role as a paragraph, even if not ideal. The instruction didn't forbid adding other headings, but they gave examples; maybe we can add other headings if needed, but they said "Use

    for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." That implies we should use h3 for any section headings, and the examples are those. It doesn't say we cannot use other headings, but to be safe we should stick to those. However we need to preserve all substantive info; we could put Travel Requirements and Working Conditions under About the role as a paragraph, but that may be mixing topics. Yet it's still preserving info. Alternatively, we could create a section "Working Conditions" using h3, even though not in examples; but the instruction says "Use

    for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." The "e.g." suggests those are examples, not an exhaustive list. So we could add other headings as needed. However they also say "Prefer a few substantive sections over many thin ones." So we should avoid many thin sections. Travel Requirements and Working Conditions could be combined into a "Working Conditions & Travel" section maybe. But we need to decide. Given the instruction to preserve all substantive info, I think we should include sections for Travel Requirements and Working Conditions, maybe combined. But we need to see if they are substantive: they have details about travel occasionally, environmental factors, lifting guidelines, etc. That's substantive. Thus we could have sections: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Working Conditions, Travel Requirements. But we need to check if we should avoid creating Pay/Schedule unless specific. We have no specific pay or schedule, so we omit those. We also need to avoid duplication: there are two About Lowe's paragraphs; we can combine into one. We also need to remove boilerplate like EEO, legal, navigation, cookie, duplicated lines, application instructions. The posting includes "Lowe’s is an equal opportunity employer..." that's EEO boilerplate; we must remove. Also "Starting rate of pay may vary based on factors including, but not limited to, position offered, location, education, training, and/or experience." That's pay info but vague; we should not create Pay section; but we could mention it under Benefits? Not appropriate. Better to omit that sentence as it's filler? It's not filler exactly but it's about pay variation; but we are not making a Pay section, so we could drop it as it's not needed elsewhere. The rule says preserve ALL substantive information

Similar jobs