Cashier Interview Questions & Answers

1. Tell me about yourself.

Why they ask: To calibrate tone, warmth, and how you frame yourself in 45 seconds. A register is a talking job — if you can't do a friendly, focused intro to a manager, they can't picture you doing it with a customer.

"I've spent the last eighteen months at the front end of a grocery store where we run twelve lanes at peak, ringing about a hundred and forty transactions on a busy Saturday shift with an average scan rate around twenty-two items a minute. My drawer variance has been under a dollar every close since I finished training. Before that I was in food service through my last year of school, which is where I first learned that the customer is either leaving calm or telling ten people they didn't, and there's no in-between. What I like about this store specifically is the front-end pace — you run higher volume than my current store, and I want a register where I can get faster and better. I'm looking for a store where I can grow into a customer-service-desk role over the next year or two."

2. Why do you want to work here specifically?

Why they ask: Cashier hiring managers see a lot of "I need a job" applicants. They're trying to find out whether you'd have applied at the store next door just as fast — and if so, they'd rather hire the person who wouldn't.

"I've been shopping at this store for about two years, mostly on Sunday mornings — I know your front end runs eight lanes plus a manned self-checkout, and your customer-service desk stays busy through the whole morning. What I like about this location is that it's high enough volume that a cashier who's good gets recognized quickly, and I've heard from two current employees that you promote from the front end into the service-desk role rather than hiring outside for it. On top of that, this store is on a bus line I already take, which means I can commit to weekend opens without a transportation risk. Specific store, specific volume, specific growth path — that's why I applied here first."

3. Tell me about a time you defused an upset customer at the register.

Why they ask: The single most important behavioral for a cashier. They want to hear that you defuse instead of escalate, that you find a real solution, and that the customer left in a better mood than they arrived — without holding up the line behind them.

"A customer got to the register with an item that rang up two dollars higher than the shelf tag she'd photographed. She was already frustrated because it was her third stop of the morning. My task was to solve it in a way that respected policy but didn't send her out angry — and to do it without stopping the four-person line behind her. I acknowledged the frustration first — 'that's the shelf price, I'll honor it' — and I keyed the price override manually to the tag price rather than making her wait while I sent someone to check the aisle. I flagged the SKU on a sticky note for my front-end lead to walk during the next lull so the tag would match by afternoon. She left with the corrected price in under thirty seconds of extra time, and the customer behind her thanked me for keeping the line moving. She's come through my lane twice since and asked how the tag got fixed."

4. Tell me about a time you caught a mistake at the register.

Why they ask: Cashiers who catch their own errors save the store money and preserve customer trust. They want a specific example, a specific mechanism, and evidence you noticed something before it turned into a variance or a chargeback.

"During a rush, a customer was buying twelve of the same yogurt cup and I noticed one had scanned twice — the running total climbed by the price of one cup, then again a half second later. My task was to catch it before the total was finalized rather than backing out a completed transaction. I stopped, said 'quick check' out loud, voided the extra scan on the running receipt, and re-tallied. Total corrected before payment, no manager keypunch needed. The customer thanked me — 'I would have noticed at home and been annoyed' — and I finished the ring in under twenty seconds of extra time. The habit I keep is watching the running total shift after each scan and stopping the second something moves wrong, because a caught error at the belt is a five-second fix and a missed one is a fifteen-minute return."

5. Tell me about a time you kept a long line moving.

Why they ask: This is the operational heart of a cashier role. They want a specific number and a specific mechanism — not "I worked fast."

"On a Sunday after a football game, our front end went from four lanes to a nine-cart deep queue in about ten minutes and my ASM was in the back. My task was to clear the line without cutting service. I did three things. First, I paged over the intercom for a second cashier — the store's policy is 'call for backup when the third cart is on the belt,' and I do it every time. Second, I stopped the small talk with the customer I was ringing, without being rude — I stayed warm and finished the transaction in a focused thirty seconds. Third, when I saw the customer three back had two items, I quietly asked the person ahead of him if it was okay to let him through, which usually gets a yes. My scan rate went to about twenty-five items a minute, the second cashier opened lane two, and we cleared the queue in about eight minutes. Nothing dropped, no drawer error, and I still got a 'thanks for keeping it moving' from three of them."

