Common Interview Mistakes: 30 to Avoid, and How to Fix Each One

The most common interview mistakes are preparation gaps you can fix in advance: not researching the company, not tying your experience to the job description, giving long answers with no clear result, and having no questions ready at the end. Fewer of them happen in the moment than people think. Most are decided by how you prepared, which means most are fixable this week.

Below are 30 mistakes, grouped by when they happen (before, during and after the interview) and by format (in-person, virtual, behavioral and technical). Each one comes with a specific fix. At the end you'll find a list of our deeper guides on what to avoid, plus a simple way to find out which mistakes you personally make. For general preparation advice, see our job interview tips.

What mistakes do people make before the interview?

These happen days before you walk in or log on. They're the easiest to fix because you control the time.

1. Researching the company for five minutes

Reading the homepage and nothing else leaves you with a vague answer to "Why do you want to work here?" and no specific questions to ask. Fix: spend 30 to 45 minutes on the product, recent news, the team you'd join and the people you'll meet. Write down two things that genuinely interest you and one question each prompts. Our guide to answering "Why do you want to work here?" shows how to turn that research into an answer.

2. Not mapping your experience to the job description

Interviewers usually probe the requirements listed in the posting. If you haven't matched a story to each one, you'll improvise. Fix: highlight the five requirements that appear most prominently, and next to each one write a specific example from your work, with a number if you have one.

3. Preparing answers but never saying them out loud

An answer that reads well in your head often runs to three minutes when spoken, or falls apart halfway through. Fix: say your top ten answers out loud at least twice, and time them. Our 20-minute out-loud practice routine gives you a structure.

4. Memorizing answers word for word

The opposite problem: scripted answers sound flat, and one unexpected follow-up knocks you off track. Fix: memorize three or four bullet points per story, not sentences. Our guide on how to not sound rehearsed in an interview covers this in detail.

5. Having stories with no results

"I worked on the migration" tells the interviewer what you were near, not what you achieved. Fix: build six to eight stories in the STAR format (Situation, Task, Action, Result) and end each one with an outcome: a number, a date, a decision or a change that stuck. The free STAR story builder walks you through it.

6. Ignoring logistics

Wrong time zone, wrong building, a video link you never opened. These problems are avoidable, and they cost you composure before the first question. Fix: the day before, confirm the time in your time zone, the address or link, the names of your interviewers and whom to contact if something goes wrong. If it happens anyway, our guide on what to do if you're late for an interview has scripts.

7. Not knowing your salary range

If the recruiter asks for a number and you haven't thought about it, you may name one that's too low or dodge in a way that sounds evasive. Fix: research the range for the role and location, and decide your target and walk-away numbers in advance. Our guide to answering "What are your salary expectations?" has sample wording, and the salary negotiation calculator helps you set the range.

Mistakes during the interview

These are the moments interviewers write down. Several of them overlap with the red flags interviewers look for in candidates.

8. Arriving at the wrong time

Late is the obvious problem, but arriving 40 minutes early puts pressure on the person who has to host you. Fix: arrive at the building 10 to 15 minutes early, or join a video call 2 to 5 minutes early. Our job interview etiquette guide covers arrival and greetings.

9. A weak answer to "Tell me about yourself"

Walking through your résumé from your first job wastes the most predictable question you'll get. Fix: prepare a 60 to 90 second answer in three parts: what you do now, one or two relevant achievements, and why this role is your next step. See our guide to "Tell me about yourself".

10. Rambling

Long answers bury your point and use up time the interviewer planned for other questions. Fix: aim for about two minutes on a behavioral answer, lead with the headline, and stop after the result. Our guide on how to stop rambling in interviews has drills.

11. Answering a different question than the one asked

Many candidates hear a familiar keyword and launch into a prepared story that only half fits. In a structured interview, where answers are rated against set benchmarks, an off-target answer can score low even when it's a good story. The US Office of Personnel Management describes highly structured interviews as using the same pre-defined questions and probes for every applicant, scored against benchmarks of proficiency (OPM guidance on structured interviews). Fix: pause for two seconds, repeat the core of the question in your first sentence, and choose the story that fits it best.

12. Saying "we" when the interviewer needs "I"

Crediting your team is good. Never saying what you did is a problem, because the interviewer can't hire your team. Fix: describe the team's goal with "we", then switch to "I" for your actions: "We needed to cut costs. I analyzed the vendor contracts and proposed…"

13. Criticizing a former employer or manager

Even when it's deserved, it makes the interviewer wonder what you'll say about them later. Fix: talk about what you're moving toward, not what you're leaving. Our list of things not to say in an interview covers this and 24 more phrases.

14. Bluffing when you don't know

Interviewers usually notice confident-sounding answers that don't hold up to a follow-up. Fix: say what you do know, explain how you'd find the rest, and reason out loud. Our guide on what to do if you don't know the answer has scripts, and we explain why honesty matters in is it OK to lie in a job interview?

15. Letting one bad answer derail the rest

One weak answer rarely decides an interview. Carrying it into the next three answers can. Fix: if you can, fix it in the moment ("Let me give you a clearer example"), then let it go. See how to recover from a bad interview answer.

