What Frustrates You at Work? How to Answer It

What the "what frustrates you" question tests, a sample answer with notes, two follow-ups, and how to adapt it for exit interviews.

When an interviewer asks what frustrates you at work, they are checking two things: whether your frustration clashes with the job you are applying for, and what you do when something annoys you. A strong answer names one real, work-related frustration that does not describe the core of this role, gives one short example, and spends most of the time on what you did about it. Good choices are usually about process, such as rework, unclear ownership or decisions that keep getting reopened, rather than about people. Keep the complaint to a sentence or two and make the action the centre of the story.

What the question tests

The question looks like an invitation to vent. It is closer to a fit check with a behavioural follow-up attached.

Fit. Your answer tells the interviewer what you will find hard about their job. If you say that interruptions drive you mad and the role is a front desk, you have probably talked yourself out of the job. If you say that you find it frustrating when work stalls waiting for approvals and the company has a slow sign-off culture, that is useful information for both sides.

Self-control. Everyone gets frustrated. The interviewer wants to hear that you notice it, keep it out of how you treat people and turn it into something constructive.

Judgement about what is worth caring about. A frustration reveals a value. Being bothered by rework says you care about other people's time. Being bothered by colleagues who "don't work as hard as me" says something less flattering, even when it is true.

Honesty. "Nothing really frustrates me" is a non-answer. It suggests either low self-awareness or a rehearsed dodge, and it leaves the interviewer to guess.

Check the frustration against the job first

The fastest way to sink this answer is to name a frustration that is a daily part of the role. You can check this before the interview rather than guessing.

O*NET OnLine, an occupation database sponsored by the US Department of Labor, rates each occupation on "work context" items on a 0 to 100 scale, where 100 means "every day" and 0 means "never". Two are especially useful here:

