Operations manager interviews are tricky because the role itself means something different at every company. At a 200-person manufacturer, an ops manager is running production lines and managing shift supervisors. At a 40-person SaaS startup, the same title might mean running the whole business behind the CEO. The interview questions differ accordingly, but the underlying things interviewers are probing for are fairly consistent.
I’ve pulled together the questions that show up most often across the different contexts, along with the reasoning behind each one. This isn’t an exhaustive list, but these 23 cover the categories that matter most.
Process and efficiency questions
These come up in every ops interview, almost without exception.
- “Walk me through a process you inherited that wasn’t working and what you did about it.”
- “How do you decide which inefficiencies are worth fixing right now versus later?”
- “Tell me about a time you used data to make a decision that surprised you.”
- “What metrics do you actually look at every day? Not what you report upward, what you personally monitor.”
- “Describe a process change you implemented that didn’t stick. What happened?”
That last one trips people up. Interviewers want to see that you have real experience, not just successes. Every ops manager who’s been doing this long enough has rolled out something that the team quietly reverted back to the old way. If you can’t name one, it either means you haven’t changed much, or you’re not paying attention to whether your changes hold.
Supply chain and vendor questions
These matter more in manufacturing, logistics, and physical goods companies, but they come up in service businesses too when vendors and contractors are part of the workflow.
- “How do you evaluate a new vendor before bringing them into a critical process?”
- “Tell me about a time a supplier let you down mid-project. How did you handle it?”
- “What’s your approach to building redundancy into a supply chain that currently has none?”
- “How do you manage vendor relationships when you have very little use?”
The use question is worth preparing for carefully. A lot of candidates give answers about “building strong relationships” without any specifics. The interviewers who ask it want to hear how you’ve actually gotten things done when you were the small customer who couldn’t threaten to pull volume.
Team management and leadership
According to the Bureau of Labor Statistics, general and operations manager is among the highest-volume management roles in the US economy, with over 3 million people employed in the category. That means competition is real, and interviewers have pattern-matched on weak answers enough to spot them quickly.
- “Describe a situation where you had to deliver results through a team you didn’t have direct authority over.”
- “How do you handle a high performer who is also creating team friction?”
- “Tell me about someone you managed who wasn’t meeting expectations. How did you approach it?”
- “What’s your process for onboarding someone into an ops role where institutional knowledge matters a lot?”
The authority question is especially common in matrix organizations where ops managers coordinate across engineering, finance, and customer success without owning those functions. If you’ve done it, you have a story. If you haven’t, you need to think through how you’d approach it before the interview.
Crisis and problem-solving scenarios
These often come as case-style questions, not behavioral ones. The interviewer describes a situation and asks what you’d do. The answer matters less than how you think out loud.
- “A key vendor just told you they can’t deliver on a commitment two weeks from now. What do you do in the next 48 hours?”
- “You’ve just taken over a team and you find out there’s a compliance issue nobody documented. How do you proceed?”
- “Revenue is down 30% month over month and nobody can explain why. Where do you start?”
- “You have to cut 20% of operating costs in 90 days without touching headcount. Walk me through your approach.”
For these, structure matters. I’d suggest something like: identify what you know versus what you need to find out, name the immediate containment action, then describe how you’d get to root cause. Interviewers are looking for calm under pressure and methodical thinking. They don’t need the perfect solution because there rarely is one.
Data and measurement questions
Operations has gotten considerably more data-heavy over the past decade. The Stack Overflow Developer Survey 2024 found SQL is still the most widely used data query language even outside engineering roles, which tells you something about how much ops and business functions have had to pick up data skills. Expect questions that probe this.
- “What’s the most meaningful KPI you’ve ever built from scratch? Why did you choose it?”
- “Tell me about a time your data said one thing but your instincts said another. What did you do?”
- “How do you communicate performance data to people who aren’t naturally numbers-oriented?”
The gut-versus-data question is one of my favorites to observe. People who say “I always trust the data” are either lying or don’t have much ops experience. Real operations work involves incomplete data all the time, and good instincts built from pattern recognition are genuinely valuable. The honest answer involves trusting both and knowing when each deserves more weight.
Questions to ask your interviewers
A good ops manager candidate usually has sharp questions. These tend to signal the right kind of thinking:
- “What’s the biggest operational bottleneck in the business right now that this role is expected to address?”
- “What does success look like for this role at 90 days? At 12 months?”
- “How does operations currently interact with [the function where ops has tension, usually engineering or finance]?”
If you’re using Craqly during a virtual interview, you can keep your prepared questions and key examples visible as a real-time overlay without switching windows mid-conversation. That’s particularly useful in case-style interviews where you’re working through a problem and want to reference a framework you prepped without breaking eye contact with the camera.
One more thing: come with specific numbers. Not “I improved throughput” but “I reduced average order processing time from 4.7 days to 2.1 days over a six-month rollout.” If you don’t have exact figures, approximate with context (“roughly 40%, though we didn’t have great baseline tracking”). Vague claims are a real red flag in ops interviews, where measurement is the whole job.