Questions to Ask in an Operations Manager Interview
For candidates interviewing for an operations manager job and deciding what to ask the hiring manager. The questions follow the order the conversation tends to take: what the job owns, the team and its shifts, the metrics and budget you would answer for, the processes, systems and vendors that are giving trouble, how much authority comes with the title, and a few to close on. Each has a note on what a good or a worrying answer sounds like, and the guide at the end turns the list around for anyone hiring an operations manager.
Want questions from the whole vault instead? Try the random question generator.
The questions
Each question, and why to ask it
The job
What would I own day to day as operations manager, and where does the job stop?
Why ask it
Operations manager can mean running a floor, a fleet, a service desk or the office itself, so settle what it means here first. A good answer names functions, such as scheduling, purchasing, maintenance or facilities. If you hear 'a bit of everything', ask which three things would be yours alone on an ordinary Tuesday.
What is the biggest operational problem you want this hire to fix?
Why ask it
This is the real job description. A manager who names one thing, such as late shipments, overtime or a system nobody trusts, has thought about what they are hiring for. A list of six with no order means you would be choosing the priority yourself, so ask which one they would want gone by the end of the year.
What would you need to see in my first 90 days to feel the operation is in good hands?
Why ask it
Compare the answer with the problem they are hiring to fix. When the two line up, such as overtime named as the trouble and a staffing plan wanted by day 90, the job has been thought through. Five fixes expected inside three months suggests the hire is late and patience is short, so ask which one comes first.
Has there been an operations manager here before, or is the role new?
Why ask it
With a first operations manager, find out who has been doing the job until now and which parts of it they mean to keep. Where the role already existed, the team will measure you against the last person, so ask how long they stayed. In both cases, find out how long the seat has been empty and who has been making the calls since.
What does a normal week look like in this job, from standing meetings to time on the floor?
Why ask it
Listen for the split between the desk and the place where the work happens. A week made only of meetings and reports suggests the role is further from the operation than the title implies, and a week with no fixed rhythm suggests nobody has had time to set one. Ask which of those meetings you would run.
Who does the operations manager report to here, and how close is that person to the daily operation?
Why ask it
It might be an owner, a general manager, a site manager or a director of operations. Ask when that person was last on the floor or listening in on the service line, and whether it was a visit or a habit. A boss who is there daily will notice your changes early, for better and worse. One who is not will know the operation through your reports, so find out what they want to see in them.
What did the last person in the job leave unfinished or half-changed?
Why ask it
A half-installed system or a reorganization stopped midway is yours on day one, along with the team's opinion of it. Ask whether you would be expected to finish it, rethink it or quietly drop it. If the role is new, ask what has been waiting for someone to own it.
How would I learn the operation in my first weeks: an overlap with the last manager, time on each shift, or straight into the job?
Why ask it
If the last manager has already gone, ask who would walk you through the site, the systems and the main customers. Time spent working each shift, including the unpopular one, before you are asked to change anything is worth asking for. 'You will pick it up' leaves the training plan to you, so ask whether the first two weeks could be kept clear of projects.
Does the role cover one site or several, and how much time is expected at each?
Why ask it
Several sites means managing people you cannot see. Ask whether each location has its own lead with real authority. If you would 'float between them', find out which site has the most trouble, because that is where you would be based in practice.
How much of the job is planning ahead, and how much is dealing with whatever broke this morning?
Why ask it
Every operations job has some firefighting, and an honest manager will say so. The worry is a job with nothing else, where improvement work is promised and there is never a quiet week to do it in. The follow-up is what the last person managed to finish that was not an emergency.
Team and shifts
How many people would report to me, and how many of them are supervisors or leads?
Why ask it
The total gives you the size of the operation, and the number of leads tells you what kind of managing it is. Thirty people through four supervisors is a coaching job. Thirty direct reports is a job of schedules and call-outs, with little time left for anything else.
Which shifts does the operation run, and which would I be expected to be on site for?
Why ask it
An operation that runs nights or weekends may want its manager seen on those shifts now and then, and it is better to hear the expectation now than to discover it. Ask what hours the last person really kept. A vague 'whatever the business needs' deserves one follow-up about a typical week.
Who gets the call when something goes wrong at 2 a.m., and how often does that happen?
Why ask it
The good version has an escalation list: a shift lead who handles most things and a clear line for when the manager is woken. The worrying version is 'you, usually'. Ask what the last two calls were about, which shows whether it is rare bad luck or a gap in the night coverage.
Is the team staffed for the current volume, or is overtime covering the gap?
Why ask it
Standing overtime tends to mean the headcount plan and the workload parted ways some time ago. Ask whether there are positions approved and unfilled, or whether the budget assumes the gap stays. The second means hitting the numbers with the people you have.
How much of the workforce is temporary, seasonal or supplied by an agency?
Why ask it
A large flexible layer changes the work: training on repeat, more quality checks, and an agency relationship to manage. Ask who decides how many temporary workers come in and how much notice the operation gets. How their hours and any move to permanent staff are handled depends on the contract and the local rules, so ask how it works at this site.
Where has turnover been highest in the past year, and what do people say when they leave?
Why ask it
Ask where, because turnover is seldom even. One shift or one supervisor's team losing people points to something specific and fixable. If nobody has asked the people who left, that is an early task for you and a sign of how closely the floor has been listened to.
Which of the supervisors or leads are strongest, and which would need most of my time?
Why ask it
An answer with names in it comes from someone who knows the team. Note whether the weaker ones are described as new and learning or as long-standing problems nobody has dealt with. The second kind comes with history, so ask what has already been said to them.
What happens to the operation when the operations manager takes a week off?
Why ask it
If things carry on, there are supervisors who can decide and procedures that hold. If the answer is a laugh, or 'the last one never really did', the job depends on one person being reachable all the time. Ask who your stand-in would be and whether they are ready for it.
Are any of the teams covered by a union or collective agreement, and who handles that relationship?
Why ask it
Neither answer is good or bad, but it changes how scheduling, overtime and discipline are done. What an agreement allows differs from one workplace to the next, so ask how it works here and whether you would sit in on meetings with the representatives. If the relationship sounds tense, ask what the last dispute was about.
What is the safety record like, and what was the last incident that changed how you work?
Why ask it
In a warehouse, plant, kitchen or fleet, safety is likely to sit with you from the first day, so ask about it plainly. A good answer includes a specific event and what was changed after it. Be wary of 'we have never had a problem', which can mean incidents go unreported. In an office-based operation, ask about data or compliance errors instead.
Metrics and budget
Which KPIs would I answer for, and who looks at them each week?
Why ask it
Expect a short list, such as on-time delivery, cost per unit, error rate or overtime hours. A handful that someone senior reads every week is a good sign. A dashboard of thirty with no audience means nobody has decided what matters, and you would be judged on whichever one is red that month.
Where do those numbers stand today against target?
Why ask it
This tells you whether you are being hired to keep a steady operation steady or to turn one around, which are different jobs with different patience from above. If the manager will not share figures in an interview, ask for the direction: improving, flat or slipping. Declining even that is worth noting.
Does the operations manager hold a budget, and what is in it?
Why ask it
Have them name the lines: labor, overtime, maintenance, supplies, freight, temporary staff. Labor is the one to check, since a budget that leaves out the payroll you schedule gives you little to manage. If finance builds the budget and the operations manager only explains the monthly variance, say that back to them and see whether they agree.
How much could I approve to spend without asking anyone?
Why ask it
The figure matters less than how it fits the work. If a broken pallet jack or a rush freight charge needs a director's signature, small problems will wait for days. How long an approval above your limit usually takes is worth knowing too.
How are the targets set: handed down, built from last year, or agreed with the operations manager?
Why ask it
Targets you helped build are ones you can defend to your own team. Targets handed down are workable too, if someone can explain where they came from. Ask whether this year's are being hit, and what happened the last time one turned out to be unrealistic.
How reliable is the volume forecast I would be planning against, and who produces it?
Why ask it
Staffing, ordering and overtime all hang on this one number. A forecast that comes from sales with no operations input can arrive late and optimistic, so ask how far out it runs and how often it is revised. If there is none, ask how the team decides how many people to bring in next week.
Is there pressure to take cost out this year, and has a figure been put on it?
Why ask it
A named figure with ideas attached is a plan you can work with. 'We need to be leaner' with no number can turn into a headcount conversation later, so ask whether staffing is on the table. Ask too where the last round of savings came from.
Which of the numbers you report would you not bet on being accurate?
Why ask it
Plenty of operations have a count that is keyed in by hand, or a metric measured in a way that flatters it. Naming one right away is candid, and it tells you where you would look first. If every number is said to be solid, ask how inventory or time records were last checked.
Processes and systems
Which process causes the most rework, delay or customer complaints right now?
Why ask it
If they name the same problem they gave as the reason for the hire, go straight to what has already been tried. An untouched problem may only need attention, while one that has outlived three fixes has a cause nobody has found or nobody is allowed to touch. Hold back from proposing a cure for a process you have not watched.
Which systems run the operation, and where do people work around them with spreadsheets?
Why ask it
The official answer is a product name. The useful one is where the system stops and the spreadsheets, whiteboards and group chats begin, because that is where errors get in. Say which systems you have used, and ask who inside the company can change a setting when something needs fixing.
How much of the way work is done is written down, and how much lives in a few people's heads?
Why ask it
Written procedures that match what happens on the floor make training and time off possible. If the knowledge sits with two long-serving people, ask how near they are to retiring or moving on, and whether writing it down would be welcomed or taken as a threat.
Does the operation follow a formal improvement method, such as lean or Six Sigma, or is it handled case by case?
Why ask it
Either can work. Where a method is named, ask for one thing it changed in the past six months, because the boards and the vocabulary can outlast the practice. Where there is none, ask who would have time to work on a fix with you, since improvement done by the manager alone stops whenever the week gets busy.
Which suppliers or vendors does the operation lean on most, and is any of them causing trouble?
Why ask it
One carrier, staffing agency or key supplier going wrong can undo a month of good work inside the building. Listen for whether there is a backup. If a vendor is already failing, ask whether replacing them would be your decision.
Who holds the vendor contracts: operations, purchasing or someone higher up?
Why ask it
You can only manage a vendor whose contract you can read and whose renewal you have a say in. Where purchasing or the owner signs the deals, ask how complaints about service reach whoever negotiates. Find out when the largest contract next comes up.
What audits, inspections or certifications does the operation have to pass, and when is the next one?
Why ask it
What applies depends on the industry and the location, so let them list it and do not assume. A date in your first two months would be your first deadline. Ask how the last one went and who prepared for it, since that know-how may have left with your predecessor.
How does the busiest stretch of the year compare with a normal month, and how did the last one go?
Why ask it
Peak is when an operation shows what it is. Ask what broke last time, how many extra people were brought in, and when planning for the next one begins. Starting just before a peak is a hard way to learn a site, so check where your start date would fall.
When did the operation last have a truly bad day, and what happened afterward?
Why ask it
You want the story: a system outage, a missed truck, half a shift calling out. An account of what was learned and changed comes from a place where problems can be raised. If the story ends with the name of the person at fault, you have seen what a mistake would cost you.
Is anything big planned for the next year, such as a new system, a move, another site or a major customer?
Why ask it
A project like that can take over the job for months, and it would probably be yours to deliver on top of the daily work. Ask who is sponsoring it and whether extra help comes with it. If nothing at all is planned, ask whether that is by choice or because nobody has had the time.
If I decided a supervisor was in the wrong role, what would I be able to do about it?
Why ask it
Authority over people is often thinner than authority over process, and this finds out. Ask what the steps are and who else would have to agree, because both vary by employer and by place. 'It has never come up' may mean nobody has been allowed to act.
When was the last time an operations manager here pushed for a change, and did it go through?
Why ask it
A past case shows more than a promise of autonomy. A story in which the change was heard, argued over and tried means the door is open. If no example comes to mind, the last person either did not ask or stopped asking.
Where does operations most often clash with other departments, and who settles it?
Why ask it
Friction with sales, finance or customer service is normal, and an interviewer who reports none may not be looking. What you need to know is the referee: a shared boss, a weekly meeting, or whoever shouts loudest. A recent example, and how it ended, will show you which.
When sales promises a customer a date or a volume, is operations asked first?
Why ask it
If yes, ask how, since a planning meeting is different from a message sent after the deal is signed. If no, you would spend part of every month delivering commitments you never agreed to. It is fair to ask whether the company wants that changed.
Does the owner, a senior leader or a large customer ever go straight to the floor with instructions?
Why ask it
In smaller companies this is common and often well meant. It still leaves the team unsure whose word counts. Ask how the manager would feel about such requests coming through you, and watch whether the idea is welcome.
How does a request for new equipment or other capital spending get approved, and what was the last one granted?
Why ask it
Old forklifts, tired software and a building at capacity cannot be fixed by better management alone. The last approved request shows whether the company invests in the operation or expects it to cope. The time it took from first request to purchase tells you the rest.
How do you want to hear bad news from the operation: right away, or once there is a plan?
Why ask it
Managers differ, and guessing wrong in your first month is costly. Some want a call the minute a shipment is at risk, others want the fix alongside the problem. Whichever they choose, ask what happened the last time bad news reached them late.
Closing
What is the company trying to do over the next two or three years, and what does it need from operations to get there?
Why ask it
Growth, a sale, a new market and holding steady each ask something different of the operation. An answer that ties the plan to capacity, cost or service means operations is in the room when plans are made. If the plan never mentions operations, you would be reacting to decisions already taken.
Is there a bonus tied to the targets we talked about, and how has it paid out in recent years?
Why ask it
Leave this for a later round or the offer stage. Each employer sets its own plan, so ask what it is based on and whether those measures are within the operations manager's control. A bonus that depends on company profit rewards you for things you do not run.
Where have people who held this job gone next?
Why ask it
A move up to director or general manager shows the seat leads somewhere. A run of people who left after a year or two shows something as well. If the last person held it for a decade, ask whether there is room above, or whether this is a job people stay in, which suits some candidates well.
Which part of this operation do you think my background has prepared me least for?
Why ask it
For an operations hire the gap is often a setting: no union experience, a smaller team, a different system, days only. Reply with the nearest thing you have done and how long it took you to get comfortable, then leave it there. If they name a gap you had not spotted, take it as a preview of your first months.
Could I walk the floor or sit in with the team before a decision is made?
Why ask it
Ten minutes in the building shows things no answer will: how tidy it is, whether people look up, what is written on the boards. Some employers will agree for a finalist, and a site may need notice or safety gear first. A flat refusal with no reason is something to weigh.
What comes next in the process, and who else would I meet?
Why ask it
The names tell you who has a say in the hire and whose backing the job depends on afterward: an owner, a finance lead, the supervisors you would manage. If nobody from the floor is on the list, say you would like to meet a supervisor before deciding. Then ask when they hope to have someone start.
How to use these questions in an operations manager interview
Practical guidance for the conversation itself
Before the interview
Work out what kind of operation it is
The same title sits over a warehouse, a production line, a service team, a group of stores and a back office. Read the posting and the company's site for clues, then put the questions into their terms: 'pick accuracy' for a distribution center, 'first-call resolution' for a service desk. Questions about shifts, safety and equipment matter most where there is a floor. Where the work happens on screens, lean on systems, forecasts and how work is handed between teams.
Match the group to the round
A recruiter's phone screen is the place for a few from The job, plus the practical points about location and hours. The hiring manager is the person for Team and shifts, Metrics and budget, and Processes and systems. Authority suits a second or final round, once the manager has shown they want you and will speak more freely, and so do the Closing questions about bonus and next steps. If a senior leader or the owner joins, ask them the one about the company's plans and what it needs from operations.
Bring your own numbers
When the manager names their headcount, volume and targets, you will want to answer with a comparison from your own work: the size of team you ran, the shifts it covered, the budget, a metric you moved and how. Write those down beforehand and use only figures you could back up. They turn your questions into a conversation between two people who run things.
Decide what would make you say no
Before the interview, write down the two or three answers that would end your interest: on call every night with no backup, targets with no budget, no say over the supervisors. In the room, with a manager you like, it is easy to wave these through. Having them on paper makes that harder to do.
In the room
Expect to ask five or six
Nobody gets through the whole list. Take the one question from each group whose answer you most need, lead with the one most likely to settle whether you want the job, and keep the rest as spares for later rounds. If the manager covers a question while describing the role, cross it off and do not ask it again for form's sake.
Ask for a date, not a policy
'How do you handle a bad week?' invites a statement of principle. 'When was the last one?' gets a date, a cause and what was done about it. Most questions under Processes and systems and Authority work better put that way.
Use what you see
If you are shown around, ask about what is in front of you: the board with yesterday's numbers, the pallets waiting in an aisle, the screen everyone keeps checking. A question about something real in the building shows how you look at an operation, and it is hard to answer with a prepared line.
Listen before you prescribe
When the manager describes a process that keeps failing, the temptation is to fix it on the spot. Say how you would start: who you would watch, what you would count, how long before you formed a view. Offering a cure for a floor you have never walked can read as overconfidence.
Reading the answers
Notice who knows the numbers
A manager who can give the headcount, the targets and last month's overtime from memory is running the operation by them, and will expect the same of you. One who has to look everything up may be further from the work, which can mean more freedom and also less help when you need a decision.
Watch for responsibility without authority
The pattern to look for across the whole conversation is a job that answers for cost, service and safety and cannot hire, spend or change a process without permission. One or two limits are ordinary. If nearly every answer under Authority ends with someone else deciding, the title is bigger than the job.
Hear how the last person is described
You will be spoken of the same way in time. A fair account of what the previous operations manager did well and where they struggled is reassuring. Blame for everything that is wrong, or a refusal to say anything, are both worth a second question about how long that person stayed.
Put one question to a second person
If the process includes a supervisor or a peer from another department, give them one question you already put to the manager, such as which process causes the most trouble. Two accounts that agree are reassuring. Where they part, weigh the one from whoever stands closer to the work.
If you are the one hiring
Have your answers ready
A strong candidate will ask about the numbers, the budget and what they could change. Decide before the interview which figures you can share, what the role can approve on its own, and how you will describe the problem you are hiring for. A candidate who hears clear answers on those three is easier to close than one who has to guess.
Turn the questions around
Most of this list becomes an interview question with a change of subject. 'Which numbers did you answer for, and where did they stand when you left?' 'Tell me about a process that kept failing and what you found when you looked.' 'How did you staff against a forecast you did not trust?' Ask for the specific case each time, and for what they did personally.
Judge the questions they ask you
What a candidate chooses to ask shows what they will pay attention to in the job. Questions about the forecast, the weakest supervisor or the vendor contracts come from someone already picturing the work. A candidate who presses on authority is not being difficult: they are checking whether they could deliver what you are asking for.
Show them the operation
Walk a finalist through the site, or have them sit in on a shift handover or a daily meeting. Watch what they notice and who they speak to. It also lets the candidate decide with open eyes, which is cheaper for both sides than a resignation three months in.