What You Should Never Do in an Interview: Insights from a Technical Interviewer

Having spent the last three years conducting interviews as part of a technical panel, I’ve seen many talented candidates miss out on opportunities simply because they didn’t know how to present their skills effectively. A great candidate isn't just someone with the right qualifications; they’re someone who knows how to communicate their expertise, experiences, and personality in a way that resonates with the interviewers. To help you avoid common pitfalls, I’ve compiled a list of things you should never do in an interview, along with tips on how to stand out.

Craft a Unique Introduction

The way you introduce yourself can set the tone for the entire interview. Too often, candidates recite their CV when asked to introduce themselves. This is a missed opportunity. I can read about your high school, your last job, and your core skills like Node.js on your resume. What I really want to know is who you are as a person and how you perceive yourself.

Your introduction should go beyond the resume and offer a glimpse into your unique selling proposition (USP). For instance, consider mentioning a favorite hobby or a personal achievement that’s not on your resume. This gives me an idea of your personality and what kind of team member you might be. That’s why I’ve adjusted my introduction question to, "How about you tell me about yourself that your resume cannot?"

Highlight Value-Driven Past Experiences

When discussing past experiences, it’s essential to focus on the value you brought to your previous roles, not just your responsibilities. Most technical interviewers already know what a Business Systems Analyst (BSA) or Data Analyst is supposed to do. What we’re interested in is how your work made a difference. For example, instead of just saying you built dashboards, explain how your dashboard provided functional benefits to the organization.

Did it streamline a process? Improve decision-making? Save time or resources? Highlight the impact of your work, not just the tasks you performed.

Find the Right Balance in Technical Details

A common mistake candidates make is either getting too technical or staying too general. There’s a fine line between providing enough detail and overwhelming the interviewer with unnecessary complexity. When discussing technical projects, describe them from an architectural standpoint and focus on the results and complexities involved.

Don’t just mention that you built a dashboard with 17 tables; explain why it was built, what the architecture was, and what purpose it served. This shows that you not only have the technical skills but also understand the bigger picture.

Be Honest About Weaknesses

When asked about your weaknesses, honesty is crucial. Interviewers can usually spot a crafted or insincere answer like, "I’m obsessive about perfection," or "I can’t move on until a task is fully completed." These types of answers don’t really help us understand where you might need support or where you’ve worked to improve.

Everyone has weaknesses, and being upfront about them shows self-awareness and honesty. For example, if you struggle with time management but have been working on it by using specific tools or techniques, share that. The panel can likely identify your weaknesses within the first 10 minutes of the interview, so it’s better to address them directly.

Discuss Failures and Learnings

Your failures are just as important as your successes, if not more so. When asked about a time you failed, share a specific example from the past, focusing on why it happened and what you learned from the experience. Then, describe how you applied that learning in a subsequent situation. This not only shows that you’re capable of growth but also that you’re resilient and able to turn setbacks into opportunities.

Stay in Your Lane

Finally, don’t talk about topics you’re not familiar with. If you’re asked about something you don’t have expertise in, it’s better to be honest about your limitations than to try to bluff your way through. More often than not, there’s someone on the panel who knows the subject well, and they’ll quickly realize if you’re out of your depth. Claiming expertise in something you can’t actually do will only hurt your credibility.

Conclusion: Good Luck with Your Next Interview!

Preparing for an interview is more than just brushing up on your technical skills; it’s about presenting yourself as a well-rounded, honest, and thoughtful candidate. By crafting a unique introduction, highlighting value-driven experiences, balancing technical details, being honest about weaknesses, discussing failures constructively, and staying within your areas of expertise, you’ll set yourself apart from the competition. Good luck with your next interview!