Teamwork, time management and problem-solving questions

Why these three questions travel together

Almost every job advert asks for a team player, someone organised, and someone who can solve problems. So almost every interview contains a question from each of those three families, usually in the middle of the conversation.

The wordings are familiar. “Tell me about a time you worked as part of a team.” “How do you stay organised?” “How do you prioritise when everything is urgent?” “Tell me about a time you handled a difficult situation.” “Give me an example of a problem you solved at work.” “Tell us about a time you overcame a challenge.”

Two of those are deliberately vague. “A difficult situation” and “a challenge” let you choose the ground, which is a gift if you prepared and a trap if you did not: unprepared candidates reach for an interpersonal problem when a logistics story would have scored better. Decide your difficult situation in advance.

The good news is that you do not need nine stories for nine questions. Three or four solid examples, told with different emphasis, cover this whole territory.

Teamwork questions: show your own part

The trap in teamwork questions is the word team. Candidates answer in the plural, the interviewer hears a description of a department, and nothing gets scored.

MIT’s career office suggests that most of a behavioral answer, roughly sixty percent of it, should be the actions you personally took. That is exactly the correction a teamwork answer needs: say what the group was trying to do in one sentence, then spend the rest on your own contribution.

What interviewers listen for beyond that is how you handle the parts of teamwork that are not pleasant. Did you pick up a gap nobody owned? Did you tell someone their part was late, and how? Did you adapt when a colleague worked differently from you? Did you give credit where it was due? A teamwork story in which everyone was lovely and everything worked is less convincing than one with a small amount of friction handled well.

The National Careers Service points out that examples do not have to come from paid work, and gives a school sports team fundraiser as a worked teamwork example. For early-career candidates that is the normal source: group projects, sports, volunteering, a society committee. Choose the one where your role was distinct.

If the question is really about disagreement rather than cooperation, it belongs to the conflict family and has its own answer.

Time management and "how do you stay organised?"

This is the family where honesty beats polish, because the interviewer wants to know what happens to their request when you already have five others.

Start with the system you genuinely use, named concretely: a single list reviewed each morning, a shared board with a column for blocked items, a calendar where tasks get booked as appointments, a notebook with a line per commitment. Vague answers about being naturally organised score nothing. Specific mechanics score well, even if they are low-tech.

Then give the harder half, which is prioritisation. How do you choose when two things are both urgent? Good answers name a rule and then apply it: deadlines that affect other people first, then the thing with the largest consequence if it slips, then the quick items that unblock someone else. Even better answers include the conversation you had rather than the silent heroics: going back to the person whose work would be late, saying what would move, and agreeing it.

Finish with evidence that the system survives pressure. One short example of a week where it broke and what you changed is worth more than a tidy description of the system working perfectly. In roles with constant inbound work, expect a follow-up about interruptions, so be ready to say how you capture one without losing the thing you were doing.

Problem solving and "a difficult situation"

A problem-solving answer has one part the others do not need: diagnosis. Most candidates jump from “the report was wrong” to “so I fixed it”, which tells the interviewer nothing about how they think.

Slow down the middle. Say what you checked first and why, what you ruled out, who you asked, and what evidence told you the cause. Two sentences are enough. The National Careers Service gives a florist example in which mixed-up wedding deliveries are resolved by driving out to correct the error and offering compensation; what makes that kind of story work in an interview is the moment you say how you established what had actually gone wrong.

For “tell me about a time you handled a difficult situation”, pick the difficulty deliberately. Operational difficulties are usually the strongest choice: a supplier who missed a delivery, a system down during your busiest hour, a colleague off sick the day before a deadline, a customer order that could not be fulfilled as sold. They let you show judgement without putting a named person in a bad light.

Close with the result and, where it exists, the preventive step. “We delivered on the Friday” is a result. “And I added a confirmation call forty-eight hours before any dated order” is the sentence that makes an interviewer write your name down, because it shows you solve the class of problem, not just the instance.

One example from each family

These are written to be adapted. Keep each to about ninety seconds spoken.

“Tell me about a time you worked as part of a team”

Situation: Four of us ran the weekend inventory move into a new stockroom layout, with the shop open throughout.

Task: I was responsible for the goods-in section and for keeping a running record so the team knew what had already been moved.

Action: I wrote the record as a shared sheet on the back wall rather than on my phone, so anyone could update it without asking me. When one colleague fell behind on the heavy racking, I moved to help him for an hour and told the supervisor we would finish goods-in later than planned rather than let the racking run into Sunday. I took the slowest part myself at the end of the day.

Result: We opened Monday with the full layout in place and no stock unaccounted for. The wall sheet is now how the store runs every delivery day.

“How do you stay organised when everything is urgent?”

Situation: In my admin role I support three managers, and in one week two of them scheduled client visits on the same two days.

Task: I had to get both visits prepared without dropping the payroll deadline, which was fixed.

Action: I work from one list that I rebuild every morning, with anything that has an external deadline at the top. Payroll stayed first. Then I went to both managers, showed them what would have to wait, and asked which of the two visit packs they wanted finished first. One of them agreed their second-day pack could be a shorter version.

Result: Payroll went in on time, both visits had what they needed, and we now put client visits on a shared calendar before they are confirmed.

“Tell me about a time you handled a difficult situation”

Situation: Our booking system went down on a Saturday morning with about thirty appointments in the diary and no way to see them.

Task: I was the senior person on shift, so the recovery was mine to run.

Action: I called a colleague at another branch to check whether the outage was ours alone, which told me the problem was local. Then I rebuilt the day’s list by hand from the previous evening’s confirmation emails in my inbox, and split the team: one person phoning to confirm times, two keeping people moving.

Result: We saw twenty-eight of the thirty, with two rebooked. I asked for an end-of-day export of the next day’s diary to be emailed automatically from then on, which has since covered two more outages.

Build four stories, not twenty

Interviewers rarely reward variety for its own sake. They reward a relevant example with your actions in it, which means the same raw material can serve several questions if you shift the emphasis.

Take the stockroom move above. Told with the shared wall sheet and the hour spent on racking in front, it is a teamwork answer. Told with the decision to let goods-in run late, it is a prioritisation answer. Told with the reason you believed the racking would overrun into Sunday, it is a problem-solving answer. Nothing about the events changed; the middle of the answer did.

So prepare four examples from the last two years, each with a different flavour: one where you organised other people, one where you organised yourself under pressure, one where you found a cause nobody had found, and one where the outcome was only partly good. Write each in four or five lines, not as a script.

Then read the job advert and mark the words these questions will come from. The National Careers Service suggests letting your answers reflect the skills the employer asked for, and this is where that happens: the advert decides which story goes first.

What loses marks

Answering in the plural. If an interviewer cannot tell which part you did, the answer is unscoreable, however good the project was.

Describing a tool instead of a method. Naming a piece of software is not a time-management answer; what you do each morning, and how you decide what slips, is.

The frictionless story. Teamwork examples with no awkward moment and problem examples where the fix was obvious suggest either a very easy job or a very selective memory. A small difficulty handled calmly is the most persuasive material you have.

Skipping the diagnosis. “So I sorted it out” is where most problem-solving answers fail. Put two sentences of how you worked out the cause in the middle.

No ending. Say what happened, and if you changed something so it would not recur, say that too. A preventive step is the cheapest way to sound like someone who has been doing the job rather than surviving it.

And going long. Ninety seconds is enough for any of these.