6. Tell me about a time you had a conflict with a coworker.

Why they ask: Front-end teams work shoulder to shoulder in a small space for eight-hour shifts, and one unresolved conflict poisons the lanes. They want to hear you address issues directly and low-drama, not vent to a manager or the group chat.

"A coworker and I kept clashing over closing — she'd leave partial go-backs at her lane so the next opener had to shelve them, and I'd been picking them up on opens. I asked her to grab five minutes before a shift and I named it plainly: our opens were slower because the previous close wasn't fully cleared. Rather than argue whose responsibility it was, I proposed we walk our own go-backs to the aisle in the last twenty minutes of every close, and I offered to cover her lane if she needed a hand. Go-backs stopped stacking on opens, and we ended up better teammates for it because we'd talked directly instead of quietly resenting each other. Two months later she covered a Saturday shift for me on ninety minutes' notice, and I don't think she would have if we hadn't had that first conversation."

7. Tell me about a time you had to admit a mistake with money.

Why they ask: A cash-handling role runs on trust. They want to hear you own errors quickly rather than hoping the drawer variance gets absorbed into the noise.

"On a Friday evening close, my drawer was seventeen dollars over. Instead of writing it off as a mystery, I flagged it to my front-end lead the same shift and stayed to help her walk the transactions. We pulled the electronic journal and found I'd rung a return as store credit when the customer had paid cash — I'd given her the credit slip but hadn't taken the cash out of the drawer to refund. My lead called the customer, explained the error, and offered to mail her the cash refund the next business day. The customer appreciated the call. I filed the variance report the same night rather than the next morning, and my lead's note on it was 'reported by cashier — no coaching needed.' The lesson I still apply is that a variance you find first is a mistake; a variance found for you starts to look like a pattern."

8. Tell me about a time you noticed a coworker doing something dishonest.

Why they ask: Front-end shrink often comes from inside — sweethearting, cash refunds pocketed, coupon fraud. They want to see you'd report to a manager rather than confront the coworker or look away.

"I noticed a coworker was regularly voiding transactions after cash payment and keeping the cash — the customers had already walked, but the electronic journal was showing a pattern I didn't like. Our policy is clear: never confront the coworker, never accuse them publicly, and never handle it directly. I asked my front-end manager for five minutes at the start of my next shift, showed her the specific transactions I'd noticed on my adjacent register's screen, and let her take it from there. Loss prevention handled the investigation, the coworker was let go, and I never had to be the person who did the confrontation. What I learned is that reporting is not disloyalty — the honest coworkers on the team are protected by it, and I'd want the same if the pattern were mine by accident."

9. Tell me about a time you worked with very little supervision.

Why they ask: A front-end manager isn't standing over you for most of your shift, and overnight shifts often run with one or two cashiers and a manager working paperwork in the back. They want to hire someone who runs the register the same way whether or not anyone is watching.

"On a Sunday overnight, my front-end lead was in the office reconciling deposits and there was one other cashier at the far register. A customer came through with a large mixed cart — grocery plus a return plus a WIC voucher — and it was exactly the kind of transaction where a cashier under no supervision might cut corners. I ran it by the book: return first so the credit posted, WIC-eligible items separated on the belt and rung in the WIC-first sequence, produce PLUs keyed rather than eyeballed, and the split-tender balance run through the customer's card for the WIC-ineligible items. Transaction took about seven minutes, no errors, drawer balanced at close. My lead told me the next morning she'd watched me on camera for a stretch and had nothing to coach. That kind of independence is how I default to working."

10. Where do you see yourself in three to five years?

Why they ask: They're trying to figure out whether you're a two-month stopgap or someone worth training for a service-desk or shift-lead path. Retailers spend real money onboarding, and turnover is expensive on the front end.

