Key Factors that Differentiate Strong Candidates from Weak Ones in Developer Interviews

This post should help you get better results next time.

Today let’s talk about the software engineering interview process. Acing an interview is a skillset, I see there are good devs who don’t know it or didn’t get it right.

Layoff happening, to help someone who may prepare for an interview, and also for myself and other interviewers not missing any good candidates.

let’s talk about it today, from an interviewer’s perspective.

Mindset

Before attending any interview. you should have this in mind: Interviewing is not and questions and answers process. or “preparing for some exam”.

It is a POC of yourself: which is a presentation and discussion to demonstrate the best of yourself. read it again.

So do not be nervous, nor prepare a long list (by using hundreds of flashcards) of answers to memorize everything, no no no, you don’t have to do this. instead of a “brute force” preparation, you can do it more effectively.

The interviewer is not possible to know everything, and in many areas, you actually know better than him, all you need to do is to make this visible.

let me explain.

DSA

First round, some companies (not all, but FANG for sure) will assign you 2 DSA problems. you can prepare like 100–150 leet code…