What do you dislike most about your current role?
answer
- one frustration, structural not personal
- state it without heat
- the charitable reason it exists
- what I actually tried
- stop at one, no list
basics
~20 sA badmouthing trap dressed as a candour test. Name one real structural frustration you can describe without contempt, give the charitable reason it exists, say what you did about it, and stop at one rather than opening a list.
how to answer
4 beats- the one thing, named without heatState a single frustration in neutral, factual language about a process, a boundary or an incentive — never a person or a role. Say it in one sentence so it lands as an observation rather than a build-up.
- the tradeoff that explains itGive the reasonable reason someone chose this: speed, headcount, stage, a constraint you can see. Being able to argue the other side is the single move that converts a complaint into judgement. If you cannot make that case, pick a different frustration.
- what I did about itDescribe one concrete attempt and its real outcome, including the part that did not move. Most of your airtime belongs here, and an honest partial result is more convincing than a clean victory.
- what I want instead, then stopClose with the property you are looking for next, in one sentence, and explicitly end the answer. Silence after it is the interviewer's turn, not an invitation to add a second complaint.
your answer
4 story prompts- Pick one frustration that is structural rather than a person, and write it in neutral words.
- Write the charitable reason the tradeoff was made; if you cannot, choose another frustration.
- Note the concrete thing you tried and what it did or did not change.
- Rehearse stopping after one item, even if the interviewer leaves a silence.
draft and rehearse your own answer in a learn session
go deeper
This is a candour and judgement probe wearing a friendly face. The interviewer wants to see whether you can criticise a real situation without contempt, and whether your frustration is structural or personal. A strong answer names one thing, explains charitably why it exists, shows what you attempted, and stops without spilling into a list of grievances.
Honestly, the thing that wears on me is that test ownership sits with the quality pod rather than with the squads writing the code. We are partway through moving off manual regression, and the model is still that a squad files a request and one of us writes the automation. Three of the nine squads have never run the suite themselves. The effect is a queue. Median turnaround on a request is about four days, and by then the person who understood the edge case has moved on to something else. I do not think it was a bad decision — when only two of us knew the framework, centralising was the fastest way to get coverage up at all. What I did was start a pairing rotation: any squad that wanted a check sooner than the queue could pair with me and keep the result. Four squads took it and now maintain their own packs, which moved roughly a third of the authoring work off the pod. The part I could not shift is that it stayed opt-in, because nobody wanted to make it a gate, so the squads who most need it are still the ones filing tickets. So what I am after is a place where developers own their tests by default. That is really the only thing on my list.
Strong because the frustration is a structure, the tradeoff is argued fairly, and the attempt has a number and a limit attached. The explicit stop at the end is deliberate. Naming the squads who resisted, or leaving out the pairing rotation, would turn this into a complaint.
The thing I find hardest is that quality work only gets funded right after something has gone wrong. I own the test platform, and nearly every improvement I have landed was approved in the fortnight following an escape that reached customers. In the quiet stretches the same proposal gets deferred to next quarter. I understand the pull. At that stage every month of runway is real, and quality investment pays back on a slower curve than a feature does, so I do not think anyone was being short-sighted. But it makes the work reactive, and reactive work is worse work — you fix the thing that just burned rather than the class of thing. What I did was stop asking for projects and start publishing a number. Every release I posted the hands-on checking hours the automation had removed and the hours still being spent, broken out by team. That turned an argument about principle into an argument about a line moving the wrong way, and it got the pipeline gate funded. Six of the nine teams are on it now and per-release checking is at thirty-one hours, down from ninety-six. What I would want to understand about working here is how quality investment gets decided when nothing is on fire. That is the whole of my complaint, and it is also my question for you.
The senior move is reframing an unwinnable principled argument as a measured one, and owning that reactive funding was partly a persuasion problem of his own. Ending on a question for the interviewer keeps it forward-facing. Contempt toward leadership, or the mechanism without the number, would drop it a level.
Safe ground is the conditions you learn under — review turnaround, feedback cadence, how much of the codebase you get to see. Pair it with what you asked for, so the answer shows initiative rather than passivity.
Pick a process or ownership problem inside your own area and show you understood the tradeoff that created it. The differentiator at this level is the attempt: something concrete you tried, and an honest account of how far it got.
Name an organisational constraint on the quality bar or on production ownership, in terms a leader would recognise. Say what you tried at the level you had, and turn the answer into a question about how this organisation decides the same thing.
The honest answer is usually an incentive problem, so state it in economic terms rather than as disappointment. At this level any contempt reads as a failure of your own influence, so pair the frustration with the mechanism you built despite it.
saying these in an interview costs you the question
- Naming a person, a manager or an identifiable colleague
- Claiming there is nothing at all you dislike
- A complaint that is really about being asked to do the job
- Rolling into a second and third grievance once you have started
- Contemptuous framing of the people who made the tradeoff
- No account of anything you tried to change
- What did you do about it?This is the follow-up that separates candour from complaining, so have the attempt ready before you name the frustration. Describe one concrete action and its real outcome, including partial or failed results. An honest partial win is stronger than a tidy success, because it shows you know where your influence ended.
- How much of that is on you?Take a genuine share without collapsing into self-criticism. Name one thing you would do earlier or differently — usually raising it sooner, or making the case in numbers rather than principle. Deflecting the whole thing outward here undoes the credit you just earned.
- What would you need from us so that does not repeat here?Turn it into a real question rather than a demand: how this team decides the thing you found frustrating, and who owns it. Keep the ask specific and small enough to be answerable in the interview, and listen properly to the answer, because it is information you actually need.