"Three years out, I want to be at the customer-service desk or a shift lead, ideally at this company. The path I'd want is: master the register and every tender in the first ninety days, get certified on returns, money orders, and the desk's back-office functions inside the first year, take on training new cashiers by month twelve, and be promotable to service-desk lead in year two. Five years out I'd like to be an ASM at the front end of a location like this one, and I'd rather grow up through one store than bounce between three. That's the kind of ownership I'm coming here to build."

11. Why are you leaving your current cashier job?

Why they ask: A gut check on maturity and how you talk about employers. Bad-mouthing the current store is a fast disqualifier — it's exactly what they'll expect you to do about them in a year.

"My current store has been a good place to learn — my front-end lead taught me most of what I know about balancing a drawer and handling a return without a receipt — but the store's volume has softened, my hours have been cut to about eighteen a week, and I'm getting scheduled off peak so I'm not building the transaction volume I want. I'm looking for a busier front end where I can run more transactions and grow into a service-desk role within a year or two. This location has both, which is exactly why I applied here first."

12. What does your availability look like — nights, weekends, holidays?

Why they ask: This is the highest-signal question in a cashier interview and the one most candidates fumble. A vague answer here quietly costs offers.

"I'm available Monday through Saturday, with Sundays off. I can open on weekdays — my earliest is 5 a.m. — and I can close every night except Tuesday, when I have a class that ends at 8:30 p.m. Saturdays I'm open bell to bell. On holidays I'm available for the day before and the day after Thanksgiving, all of the pre-Christmas weekend, and December 26 and 27; I can't work Thanksgiving Day or Christmas Day because of a family commitment, but I can pick up an extra shift in the surrounding week to trade for it. If the schedule tends to change week to week, I just ask for a week's notice where possible so I can plan around my class."

13. Walk me through how you'd ring a sale that includes a return, a new item, and a gift card as partial tender.

Why they ask: A concrete test of whether you've actually run a POS at volume. The mechanics should be automatic — if you hesitate on the sequence, you'll be a slow line under a queue.

"I'd start with the return so the credit is on the transaction — scan or key the return item, confirm the receipt or lookup by card if it's a receipt-less return per store policy, apply the credit. Then I'd ring the new item, either scanning it or keying the SKU if the barcode won't read. Once the total shows the new balance owed after the return credit, I'd apply the gift card as first tender, watching to see if it covers the balance or leaves a remainder — most POS systems will prompt for a second tender automatically. I'd take a card or cash for the remainder, hand back the receipt and, if the gift card has a residual balance, the card with the balance printed on the receipt. Then I'd flip the pad for the signature or tap prompt and thank the customer by name if I have it. Sequence matters — running the return second makes the math messier and slows the line."

14. What POS systems have you used, and which do you know best?

Why they ask: Skills transfer between registers, but naming the specific system saves the manager a training day. They want the honest inventory — including 'I haven't used yours but I ramped on my last one inside a shift.'

"I've run NCR Advanced Checkout at my current grocery store for the last eighteen months — full transactions, returns, produce PLU entry, WIC and EBT tenders, coupon redemption, and end-of-shift close. Before that I used Toshiba TCx Sky at a big-box for six months, which is where I first learned the split-tender and price-match functions. I've done a couple of shifts on Square for Retail at a friend's boutique, so I know the basic ring and return flow but wouldn't call myself deep on it. If you're on IBM's Toshiba stack or an ISS45 setup, I'd expect to ramp inside a shift — the fundamentals of tender types, discounts, and returns transfer, and I always ask to be walked through voids, no-sales, and refunds specifically before I run one live."

15. How do you count down a drawer at the end of a shift?

Why they ask: A cash-handling role runs on this. They want to see structured mechanics — bills sorted, coin counted, deposit reconciled — not vague hand-waving.

