3 Costly Interview Mistakes to Avoid

What I learned as an Amazon Bar Raiser

With or without layoff news or the fear of AI taking away jobs, interviews remain a constant pressure test. Some people interview only when necessary. Others intentionally stay in the market to gauge their value. There is no right or wrong approach.

Clearing an interview feels validating. Rejection stings, especially when you know you are good at your job.

For a long time, I treated interviewing as a corporate tax. When asked to interview candidates, I looked for a way out. Over time, I realized interviewing helps shape who you get to work with every day.

My perspective shifted completely after going through Amazon’s Bar Raiser program. By the time I left Amazon last year, I had conducted more than 500 interviews across levels and functions. One of the biggest misconceptions experienced professionals have is assuming job performance automatically translates into interview performance. They assume their resume and work portfolio would just speak for itself. It does not.

Interviewing is its own skill.

Across hundreds of interviews, I noticed that most strong candidates who were rejected were not lacking technical skill or experience. They struggled in one of three areas:

• They failed to make their impact visible

• They demonstrated work below the expected level

• They accidentally created trust concerns

In this edition, I will go deeper into these patterns and why they often derail even otherwise strong candidates.

The Basics

Every company evaluates candidates differently, starting from resume screening to online assessments, phone screens, and onsite rounds including functional and behavioral interviews.

The format varies, but most interview loops try to answer the same questions:

• Can this person do the job?

• Can this person operate at the required level?

• Can this person work effectively with others?

At Amazon, the Bar Raiser round ensures hiring standards are applied consistently across the company. A Bar Raiser facilitates the final debrief, synthesizes evidence from all interviews, and helps the panel arrive at a hire or no hire decision. The bar is clear and demanding: a candidate should be better than 50 percent of people currently in that role.

One thing Amazon does exceptionally well is removing subjectivity from hiring decisions. The process is structured, evidence-based, and data-driven, leaving little room for gut feel or emotion-driven decisions. This does not mean mistakes do not happen, but they can usually be traced to where the panel misread evidence.

Most candidates prepare by understanding the functional bar, reading about company culture, rehearsing STAR formatted answers, and practicing polished responses. They often walk out feeling they did well, only to receive a No Hire decision they do not understand.

Here are the three nuanced areas where strong candidates often stumble.

Mistake 1: The “We” vs. “I” Ambiguity

When discussing past projects, candidates often default to “we.” It appears collaborative. “We launched this. We solved this. Our team improved this metric.” Experienced professionals often under-explain their role because they assume their reputation or title should speak for itself.

Collaboration is great. But the interviewer needs to evaluate you, not your team. If your individual contribution is buried in generalities, that data point is lost.

A strong interviewer will constantly separate what the team did, what your manager drove, what you personally owned, and how much influence you actually had.

The Better Approach

Be specific about three things: what you personally owned, what you personally built or influenced, and what would have gone differently without you.

Vague: “We redesigned the payment system. It was complex work across multiple teams. We reduced latency and improved reliability. I was part of the core backend team.”

Clear: “I owned the checkout service redesign. I designed the API contract and made the call to move from synchronous to async processing because we were expecting a significant traffic spike. I also owned the stress testing to validate the design under 10x load. Without that redesign, we would have hit our scaling ceiling within the next quarter.”

The second version makes ownership visible without sounding arrogant. It clearly shows:

• the decision made

• why it mattered and

• the impact of that decision

One practical way to prepare is to document each project example you plan to discuss with:

• the overall outcome

• your specific contribution

• one thing that would have gone differently without you

If you find yourself saying “we” more than “I,” you probably need to sharpen the example further.

Mistake 2: Misjudging the Bar (Leveling)

A common mistake candidates make is sharing perfectly good examples that are simply below the bar for the role they’re interviewing for, or that just don’t answer the question asked.

This is the leveling mistake.

For senior roles, interviewers are evaluating scale, ambiguity, complexity, cross-functional influence, strategic judgment, and the ability to operate independently. They’re not looking for solid execution. They’re looking for direction-setting.

Many strong candidates struggle in senior interviews because they still describe themselves as executors instead of decision-makers.

The Better Approach

Map your examples to the role’s actual expectations:

Under-leveled (for senior role): “I led the migration to a new database, coordinated with the database team, wrote migration scripts, and managed the rollout with zero downtime.”

