by A manager interview tests whether you can run people processes on repeat: delegating without micromanaging, giving feedback that changes behavior, and making a hiring or firing call under a deadline. Interviewers who've heard a hundred versions of "I lead by example" are listening for what you actually do on a Tuesday.
These questions apply to general manager and operations manager roles across industries. If you're interviewing for a specific title, like operations manager or department manager, expect the same core questions with more detail on budgets, staffing levels, or the team you'd be inheriting.
The 18 questions below cover delegation, performance management, hiring, and the conflict calls that come with running a team, with a sample answer specific enough to adapt to your own numbers.
Manager at a glance
| Item | Details |
|---|---|
| Typical employers | Retail, professional and technical services, construction, wholesale trade, manufacturing, and any industry with a team to run |
| Median pay | $105,770 a year for general and operations managers (BLS, May 2025) |
| Job outlook | 5% growth from 2025 to 2035, about 181,300 more jobs over the decade (BLS) |
| Education | Bachelor's degree typical for entry; most companies also want 3 to 5 years of experience in the function before promoting someone into management |
| Key tools | Excel, Microsoft Project or Asana, an ERP system like SAP or Oracle, a CRM like Salesforce, and a scheduling or performance-review platform |
| Interview format | 1 to 4 rounds: a recruiter screen, a hiring manager interview, a peer or panel round, and sometimes a case study or work sample |
How the interview usually works
- Recruiter screen (20 to 30 minutes). Confirms the size of the team you've managed, your tenure in each role, and comp expectations.
- Hiring manager interview. Mixes philosophy questions with scenarios pulled from the actual team you'd be running.
- Panel or peer interviews. Often include future direct reports or the departments your team depends on most, since fit with people you don't manage matters too.
- Case study or work sample, common at larger companies: a mock 1:1, a prioritization exercise, or a walkthrough of how you'd handle a real open issue on the team.
- Reference checks. Many companies call former direct reports, not just former managers, specifically to ask about your management style.
General and background questions
1. What do you think makes a successful manager?
Why they ask: They want to hear if your definition comes from what you actually do, not a scripted answer about leadership qualities.
How to answer: Name 2 or 3 specific behaviors, not adjectives, and tie one to something you actually do weekly.
Sample answer: A manager who tells the truth early. On my team, that means flagging a slipping deadline the day I notice it, not the day it's due, and telling a direct report their performance is a problem in week 3 of a slump, not month 3. Past that, I'd point to two things: protecting your team's time from meetings that don't need them, and knowing each person's actual skill gaps well enough to hand out stretch work that fits. I manage a team of 8 right now, and the two who've grown the fastest are the ones I've been most specific with about what to fix next.
2. How do you approach delegating tasks to your team?
Why they ask: Delegation failures show up as either micromanagement or dropped work, and they want to know which failure mode you avoid.
How to answer: Describe how you match work to skill level, what you check in on, and what you let go of entirely.
Sample answer: I delegate based on where someone is on a task, not just their title. A new hire gets a task broken into steps with a checkpoint at the halfway mark; someone who's done it before gets the outcome and the deadline, and I stay out of the how. When I handed our monthly reporting process to a senior analyst last year, I gave her the numbers I needed and the due date, and I didn't ask for a draft until she was ready to show one. That's different from how I hand a new process to someone in their first 90 days, where I'll check in after step one instead of waiting for a finished product.
3. How do you stay organized managing multiple priorities?
Why they ask: A manager juggling a team, a budget, and their own boss's requests needs a real system, not a claim about being organized.
How to answer: Name the actual tool and cadence you use, and how you decide what drops when everything can't fit.
Sample answer: I run a single weekly priority list, top 5 items only, reviewed Monday morning and again Thursday to catch what's slipping. Everything else lives in Asana where my team can see it, but the top 5 is what actually gets my attention. When something new lands mid-week, like an urgent request from my VP, I say out loud in my reply what it bumps, instead of quietly absorbing it and letting something else slide unannounced. That habit alone has cut most of the "wait, why didn't this get done" conversations I used to have.
Role-specific questions
4. How do you set goals and track your team's progress toward them?
Why they ask: Goal-setting reveals whether you manage by outcomes or by busywork.
How to answer: Describe your goal-setting process and review cadence, with a real example.
Sample answer: I set quarterly goals with each direct report that tie to 1 or 2 team-level numbers, not a long list. Last quarter, our team goal was cutting order-processing time from 48 hours to 24, and each person's individual goal was a specific piece of that: one person owned the intake form redesign, another owned a vendor SLA renegotiation. We reviewed progress every other Friday in 15 minutes, just the number and what's blocking it. We landed at 27 hours by the end of the quarter, short of the target, and I said so plainly in the wrap-up instead of rounding up.
5. How do you measure your own success as a manager?
Why they ask: Some candidates measure their own comfort; interviewers want business and people outcomes.
How to answer: Give 2 concrete measures, one team-output and one people-development.
Sample answer: Two numbers. First, whether the team hits the goals we set, which last year meant our on-time delivery rate went from 82% to 94%. Second, whether people on my team are growing, which I track less formally: how many took on a stretch project, how many got promoted or moved into a role they wanted. I had 2 direct reports promoted in the last 18 months, one internally and one who used what she built on my team to land a manager role elsewhere. I count that as a win too, even though it meant replacing her.
6. Walk me through how you manage ongoing performance, including a formal improvement plan.
Why they ask: Performance management is where new managers either avoid conflict or handle it badly, and they want your actual process.
How to answer: Describe your regular feedback cadence first, then what triggers a formal plan and what's in it.
Sample answer: Most performance issues get caught in our biweekly 1:1s before they need a formal process, since I flag a specific miss the week it happens rather than saving it for a review. If a pattern doesn't improve after 2 or 3 direct conversations, I move to a written plan: 2 or 3 measurable goals, a 30- or 60-day timeline, and check-ins every 2 weeks with HR looped in from the start. I've put 2 people on formal plans. One hit the goals and is still on my team 2 years later; the other didn't, and we parted ways at the end of the 60 days, which was hard but not a surprise to either of us by that point.
7. What's your hiring process when you need to fill a role on your team?
Why they ask: Hiring quality shapes a manager's ceiling more than almost anything else, and they want a repeatable process, not gut instinct.
How to answer: Describe your steps from job description through final decision, including how you check for a real skills match.
Sample answer: I start by rewriting the job description around the actual gap on my team, not a generic template, since a vague posting draws vague candidates. I screen resumes for specific, verifiable achievements, then run a 30-minute phone screen focused on 1 or 2 must-haves before anyone spends time on a full loop. For the final round, I use a work sample close to the real job, like a mock prioritization exercise for a project manager role, because it tells me more in 20 minutes than another round of behavioral questions. My last 4 hires all came through that process, and I've had zero turnover on that group in 18 months.
8. How do you build working relationships with other departments?
Why they ask: Managers who can't work across department lines create bottlenecks their own team pays for.
How to answer: Describe a concrete habit, like recurring check-ins, and a specific example of resolving friction with another team.
Sample answer: I set up a standing 20-minute biweekly with the leads of the 2 departments my team depends on most, purchasing and IT, even when there's nothing urgent, so the relationship isn't cold the first time I need a favor. When our rollout of a new intake system got stuck because IT deprioritized it behind their own roadmap, I sat down with their lead, showed her the cost in hours my team was absorbing every week, and we agreed on a smaller phase-one scope that fit into her sprint. It shipped 3 weeks later instead of staying stuck indefinitely.
9. How do you decide what your team works on when there's more urgent work than capacity?
Why they ask: They want a triage framework, not "we just get it all done."
How to answer: Name the criteria you weigh and how you communicate what's getting cut or delayed.
Sample answer: I weigh 2 things: what has a hard external deadline, like a client commitment or a compliance date, and what has the highest cost if it slips. Everything else waits. When our team got hit with an unplanned audit request on top of a product launch last spring, I moved 2 people off launch prep for a week and told the launch stakeholder directly that the date might slip by 3 days, rather than let my team quietly absorb both. It slipped by 2 days, and nobody was surprised, because I'd said so out loud a week earlier.
Behavioral questions
10. Tell me about the biggest challenge you've faced as a manager.
Why they ask: They want to see how you solve a hard problem involving people, not a process.
How to answer: Name a real, specific challenge, what you did, and the outcome, including what didn't work at first.
Sample answer: Inheriting a team of 6 where 2 people had applied for my job and didn't get it. The tension was obvious in the first week; one of them barely spoke in meetings. I asked for a 1:1 with each of them specifically to name it: "I know this is a hard transition, and I'd rather talk about it than pretend it isn't there." One came around within a month once she saw I'd back her ideas in front of the team. The other stayed guarded for close to a year and eventually transferred to a different team, which turned out to be the right outcome for both of us.
11. Tell me about a time you turned around an underperforming team or project.
Why they ask: This is the "can you fix things" question, and they want specifics, not a happy ending with no detail.
How to answer: Name the starting metric, what you diagnosed as the cause, what you changed, and the ending metric.
Sample answer: I took over a support team with a customer satisfaction score stuck at 71% and a 6-week backlog. I spent the first 2 weeks just reading closed tickets instead of changing anything, and found that half our reopened cases came from 3 recurring issues nobody had documented a fix for. I built a short internal knowledge base for those 3 issues, changed our queue so senior reps handled reopens instead of whoever was free, and set a weekly backlog number the team could see. Satisfaction hit 86% and the backlog cleared in 10 weeks. None of it was complicated; it just hadn't been anyone's job to look.
12. Tell me about a time you had to motivate a disengaged employee or team.
Why they ask: Disengagement is common, and they want to see you diagnose the cause instead of giving a generic pep talk.
How to answer: Describe how you found the real reason, what you changed, and whether it worked.
Sample answer: A strong performer on my team went quiet for about 6 weeks: less input in meetings, later on deadlines. Instead of assuming burnout, I asked directly in a 1:1 what had changed, and it turned out he felt stuck doing the same kind of work for 2 years with no visible next step. I couldn't promote him the next month, but I could give him ownership of a project outside his usual lane, leading our team's part of a cross-functional launch. His output was back to normal within 3 weeks, and he was promoted into a senior role 8 months later. Real ownership over the work changed his output faster than another conversation about motivation would have.
13. Tell me about a time you managed a heavy workload or deadline pressure.
Why they ask: They want to see how you handle pressure without passing panic down to your team.
How to answer: Name what you did to manage your own load and protect the team's, with a real deadline and number.
Sample answer: Our team had 3 weeks to migrate a client off a legacy system after their original vendor shut down with almost no notice. I blocked my own calendar to 2 fixed meetings a day so I could stay hands-on instead of managing from status updates alone, and I told my own manager on day one that something else on our roadmap would slip. I split the migration into 4 pieces across the team with daily 10-minute check-ins instead of one long weekly meeting, since daily visibility caught problems while they were still small. We finished with 2 days to spare, and I made sure my manager knew which 3 people carried the heaviest part of it.
14. Tell me about a time you had a difficult conversation with an employee.
Why they ask: This is where conflict-avoidant managers show themselves; they want a specific, uncomfortable conversation, not a vague summary.
How to answer: Name what the issue was, what you actually said, and the result.
Sample answer: I had to tell a well-liked team member that his constant interrupting in meetings was undermining quieter teammates, based on feedback from 3 different people. I told him directly what I'd heard, gave him one specific recent example, and asked what he thought was happening. He was defensive for about a minute, then admitted he hadn't noticed the pattern. We agreed on one concrete change: he'd let others finish a full thought before responding, and I'd tell him privately if I saw it slip. Two teammates mentioned within a month that meetings felt different. The conversation was uncomfortable for about 10 minutes and saved months of quiet resentment.
Situational questions
15. Two people on your team are in an ongoing conflict that's affecting the group's work. What do you do?
Why they ask: Unresolved peer conflict drags down a whole team, and they want to see you intervene directly instead of hoping it resolves on its own.
How to answer: Describe talking to each person separately first, then together, and what you'd do if it didn't resolve.
Sample answer: I'd talk to each of them one on one first, since the story often looks different from each side, and I want the facts before I referee anything. Then I'd bring them together myself, name the specific behavior affecting the team, like missed handoffs or short answers in meetings, and ask each of them what they need from the other to fix it, not just to feel heard. I'd set one concrete agreement and check back in 2 weeks. If it hadn't improved, I'd get more directive about what has to change, including telling one or both of them plainly that the way they're working together right now can't continue on this team.
16. A strong performer tells you they're considering an offer from another company. What do you do?
Why they ask: Retention conversations happen under time pressure, and they want to see you respond with something real instead of a reflexive counteroffer.
How to answer: Describe what you'd ask first, what you can actually offer, and how you'd handle it if they leave anyway.
Sample answer: First, I'd ask what's driving it, since pay, growth, and burnout call for different responses and a counteroffer only fixes one of the three. If it's pay and I have room, I'd move on it within days, not weeks, since a slow response reads as not caring. If it's growth, I'd say plainly what I can offer in the next 6 months and what I can't, rather than promise a title change I'm not sure I can deliver. I've had one person stay after a real growth conversation and one person leave anyway after I told her straight that the promotion timeline wouldn't move fast enough. Either way, I'd rather lose someone to an honest answer than keep them on a promise I can't back up.
17. You need to put an underperforming employee on a formal improvement plan. Walk me through that conversation.
Why they ask: This is the moment new managers most often go vague or apologetic, and they want to see clarity without cruelty.
How to answer: Describe how you'd open the conversation, what you'd put in writing, and how you'd handle their reaction.
Sample answer: I'd open with the pattern, not a surprise: "We've talked about the missed deadlines in our last 3 1:1s, and it hasn't changed, so I'm putting a formal plan in place." I'd have 2 or 3 specific, measurable goals in writing before the meeting, not drafted live, with a 30-day check-in date already on the calendar. If they got emotional or defensive, I'd let them finish before responding, and I'd stick to specific examples rather than get pulled into a debate about intent or fairness. I'd also say plainly what happens if the goals aren't met, since a plan that doesn't name the consequence isn't honest about what it is.
18. You take over a team where morale is low and performance has been slipping for a year. What do you do in your first 30 days?
Why they ask: They want to see a diagnostic approach before a fix, not a manager who reorganizes everything on day one.
How to answer: Describe what you'd listen for first, what you'd hold off on changing, and the first concrete move you'd make.
Sample answer: The first 2 weeks are mostly listening: individual 1:1s with everyone on the team, plus whatever data already exists, like turnover, project timelines, or engagement survey results if the company runs them. I'd resist announcing changes in week one, since a team that's already been through churn reads fast changes as more instability. By week 3, I'd pick one visible, fixable problem, something like a standing meeting everyone hates or a broken handoff process, and fix it fast so the team sees I act on what I hear. The bigger structural issues, like role clarity or workload, I'd tackle by day 45 once I understand what's actually driving them.
Questions to ask the interviewer
- What does the team I'd be managing look like right now: size, tenure, and any open performance issues I should know about?
- What's the biggest reason the last person in this role left or moved on?
- How much budget or hiring authority comes with this role?
- What does a strong first 90 days look like, and how would you and I both know it's going well?
- How does this company handle performance management and formal improvement plans?
- What's the working relationship like between this team and the departments it depends on most?
How to prepare
- Bring 3 specific stories: a hiring decision, a difficult conversation, and a project that didn't go as planned, each with real numbers.
- Know your team's actual metrics from your current or last role: headcount, turnover, and a performance number you moved.
- Review your own delegation habits honestly, and be ready to describe one task you should have handed off sooner.
- Practice saying a hard sentence out loud, like telling someone their performance isn't meeting the bar, since interviewers can tell when it's the first time you've said it.
- Research the team you'd inherit if you can, its size and its recent wins or setbacks, so your own questions sound informed.
If you're interviewing for a title-specific version of this role, see our store manager interview questions, accounting manager interview questions, or operational excellence manager interview questions. If you're weighing whether a management title actually comes with authority, team lead vs. supervisor and district manager vs. regional manager break down where similar-sounding titles differ. </content>
