15 Store Manager Interview Questions (and What to Listen For)

The best store manager interview questions are situational: they ask a candidate to walk through a specific moment, such as a callout on a busy Friday, a conflict between two employees, or an angry customer, so you hear judgment instead of a rehearsed answer. Ask every candidate the same questions, listen for specifics (who, what, when, what they did, what happened), and score against what a strong answer sounds like.

Below are fifteen questions grouped by what they reveal, each with what to listen for and a red flag. They work for retail store and assistant store managers, restaurant general managers, and department managers in hospitality.

By Ryan Reisner, Founder of The Reisner Group and SeekerPitch

How to run the interview so the answers mean something

The questions matter less than how you ask them. A few rules make the answers comparable:

• Ask every candidate the same questions in the same order. It's the simplest way to reduce bias and compare people fairly.
• Ask for real moments. Start with "Tell me about a time…" and follow with "What would you do differently now?" The first shows what they've done; the second shows how they think.
• Follow up for specifics. "What did you say? What happened next? Who else was involved?" Vague answers stay vague until you ask.
• Take notes and score right away, before the next candidate blurs the first.
• Talk less than they do. Silence is an interview tool.

Leading people under pressure

1. "It's Friday night, two people called out, and a table has been waiting forty minutes. Walk me through your next ten minutes."

Strong answer: Prioritizes in order, communicates with the team and the customer, makes a clear call, and explains the trade-offs.

Red flag: Freezes, blames the people who called out, or describes doing everything personally instead of directing others.

2. "Tell me about a time you were badly short-staffed. What did you do?"

Strong answer: Specific actions, who they asked, what they cut or delayed, and what they changed afterward.

Red flag: A story with no decisions in it, or one where the hero is always "I."

3. "Describe a time everything went wrong at once. How did you keep your team steady?"

Strong answer: Describes tone, communication, and keeping people focused, not only fixing the problem.

Red flag: Takes credit for calm while describing a chaotic team.

Coaching and developing people

4. "Tell me about an employee who was struggling. What did you do?"

Strong answer: Diagnoses the cause, has a direct conversation, sets clear expectations, follows up, and can say how it ended.

Red flag: Went straight to discipline, or avoided the conversation until it was too late.

5. "Tell me about someone you helped get promoted."

Strong answer: Names a real person, what they saw in them, and what they did to help.

Red flag: Can't name anyone, or describes people who left as someone else's fault.

6. "How do you train a new hire in their first two weeks?"

Strong answer: A concrete plan with check-ins, not "I show them the ropes."

Red flag: Training means shadowing someone else with no follow-up. The early weeks are when many hires decide whether to stay; more on that in why frontline hires quit in the first 90 days.

Conflict and communication

7. "Two of your employees can't work together. What do you do?"

Strong answer: Hears both sides separately, separates facts from feelings, sets expectations, and checks back.

Red flag: Takes a side quickly, ignores it, or moves one person without addressing the cause.

8. "Tell me about a time you had to deliver bad news to your team."

Strong answer: Is direct, explains the why, listens to the reaction, and follows up.

Red flag: Avoids it, delegates it, or describes spinning it.

9. "Tell me about a time you disagreed with your district manager. What happened?"

Strong answer: Raised it respectfully, with facts, and either changed the outcome or carried out the decision wholeheartedly.

Red flag: Complains about leadership to the team, or says they've never disagreed.

Accountability and standards

10. "Tell me about a time you missed a number, such as sales, labor, or shrink. What happened?"

Strong answer: Owns it, explains what the data showed, and describes what they changed.

Red flag: Blames the market, the team, or the corporate plan.

11. "Have you ever had to hold a friend on your team to a standard? What did you do?"

Strong answer: Treated the person fairly and consistently and kept the relationship professional.

Red flag: Makes exceptions, or ended the friendship to avoid the conversation.

12. "Tell me about a policy you disagreed with. How did you handle it with your team?"

Strong answer: Raised concerns upward and presented the decision to the team constructively.

Red flag: Undermines the policy in front of employees.

Customers and integrity

13. "Describe the angriest customer you've handled. Walk me through it."

Strong answer: Listens, stays calm, resolves the issue, and protects the employee involved.

Red flag: Argues, escalates, or leaves the employee to handle it alone.

14. "What would you do if you found out an employee was breaking a cash or safety rule?"

Strong answer: Follows the process, documents it, involves the right people, and treats the person fairly.

Red flag: Handles it informally without telling anyone, or jumps to conclusions.

15. "Tell me about a decision you made that you later realized was wrong."

Strong answer: Takes ownership, explains what they learned, and shows real reflection.

Red flag: Can't think of one, or tells a story that's really a compliment.

A simple scoring rubric

Score each answer from 1 to 4 right after the interview, using the same anchors for every candidate:

• 1: Vague, general, or blames others. No clear actions or outcome.
• 2: Some specifics, but unclear what the candidate personally did or why.
• 3: Specific and owns the decisions. Describes actions and outcomes.
• 4: Specific, owns the decisions, considers both the people and the business, and shows what they learned.

Add the scores, but also read your notes. A candidate who is strong on people skills and weaker on standards is a different hire from the reverse.

Common mistakes when interviewing managers

• Hiring on experience alone. Years in role and team size don't show how someone leads. I've written about why the manager is the hire that matters most in Forty Résumés, One Address.
• Asking only hypotheticals. People tell you what they'd like to do. Ask what they actually did.
• Changing the questions for each candidate. Then you're comparing answers to different tests.
• Going with your gut. A gut feeling is useful as a prompt to ask more, not as the decision.
• Skipping references. What former colleagues say about how a manager treated them is some of the best evidence you can get.

What if you're interviewing dozens of managers?

Multi-unit operators often hire managers across many locations, and a district manager can't run a long live interview with every applicant. One approach is to put a structured screen in front of the live interview, so the first conversation is consistent for everyone and your district managers spend their time on the people who've shown how they handle real situations. SeekerPitch's manager screening software does this with a short conversational voice interview, and your team makes every hiring decision.

The bottom line

A good manager interview is a structured conversation about real moments: same questions for every candidate, specifics rather than generalities, and a simple rubric to score the answers. Use these fifteen questions as a starting point, adjust them to your roles, and pay as much attention to how candidates talk about people as to what they've achieved. The manager you hire will shape everyone else's experience, so the interview is worth the preparation.

Related: why frontline hires quit in the first 90 days.

---

SeekerPitch is AI behavioral screening for frontline and operations hiring. Sophia interviews every applicant in a 3–15 minute conversational voice interview, scoring 17 behavioral dimensions across five Job DNA zones — and no candidate is ever rejected by AI, because a human makes every final decision. Built by The Reisner Group.