To answer “tell me about a time you handled a heavy workload,” tell the story of one specific overloaded stretch: what landed on you and why, how you sorted it, who you told and what you asked for, what you delivered and what you deliberately let slip. Interviewers are checking that you stay organized, communicate early and protect quality under volume, rather than quietly working longer hours until something breaks. End with the result and one thing you changed so the next peak was easier.
A past story, not a method
This is a behavioral question, so it wants a real event. It is easy to confuse with its hypothetical cousin:
| “Tell me about a time you handled a heavy workload” | “How do you handle a heavy workload?” | |
|---|---|---|
| Type of question | Behavioral: a real past event | General: your usual approach |
| What you lead with | The situation: when, where, how much | Your method: how you sort and communicate |
| Evidence | The outcome of that week or month | A short example that proves the method |
| Length | About 90 seconds to two minutes | About 60 to 90 seconds |
Many candidates answer the story version with their general method and never reach a real event. If you are asked “how do you,” our guide to how do you handle a heavy workload has short method-first answers. This page is for the story.
What the interviewer listens for
- A cause. Why the load was heavy: a colleague left, a seasonal peak, a storm, an outage. Not “I'm always this busy.”
- Triage. How you decided what came first: deadline, impact, safety and who was waiting.
- Communication. Who you warned and what you asked for, before deadlines passed.
- Quality. What you refused to compromise.
- Sustainability. You didn't burn yourself or your team out, and you changed something afterwards.
Public-sector panels often use the framework's own words. The UK Civil Service Success Profiles behaviour “Delivering at pace” is defined as taking responsibility for delivering timely and quality results with focus and drive, and the NSW framework's “Plan and prioritise” capability is about planning to achieve priority outcomes and responding flexibly to changing circumstances (both checked November 2026); our Success Profiles interview guide explains how those answers are scored. Outside government, it is common in administrative, healthcare, contact-centre, logistics, recruiting, accounting and agency roles: anywhere work arrives in waves.
Choosing the right stretch
- A specific, dated period: “the three weeks after our coordinator left,” not “tax season every year.”
- A real cause beyond normal busy days.
- Choices you made, including something you postponed or handed off.
- A result you can describe: deadlines met, a backlog cleared, service kept up.
Avoid stories where all-nighters were the solution, where the overload came from your own delays (unless you own that and show the fix), or where you dropped something important without telling anyone. If the heart of the story is choosing between two important demands rather than sheer volume, the competing-priorities question suits it better.
A structure: load, sort, say, deliver, reset
- Load (about 20 seconds): what landed, why, and the scale in numbers.
- Sort (about 25 seconds): how you triaged, and the rule you used.
- Say (about 20 seconds): who you told, what you asked for and what you postponed.
- Deliver (about 20 seconds): the result.
- Reset (about 15 seconds): what you changed so the next peak was easier.
It is the STAR method with the Action split into sort and say. The “say” step is the one most candidates leave out, and it is often what the interviewer is waiting for. For triage language, see how to prioritize multiple tasks.
Five overloaded stretches, told well
We wrote these to show the shape in different jobs; they are not real candidates' stories. Use your own situation, your own numbers and your own words.
Entry-level: an inherited inbox
“Two months into my first job as an administrative assistant at a property management company, the other assistant left with a week's notice. I inherited her inbox, about 300 unanswered emails, on top of my own work for four property managers. On the first morning I sorted everything into three groups: repairs or tenant safety, anything with a date attached, and everything else. I told my manager the plan and asked her which routine requests could wait two weeks; she agreed that filing and newsletter updates could. I wrote three template replies for the most common questions, which covered about a third of the emails, and blocked the first hour of each day for the backlog. Within two weeks the inbox was under 30, no repair request had been missed, and the templates shortened the new assistant's training.”
Customer-facing: an airline contact centre in a winter storm
“I worked in an airline's customer contact centre when a winter storm cancelled several hundred flights over two days. Wait times went from minutes to hours, and nearly every call was a rebooking. Our team leader asked us to put customers flying within 24 hours first, so I handled those calls first and pointed later travelers to the self-service rebooking option with clear instructions. I kept a running note of the waiver rules, which changed every few hours, because getting them wrong would have meant repeat calls. When I noticed customers being rebooked onto flights that were themselves at risk, I told my team leader, and she raised it with the operations desk. I handled about twice my normal volume over the two days, my quality score held, and my running note became the team's shared policy sheet for the next disruption.”
Trades: an HVAC technician in a heat wave
“I'm an HVAC technician, and during a week-long heat wave our service calls roughly tripled while two of our six technicians were off. Dispatch was booking calls in the order they came in. I asked the dispatcher whether we could triage instead: households with elderly people, infants or medical needs first, then commercial cooling for food or medicine, then everyone else. She agreed, and the owner backed it. Between jobs I called customers further down the list myself to give an honest arrival window and simple ways to keep cool, which cut the angry follow-up calls. I took extra jobs in the evenings but kept to our rule of no rooftop work alone after dark. By the end of the week every priority call had been answered within a day, and the owner made the triage list part of our heat-wave plan.”
Office: a recruiter covering a colleague's roles
“As a recruiter at a healthcare staffing firm, I took on a colleague's 18 open roles while she was on leave, on top of my own 15. I spent the first afternoon putting all 33 in one list with the hiring deadline, the stage each role was at and how hard it would be to fill. Then I met each hiring manager briefly to confirm priorities, and three agreed to push their start dates back a month. For two very specialized roles I asked my director to approve a partner agency, which she did. I batched first-round phone screens into two afternoons a week to keep mornings for offers and candidate calls. Over six weeks we filled 14 roles, including all eight marked urgent, and none of my own roles slipped. I also set up a shared tracker so the next handover takes an hour, not a day.”
Manager: peak season in a fulfilment centre
“I was a shift manager at an e-commerce fulfilment centre during peak season, when order volume more than doubled from mid-November and my shift grew from 60 to about 110 people with seasonal hires. The load was on the team as much as on me. Before peak, I paired every new starter with an experienced buddy for their first three shifts and moved my two strongest leads to training and problem-solving instead of picking. During peak I ran a five-minute huddle at the start of each shift with the day's volume and one focus, and I protected breaks on the heaviest nights, because tired people make picking errors and get hurt. Each evening I sent my site manager volume, backlog and next-day staffing, so extra shifts were approved before we needed them. We shipped on time through the season with fewer picking errors than the previous peak, and the buddy system became standard.”
Follow-ups after a workload story
- “What did you let slip?” Name it, and say who knew and agreed.
- “How did you know you were at capacity?” A concrete signal: a queue, a backlog count, a date you couldn't meet.
- “What would you do differently?” Usually: raise the flag sooner.
- “How do you look after yourself in weeks like that?” Something real and brief; our guide to how you handle stress covers this.
- “What if your manager had refused to move anything?” Say how you would have narrowed the scope or asked for help elsewhere, and that you would have kept them informed.
Mistakes that sink a workload answer
- Hours as the hero: “I just worked until midnight” tells the panel the next overload will break you.
- No numbers. How many emails, calls, roles or orders, and over how long?
- Silent triage. If nobody knew what you postponed, it reads as dropping work.
- A complaint about the employer that caused the overload.
- No reset. Interviewers like hearing what you changed afterwards.
Rehearse it out loud: say the load in one sentence with a number, then time yourself. An AI mock interview builds questions from your résumé and the job description and scores each spoken answer out of 10. Prepare “what did you let slip?” too; most candidates haven't. You can also try a typed answer in the free practice demo.
Where CoPilot Interview fits
CoPilot Interview is an AI interview assistant with a free AI mock interview that builds questions from your résumé and the job description, reads them aloud and scores your spoken answers out of 10, so you can rehearse workload and pressure stories before a busy-role interview. Mock interviews run in 10 languages. The free plan gives 15 minutes a day of live help in sessions of up to 15 minutes, with AI mock interviews included. Paid plans are Standard at $24.99 a month and Pro at $39.99 a month. It runs as a desktop app for Windows 10 and 11 and macOS 12 or later, a free iPhone and iPad companion on the App Store (iOS 16 or later) and an Android companion in beta.
In the real interview, follow your employer's rules on AI help. AI can help you structure and tighten a story, but it must not invent one: every event, number and name in your answer has to be true and yours.
Disclosure: CoPilot Interview is our product, so weigh what we say about it accordingly.
Frequently asked questions
What is a good example of handling a heavy workload?
A specific period with a real cause, such as a colleague leaving or a seasonal peak, where you sorted the work, told the right people what would move, delivered what mattered most and changed something afterwards.
Is it OK to say I asked for help?
Yes. Asking early, with a clear request, is one of the things interviewers want to hear. Asking only after a deadline has passed is the warning sign.
Should I mention working overtime?
Briefly, if you did, but not as the solution. Panels are more reassured by how you sorted and communicated than by extra hours.
How is this different from “tell me about a time you worked under pressure”?
Pressure questions are usually about stakes or a tight deadline; workload questions are about volume over a period. One story can answer both if it has both.
How long should the answer be?
About 90 seconds to two minutes, with the most time on how you sorted the work and who you told.
Rehearse it out loud before the real one
The AI mock interview builds questions from your resume and the job description, reads them aloud and scores each spoken answer out of 10. Included on the free plan.
Start a mock interview