"I close in a set order so nothing gets skipped. First I run a mid-shift skim if any large bills are stacking up — anything over a hundred dollars in fifties or hundreds goes to the safe drop mid-shift, per policy. At close, I run the register's Z-report to get the expected drawer total. Then I count the cash — bills sorted face-up by denomination, banded in standard straps at $100 for ones, $250 for fives, $500 for tens, $2,000 for twenties; coin counted or rolled to policy. I subtract the starting float, compare against my counted amount, and if it's off, I count a second time before recording a variance — usually the mistake is in the coin or the float carry-over. I fill in the deposit slip, seal the deposit bag, log the variance if any, and store the float for the next shift per policy. Anything over a five-dollar variance I flag to my manager same-shift rather than let it show up on the daily report."

16. A customer wants to pay part with EBT / SNAP, part with WIC vouchers, and the rest on a debit card. How do you handle it?

Why they ask: Multi-tender transactions with WIC and EBT are the kind that go wrong the first time a new cashier tries them, and they can hold up a line for ten minutes. They want to see you know the sequence and the eligibility rules.

"I'd separate the belt into three groups before I start scanning — WIC-eligible items first, SNAP-eligible items second, non-eligible items last — because the sequence saves us from having to re-tender halfway through. I ring the WIC items first and process the WIC voucher, which requires matching the exact eligible product list on the voucher; if a substitution is needed, I flag it before the swipe, not after. Then I ring the SNAP-eligible items and run the EBT tender for that subtotal — SNAP won't cover taxable items like hot deli food or prepared items, so those get grouped in the third tender. Finally I ring the remaining non-eligible items and run the debit card for the balance. I keep a calm cadence and narrate what I'm doing — 'we'll do the WIC first' — because customers using these tenders often expect a hassle, and the tone shift matters."

17. A customer wants to return an item without a receipt. What do you do?

Why they ask: Testing whether you apply policy with judgment or robotically. Retail managers want cashiers who protect the store and the customer relationship at the same time.

"I'd start by looking up the transaction — most systems can find the sale from the customer's card even without a receipt if it's within thirty to sixty days. If I can find it, I run the return normally. If I can't, I explain the store's receipt-less return policy plainly — usually store credit at the lowest recent sale price, with an ID captured for the return-tracking system — and if the item is above the receipt-less limit or the customer's return history flags in the system, I escalate to the customer-service desk or a manager for a final call rather than promising something I can't deliver. I never make up a rule on the spot, and I never argue policy with a customer — I explain what I can do and hand off to a lead where the answer is no. The goal is that the customer leaves knowing exactly what will happen next, even if the answer isn't what they wanted."

18. A customer's produce doesn't have a sticker. Walk me through what you do.

Why they ask: Produce codes are one of the top-three ways a new cashier slows a line, and one of the top-three ways shrink creeps in. They want to see you know the mechanism and don't just guess.

"I never guess a produce code — the wrong one costs the store money or overcharges the customer. Most POS systems have a produce-lookup button that lets me search by name; I use that first. If the search returns multiple varieties — say Fuji versus Gala apples — I ask the customer which it is rather than assume, because organic and conventional codes differ by $0.20 to $1.00 a pound and I can't eyeball that. I weigh the item on the built-in scale, confirm the tare weight is zeroed if it's in a plastic bag, key the PLU, and confirm the price on the display before moving to the next scan. I keep a mental list of the store's ten most-asked codes — bananas, Roma tomatoes, avocados, limes, russet potatoes, yellow onions, cilantro, jalapenos, green bell peppers, and lemons — so those don't slow me at all. If I really can't identify it, I call for the produce manager on the intercom rather than guess."

19. A coupon looks suspicious — a photocopy, or a barcode that doesn't match the item. How do you handle it?

Why they ask: Coupon fraud is a top-three shrink driver at grocery. They want to see you know the tells, follow the mechanics, and don't embarrass the customer while doing it.

"I check three things quickly on every coupon: the expiration date, the item eligibility, and the barcode. If it's a photocopy — the paper's wrong, the fold marks are wrong, or the barcode is blurry — the register usually won't take it and I've saved myself the awkward conversation. If the register does take a coupon that shouldn't scan, or the coupon rings a discount that doesn't match the item in the cart, I stop the transaction politely — 'looks like this one won't apply to this item, let me get a quick lead check' — and I page the front-end lead rather than accuse the customer. Most of the time it's a customer who used a coupon site that generated a bad printout; sometimes it's not. Either way, the answer is a calm hand-off, not a confrontation. Loss prevention prefers we don't accuse — we just don't accept."