Better leveled: “We were starting to hit scaling limitations that were beginning to affect the product roadmap. I led the technical evaluation of multiple options, documented the trade-offs, aligned leadership around the recommendation, and planned a phased migration strategy with rollback mechanisms built in. The migration itself succeeded with zero downtime, but more importantly it changed how the team approached long-term capacity planning.”

The difference: the right-leveled example shows architectural thinking, stakeholder alignment, risk management, and technical leadership.

It’s not execution. It’s direction-setting.

Before your interview, write out your projects. Next to each one, write the seniority level it actually demonstrates:

• Does this demonstrate execution?

• Ownership?

• Strategic influence?

• Organizational impact?

Many candidates preparing for senior roles actually only have one strong senior-level example. That becomes a problem quickly during interview loops.

Mistake 3: The Trust Red Flag

Many candidates think interviews are purely about proving competence. In reality, companies are also evaluating the long-term cost of managing you and working with you.

This is one of the least discussed reasons candidates get rejected, and most candidates do not realize how heavily it influences hiring decisions.

Hiring managers and teammates are silently asking one question: “Do I want to work with this person every day?” If a manager senses you could be a “squeaky wheel” or difficult to manage, your strong skills will not save you.

Being highly competent but difficult to work with is often viewed as a net negative at senior levels.

This usually shows up subtly:

• Correcting interviewers aggressively

• Talking about past teammates with contempt

• Framing disagreements as proof that everyone else was wrong

• Showing certainty where intellectual humility would have been stronger

Under pressure, candidates often optimize for sounding correct and smart instead of sounding trustworthy.

The Better Approach

Watch for these patterns:

Correcting the interviewer: If the interviewer misunderstands your design, clarify without creating friction.

• Better: “I might not have explained that clearly. What I meant was…”

• Risky: “Actually, that’s not quite right.”

Over-explaining dissent: If you say you pushed back on a decision, explain what you learned.

• Better: “I initially disagreed, but later realized I underestimated the migration risk.”

• Risky: “I disagreed, and eventually they rebuilt it my way.”

Showing contempt for other approaches: Every technical decision has trade-offs. If you dismiss an alternative as “obviously worse,” you’re signaling that people who chose differently were stupid.

One of the most important behavioral questions to practice is: “Tell me about a time you disagreed with someone.”

A strong answer should show:

• what the disagreement was

• why the other person thought differently

• how the situation was resolved

• what you learned

• what you would do differently now

If your story only makes you sound smart and everyone else look incompetent, rewrite it.

A Real Example: The Concern Wasn’t Capability

I was once the Bar Raiser for a Principal-level interview loop. One candidate appeared functionally very strong, but their answers were terse and delivered with a condescending tone. Interviewers had to probe hard just to extract the relevant details.

Once we got the details out, the answers itself met the functional bar. But the interaction left multiple interviewers uneasy.

During the debrief, the panel shared this unease and concern. The concern was not capability. The concern was whether peers would trust them, collaborate with them, or want to work with them especially under pressure.

The final decision was no hire.

How you make people feel during the interview often becomes a proxy for how they imagine it will feel to work with you every day.

Now Your Turn

Most people read advice and move on. Internalizing these lessons requires work.

Many professionals only start documenting their work after a layoff, burnout, or failed interview. By then, a lot of the most valuable context is already gone.

Start now.

Pull together 3 to 5 projects you are most proud of. The ones you would actually use in an interview. For each one, ask:

• What did I personally own?

• What decision or influence was mine?

• What would have gone differently without me?

• Why did it matter?

• What did I learn or change afterward?

• What level does this truly demonstrate: execution, ownership, strategic thinking, or impact?

• Then ask the harder question: Is this the level the role I want next actually requires?

Also practice this behavioral question:
“Tell me about a time you disagreed with someone.”

• Can you fairly represent the other person’s perspective?

• Can you show confidence without arrogance?

• Can you show that you cared more about getting to the right answer than being right?

The candidates who consistently got hired were not always the smartest people in the room. They were the ones who made their impact easy to understand, demonstrated the right level of thinking, and built trust in how they would show up with others.

That is what gets people hired.

If this resonated, leave a ♡ so I know what to write about next.