Operations Manager interview questions and answers

In my last role running a fulfilment centre, I reviewed five numbers every morning: orders dispatched against plan, on-time dispatch percentage against the customer cut-off, order accuracy measured by picking errors, units per labour hour by shift, and backlog carried into the day. Safety incidents were always the first item. These cover the customer promise, quality, productivity and risk in a few minutes. Weekly I looked at cost per order, attrition and absenteeism. Each KPI had an owner, and anything red got a short note on the cause and the action by the next morning’s meeting.

I start from the volume forecast by day and, where possible, by hour, agreed with sales or planning. I divide by standard productivity for each activity, for example orders picked per hour, to get labour hours needed, then add allowances for breaks, absenteeism and training. That gives headcount by shift. Because volumes vary, I keep a core team sized for normal days and use flexible levers for peaks: overtime within legal limits, cross-trained staff who can move between activities, and contract staff from an agreed agency with notice periods. I review forecast against actual every week and correct the plan.

Lean identifies wastes that add cost without value for the customer: overproduction, waiting, transport, over-processing, inventory, motion, defects, and unused skills of people. During my management trainee project at a bottling plant, I saw operators walking to a central store several times a shift to fetch labels and caps. That is motion and waiting. We set up a small point-of-use rack near each line with a two-bin system, so the store refilled one bin while the other was in use. Walking trips dropped sharply, and line stoppages due to missing materials almost stopped.

Say customer complaints about late deliveries rose in one city. With a fishbone diagram, I list possible causes with the team under headings like people, methods, machines, materials, measurement and environment. Then we check which causes the data supports. Suppose the data shows trucks leave the hub late. Why? Loading finishes late. Why? Orders reach the hub after the planned cut-off. Why? The upstream warehouse dispatch time was moved. Why? A new shift pattern there was not aligned with ours. The root cause is a planning gap between two sites, not lazy drivers. The fix is a joint dispatch schedule, then we track on-time departures.

I write SOPs with the people who do the work, not alone at a desk. I watch the task, note each step, and keep it short: purpose, scope, steps in order with photos where useful, key quality and safety points, and what to do if something goes wrong. I test the draft by asking a new person to follow it. Then I train the team, put a one-page version at the workstation and ask supervisors to do quick checks during shifts. If people keep skipping a step, I find out why, because often the SOP is wrong or impractical, and I update it with a version number.

I would start with a cost breakdown over the last year: labour, overtime, contract staff, rent, utilities, transport, consumables and vendor services, and find the largest and fastest-growing lines. Then I look for waste rather than cutting service. Typical areas are overtime caused by poor shift planning, high contract staff rates, rework from errors, energy use outside working hours and vendor contracts never renegotiated. I would set a target per line with owners, track savings monthly, and watch service KPIs alongside so we notice if cuts start to hurt. In my last site, overtime and vendor renegotiation alone delivered most of the target.

I look for where work piles up, the step with the highest utilisation and the longest queue in front of it. Little’s law helps too: work in progress equals throughput times lead time, so a growing queue with steady throughput means lead time is rising there. In a claims processing team, I found the bottleneck was document verification. Following the theory of constraints, we first made sure that step was never idle or doing rework, by checking files for completeness before they reached it. Then we moved simple verifications to another team and added a checklist. Only after that did we consider adding headcount.

First I check the SLA data with the vendor so we agree on the facts, for example housekeeping tasks completed on time at each site. Then I hold a joint review to find causes, such as staffing shortfalls, poor supervision or our own unclear instructions. I ask for a written corrective action plan with dates and track it weekly. The contract’s penalty clause gives me leverage, and I apply it if performance does not improve, but penalties alone rarely fix service. If the vendor still fails after the agreed period, I start bringing in an alternate vendor at one site, so we are ready to switch without disruption.

At a home appliance service company, technician first-visit fix rate was low, so customers needed repeat visits. In Define, we set the goal and scope with the service head. In Measure, we collected data on a few thousand jobs, recording the fault, parts carried and the reason for each revisit. In Analyse, a Pareto chart showed most revisits came from a few faults where the needed part was not in the technician’s van. In Improve, we changed van stock lists by area, using fault history, and added a pre-visit call to confirm the model. In Control, we added the fix rate to the weekly review. Revisits dropped noticeably.

I start planning about three months ahead with a volume forecast by week, agreed with sales. From that I plan extra staff, including when to hire and train them, because new people are slow in the first weeks. I check space and equipment, such as extra dock slots, handheld scanners and printers, and book transport capacity with carriers early. I agree a system change freeze with IT during the peak. We run a mock peak day to test the plan. During the peak, I hold short twice-daily reviews, keep a reserve team, and agree escalation contacts with key partners. Afterwards we record lessons for next year.