20. The register goes down mid-shift and management asks you to keep ringing on paper for ten minutes. What do you do?

Why they ask: Rare, but it happens — and the cashiers who can do the math on paper get moved to service desk faster. They want to see comfort with mental math and a manual receipt.

"I'd grab the paper receipt pad and a calculator if allowed, and I'd tell each customer up front the transaction is running manual so they can decide whether to wait. For each item, I record the SKU or description, the shelf price, and the taxable/non-taxable status. I keep a running tape on the calculator for subtotal, apply tax at the state or store rate to the taxable subtotal, add coupons and store discounts as line-item deductions, and total. I count out change from the drawer by counting up from the total to the amount tendered — the classic 'thirty-two, then eight makes forty, then ten makes fifty' — so I never lose track. I hold every manual receipt in a stack for my front-end lead to re-enter into the system when it's back up. It's slower — maybe half the normal pace — but the drawer still balances at close because every line is on paper."

21. A customer asks for a competitor price match. Walk me through your policy.

Why they ask: Price matching is a common front-end pause point, and a cashier who knows the rules is faster than one who calls for a lead every time.

"First I confirm the store's price-match policy — every retailer's is different — which usually specifies which competitors qualify, whether the match applies to online prices, which categories are excluded (electronics, seasonal, clearance), and the maximum discount that can be applied without a lead override. I ask the customer to show me the competitor's ad, receipt, or website — screen-share is fine at most stores now — and I verify the exact product, the exact size, and the current date on the competitor's listing. If it matches within policy, I key the price-override function to the competitor price and note 'PM' in the transaction. If it's outside policy or above my override threshold, I call for my lead rather than deny — the customer's ask is legitimate, the answer just has to come from someone with the button. Fast, calm, no arguing over policy at the belt."

22. A customer buys beer or tobacco and looks close to the legal age line. What's your procedure?

Why they ask: Age-restricted transactions are the single fastest way a cashier can cost the store a fine and their own job. They want to see you card every time and know how to spot a fake ID without a lecture.

"I card every customer buying alcohol or tobacco, every time, regardless of how old they look — most retailers have a 'card everyone under 40' or 'card everyone' policy, and I follow whichever one this store has. I take the ID in my hand — I don't just look at it in the customer's wallet — and I check three things: the birthdate math against today's date, the physical characteristics against the customer (photo, height, eye color), and the ID's security features (holograms, correct font, no smoothing or reprint marks around the photo). The POS prompts me to key the birthdate, which I do rather than pressing 'over 21' — the key-in creates a compliance record. If the ID looks off or the customer refuses to hand it over, I decline the sale politely — 'I can't ring the alcohol, but I can ring the rest' — and I page the lead. I never argue an age refusal at the belt."

23. A customer is yelling at you about a price. What do you do?

Why they ask: Testing composure. They want to see you don't escalate, don't argue, and don't take it personally — while still moving the line.

"First I'd drop my volume rather than match theirs — 'I hear you, let me look' — because tone drops de-escalate faster than words do. I'd check the shelf price on the SKU if it's on my screen or call the department for a quick shelf-check while I keep the transaction paused. If the shelf tag matches their claim, I'd override to the tag price and note the discrepancy for the aisle team; if it doesn't, I'd explain plainly what I see and offer to hold the item while the lead confirms. If the customer stays escalated, I'd page the lead and stay calm — I don't argue back, I hand off. What I never do is match the customer's volume, deny before I've checked, or roll my eyes for the line to see. The customer behind them is watching, and how I handle this call decides whether they come to my lane next time or someone else's."

24. A friend comes through your line and asks you to give her the employee discount.

Why they ask: One of the ethics-question staples. A candidate who bends here is a candidate who will bend at the drawer later.

