Tell me about your management style.
Why they ask. This tests leadership ability and self-awareness — the BLS notes that managers coordinating workers and administrative duties must show leadership ability (U.S. Bureau of Labor Statistics, 2025). They want to know your default setting and whether it suits this team.
How to approach it. Name the style in one line, then describe the mechanism that proves it — meeting cadence, how goals are set, how problems reach you. Finish by saying how you flex the style for a new hire versus an experienced report.
Sample answer — customer support manager, 18 agents through two team leads
I'd call it structured and hands-off, in that order. At my last employer I managed 18 support agents through two team leads. Every direct report had a 30-minute weekly one-to-one with a shared agenda they owned, and I kept a running notes doc so nothing got re-litigated. The team ran against three numbers on a Monday scorecard: first response time, resolution rate and quality sampling. I didn't touch tickets unless an escalation hit the two-hour mark. Where I flexed was tenure — a new lead got a daily ten-minute check-in for her first six weeks, then we dropped to weekly once her queue was stable. By the end of my second year, one of those leads had taken over half my scorecard reviews and was running the team during my leave.
Mistake to avoid. Answering with adjectives only — "supportive but hands-off." Fix: attach a mechanism to each adjective, such as one-to-one frequency, how goals are set, and when you step in.
How do you manage when your direct reports are supervisors rather than front-line staff?
Why they ask. This is the delegation and span-of-control test. General and operations managers usually manage through subordinate supervisors, and the occupation excludes first-line supervisors (O*NET OnLine) — they need to know you can let go of the work you used to do.
How to approach it. Describe what you hold supervisors accountable for, how you get information without going around them, and the rule you use for when you speak directly to their teams.
Sample answer — operations manager, three shift supervisors, 60 staff
I owned the site; my three shift supervisors owned their shifts. Each of them brought the same four numbers to a Tuesday meeting — output, overtime hours, safety incidents and open vacancies — and we spent most of the hour on the exceptions. I walked the floor every day, but I made it a rule to pass anything operational back to the supervisor rather than fix it myself; if I'd handed out instructions directly, their authority would have gone. The one exception was safety, where I'd stop a line on the spot and debrief with the supervisor after. I also ran a monthly skip-level with four rotating staff so I wasn't only seeing the shift through three sets of eyes. Overtime dropped two shifts in a row once the supervisors were planning cover themselves.
Mistake to avoid. Telling stories where you personally solved the front-line problem. Fix: in each example, say explicitly what you asked the supervisor to own and how you checked it.
Walk me through how you read a monthly performance report and what you do with it.
Why they ask. Commercial and operational judgement. A reported task for general and operations managers is reviewing financial statements, sales or activity reports, or other performance data to measure productivity or goal achievement, or to identify areas needing cost reduction or program improvement (O*NET OnLine).
How to approach it. Name the actual report and tool, say which two or three lines you look at first and why, then describe one decision that came out of a variance. Show the sequence: look, ask, verify, act.
Sample answer — branch manager, retail network, P&L for one site
I started with the variance column, not the totals. Each month I got a site P&L in Excel against budget, plus a labour report from the scheduling system. I looked at three lines first: sales against forecast, labour as a percentage of sales, and shrink. In March one year labour was running well over plan while sales were flat, which usually means either scheduling drift or unrecorded overtime. I pulled the shift schedules and found we were double-covering the 4pm handover five days a week because two supervisors had each built cover for it. I changed the template, kept one hour of overlap on the two busiest days, and the line came back inside budget the following month. I also started sending supervisors their own labour numbers weekly, so they saw drift before I did.
Mistake to avoid. Describing the report but never naming a decision. Fix: end every data answer with the change you made and what moved afterwards.
Tell me about a time you turned around an underperformer.
Why they ask. Performance management — whether you act early, document, and separate capability problems from motivation problems.
How to approach it. Set out what "underperforming" meant in measurable terms, what you found when you asked, the plan with dates, and the outcome. Say what you'd check differently next time.
Sample answer — account management team lead, six reports
One of my six account managers was missing renewal targets by a wide margin two quarters running. Rather than open with the number, I asked him to walk me through his pipeline in the CRM, and it turned out he was spending most of his week on two accounts that were never going to renew. We agreed a 60-day plan in writing: weekly pipeline review, a cap of three hours a week on those two accounts, and shadowing a colleague on two renewal calls. I wrote down what good looked like at 30 and 60 days so there was no ambiguity. He hit target at the end of the second quarter and stayed. What I'd do earlier next time is check the pipeline detail in month one — I let a full quarter pass before I looked closely.
Mistake to avoid. Saying "we had a conversation and things improved." Fix: name the written plan, the review dates and the measurable standard you set.
Tell me about a time you had to cut costs or absorb a budget reduction.
Why they ask. Judgement under constraint, and whether you protect output and people at the same time. Identifying areas needing cost reduction is a core part of the general and operations manager role (O*NET OnLine).
How to approach it. Give the size of the cut relative to the budget, the options you weighed, what you chose to protect and the trade-off you accepted. Interviewers trust answers that admit a cost.
Sample answer — facilities manager, two office sites
I was told to take about 12 percent out of an annual facilities budget without reducing headcount. I listed every line in a spreadsheet and sorted them by whether staff would notice within a week. The savings came from three places: consolidating two cleaning contracts into one at re-tender, moving printing to a managed service, and closing one floor over summer when occupancy data showed it was running under a third full. I protected the maintenance reserve, because deferred repairs come back bigger. The trade-off was a slower helpdesk response on non-urgent tickets, which I flagged to department heads before it happened rather than after. We came in under the reduced number and no one lost a job.
Mistake to avoid. Presenting a cut with no downside. Fix: name the thing that got worse and say how you communicated it in advance.
Describe a conflict between two people who reported to you.
Why they ask. Behavioural evidence of how you handle people problems — specifically whether you intervene, stay neutral, and fix the structural cause rather than just calming everyone down.
How to approach it. Describe the conflict as a work problem first (overlapping ownership, unclear priority), then the conversations, then the change you made so it didn't recur.
Sample answer — department manager, two supervisors
My two supervisors stopped speaking after an argument about who owned the weekend schedule. I met them separately for 20 minutes each, then together, and I kept the meeting on the work: who publishes the roster, by what day, and who approves swaps. It turned out both had been told they owned it by my predecessor. I wrote a one-page RACI, put the roster publication on one supervisor and swap approval on the other, and we reviewed it at the end of the month. I also told both of them plainly that I expected professional communication regardless of the ownership question, and that I'd address it as a conduct issue if it continued. It didn't. The roster has gone out on Thursdays ever since.
Mistake to avoid. Taking a side or outsourcing it to HR immediately. Fix: show the separate conversations, the joint one, and the structural fix you made afterwards.
Tell me about a time you had to let someone go.
Why they ask. They want to know you can make a hard people decision properly — with process, documentation and some care for the person and the team left behind.
How to approach it. Focus on the process you followed and the dignity of the handling. Keep the person anonymous and don't editorialise about them. Rules on notice and documentation vary by employer, state and country, so say you worked with HR rather than claiming to know the law.
Sample answer — warehouse operations manager, 40 staff
I had a team member whose attendance had been informally tolerated for over a year. I started by documenting the pattern from the time system — 14 unexplained absences across four months — and sat down with HR before anything else, because our policy and the local requirements weren't mine to interpret. We ran a formal process: a written expectation, a four-week review, a second review. He didn't meet either. The termination meeting lasted ten minutes, with HR present, and I had his final paperwork and equipment return ready so he wasn't left waiting. Afterwards I told the shift what was and wasn't my information to share, and covered his shifts myself for a week while we recruited. The rest of the team's attendance improved once they saw the standard was real.
Mistake to avoid. Describing a dismissal that happened fast and informally. Fix: show the documentation trail and the point where you involved HR.
How do you manage people you were recently peers with?
Why they ask. Internal promotion is common — many managers advance within their own organisations from lower-level management or supervisory positions (U.S. Bureau of Labor Statistics, 2025-08) — so this tests whether you can reset relationships without either over-asserting or avoiding authority.
How to approach it. Describe the reset conversation you had with each person, what you changed immediately, and what you deliberately kept.
Sample answer — promoted to team manager, seven former peers
When I was promoted I had seven former peers reporting to me, including a close friend. In my first fortnight I did a 30-minute one-to-one with each of them and asked two questions: what do you want from me that you didn't get before, and what should I stop doing now that I'm not on the tools. I made two changes straight away — I stepped out of the team's informal chat and started running a visible Friday priorities list so decisions weren't made in corridors. With my friend, I said plainly that I'd have to treat his work the same as everyone's and that he should tell me if I ever got that wrong. The hardest part came three months in, when I had to decline his leave request during peak. I did it the same way I'd have done for anyone, and explained the reason.
Mistake to avoid. Claiming nothing changed. Fix: name one thing you stopped doing and one conversation you had with each person.
How do you decide between promoting internally and hiring externally?
Why they ask. Succession planning and hiring judgement — whether you develop people or default to the outside market.
How to approach it. Give your criteria first, then a real decision that went each way. Mention what you do for the internal candidate who didn't get it, because that's what separates experienced managers.
Sample answer — operations manager, filling a supervisor vacancy
My rule is that I look internally first unless the team is missing a capability it can't build in six months. When a supervisor post opened I had two internal candidates. I ran the same interview and a scheduling scenario exercise for internal and external applicants so the comparison was fair, and scored all five against the same four criteria. One internal candidate won it. The other had the technical skill but had never handled a disciplinary conversation, so I told her that directly, put her on two months of co-running the shift handover and gave her the summer cover role. She took the next supervisor vacancy nine months later. The time I went external was for a compliance-heavy role where no one in the team had the qualification and the audit date was four months out.
Mistake to avoid. Saying "I always promote from within." Fix: give one example of each and the criterion that decided it.
What would your first 90 days look like here?
Why they ask. Planning and prioritisation, plus whether you've understood the scope of the job on offer rather than the one you last did.
How to approach it. Structure it in three blocks, front-load listening and data, and hold back on big changes until you've seen a full cycle. Tie it to something specific from the job description or the conversation.
Sample answer — incoming department manager, 25 staff across two sites
First 30 days I'd listen and count. One-to-ones with every direct report and a sample of the wider team, plus a half-day at each site on different shifts, and I'd ask for the last six months of your performance reports so I can see the trend rather than one snapshot. Days 30 to 60 I'd test what I'd heard: pick the two or three themes that came up repeatedly, check them against the data, and agree with you which are mine to fix this year. From day 60 I'd start making changes, beginning with anything cheap and visible — usually meeting structure or how priorities get communicated. I wouldn't restructure anything in the first quarter unless something was unsafe or losing money, because I'd rather see one full reporting cycle first.
Mistake to avoid. Promising specific changes before you've seen the operation. Fix: commit to a listening-and-data phase, then say what would trigger an earlier intervention.
Aspirational Hub
