10 Common Interview Mistakes and How to Avoid Them

Rambling is the single most common interview mistake and also one of the easiest to fix with practice. Here are proven techniques: **The structural approach:** 1. Before answering, take 3-5 seconds to mentally outline your response 2. Signal your structure upfront: "There are two main points I'd like to make here..." 3. Deliver each point concisely 4. End with a clear conclusion, then stop talking **The time-check approach:** • Behavioral questions: target 2 minutes maximum using the STAR method • Direct questions ("What's your greatest strength?"): target 30-45 seconds • Technical explanations: target 3-5 minutes, then check in with the interviewer **Practice techniques:** • Record yourself answering common questions and listen back — you will hear the rambling patterns immediately • Practice with a friend who raises their hand when you exceed 2 minutes • Use the "newspaper headline" test: could you summarize your answer in one sentence? If not, you are including too much detail. **In the moment:** • If you catch yourself rambling mid-answer, it is perfectly acceptable to say: "Let me cut to the key point here..." and refocus • Watch the interviewer's body language — if they are looking away or shifting, you have likely been talking too long • End with: "I'm happy to go deeper on any part of that" — this gives them control of the depth

The questions you ask reveal as much about you as the answers you give. Here are high-impact questions organized by category: **About the role and team:** • "What does a typical first 90 days look like for someone in this role?" • "What's the biggest challenge the team is facing right now?" • "How do you measure success for this position in the first year?" **About engineering culture:** • "How does the team approach code reviews?" • "What does the deployment process look like? How often do you ship to production?" • "How are technical decisions made — is it top-down or team-driven?" **About growth:** • "What growth opportunities have past people in this role pursued?" • "How does the company support continuous learning? Conference budgets, learning days?" **Questions that impress:** • "I read your recent blog post about [specific topic]. How has that initiative progressed?" (shows research) • "What's one thing you wish you had known before joining [Company]?" (shows genuine curiosity about culture) **Questions to NEVER ask in early rounds:** • "What's the salary?" — Wait for the offer stage • "How soon can I get promoted?" — Sounds entitled • "What does the company do?" — Shows zero preparation • "How many vacation days do I get?" — Comes across as disengaged • "Did I get the job?" — Puts the interviewer in an uncomfortable position

Salary discussions in early rounds weaken your negotiating position. Here is how to navigate them gracefully: **If asked "What are your salary expectations?" in a phone screen:** **Best response:** "I'm focused on finding the right role and team fit right now. I've done market research and I'm confident we can find a number that works for both sides once we've established mutual interest. Could you share the budgeted range for this role?" **If they insist on a number:** "Based on my research on levels.fyi and similar sources, I understand the range for this level is approximately $X to $Y. I'd be looking for something competitive within that range, but I'm most interested in the overall opportunity." **Key principles:** • Always try to get them to share the range first — whoever names a number first anchors the negotiation • If you must give a range, make your bottom number something you would genuinely be happy with • Never lie about current compensation (it is illegal to ask in many states, and lies can be verified) • Frame everything around market data, not personal needs **If asked about current salary (in states where it is legal to ask):** "I'd prefer to focus on the market value of this role and what I'd bring to it, rather than anchoring to my current compensation. What's the range you've budgeted for this position?"

The line between confidence and arrogance is thinner than most people realize. Here is how to stay on the right side: **Confidence sounds like:** • "I built a system that handled 10K requests per second" (factual, specific) • "I'm still developing my skills in [area], but here's what I've done so far" (honest about growth areas) • "I'd love to learn more about how your team approaches [topic]" (curious, not all-knowing) • "In my experience, [approach] has worked well because [reason]" (opinion backed by evidence) **Arrogance sounds like:** • "That's a pretty basic question" (dismissive) • "I could probably solve any problem you throw at me" (overreaching) • "At my last company, I was the only one who could handle [X]" (hero complex) • "I don't think I have any weaknesses" (lacking self-awareness) **Three rules for projecting confident humility:** 1. **Credit your team** — "We achieved [result]" is more impressive than "I single-handedly did everything." 2. **Show learning orientation** — Mention something you learned recently or are actively working to improve. 3. **Ask thoughtful questions** — Truly confident people are curious and comfortable admitting they do not know everything. **The ultimate signal of confidence:** Being comfortable saying "I don't know, but here's how I'd approach figuring it out." This shows more intellectual strength than bluffing through an answer.