"I'd say no calmly and specifically — 'I can't ring the employee discount on this, it's non-transferable and it'd get us both in trouble,' and I'd ring the sale at full price. If she pushed, I'd repeat the answer once and move on, and I wouldn't apologize for it because there's nothing to apologize for. What I wouldn't do is get into a debate at the belt with a line behind her, and I wouldn't run the discount and tell myself I'd never do it again. The policy exists for a reason — every store's employee-discount fraud pattern starts with 'just this once for a friend,' and I've watched people lose their jobs over it. If she'd like to come shop with me on a day I'm off and I want to use my own discount on my own purchase, that's a different conversation."

25. You see a customer at self-checkout skipping items past the scanner. What do you do?

Why they ask: The self-checkout attendant is a common early-shift assignment for a cashier. They want to see you follow policy — usually 'do not confront' — and use the tools available.

"Store policy on this is almost always: never confront the customer, never chase, and never accuse. What I'd do is walk over calmly under the pretense of helping — 'looks like the scanner's giving you trouble, let me help with that one' — and re-scan the item openly. Most 'skips' stop the moment the customer realizes the attendant is watching, and it saves the transaction without a confrontation. If the pattern continues after the intervention, I'd radio my lead or loss-prevention discreetly with the lane number and let them decide next steps. I document what I saw at the end of the shift on our incident log. What I don't do is grab the item back, raise my voice, or block the customer's exit — that's how attendants get hurt and stores get sued."

26. A customer at the register wants to chat while ten people are in line behind them. How do you handle it?

Why they ask: Front-end managers are trying to hire someone who's warm and fast — most people are one or the other. They want to see how you preserve both.

"I stay warm but pick up the pace of my hands rather than my words. I keep the conversation going — 'sounds like a busy weekend' — but my scanning stays at full speed, and I finish the transaction in the same rhythm I would with anyone else. When I hand back the receipt, I close the loop cleanly — 'take care, come back soon' — and move to the next customer without cutting them off mid-story. Most people read the visual cue that the line is deep and either wrap it up naturally or come back to chat another day. What I'd never do is snap 'I've got a line' — that turns a chatty customer into an angry one, and now I have two problems instead of one."

27. A customer's card gets declined in front of a line.

Why they ask: Handled poorly, this embarrasses the customer, breaks trust, and slows the line — the trifecta of a bad checkout. They want to see discretion.

"I don't say 'declined' out loud — the whole line is listening. I say quietly, 'looks like it didn't go through — do you have another card you'd like to try?' and I hand the card back with the tap or dip motion suggested rather than commented on. If they don't have another card, I offer to hold the cart at the customer-service desk under their name so they can come back — that gives them a way out that isn't 'now I have to put groceries back with everyone watching.' Nobody in line hears the word decline, the customer leaves with dignity, and I keep the line moving. The habit here is that you protect the person you're ringing, always — the line will forgive a thirty-second pause; the customer won't forgive being embarrassed."

28. Your drawer is short forty dollars at the end of a shift and you don't know why. What do you do?

Why they ask: A behavioral proxy for whether you'll cover a variance or report it. Covering is disqualifying because it starts a pattern.

"I count it a second time to make sure the shortage is real — sometimes coin miscounts to fives or tens by mistake. If it's still short, I report it to my front-end lead the same shift and fill out the variance report — I don't try to cover it out of pocket, and I don't hope it goes unnoticed. My lead and I look at the electronic journal for the shift and try to identify the transaction it came from — a miscounted change return, a missed void, a refund that ran to cash instead of card. Sometimes we find it; sometimes we don't. Either way, the report is filed and I don't fall into the pattern of covering. Coverage looks generous once and looks suspicious the second time — the honest report is the only path."

29. A customer comes back saying you gave them the wrong change but they've already left the store and can't prove it.

Why they ask: A judgment call that mixes customer service and integrity. There isn't one right answer — they want to hear your reasoning.

