The 5 Interview Mistakes You're Making Without Realizing
Common mistakes I’ve seen candidates make during the interviews and how you can avoid them in your next interview
Hey, Prasad here 👋 the voice behind the weekly newsletter “Behavioural OS for Techies.”.
Welcome to this week’s article in which I’ve highlighted common interview mistakes that candidates make unknowingly.
At the end of this article, you'll find a bonus: 3 handpicked AWS Solutions Architect positions from various locations. These roles come with visa sponsorship options. If your skills align, consider applying.
If you like the article, click the ❤️ icon. That helps me know you enjoy reading my content. Feel free to hit reply if you have any suggestions/questions or to simply say ‘Hi’. Remember networking helps! I read every email.
Let’s dive into the article.
Interviews can be nerve-wracking experiences, especially when you're vying for a position you really want. While it's natural to feel some anxiety, being aware of common pitfalls can significantly improve your chances of success.
Let me start with a conversation with one of my LinkedIn connection.
Them:
Hi Prasad, I had recently attended a solution architect interview at AWS and got eliminated at the technical phone screen stage. I see a lot of solution architect roles at AWS and am very much interested to apply. Do you know if there will be a cooling period before I can interview again?
Me:
It will depend on how your interview went. Cooling period is generally 6 months. Sometimes if the role is a mismatch, then there is no cooling off period. But if the role was a match and the candidate could not perform as per expectations, then there is cool off period to ensure the candidate gets enough experience before applying again.
Them:
The interview went really well. I answered most of the questions. But still got rejected. Recruiter did not provide any feedback.
Me:
If you can tell what questions were asked and what you answered, then we can try and guess.
They shared with me a gist of questions that were asked to them and the answers they have give the interview. Based on that, I explained to them where they could have done better. Best part, while re-iterating the experience with me, they themselves realized the mistakes they made.
I’ve seen this often when the candidates feel like their interview went well, but they are rejected. They are disappointed because they don’t even understand the reasons of the rejection.
In my years of interviewing, I've spotted five big mistakes that keep popping up. These aren't obvious errors. Most people don't even realize they're making them.
I'm going to share details about these mistakes and show you how to avoid them. This inside knowledge could be the edge you need in your next interview.
Let’s get started!
1. Failing to Provide Comprehensive Answers
One of the most common mistakes I’ve seen interviewees make is providing incomplete or surface-level answers to technical questions. If they dive-deep, they ramble a lot instead of coming to the point. Let's consider a real-life example:
🔆 Scenario: An interviewer asks, "What happens when you enter a url in the browser?"
This is one of the most common question and there are a number of articles on the internet to help you understand the concepts. Most probably you know the answer well. However, it’s important how you articulate the answer and explain each of the step in a logical manner without skipping the details.
🚫 Mistake: The candidate provides a general answer about HTTP requests and server responses but fails to mention fundamental and crucial element like browser caching.
🔥 Why it matters: In technical interviews, especially for roles like Solutions Architects or Software Engineers, interviewers are looking for depth of knowledge. They want to see that you understand the basics and the intricacies of how systems work.
Though, these kinds of mistakes are not deal breakers. The interviewer at this point provides a hint and candidates picks up to explain any missed step. However, it’s easy to steer clear of these mistakes.
👉 How to avoid it:
Take a moment to organize your thoughts before answering. Break down your answer into steps or components.
Think Loud. Consider the entire process, from user action to final result. It helps the interviewer understand your thought process.
Listen to the interviewer carefully and pick up on the hints provided by the Interviewer.
Enjoy reading the article? Please share the newsletter with your friends and colleagues to spread the word and get referral awards.
2. Jumping to Solutions Without Asking Clarifying Questions
Another critical mistake I’ve seen interviewees doing is rushing to provide a solution without fully understanding the problem or context. This often happens when candidates are eager to demonstrate their problem-solving skills.
🔆 Scenario: The interviewer asks, “How would you design a web app selling tickets to users across different regions?”
You are more likely to get at least one such open ended question where you have got a high level requirement statement and you need to find out more details about the customer needs/requirements.
🚫 Mistake: The candidate immediately starts proposing a technical solution without asking for more details about the requirements or constraints.
🔥 Why it matters: Understanding the client's needs thoroughly is crucial. Jumping to conclusions without gathering all necessary information can lead to misaligned or suboptimal solutions.
👉 How to avoid it:
Always start by asking clarifying questions. Seek to understand the full context, including:
Business requirements
Technical constraints
User expectations
Scalability needs
Security considerations
Budget limitations
Summarize your understanding before proposing a solution.
Present your thought process, explaining why you're considering certain approaches.
3. Inability to Showcase Real-World Experience
Interviewers often ask about challenging scenarios to gauge your experience and problem-solving skills. A common mistake is providing answers that lack your own real-world experiences.
🔆 Scenario: The interviewer asks, "How do you deal with a challenging customer?"
🚫 Mistake: The candidate responds with a textbook answer about having one-on-one discussions with customers, explaining benefits and risks, and making amendments to propose a best solution aligned to customer needs. The answers talk about hypothetical scenarios like “Whenever I have a tough customer” or “If I have a tough customer”
🔥 Why it matters: Interviewers expect candidates to have faced and successfully navigated challenging situations. They want to know about your experience in handling such situations.
👉 How to avoid it:
Prepare specific examples from your past experiences. Reflect on lessons learned and how you've grown from these experiences.
If you lack direct experience, draw from similar situations or observations. Be authentic, don't try to force a fit. Show eagerness to learn and adapt.
Use the STAR method (Situation, Task, Action, Result) to structure your response.
Read the last week’s article in which I explained how to do the STAR format right way.
4. Overlooking the Importance of Soft Skills and Non-Verbal Communication
While what you say is important, how you say it can be equally crucial. Candidates focus solely on demonstrating their technical prowess, forgetting that soft skills and non-verbal communication are equally, if not more, important in many roles.
🔆 Scenario: This aspect is important throughout the interview! Irrespective of the questions asked, you will have the opportunity to showcase your non-technical skills.
🚫 Mistake: Neglecting to highlight communication skills, teamwork abilities, leadership potential, and adaptability. Avoiding eye contact, fidgeting excessively, or displaying closed-off body language.
🔥 Why it matters: Candidates can be trained on tech skills, but what interviewers look for is the behavior and right attitude. Soft skills are often what set exceptional candidates apart from technically proficient ones. Non-verbal cues can convey confidence, enthusiasm, and professionalism. Interviewers often subconsciously pick up on these signals.
👉 How to avoid it:
Be proactive in demonstrating your soft skills in action. Highlight instances where you've collaborated with diverse teams and taken initiatives.
Practice maintaining appropriate eye contact. Smile genuinely and show enthusiasm through your facial expressions. Mock interviews help!
Be mindful of your posture. Sit up straight and lean in slightly to show engagement. Don’t be nervous.
5. Neglecting to Ask Thoughtful Questions
At the end of most interviews, you'll have an opportunity to ask questions. Failing to do so, or asking superficial questions, can leave a poor impression.
🚫 Mistake: Either not having any questions prepared or asking basic questions that could be easily answered by looking at the company's website.
🔥 Why it matters: Asking insightful questions demonstrates your genuine interest in the role and the company. It also shows that you're thinking critically about how you would fit into the organization and your growth.
👉 How to avoid it:
Prepare a list of thoughtful questions beforehand. Ask about current projects, challenges the team is facing, or the company's future direction.
Inquire about opportunities for growth and development within the role.
Show interest in the interviewer's experience with the company.
There are other mistakes that interviewees make, like shying away from showcasing their failures or admitting when they don’t know the answer. It deserves a full article on its own as I have too many anecdotes to share :)
🎯Quick Recap
To recap, here are the 5 most common mistakes I have seen candidates making in interviews without realizing.
Failing to Provide Comprehensive Answers
Issue: Giving incomplete or surface-level responses to technical questions
Solution: Organize thoughts, break down answers into steps, think aloud, and listen to interviewer hints
Jumping to Solutions Without Clarifying
Issue: Proposing solutions without fully understanding the problem or context
Solution: Ask clarifying questions about requirements, constraints, and expectations before offering solutions
Inability to Showcase Real-World Experience
Issue: Providing textbook answers instead of personal experiences
Solution: Prepare specific examples from past experiences, use the STAR method (Situation, Task, Action, Result)
Overlooking Soft Skills and Non-Verbal Communication
Issue: Focusing solely on technical skills, neglecting communication and body language
Solution: Highlight soft skills, maintain eye contact, show enthusiasm, and practice good posture
Neglecting to Ask Thoughtful Questions
Issue: Not asking questions or asking superficial ones at the end of the interview
Solution: Prepare insightful questions about the role, company, and team challenges
Navigating a job interview successfully requires more than just technical knowledge or experience. Approach each interview as an opportunity to learn and grow, regardless of the outcome. Reflect on your performance after each interview, identifying areas for improvement. With practice and mindfulness, you'll become more confident and effective in presenting your best self to potential employers.
JOB OPENINGS
This week, I've specially curated Solutions Architect positions at AWS that offer VISA sponsorship. For a complete list of vacancies, head over to the Amazon Job portal.
My goal is to feature 3 job opportunities in each newsletter. We're kicking off with SA roles at AWS as that's my area of expertise, but I'm planning to expand our scope to include openings from other companies down the line. Hiring managers, if you'd like to get your job listing in front of our 6800+ subscribers, don't hesitate to drop me a reply.
Here are this weeks’ 3 highlights:
1) Solutions Architect
Location: Singapore
Visa Sponsorship: Available
Link to job description: https://www.amazon.jobs/en/jobs/2709816/solutions-architect
2) Solutions Architect, MENAT
Location: Dubai, UAE
Visa Sponsorship: Available
Link to job description: https://www.amazon.jobs/en/jobs/2737962/solutions-architect-menat
3) Sr. Specialist Solutions Architect, Analytics, Startups, EMEA
Location: London, UK
Visa Sponsorship: Available
Link to job description: https://www.amazon.jobs/en/jobs/2679083/sr-specialist-solutions-architect-analytics-startups-emea
If you liked this article, click the ❤️ icon. That helps me know you enjoyed the content.
If you think someone else would find this useful, please share this post. That allows more people to benefit from the information.
Please share the newsletter with your friends and colleagues to spread the word and get referral awards.