Most interviews are lost on a few repeated mistakes, not on hard questions. This guide lists the ones that cost offers, grouped by before, during and after the call, with the fix next to each.
Before the call: no research, no questions ready, a bad video setup. During the call: rambling, answering a different question, blaming an old boss, freezing, lying, reading from a script. After the call: no follow-up. Each one is easy to fix once you can name it.
If you fix only three things, fix these. Answer the question that was asked, in under two minutes. Never speak badly of a past employer. Send one short thank-you email the same day. The rest of this guide goes through every mistake with what it looks like and what to do instead.
Key takeaways
What it looks like: the interviewer asks "What do you know about us?" and you repeat the first line of their website. Interviewers notice this in seconds.
The fix: spend twenty minutes. Read the job description twice, the About page, one recent news item or product update, and the profile of the person interviewing you. Write three facts you can use in an answer. The job-description question tool turns the posting into the questions that role usually gets.
What it looks like: "Do you have any questions for us?" is met with "No, I think you covered everything." That reads as no interest.
The fix: prepare three questions about the work, not about leave policy. Good ones: "What does a strong first three months look like in this role?" and "What is the team working on right now that this hire would join?"
What it looks like: you are asked about a project from two years ago and you cannot say what you did on it. Everything on your resume is fair game.
The fix: for each line on the resume, be able to say what the problem was, what you did, and what came out of it. The STAR builder helps you write that shape for each one.
What it looks like: you join from a phone in a noisy room, the camera looks up your nose, and the first five minutes go on "Can you hear me now?"
The fix: a laptop on a table, camera at eye height, a light in front of you and not behind, a headset or earphones, and a five-minute test call the day before.
What it looks like: an answer that keeps going because you are not sure it landed. The interviewer stops listening around the ninety-second mark.
The fix: say the answer in one sentence first. Then give two or three supporting points. Then stop. If they want more, they will ask. Practice with the AI mock interview, which forces you to finish on time.
What it looks like: they ask about a time you disagreed with a manager and you describe a time you led a project. It happens when you have rehearsed a story and reach for it no matter what was asked.
The fix: repeat the key word of the question in your first sentence. "A time I disagreed with a manager was..." If the question is unclear, ask: "Do you mean a technical disagreement or a priority one?"
What it looks like: "My last manager was a nightmare" or "That company had no idea what it was doing." The interviewer hears how you will talk about them next year.
Say: "I learned a lot there, and I am looking for a role with more [ownership / scope / growth] than that team could offer."
Then: one thing you did well there, one thing you want next, and stop.
What it looks like: a long silence, then "Sorry, my mind went blank." It happens most on questions you did not expect, and it is worse on video, where silence feels longer.
The fix: have a holding line ready so silence never lasts. "Let me think about that for a second" buys you time and sounds calm. Then say what you do know. The full method, with the exact phrases, is in what to say when you do not know the answer.
What it looks like: a skill on the resume you last used in college, a team of two described as a team of ten, a project you watched described as a project you led. Follow-up questions find it, and a reference call confirms it.
The fix: say what is true and frame it well. "I used it in one project, and I would need a week to be fluent again" is a fine answer. It is honest, and it shows you know your own level.
What it looks like: your eyes track left to right, your voice goes flat, and every answer sounds like the same paragraph. Interviewers spot reading at once.
The fix: keep notes as five or six words per topic, not sentences. Glance, then look up and speak. Anything you would need to read out loud is something you do not know well enough yet.
What it looks like: you look at the interviewer's face on the screen, which is below the camera, so to them you appear to be looking down the whole time.
The fix: put the call window as close to the camera as you can, and look at the camera when you say your first sentence. Then it is fine to look at the screen while you explain.
| Mistake | What the interviewer sees | Fix |
|---|---|---|
| Camera too low or too high | Ceiling, or the top of your head | Stack books under the laptop until the lens is at eye level |
| Light behind you | A dark shape against a bright window | Face the window, or put a lamp behind the screen |
| Built-in laptop microphone | Echo, typing noise, the fan | Any wired earphones with a mic are better |
| Notifications left on | Chat pings during your answers, and pop-ups during a screen share | Turn on Do Not Disturb, close chat apps, silence the phone |
| Sharing the whole screen | Your tabs, your desktop, your file names | Share one window only, and open it before the call |
| Virtual background with a moving edge | A flickering outline around your hair | A plain wall behind you beats any filter |
| Joining at the exact minute | You, still updating the app | Join three minutes early with the camera on |
One more that people forget: the name shown on the call. Set it to your real name before you join. A nickname or the laptop model is not a first impression.
What it looks like: the interview ends, and the recruiter hears nothing from you. Most candidates do this, which is why the ones who write are remembered.
Write: "Thank you for the time today. I enjoyed the part about [one specific thing you discussed]. I am keen to move forward and happy to share anything else that helps."
Then: four lines at most, sent the same day, to the person who interviewed you or to the recruiter who set it up.
What it looks like: you get another offer, or lose interest, and stop replying. Recruiters move between companies and they remember names.
The fix: one line closes it cleanly. "Thank you for the process. I have accepted another role, and I would be glad to stay in touch." It takes a minute and keeps the door open.
What it looks like: "Why was I rejected?" Companies rarely answer that, for legal reasons as much as anything.
The fix: "If there is one area you would suggest I work on before applying again, I would value hearing it." Some will tell you. Then the preparation guide and the HR question guide cover the next attempt.
Fix the mistakes above with the guide and the free tools first. In a live video interview, ClapAssist listens on your own computer and shows the shape of the answer, drawn from your resume: one sentence to say, then the points. It helps most with mistake 8, freezing, and with mistake 5, rambling, because you can see where the answer ends. It will not do your research, and it does nothing in an in-person interview or on locked-down coding platforms. Read how it works before you rely on it.
Outside pages that back the advice above, opened and checked on the date shown.
ClapAssist is a small desktop app for Mac and Windows. It listens to your video interview on your own computer and shows an answer written from your resume, one short sentence to say first and then the points. It never joins the call and stays out of screen shares and recordings.
Not answering the question that was asked. Candidates reach for a rehearsed story and the interviewer has to steer them back. Repeat the key word of the question in your first sentence and you avoid it.
Anything negative about a past employer or manager, "I do not have any questions", and a skill claim you cannot back up in the next question. All three cost more than a weak answer would.
Say the answer in one sentence first, add two or three points, then stop. Practice finishing inside a minute with a timed mock so the stopping becomes a habit.
A plain "I do not know" with nothing after it is a missed chance. Saying what you do know, how you would find out, and then asking a clarifying question is fine and often scores well.
Yes, the same day, four lines at most. Mention one specific thing you discussed. Very few candidates do it, so it stands out.
Not knowing their own final-year project in detail, giving an introduction that is a list of marks and hobbies, and saying "no questions" at the end. The fresher preparation guide covers all three.
Reading full sentences is noticed at once: eyes track sideways and the voice goes flat. Short keyword notes that you glance at are fine and interviewers expect them.
ClapAssist gives you the first sentence in the live call, so the silence never starts. Ten free minutes, no card.