16. Closed or distracted body language

Looking at the table, crossing your arms or fidgeting with a pen can read as disengaged, even when you're just nervous. Fix: sit upright, keep your hands visible and relaxed, and look at the person speaking. Our guide to body language in an interview covers both in-person and on-camera interviews.

17. Having no questions, or the wrong ones

"No, I think you covered everything" signals low interest. Opening with time off or perks signals the wrong priorities. Fix: prepare five questions about the work, the team and how success is measured, and ask two or three. See our lists of questions to ask the interviewer and questions not to ask in an interview.

Mistakes after the interview

18. Skipping the thank-you note

A short note won't rescue a weak interview, but leaving it out is a missed chance to restate your interest and add a point you forgot. Fix: send a three-to-five sentence email to each interviewer within 24 hours. Our thank-you email templates are ready to adapt.

19. Following up too often, or reading too much into silence

Hiring timelines slip for reasons that have nothing to do with you. Emailing every two days doesn't speed them up. Fix: ask about the timeline at the end of the interview, then follow up once after that date passes. See how long it takes to hear back after an interview.

20. Not reviewing what happened

If you don't write down the questions and how your answers landed, you'll repeat the same mistakes in the next interview. Fix: within an hour, note every question, rate your answer from 1 to 5, and write one thing to change. If you were rejected after an interview that felt good, read why you might not get the job after a good interview before you assume the worst.

What mistakes are specific to each interview format?

Some mistakes only happen in one format. If you know which format you're facing, check the matching rows. Our overview of the types of job interviews explains each format.

For more detail on the virtual rows, see our list of virtual interview mistakes. The technical rows are expanded in coding interview mistakes, and the narration habit has its own drills in how to practice thinking out loud in coding interviews.

How do you find out which mistakes you're making?

Most people can't see their own habits. You don't notice that you say "basically" in every answer or that your stories stop before the result. Three ways to find out:

1. Record yourself. Answer five common questions on video, then watch it back with the sound off (body language) and then with the sound on (content). Our recording checklist keeps it simple.
2. Ask someone who interviews people. A friend who hires in your field will spot gaps that a general listener misses.
3. Use a scored mock interview. A score per answer, with a note on what to fix, shows you patterns across a whole session rather than one answer at a time.

After a real interview, use your notes from mistake #20 to pick the one or two habits that cost you most, and practice only those before the next one.

Guides on what to avoid

Each of these covers one area in depth:

• Things not to say in an interview: 25 phrases and what to say instead
• Interview body language: posture, eye contact and nervous habits, in person and on camera
• Job interview etiquette: arrival, greetings, phones, interrupting and follow-up
• What to do if you're late for an interview: scripts for before, during and after
• Virtual interview mistakes: 20 video-call errors and their fixes
• Red flags interviewers look for in candidates, and how to avoid triggering them
• Questions not to ask in an interview, with a better version of each
• Is it OK to lie in a job interview? Honest ways to handle gaps and weak spots
• Why didn't I get the job after a good interview?
• Coding interview mistakes: 20 errors in technical rounds
• How to recover from a bad interview answer
• What to do if you don't know the answer in an interview
• How to not sound rehearsed in an interview
• How to practice thinking out loud in coding interviews

If you plan to use AI tools as part of your preparation, our guide to AI interview assistant mistakes to avoid covers the common pitfalls.

Practice it

The fastest way to fix these mistakes is to make them in practice, where they cost nothing. Rehearse out loud with a mistake-spotting AI mock interview: CoPilot Interview's Mock Interview builds questions from your résumé and the job description, reads each one aloud, and scores your spoken answer out of 10 with what to fix and a model answer. Watch for mistakes #10, #11, #12 and #27 in your scores, since rambling, off-target answers and missing results show up clearly when every answer is rated. The free plan gives you 15 minutes a day with no account. Follow each employer's rules on AI tools, and use AI to prepare beforehand.

FAQ

What is the biggest mistake people make in an interview?

Not preparing specific examples. Without stories that have clear results, answers stay vague, run long and miss the question. Building six to eight STAR stories tied to the job description fixes most other mistakes too.

Can one mistake cost you the job?

It can, but usually it doesn't. Interviewers typically judge your answers as a whole. A serious red flag, such as dishonesty or hostility toward a former employer, carries more weight than a stumble on one question.

Should I apologize for a mistake during the interview?

Briefly, if it helps you correct it. Say "Let me give you a clearer answer" and then give it. A short correction looks composed; repeated apologies draw more attention to the mistake.

How long should my interview answers be?

As a rule of thumb, aim for about two minutes for a behavioral answer and under a minute for simple factual questions. Lead with the main point so the interviewer can ask for more detail if they want it.

What should I do right after a bad interview?

Write down the questions and your answers while you remember them, send a thank-you note anyway, and pick one or two things to practice before the next interview. Then stop replaying it.

Is it a mistake to bring notes to an interview?

No. A notepad with your questions and a few keywords is usually fine. Reading full answers from paper or a screen is the mistake, because it breaks eye contact and makes answers sound scripted.