The Interview Process for Software Engineers

Acing an interview starts well before the interview itself- years before, in fact. You need to get the right technical experience, apply to companies, and begin preparing to actually solve questions. The following timeline outlines what you should be thinking about when.

If you're starting late into this process, don't worry. Do as much "catching up" as you can, and then focus on preparation. Good luck!

Pict 1

Pict 2

Four Aspect if you're evaluated candidates :

• Prior Experience
• Culture Fit (or your personality, particularly with relation to the company) tend to matter more at smaller companies than at big companies. One way it might come up is if the company's culture is to let employees make decisions independently, and you need direction.
• Coding Skills
• Analytical Ability

Candidate will get rejected if :

• People often perceive you as argumentative, or with any other nasty adjectives, keep an eye on this behavior in an interview. Even an otherwise superstar candidate may get rejected if people don't want to work with them
• Spend some time preparing for questions about your resume. It's not the most important factor, but it matters. Even a little bit of time here can help you improve in major ways. It's a great "bang for you buck."
• Focus mainly on coding and algorithm questions

Incorrect Answers

First, responses to interview questions shouldn't be thought of as "correct" or "incorrect." When I evaluate how someone performed in an interview, I never ask myself, how many questions did they get right? Rather, It's about how optimal your final solution was, how long it took you to get there, and how clean your code was. It's not a binary right vs wrong; there are a range of factors.

Second, your performance is evaluated in comparison to other candidates. For example, if you solve a question optimally in 15 minutes, and someone else solves an easier question in five minutes, did that person do better than you? Maybe, but maybe not. If you are asked really easy questions, then you might be expected to get optimal solutions really quickly. But if the questions are hard, then a number of mistakes are expected.

Dress Code