"I'd take it seriously without immediately assuming either way. I'd ask which lane they were at, what time, and how much they think they're short — then I'd get my lead involved and pull the electronic journal for that transaction. The system will show the amount tendered and the amount returned, and if my drawer counted long by the same amount at end of shift, that confirms the customer's story. If the numbers match, we refund the difference and apologize. If the numbers don't support the story, my lead can explain what the journal shows and, depending on the amount and the store's practice, either escalate to a manager or offer a store-credit gesture. What I don't do is refuse without checking or refund without checking — both cost the store or the customer more than the honest look."

30. A coworker is being rude to a customer at the next lane over. What do you do?

Why they ask: They want to hear you'd intervene without publicly embarrassing your coworker.

"If I'm not currently ringing someone, I'd step over and offer to take the customer at my lane — 'I can help you right over here,' calmly — which pulls them out of the escalation without making it a scene. If I am ringing someone, I'd finish that transaction and then check in with the coworker after the customer has left — 'looked rough, everything okay?' — because sometimes the coworker just needs a five-minute break or a heads-up they were showing stress. If the pattern repeats across shifts, I'd mention it to the front-end lead privately at a shift-change; I wouldn't screenshot it into a group chat or bring it up in front of other coworkers. The move is to protect the customer in the moment and give the coworker a chance to reset before making it a management issue."

31. The store's WiFi goes down and cards aren't processing. Ten people are in your line.

Why they ask: How you communicate under pressure. They want to see triage, not panic.

"I'd announce the situation to the line calmly and clearly — 'the card system is down store-wide, we're taking cash only until it's back, and I'll page a lead to give you a status.' I'd give each customer the option to pay cash if they have it, park the cart at the customer-service desk for pickup once cards are back, or come back later — and I'd honor the price they're at now for the parked carts. The point is not to keep ringing at all costs; the point is to give the customer a real option and a clear expectation. I'd page my lead over the intercom so the message is one voice, not eight — and I'd keep my tone lower than the frustration in the line, because the room mirrors whoever is at the register."

32. A customer becomes verbally abusive or threatens you.

Why they ask: Testing whether you know when to stop de-escalating and involve a manager or security. Cashiers who don't call for help get hurt.

"I stop the transaction and page the lead over the intercom immediately — 'lead to lane four for a customer concern' — because verbal abuse is the moment where a cashier has to hand off, not keep ringing. I stay calm, I don't argue back, I don't match volume, and I don't touch the customer or their belongings. If they threaten a specific harm, my lead's call is to involve security or, at grocery, to call the store's manager-on-duty who has the authority to ask the customer to leave. I write the incident up in the log the same shift with time, lane, and specifics. What I don't do is try to be the hero and de-escalate a threat — that's what leads and loss prevention are trained for."

33. A customer tries to return an obviously used or worn item within the return window.

Why they ask: Judgment on policy versus customer preservation. They want to hear that you'd escalate rather than deny or accept unilaterally.

"I'd look at the item, check the return window, and check whether store policy allows returns on worn or used items — for grocery, most food returns are refused for safety reasons; for general merchandise, worn items usually go to store credit rather than a refund, with manager discretion. If it's outside my policy latitude, I'd say plainly, 'I can't take this on my register, but let me get my lead so we can look at it together,' and I'd escalate calmly. What I wouldn't do is accuse the customer of using the item, deny without checking, or accept a return I don't have the authority to accept. Escalate cleanly and let the lead make the discretionary call — that's what leads are there for."

34. Your ride falls through the morning of a Saturday open shift. What do you do?

Why they ask: A pointed reliability test. They want to hear you take ownership of getting to the shift, not that you'd call out.

"First I'd call the store — not text — as soon as I know, so my lead has a real conversation with a plan, not a heads-up that I'm not coming. Then I'd exhaust the alternatives: rideshare, a coworker who might swing past, a bus route that gets me there thirty minutes late, a family member. If the answer is I really can't get there, I'd offer to swap the shift with someone else in the group chat and take one of theirs later in the week. If the answer is I can be there late, I'd communicate the ETA and offer to stay late to make up the coverage. What I wouldn't do is text 'not coming' and go back to sleep — that's the behavior that ends a job."