Cashier Part Time

We need to output HTML fragment with sections only if real content. Remove boilerplate, navigation, EEO, etc. Keep substantive info: Impact at Lowe's (maybe not a heading? It's intro paragraph). We need headings for sections: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We need to map content. Let's parse the posting: - Intro: "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." - "How We Support You" paragraph about benefits: mentions benefits beyond competitive pay and flexible schedules, health insurance, tuition assistance, 401(k) matching, Employee Stock Purchase Program, 10% Associate Discount, Track to the Trades program, link. - "Your Day at Lowe's" paragraph describing duties. - "Key Responsibilities" bullet list (actually lines without bullet markers but each line separate). Items: Deliver a fast, friendly, and professional checkout experience; Proactively assist customers in the self-checkout area; Scan and bag items accurately and efficiently; Manage a cash register, payments, and exchanges; Answer customer questions; Help maintain a clean, safe workstation; Complete other duties as assigned. - "Minimum Qualifications" list: Reading, writing, and performing basic arithmetic (addition and subtraction); Ability to stand and sit for prolonged periods of time; Experience using a computer, including inputting, accessing, modifying, or outputting information; Minimally lift 10lbs unassisted or over 15lbs with or without accommodation; Obtain sales-related licensure or registration if required by law in your state. - "Preferred Qualifications": Retail and/or customer service experience; Bilingual skills. - Then a paragraph about Lowe's commitment to growth and teamwork extends to community, encouraging bilingual, military, veteran talent to apply. - "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. - "Working Conditions": Environmental factors vary by location... etc. - "About Lowe's": description of company (two similar paragraphs duplicated). We need to keep substantive info but not duplicate. Likely we can keep one concise description. - Then EEO statement and Starting rate of pay may vary... plus link to benefits again. We need to remove boilerplate: EEO, legal, duplicated lines, application instructions (none), cookie/navigation. We need to decide which sections to include. We have content for: - About the role: Could be the intro "Your Impact at Lowe's" and maybe "How We Support You"? But "About the role" heading expects description of role. Could use "Your Impact at Lowe's" and "Your Day at Lowe's". But we need to follow instruction: use

