Answering operations interview questions without inventing a number

Interviews for operations roles are unusual: almost every question is the same question. Has this person kept something running, and did they know what was happening while they did it?

The questions below are forms of that question. Each one shows what it is testing and how to answer it without inventing a result you cannot defend.

What to take away

The questions, what they test, and how to answer

Walk me through a process you improved.

Test whether you understand a process as a sequence with a measurable output. Did you change it on purpose or just work harder? Describe the process as it was, what you saw go wrong, what you changed, why that change and not another, and what happened afterward.

If you measured before and after, say what you measured and how it moved. If you did not, say what you observed change and how you would measure it now.

Tell me about a time something broke on your watch.

Testing ownership and honesty. Interviewers in this field have all had things break and distrust anyone who has not. Answer with what broke, what you did in the first hour, what you did afterward to stop it recurring, and what you would do differently.

Do not blame a supplier, a system or a colleague, even where they were at fault; describe what you controlled.

How do you prioritize when everything is urgent?

Testing whether you have a method or just a temperament. A good answer names a rule: what stops the operation first, then what affects a customer, then what affects cost, or whatever the real ordering was where you worked. Then give an example of applying it and of telling somebody their urgent thing was going to wait.

How would you onboard a new supplier?

Testing whether you think in steps and controls. Answer as a sequence: what you would need to know before agreeing anything, what checks you would run, what the contract has to contain, how you would trial them, and what you would monitor after go-live. Interviewers listen for whether you mention what happens when the supplier fails.

What would you do in your first month?

Testing whether you plan to learn before you act. The safe structure: understand what the operation is measured on, meet the people who run each part, find out what breaks most often.

Change nothing structural until you have done all three. Candidates who arrive with a plan to fix things they have not seen are marked down.

How do you handle someone who will not follow the process?

Testing influence without authority, which is most of the job. Answer with a case: find out why they are not following it, because the process is often the problem; fix the process if so; if not, make the cost of not following it visible to them and to their manager. Then say what you did when that did not work.

What would you measure for this operation?

Testing whether you understand what the operation is for. Before answering, ask what it is measured on now.

Then propose a few measures tied to the outcome the operation exists to produce, and say what you would do with each. A long list of generic measures is a poor answer. Three you can explain the use of is a good one.

Describe a process you would design from scratch.

Testing whether you can think about controls before volume. Start with the outcome, then the failure modes, then the checks that catch each one, then the steps. Candidates who start with the steps and never mention what could go wrong have described a flowchart, not a process.

Tell me about a time you had to deliver bad news upward.

Testing whether you report problems early. The answer they want is one where you told your manager something was going wrong before it became a crisis, with what you had already done and what you needed. The answer they fear is one where you fixed it quietly and told nobody.

Why operations?

Testing whether you know what the work is. Answer with what you actually like about keeping things running: the visible result, the problem-solving, the fact that the work matters when it fails. Avoid saying you like being organized, which describes a trait rather than a job.

The questions in one view

Answering without inventing a number

Operations interviewers ask for results and will probe any figure you give, because they know how often figures are manufactured for interviews. Three habits keep you safe.

State what you measured, in what unit, over what period, and how it was collected. A result with its method attached is credible; a bare percentage is not.

If you did not measure, say so, then describe the observable change: the backlog that cleared, the complaints that stopped, the shift that no longer ran late. Then say how you would measure it if you did it again. That answer shows more understanding than a suspiciously precise figure.

Never quote a number you would not be comfortable being asked to show evidence for. Some employers do ask, and in this field the evidence usually exists.

Questions to ask them

The interviewer's questions reveal what is broken in their operation. If they ask twice about suppliers, a supplier is the problem. Use what you hear.

What you do not have to answer

Some questions are not about the work. In most jurisdictions employers are restricted in what they may ask before making an offer, particularly about health and other personal characteristics, and the specifics vary by country. This site does not state the rules.

In the United States the Equal Employment Opportunity Commission publishes guidance on pre-employment inquiries; other countries have an equivalent body. Where a question seems to cross that line, answer the work question underneath it, such as whether you can work the shift pattern described, and note the exchange afterward.

Related reading on this site

Build a story bank for most questions above with the interviews guide. Learn what the field actually is and the four questions that tell you which operations job type you are interviewing for in the operations careers guide.

For the questions to ask about pay before accepting, see the operations pay guide. For the questions you should have asked about the posting before the interview, see where operations roles are advertised.

Common questions

What if my best example is from a job outside operations?

Use it. The question is whether you owned a process and its consequences, and that happens in many jobs. Say plainly that the setting was different and what transfers.

How technical should I get about systems?

As technical as the interviewer is. If they ask which platform you used, name it and say what you did with it. If they do not ask, a mention is enough; nobody is hiring you for the software.

Should I admit I have never handled a supplier?

Yes, then answer the question as a design problem, which is what it is. An honest answer with a clear sequence beats a pretended experience with no detail.

What if I cannot think of a time something broke?

Look harder. Everyone who has kept anything running has had it fail. If you genuinely have not, describe the closest thing and what you learned from watching someone else handle a failure.

How long should each answer be?

About two minutes for a story, less for a factual question. If the interviewer wants more they will ask, and the follow-up questions are where the assessment actually happens.