In the first two weeks I would mostly listen and observe: walk every shift, meet supervisors and staff one to one, review the data and talk to key customers. I would also fix any urgent safety risks immediately. By the end of the first month, I would pick two or three priorities that drive most of the problems, for example backlog and accuracy, rather than chasing every KPI. Then I would set up a daily performance meeting, clear owners and visible boards. I would make people changes only after giving everyone clear expectations and support. By day ninety, I would expect a steady trend on the chosen priorities.

A large corporate client of our facility services company complained to our CEO that their cafeteria hygiene audit had failed for two months running. I called the client’s admin head the same day, apologised, and visited the site the next morning. I found the problem was high staff turnover at that site, so trained people kept leaving. I put an experienced supervisor there temporarily, ran refresher training for all staff and set up a weekly joint audit with the client. Within a month, audits passed. Longer term, we revised wages for that site to match the local market, which reduced turnover.

In a warehouse I managed, a forklift reversed into a racking upright and part of a pallet fell. Nobody was hurt, but it was close. I stopped operations in that aisle, made sure everyone was safe and had the racking inspected before reopening. We reported it as a near miss and did a proper investigation with the operator, supervisor and safety officer. The causes were a blind corner, no pedestrian segregation in that zone and pressure to load quickly. We added mirrors, marked walkways, introduced a speed limit and reminded supervisors that speed never overrides safety. Near-miss reporting increased after we shared the outcome openly.

A shift supervisor in my team was repeatedly late in submitting shift reports and, more seriously, had approved overtime for people who had not worked it. First I gathered the facts from attendance and system records. I met him with HR, showed him the evidence and listened to his explanation. The overtime issue breached company policy, so after a proper inquiry the company ended his employment. I made sure the process was fair and documented, and I spoke to his team afterwards without sharing private details, explaining that rules on attendance and overtime apply to everyone. I also tightened overtime approval controls.

At a customer service centre, I wanted to move from individual email handling to a shared queue with categories, so urgent issues would not sit in one person’s inbox. Senior agents resisted because they felt they were losing ownership of their customers. I asked two of them to help design the categories and run a two-week pilot in one team. The pilot showed faster response times and fewer missed emails, and the senior agents presented the results themselves. We kept an option for agents to follow up on complex cases they had started. After that, the rest of the centre adopted it with little pushback.

As a shift in-charge trainee at a dairy plant, our main chilling unit failed late in the evening with milk tankers still arriving. The maintenance team could not say how long repair would take. Milk quality would suffer if it was not cooled within a few hours. I called my manager, and with his approval, I diverted the next tankers to our sister plant, used the backup chiller for milk already received, and paused new intake. I informed the procurement team so farmers’ collection centres were updated. The repair took six hours, and we lost no milk. Next day we reviewed the backup plan formally.

In my first operations role at a logistics hub, the day and night shift supervisors kept blaming each other for unfinished work at handover. Arguments were affecting the teams. I met each of them separately, then together, and focused on facts rather than blame. The real cause was that there was no clear definition of what each shift had to complete. We agreed a handover checklist, a short joint handover meeting at shift change, and a shared tracker of open items. I reviewed it with them for a few weeks. Complaints stopped, and backlog carried between shifts reduced.

Yes. In my current role I manage two sites about three hours apart and spend at least two days a week at the second site. I have learned that regular presence matters, so I would plan a fixed visit schedule for each site, with unannounced visits occasionally. Between visits, I rely on daily KPI reports, a short video call with each site lead, and strong site leaders who can take decisions locally. I would like to understand how often you expect me at each site and the travel policy, but frequent travel is something I am already used to.

During my MBA summer internship at a grocery delivery company, I spent eight weeks in a dark store improving picking accuracy. I enjoyed being on the floor, working with pickers and seeing a change show up in the numbers the next day. That is what I want from my career: practical problems with visible results. Your company is expanding warehouses into smaller cities, and your management trainee programme rotates through inbound, outbound and transport, which would give me a complete view. I am prepared for shifts and floor work in the first years, because that is how good operations managers learn.

I am currently at ₹15 lakh CTC as an operations manager handling one warehouse with about 180 people. This role covers three sites and a larger team, so I am looking for ₹19 to 20 lakh fixed, plus the performance bonus. I would also like to understand the travel allowance and whether there is a relocation benefit, since the base location is a different city for me. I am flexible on the structure, but the total needs to reflect the added responsibility and travel. My notice period is 60 days.