I’ve interviewed about 500 people over the past three years. I remember maybe 30 of them as good fits, and the rest usually tripped up on something they could have easily avoided. After about 200 interviews, I realized I could tell within the first 5 minutes if someone was going to get rejected — just by watching for five red flags. These aren’t small things. They’re big mistakes that tell me the candidate probably won’t work out.
I’m not trying to scare you — I want to help you avoid these traps. In my experience, avoiding these mistakes already puts you ahead of most people who apply.
Mistake #1: Leading with “Compensation First” Energy
The Pattern
Some candidates start the conversation by asking about pay and benefits before they’ve asked anything about the actual work. They’ll jump in with “Is this remote? What’s the PTO? How much does it pay?” — without showing any interest in the team or the role itself.
What I’m Actually Thinking
If the first thing you ask about is salary and perks, it raises a red flag for me: “This person is only here for the money.” Even though 24% of employers do lose good candidates because pay expectations weren’t discussed early enough, bringing it up first makes you look like you’re only interested in the deal. I start thinking, “They’ll leave the moment someone offers $5K more. Why invest in training them?” I’ve actually told colleagues after a call: “Thanks, but this person only seemed to care about the compensation.”
The Story
I had one candidate who, in the first 10 minutes, jumped straight into questions about salary, retirement benefits, and working from home — before asking about the team or projects. When they said, “Can we discuss comp first?” it felt like I was talking to a negotiator, not someone excited about the work. We didn’t make an offer. I already knew it wasn’t the right fit.
What to Do Instead
Show real interest first. Start by asking about the role and the team. For example: “What’s a typical day like on this team?” or “What would success look like in this first role?” These show genuine curiosity. Later, you can ask something like: “When would be a good time to discuss compensation?”
- Show your enthusiasm. Try saying: “I’m really excited about this role. I’d love to know the salary range at some point so it’s a good fit for both of us — but could we talk about the role first?”
- Ask about challenges, not just benefits. For instance: “What’s the biggest challenge the new hire will tackle in the first 6 months?”
- Do your homework ahead of time. Often the recruiter will share a range early on. If not, try: “I’m curious about the salary range for this role. I know it matters for both of us, but I’d love to learn more about the job first.”
Talking about salary is completely fine — it’s expected. But leading with it makes you sound like you’re only in it for the pay, not the work. It turns what should be a partnership conversation into a transaction.
Mistake #2: Treating the Interview as an Interrogation Instead of a Conversation
The Pattern
Some candidates just sit there, answer my questions, and that’s it. They never ask me anything. When I get to the end and say, “Do you have any questions for me?” they just shrug and say, “Nope, I think you covered everything.”
What I’m Actually Thinking
When someone asks zero questions, I immediately wonder: “Do they even care? Did they bother researching this role?” It comes across as disinterest. I think, “If they’re not curious about the team or what we’re trying to do, why should I be curious about them?” It’s a sign that the person is passive — just waiting to be tested instead of actively engaging. Simply put: no questions = no interest in my eyes.
“Candidates who never ask questions may be less ambitious… unwilling to dig deep to find solutions.”
The Story
One candidate was technically strong and answered everything well. But when I asked, “What questions do you have for me?” she just said, “No, I think we covered it.” That’s when I knew she wouldn’t move forward. I wanted someone who was already thinking, “How can I help this team succeed?” — someone who would ask things like “How do you measure success in this role?” or “What’s the team culture like?”
What to Do Instead
Treat it like a two-way conversation. An interview is just as much about you deciding if they’re right for you as it is about them deciding if you’re right for them. Prepare 5–7 good questions that show you’ve done your research and are seriously thinking about whether this is the right fit.
- Ask about the role’s impact: “How does this position contribute to the company’s overall goals?” or “What does success look like in this position after 3 months?”
- Ask about the team and culture: “Can you tell me about the team I’d be joining?” or “What’s your favorite part about working here?”
- Ask smart, research-backed questions: “I saw you just launched [Product X]. How did the engineering team decide which features to prioritize?”
- Show you’re thinking long-term: “What opportunities for growth or new challenges will this role offer in the next year?”
The best interviews feel like a real conversation between two people figuring out if they’re a good match — not a one-sided test. Asking good questions makes me think, “This person really cares,” and it also helps you decide if you actually want the job.
Mistake #3: The “Rehearsed Robot” Syndrome — When Preparation Becomes a Liability
The Pattern
Some candidates sound like they’re reading from a script. They deliver answers word for word: “Our team used Agile scrum methodology and delivered on time. We always communicated twice weekly.” Their tone is flat, with no emotion or personality. The moment I ask an unexpected follow-up question, their face drops and they freeze.
What I’m Actually Thinking
I always notice a rehearsed answer. In my head I’m thinking, “This doesn’t sound real.” It sounds polished but not authentic. When I ask a follow-up like “What would you do differently next time?” or “Can you give me another example?” they stumble. That tells me their perfect answer wasn’t really theirs — it was memorized, and they can’t think on their feet. That’s a problem.
The Story
I interviewed someone for a leadership role who gave me a perfect STAR answer about leading a team. It was well structured with impressive results. But when I asked, “What would you change about that project if you had another chance?” he had nothing. He froze and mumbled something unclear. That’s when I thought, “That was just a rehearsed pitch, not real experience.” If a story can’t bend, it probably wasn’t yours.
What to Do Instead
Prepare talking points, not scripts. Know your stories well, but tell them in your own words. Practice explaining the same experience in different ways so you’re ready for follow-up questions.
- Use the STAR method loosely: Know the Situation, Task, Action, and Result for each story — but explain it like you’re having a conversation, not giving a speech. It’s perfectly fine to pause and say, “That’s a great question, let me think a moment.”
- Practice with unexpected questions: A great way to do this is with an AI mock interview tool. It throws random follow-up questions at you so you learn to adapt on the spot. By practising with unexpected questions, your answers become more flexible and natural.
- Sound like a real person: Don’t try to cut out every filler word. The occasional “um” or “you know” is fine. A perfectly polished answer with zero personality is actually suspicious.
Remember: Preparation isn’t the same as memorization. Interviewers want a real person who can think on their feet, not someone reading from a script.
Mistake #4: Zero Evidence of Company Research (Beyond the Homepage)
The Pattern
When I ask “Why do you want to work here?” or “What do you know about us?” some candidates just repeat the mission statement or say, “I read that you’re committed to innovation.” Nothing specific — no mention of actual products, teams, or recent news. It’s clear they spent 30 seconds on the homepage and called it research.
What I’m Actually Thinking
Anyone can find a mission statement online. If that’s all you’ve got, I think: “They barely spent any time learning about us.” I wonder, “If you won’t spend 30 minutes learning about us before the interview, how much effort will you put into the actual job?” It shows a lack of effort and interest. We want someone who’s excited about our mission and ready to add value from day one.
The Story
One candidate told me: “I’m excited about your commitment to innovation” with a big smile. I almost laughed inside — that’s something you could say about any tech company.
By contrast, a different applicant said: “I noticed your team just shipped Project Atlas, and your Q3 earnings show a 40% increase in user engagement. I’d love to know how the engineering team prioritized features for that.” That candidate got the offer. She had clearly done her homework — she knew our numbers and asked smart questions.
What to Do Instead
Do thorough company research before the interview. Put together a quick research document for yourself:
- Press releases & news: Check recent announcements, product launches, or funding news. If the company is public, look at their latest earnings calls or investor presentations — you might find useful numbers to bring up.
- Team & culture: Look at your interviewers’ LinkedIn profiles and those of team members. If someone worked at a well-known company or you have a mutual connection, that’s great conversation material.
- Employee reviews: Skim Glassdoor to get a general sense. Look for patterns about management or culture. This could lead to a thoughtful question like, “I saw employees love your mentoring culture. Can you tell me more about how new hires are onboarded?”
- Competitors and industry: Knowing where the company fits in its market shows initiative. For example: “I know [Competitor X] released a similar product last quarter. How are you thinking about differentiating your upcoming feature?”
- Write it all down: Organize your findings in a document, focusing on key areas: mission/values, leadership, products, recent news, culture, and market position. Use bullet points you can quickly review before the interview.
With this preparation, you’ll be ready to answer “Why us?” with real specifics: “I read your CEO’s blog on AI ethics” or “Your team’s recent push into healthcare tech really resonates with my background.” That kind of effort tells me you’re already thinking like someone on the team.
Mistake #5: The “Too Humble” Trap — Underselling Your Achievements
The Pattern
Some candidates have impressive experience but never take credit for it. They say things like “We increased sales by 20%” or “I helped with our onboarding process.” It’s always “we” and “the team,” never “I did X.” When I push for specifics, they give vague answers. It’s like they’re so afraid of sounding boastful that they make themselves invisible.
What I’m Actually Thinking
This is the most frustrating thing for me. What I’m thinking is: “You have real achievements here, but you won’t let me see them.” I want to say, “Please just tell me what you did!” As a hiring manager, I need solid evidence to put your name forward. If all I hear is vague language, I can’t make a case for you. The bottom line: I want to hire you, but you’re making it impossible.
A survey found that more than half of hiring managers value on-the-job experience and results above everything else. If you don’t confidently own your impact, it’s as if your achievements don’t exist.
The Story
I interviewed a candidate who had led a significant project — but every time he described it, he said “the team” did this, “we” did that. I kept pushing: “What was your specific role?” Eventually he said, “Well, I did some of the code reviews.” That was it. We couldn’t make a case for him.
He could have said: “I set up a new code review process that caught bugs and improved uptime by 30%.” With that kind of answer, I could have championed him. Instead, he faded into the background.
What to Do Instead
Own your “I” and use numbers. Be specific and personal. See the difference:
- Instead of “I helped improve onboarding,” say: “I redesigned our onboarding workflow, cutting new-hire ramp-up from 6 weeks to 3 weeks (saving an estimated $120K annually).”
- Instead of “We launched a new feature,” say: “I led a cross-functional team to launch Feature X, which increased user engagement by 15%.”
- Instead of “I helped manage the budget,” say: “I managed a $500K budget, allocating resources to reduce costs by 10%.”
The Cultural Nuance
If you come from a culture where modesty is important, speaking up about yourself might feel awkward. But remember: the interview is the time to make sure your contributions are visible. Every hiring manager I know wants someone who can say, “Here’s what I did.” That’s not arrogance — it’s clarity.
You can be humble and clear at the same time: “I spearheaded the X project (working closely with others)… leading to Y.” This way you give your team credit and highlight your achievement. Ultimately, I need facts — when you present them confidently, I know I’m hearing the truth.
Now You Know What Hiring Managers Are Really Thinking
After three years on the other side of the table, I’ve learned to see through rehearsed answers, spot a lack of effort, and look for specifics. None of these five mistakes happen because you lack skill — they’re about how you communicate your fit for the role. Now that you know what I (and other hiring managers) are looking for — and what not to do — you’re already ahead. You’ll walk into your next interview armed with the right approach and far more confident.
Good luck, and go crush your next interview!
Catch These Mistakes Before They Cost You an Offer
Practice with an AI interviewer that gives you direct, real-time feedback. Our platform creates realistic interview conversations with unexpected follow-ups — so you learn to respond naturally and stop making the mistakes hiring managers notice instantly.
Start Practicing Free
