Most interviews are not lost on the hard questions. They are lost on the throwaway sentences, the ones you say while relaxing between two real answers. A hiring manager will forgive a shaky answer about a technical failure. What sticks is the offhand line that reveals how you think about work, about other people, and about yourself.
What follows is not a list of things that sound rude. Rudeness is rare and easy to spot. These are seven phrases that sound perfectly reasonable when you say them, and that quietly change the interviewer's mental model of you. For each one: the exact wording people use, what the person across the table actually infers, and a line you can say instead.
1. "My last manager was a nightmare"
The wording varies. "The culture there was toxic." "My boss took credit for everything." "Honestly, the whole team was dysfunctional." Sometimes it is completely true. That is the trap: because it is true, you feel entitled to say it.
Here is the inference. The interviewer does not know your old manager and cannot verify anything. What they do have is a live demonstration of how you talk about a workplace once you have left it. And the person listening is a future ex-manager. You are showing them, in real time, what your exit interview about them will sound like.
There is a subtler second read. Blame-heavy stories are low on agency. If the story is "they were awful and there was nothing I could do," the interviewer hears someone who did not try. Even in genuinely bad environments, strong candidates can describe an attempt.
Say this instead: "The way decisions were made there did not fit how I work best. Priorities shifted weekly, so I started running a short Friday scoping call with my lead to lock the next week. It helped, but the underlying pattern did not change, and that is why I started looking."
It names a real problem, describes an attempt, and lands on a forward-looking reason. If the interviewer pushes for detail, stay factual: describe the mechanism, not the person. "Feedback came only during annual reviews" is fine. "My manager was insecure" is not.
2. "No, I think you've covered everything"
This is the most common item on any list of things never to say in interview settings, and it is still said constantly, usually out of politeness. You have been talking for fifty minutes, the interviewer looks tired, and you do not want to drag it out.
What gets inferred is not laziness. It is low interest. Interviewers spend their week with people who want the job at a level of abstraction. The candidate who asks a sharp question has clearly imagined doing the work. And your questions are data about how you think: "how is success measured in the first six months?" signals outcomes; "who would I work with day to day?" signals collaboration. There is a practical side too. Take no information out of the room and you are outsourcing your decision to a job description.
Say this instead: pick two or three that are real for you.
- "What does the person in this role need to get right in the first ninety days for you to feel this hire worked?"
- "Is this a new role or a backfill? What did the last person do differently?"
- "What is the part of this job that people underestimate before they start?"
- "How does this team decide what not to do when everything is priority one?"
Avoid questions that are really compliments in disguise ("what makes your culture so special?"), and anything answered on the homepage. If the interviewer genuinely was thorough, name what you learned: "You covered scope and the team. The one thing I am still curious about is how the reporting line works during the reorg you mentioned."
3. "I'm flexible, I'd be happy doing anything"
Said in good faith, almost always. You want to signal openness and low ego. Junior candidates say it because they feel they cannot afford to be picky; career changers say it because they are unsure what they qualify for.
The interviewer hears: this person has no thesis about their own career. That becomes a hiring risk, because someone who would be happy anywhere might leave for anywhere. A manager wants a reason to believe you will still be interested in this work in eighteen months, and "I'll do anything" removes that reason.
It also makes you hard to sell internally. Your interviewer goes into a debrief and has to describe you in one sentence. If you did not supply a sharp one, they will invent a vague one, and the vague candidate loses every time. Flexibility itself is fine. State it as a margin around a direction, not as an absence of one.
Say this instead: "What I want to be doing is the analytics side of customer operations, that is where I have gone deepest and where my last two moves pointed. Within that, I am genuinely open on scope, and I have no problem picking up the messy adjacent work, I did a lot of it when the reporting stack got rebuilt last year."
Direction plus flexibility. Not flexibility instead of direction.
4. "My biggest weakness? I'm a bit of a perfectionist"
Along with "I work too hard" and "I care too much," this is the most transparent move in the repertoire, and interviewers have heard it a thousand times. The variants keep getting more sophisticated ("I take on too much because I struggle to delegate") but they land the same way, because they are all strengths in costume.
The inference is not "this person is weak." It is "this person will not be candid with me," and that damage is disproportionate. The weakness question is not about the weakness. It is a test of self-awareness under mild pressure, and a humblebrag fails the real test while appearing to pass the fake one. People fear that naming a genuine gap disqualifies them. It rarely does, as long as the gap is not the core of the job and you can show movement.
Say this instead: "I am not naturally good at pushing back on stakeholders. For a long time I absorbed the extra request by working later. It caught up with me on a launch two years ago, when I missed a deadline that mattered because I had said yes to four things I should have flagged. Now, when a request lands, I reply with what it will displace and let them choose. It feels blunt, but people respond well to it."
Real gap, real consequence, real correction. Do not pick a weakness that is fatal to the role you are applying for, and never pick "I am bad with deadlines" if the job is deadline-driven. Choose something true and non-central.
5. "So what's the salary, and how much holiday do we get?"
Timing, not topic. Compensation is a legitimate, necessary conversation and you should absolutely have it. Asking in the first ten minutes of a first interview, before you have made any case for yourself, is what causes the problem.
The inference is about sequencing. Every interviewer runs an implicit model of what a candidate is optimizing for, and the earlier a topic comes up, the higher it sits in that model. Work first, money later, and you look like someone who wants the job and expects to be paid properly. Reverse the order and you look like someone shopping, which weakens your position in the exact negotiation you were trying to get ahead of.
One version hurts more: the string of comfort questions clustered together. Salary, then holiday, then remote days, then "is there flexibility on the start date." Individually, all fair. Fired off in minute eight, they read as someone planning their absence before their arrival.
The exception is real: if a recruiter opens the screening call by asking your expectations, answer directly. The range is the point of that call. Do not be coy there.
Say this instead, later in the conversation and framed as alignment: "Before we go further, it would help to check we are in the same range so neither of us wastes time. The roles I have been speaking to are landing between X and Y. Does that work with the band for this position?"
Ask about holiday and remote policy once an offer is in motion, or ask HR. That is what they are there for.
6. "To be honest, I'm not totally sure what the role involves"
Said with a self-deprecating laugh, usually as an invitation for the interviewer to explain. Sometimes it is even fair: plenty of job descriptions are copy-paste sludge and the recruiter told you almost nothing.
The problem is that the sentence puts the burden of your preparation on them. The interviewer infers that you applied indiscriminately, or did not spend twenty minutes on the company before showing up. The fix costs almost nothing, which is exactly why the omission is judged so harshly. Close relatives: "I haven't had a chance to look at your product yet." "Sorry, remind me what the company does?"
When the description genuinely is vague, show your work and then ask a precise question. Bring a hypothesis, not a blank.
Say this instead: "From the description and from what I could see of how your onboarding flow works, my read is that this role sits mostly between the product team and support, and that the first job is cutting down repeat tickets. Is that roughly right, or is the emphasis somewhere else?"
Even if your read is wrong, you win. You demonstrated preparation, gave them something concrete to correct, and turned a passive moment into a real conversation. Being wrong with evidence beats being blank.
7. "I'm a real people person and a hard worker"
The purest example of interview phrases to avoid, because it is not false, it is empty. Nobody says they are a lazy loner. Any claim whose opposite would never be made carries zero information, and interviewers filter it out automatically. Same family: "I'm very detail-oriented," "I'm passionate about what I do," "I'm a fast learner."
The inference is thinner than people expect. It is not that the interviewer disbelieves you. It is that they now have nothing to write down. Interview notes are made of specifics, and at debrief the candidate who filled the notepad with facts beats the one who filled it with adjectives. You can be the hardest worker in the pipeline and lose to someone less capable who described one real thing they built. There is a status effect too: describing yourself in adjectives is what people do when they cannot describe themselves in evidence, so the habit reads as inexperience.
The rewrite rule is mechanical: for every adjective you are tempted to use, replace it with the shortest true story that would let someone conclude the adjective themselves.
Say this instead: "The part of the job I am best at is being the person other teams come to. At my last place the support leads started routing edge cases to me directly rather than through the queue, because I would actually go and sit with them for twenty minutes instead of sending a link. It was not in my remit, but it cut our escalation back-and-forth by about half."
Nobody said "people person." Everybody understood it.
The pattern underneath all seven
Every one of the seven transfers effort from you to the interviewer, or responsibility from you to someone else. Blaming a manager moves responsibility. Having no questions moves the work of assessing fit. "I'll do anything" moves the job of defining your value. The fake weakness moves the discomfort of honesty. Early salary questions move the framing. Adjectives move the burden of proof. Nobody is consciously scoring this. Interviewers just leave the room with a feeling about who would be low-friction to work with, and these sentences are where that feeling comes from.
So write down the three or four stories you will actually use, with numbers in them, and know them well enough that you reach for a story instead of an adjective under pressure. Then do the boring preparation on your own material, because most of these phrases are what people fall back on when they have not reviewed their own history recently. If your CV and your LinkedIn profile are stale, your recall of your own work is stale too, and vague language is the symptom.
None of these are unrecoverable. If you hear yourself saying one, correct it in the room. "Actually, let me put that better." Interviewers respect that far more than they penalize the original slip, because it demonstrates exactly the self-awareness the whole conversation was built to test.