for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). So we should use those exact headings if we have content. Thus we need to map: - About the role: maybe combine "Your Impact at Lowe's" and "How We Support You"? Actually "How We Support You" is about benefits, not role. But we could put role description in About the role: "As a Lowe's cashier, you'll ensure every customer exits Lowe's on a high note..." plus "Your Day at Lowe's" description. - Responsibilities: the Key Responsibilities list. - Requirements: Minimum Qualifications. - Qualifications: Preferred Qualifications? Or we could treat Requirements as minimum qualifications, Qualifications as preferred qualifications. - Skills: maybe bilingual skills? Could be part of Qualifications. But we could have Skills section for bilingual skills? However we already have Preferred Qualifications includes bilingual skills. Might be better to put under Qualifications. - Benefits: we have benefits described in "How We Support You": health insurance options, tuition assistance, 401(k) matching, Employee Stock Purchase Program, 10% Associate Discount, Track to the Trades program. Also mention competitive pay and flexible schedules (but we shouldn't create Pay or Schedule sections unless explicitly stated). Pay: they mention competitive pay but not specific; we should not create Pay section because it's vague? The instruction: never create Pay/Schedule/Benefits sections unless the posting actually states them. They do state benefits (list). They mention competitive pay and flexible schedules but not specific numbers. Should we create Pay section? It says "competitive pay" but not specific; that's still stating pay exists but not a number. The instruction: "never create Pay/Schedule/Benefits sections unless the posting actually states them." It says "states them" meaning mentions pay or schedule? It says "competitive pay" is stating pay exists. However they also say "Prefer a few substantive sections over many thin ones." And they say "never emit a heading followed by filler/placeholder text (e.g. 'commensurate with experience', 'not specified', 'N/A', 'varies', 'TBD')". "competitive pay" is not filler; it's a statement. But they also say "never create Pay/Schedule/Benefits sections unless the posting actually states them." Since they state competitive pay, we could include a Pay section with that statement. However they also say "Prefer a few substantive sections over many thin ones." Might be better to incorporate pay info into Benefits or About the role? But they said to use headings for Benefits, Pay, Schedule if present. Since they mention competitive pay and flexible schedules, we could include Pay and Schedule sections. However flexible schedules is schedule info. They mention "flexible schedules". So we could have Schedule section with that statement. But we need to check if they actually state schedule: "As a Lowe's associate, you'll gain access to many benefits beyond competitive pay and flexible schedules." That's a statement about benefits beyond competitive pay and flexible schedules. So they mention flexible schedules as a benefit. So we could include Schedule section with that statement. But we need to avoid filler like "varies". Not applicable. Thus we could have: - Benefits: list of specific benefits (health insurance, tuition assistance, 401(k) match, ESPP, 10% discount, Track to the Trades). Also maybe mention competitive pay and flexible schedules? Actually those are separate. - Pay: "competitive pay" (maybe also mention that starting rate may vary based on factors... but that's later in EEO part; we should remove that as boilerplate? It's near the end: "Starting rate of pay may vary based on factors including, but not limited to, position offered, location, education, training, and/or experience." That's more detail but still about pay. However that sentence appears in the EEO/legal boilerplate? It's after the benefits link. Might be considered boilerplate but it's still about pay. The instruction: remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate. That sentence might be considered part of EEO/legal? It's about pay variation; could be considered boilerplate. Safer to omit it. Thus Pay section: just "competitive pay". But that's thin. Might be better to omit Pay section and incorporate into Benefits? But they said to use Benefits heading for benefits. Pay is separate. Given the instruction to prefer few substantive sections over many thin ones, maybe we should not create Pay or Schedule sections because they are thin (just a phrase). Instead we could incorporate that info into Benefits section as part of "benefits beyond competitive pay and flexible schedules". But the Benefits section should list benefits; we could mention that they offer competitive pay and flexible schedules as part of benefits. That would be substantive enough. Thus we can have Benefits section that includes: competitive pay, flexible schedules, health insurance options, tuition assistance, 401(k) match, Employee Stock Purchase Program, 10% Associate Discount, Track to the Trades program. That seems substantive. Thus we will not create separate Pay or Schedule sections. Now we need sections: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits. Do we have Skills? Could list bilingual skills as a skill. But we already have Preferred Qualifications includes bilingual skills. Could put under Qualifications (preferred). Or we could have Skills section for bilingual skills. However we already have Qualifications (maybe split into Requirements and Qualifications). We'll treat Requirements as minimum qualifications, Qualifications as preferred qualifications. Skills maybe not needed. But we need to follow the instruction: use headings for those sections only if we have real specific content. We have content for About the role, Responsibilities, Requirements (minimum), Qualifications (preferred), Benefits. Skills maybe not needed; we could omit. Thus output:

About the role

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. Your day may involve answering customer questions, assisting with payments and exchanges, and, 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.

Responsibilities

• Deliver a fast, friendly, and professional checkout experience
• Proactively assist customers in the self-checkout area
• Scan and bag items accurately and efficiently
• Manage a cash register, payments, and exchanges
• Answer customer questions
• Help maintain a clean, safe workstation
• Complete other duties as assigned

Requirements

• Reading, writing, and performing basic arithmetic (addition and subtraction)
• Ability to stand and sit for prolonged periods of time
• Experience using a computer, including inputting, accessing, modifying, or outputting information
• Minimally lift 10lbs unassisted or over 15lbs with or without accommodation
• Obtain sales-related licensure or registration if required by law in your state

Qualifications

• Retail and/or customer service experience
• Bilingual skills

Benefits

• Competitive pay and flexible schedules
• Multiple top-tier health insurance options
• Tuition assistance program
• Company-matching 401(k)
• Optional Employee Stock Purchase Program
• 10% Associate Discount
• Track to the Trades program to learn new trade skills

We should also maybe include a short paragraph about Lowe's commitment to community encouraging bilingual, military, veteran talent. That is substantive but not fitting into any of the headings. Could we add a section like "About Lowe's"? The instruction list includes About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. Not About Lowe's. But we could include it under About the role? Might be okay to add a paragraph about Lowe's after About the role? But we should not invent headings not listed. However we could incorporate that info into About the role as extra sentence. But it's about company, not role. Might be better to add a separate section like "About Lowe's" but not in allowed headings. 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 exclusive list. But they say "Use

for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." It