• [Dealing With Unpleasant, Angry, or Discourteous People](https://www.onetonline.org/find/descriptor/result/4.C.1.d.2). Customer Service Representatives score 80, which sits between weekly and daily. Rude customers are a bad choice of frustration for that job.
• [Time Pressure](https://www.onetonline.org/find/descriptor/result/4.C.3.d.1), defined as how often the job requires meeting strict deadlines. If your target role scores high, "tight deadlines" will sound like you do not want the job.

Look up your target occupation, scan its work context ratings, and rule out any frustration that maps onto something it rates high. What is left is your shortlist.

Frustrations that usually work (as long as they are true for you):

• Rework because nobody agreed what "done" meant before starting
• Decisions that get reopened after everyone has committed to them
• Unclear ownership, where a task falls between two teams
• Information that one person holds and nobody else can find
• Meetings that end without a decision or a next step

Frustrations that usually hurt you:

• A specific person or former boss
• Anything that sounds like the job itself: customers, deadlines, ambiguity in a startup, repetitive work in an operations role
• Pay, hours or workload, which sounds like you are already negotiating
• Fake weaknesses such as "people who are less committed than me"

A sample answer, with notes

This is an illustrative answer for an operations or marketing analyst, not a real person's story. Use your own example: a borrowed one falls apart at the first follow-up question.

What frustrates me most is rework that could have been avoided, where something is finished and then has to be redone because we never agreed what it was meant to answer.

In my last role, I built a monthly performance report for the sales team. I spent about a week on the first version, and when I presented it, the sales director said it was not what she needed. She wanted to know which regions were behind target, and I had built a channel breakdown. Neither of us was wrong; we had just never written it down.

I was annoyed, mostly at myself. So for every request after that, I wrote a short brief before starting: the question the work answers, who will use it, what decision it feeds into, and what the first version will and won't include. I sent it to the requester and only started once they replied. It added maybe ten minutes per request. The next report went through with one small change, and two other analysts on the team started using the same brief.

It still bothers me when work gets thrown away, but now I treat it as a signal that the brief step got skipped, and I go back and fix that rather than just redoing the work.

Why this works:

• The frustration is about a process, not a person. The sales director is not the villain; the missing agreement is.
• It shows a value the employer wants. Caring about wasted effort reads as caring about the team's time.
• Most of the answer is the action. The complaint is one sentence. The brief, and the fact that others adopted it, take up the rest.
• The ending is honest. It does not claim the frustration disappeared. It shows a habit for handling it, which is more believable.
• It has an example ready. Interviewers often follow up by asking for an example, so have one ready. One well-told example beats three thin ones.

Spoken aloud, this takes about a minute and a half. That is about right for this question; it is less weighty than "tell me about a conflict", so keep it shorter.

Two follow-ups to prepare

"How do you handle it in the moment?" The interviewer wants to know what happens before you have had time to design a process. Give a concrete habit: you ask one clarifying question before reacting, you write down what went wrong and raise it later in a calm setting, or you separate fixing today's problem from preventing the next one. Avoid saying you "just stay calm"; describe what you actually do.

"What would you do if that happened here and you couldn't change it?" This checks whether you can live with things outside your control. A good answer: you would raise it once with the person who owns the process, with an example and a suggested fix, then work within the decision. Saying you would keep pushing until it changed suggests you cannot let things go.

Common mistakes

• Naming a person. Even a deserved complaint about a former manager tells the interviewer how you might talk about them.
• Venting. If the frustration takes more than two sentences, you have stopped answering the question.
• No action. A frustration with no response sounds like a complaint. Always say what you did.
• Picking something you can't change, then saying you changed it. "I fixed company politics" will not survive a follow-up.
• A humblebrag. "I get frustrated when others don't care as much as I do" is a cliché, and it is also a criticism of your future colleagues.
• Saying "we" throughout. Oregon's Department of Consumer and Business Services, in its STAR method guidance, tells candidates to describe one specific event and to use "I", not "we", when describing their actions.

Two other versions of the question

"Name one thing at work that excites you and one that frustrates you." Pair them so they come from the same value. For example: you are energised when work ships and you can see people using it, and frustrated when finished work sits waiting for approval. That makes the frustration read as the flip side of a strength rather than a flaw. Give the exciting half a little more time than the frustrating half.

"What did you find most frustrating about your job?" in an exit interview. This one is different, because the employer genuinely wants the candid answer. In a 2016 Harvard Business Review article, Everett Spain and Boris Groysberg describe exit interviews as a way for companies to learn why skilled people leave and how the organisation could improve. So be more specific than you would in a hiring interview, but keep the same discipline: describe what happened and its effect on your work, focus on systems rather than personalities, and suggest one fix. Remember that the conversation may be noted down, and that the people involved may be asked for references later.

Related questions

This question often comes up alongside a policy you disagreed with and which of our core values resonates with you most. Prepare them together so your answers do not contradict each other: if you say ambiguity frustrates you, do not then pick "move fast" as the value you love.

Practising it

Write your answer in three parts (the frustration in one sentence, the example, what you did and what changed), say it aloud and time it, then have someone ask the two follow-ups without warning. If you use Verve AI's Interview Copilot, you can add STAR stories like this one to its Knowledge Base, and the copilot draws on the documents you have enabled when it suggests answers.

For more prompts broken down the same way, browse the interview question bank.

Sources

• O*NET work context scale (0 to 100, "every day" to "never") and the "Dealing With Unpleasant, Angry, or Discourteous People" item; Customer Service Representatives score 80: https://www.onetonline.org/find/descriptor/result/4.C.1.d.2
• O*NET "Time Pressure" item ("How often does this job require the worker to meet strict deadlines?"): https://www.onetonline.org/find/descriptor/result/4.C.3.d.1
• O*NET work context categories (conflictual contact, pace and scheduling): https://www.onetonline.org/find/descriptor/browse/4.C
• O*NET OnLine sponsored by the U.S. Department of Labor, Employment & Training Administration: https://www.onetonline.org/
• Oregon DCBS on the STAR method (one specific event, "I" not "we"): https://www.oregon.gov/DCBS/jobs/Pages/the-STAR-method.aspx
• Spain and Groysberg, "Making Exit Interviews Count", Harvard Business Review, April 2016 (exit interviews as a way to learn why people leave and how to improve): https://hbr.org/2016/04/making-exit-interviews-count
• Verve AI Knowledge Base (STAR stories, answers draw on enabled documents): https://docs.vervecopilot.com/features/knowledge-base