10 small mistakes that wreck your job interviews

Sometimes it’s not that you’re not a fit. Sometimes it’s just a small bundle of mistakes that add up - and turn a great interview into one big miss.

In the new mini-episode of Developers Outside the Box, we lay out the 10 most common mistakes we’ve seen again and again - and how to easily avoid them.

1. Misunderstanding what “not a fit” means

When an interviewer says “not a fit,” it’s not necessarily because you did something wrong. In many cases, it’s a very specific need of the team or company - someone with particular experience, a certain work style, or fit with an existing team.

Don’t take “not a fit” too personally. It doesn’t say anything about you as a person or professional. Sometimes you’re great - you just didn’t match what they needed. Move on, and look for the place where you do fit.

2. Aligning salary expectations too late

Nothing is more frustrating than investing hours in interviews, tasks, and tests - only to find the salary gap is impossible to bridge. It frustrates you, and it frustrates the interviewers.

The most important tip: align salary expectations as early as possible. Don’t be shy to bring it up in the first intro call. It’s not rude - it’s professional.

3. Not telling your story sharply and clearly

Many candidates start with a life story from the army, university, the first job - and forget time is limited. The interviewer isn’t after a biography, but a quick brief that makes it clear why you’re worth working with.

Think of yourself like a movie trailer: what’s your story in 90 seconds? Where’s the spark? What’s unique about you? Focus on your strongest points, highlight what’s relevant to the role - and leave room for follow-up questions.

4. Diving into tiny technical details

Some candidates sail off into function names, lines of code, and even esoteric APIs. The problem? It signals too narrow a focus - instead of showing system-level thinking.

In interviews, always ask yourself: am I showing the big picture? We’re looking for developers who see the system, the business needs, and how the parts connect - not just the tiny technical implementation.

5. Getting hyped about a small project like you solved climate change

Enthusiasm is great. But when a candidate describes changing a button color like they built a missile control system, it signals a lack of proportion - and especially a lack of experience with truly complex systems.

When you talk about projects - put them in the right proportion. What was the challenge? What was the real impact? Being able to tell small from big - that’s real seniority.

6. Showing no process thinking or failing to demonstrate STAR

When you’re asked to tell about a project and you jump from topic to topic without clear order - it’s a red flag. Process thinking is one of the most important traits in technical roles.

Practice telling professional stories using the STAR method: what was the Situation? what was the Task? what Action did you take? and what was the Result? It makes you much clearer and more impressive.

7. Not explaining what you learned from past projects

Many candidates say what they did - but forget to say what they learned. Without that, it’s hard for interviewers to see self-awareness and the ability to improve over time.

Don’t be afraid to talk about mistakes, decisions you’d make differently, or key takeaways from the journey. It shows you’re not just a doer - you’re a grower.

8. Not knowing the company’s product at all

One of the clearest signs of low effort: showing up without knowing what the company does. It signals a lack of seriousness and genuine interest.

Before an interview - take ten minutes to check the product, try the app, or read about the company’s services. Small effort - huge impression.

9. Not being honest

Interviewers are especially sharp at spotting gaps between what you say and what you feel. When things sound over-scripted - it creates discomfort.

Better to be honest, even if it means admitting a weakness or lack of experience in a certain area. Authenticity and the ability to speak plainly about yourself matter far more than sounding “perfect.”

10. Not asking questions at the end of the interview

When an interviewer asks if you have questions - they’re not just being polite. They’re checking whether you were engaged, curious, and serious about the role.

Prepare 2–3 smart questions about the role, the team, or the tech. Good questions don’t just show you’re serious - they give you important information to decide if this is the right place for you.