That's why it's very important to prepare for every single interview as well as possible, so you don't waste this opportunity.
In this article, I will share the exact step-by-step framework that I was polishing over the last 3 years, and that helped me to pass dozens of technical interviews.
Why You Need To Prepare?
You can't just become a developer, because you want it, and because you watched a couple of YouTube tutorials.
As a developer, you create software that generates millions of dollars, and your mistakes can cost a lot of money to the company.
Of course, you can make mistakes.
I was breaking a multi-million dollar website a couple of times, and nobody blamed me for that. As this is a normal part of development.
(Moreover, I was fixing it pretty quickly )
But when you apply for the job, you need to show that you are a PROFESSIONAL.
That you mean business, and that you are serious about programming.
And the best way to show it is to perform well in the interview.
By showing your great portfolio, and coding skills, and looking really prepared for this conversation.
When you are actually prepared, people can feel that straight away.
So, let's now break down the preparation framework.
Interview Preparation Framework
1: Gather Info
You need to know as many things about the company, as possible.
And you need to understand what type of interview you are going to have, so do the following: Ask the recruiter what can you expect on the technical interview during your first call or via email.
Google “[Company Name] Interview Questions”.
Check reviews on Glassdoor
Check the Job Post itself and all requirements.
A huge source of info can also be your friend who works there. Referrals are LIFE HACKS!
This research approach, once helped me to find the exact interview question I was going to have, somewhere in the reviews, and I prepared well for this question and landed it perfectly. It was a $100 000+ job, and 30 minutes of googling, helped me to land it.
2: Prepare
Different types of interviews require different preparation approaches, so if you don't know what type of interview you are going to have, get back to the previous step.
If you know, here is my recommendation: Algorithmic Interview: LeetCode (60% easy questions, 40% medium questions).
Normal Interview: Everything Search in Google: “Top [YOUR TECHNOLOGY] Interview Questions”
Revise everything from your studies
Learn well all “Company Interview Questions” if you were able to find them in Step 1
And please, don’t expect anything from the interview!!!
Yes, it's a great chance to get a job, but it's also a great chance to learn something new.
So don't expect anything from it, just mechanically prepare for it, like a robot!
3: Interview
It’s very important to start your interview on a good note. Smile!!! Say something about the weather or make a small joke. It will also help to decrease the stress and build rapport with the person.
Now we are getting to the technical questions part, and here are some tips that can help you to do well with that part: Ask clarifying questions if you are not sure.
Say as much as you can when answering questions. The more you say, the less likely you will get a follow-up question that you don’t know the answer to (But say as much as you can WITHIN the question, do not start talking about random not related topics, as it will show you as an unprofessional person).
Never just say: “I don’t know”. Say something related, or something that you know, and finish with: “…, but I don’t remember exactly what X means”.
Always TALK when you are writing the code. Explain what you are writing and WHY are you writing it. It will do 2 things: Show how are you thinking
Let the interviewer help you if you start moving in the wrong direction
Give yourself time to think. It’s better to take 10 seconds to think about a good answer. You can start with words: “Okay, soo…..”, so the interviewer knows what you are thinking.
When you code, always write PSEUDO code, or at least a PLAN before starting to write the solution.
At the end of the interview, do these 2 must-have things: Ask what are the next steps of the recruitment process.
Ask about the feedback RIGHT on the interview.
4: After the interview
Although the interview has ended, the recruitment process hasn't, so you still have to do a couple of important steps: Write down all the questions you had difficulty answering. And study them! It will help you in future interviews.
If you receive a rejection. Try to find out what was the main reason and what they recommend you to improve.
If a company just ghosts you, send a follow-up email in 3-5 days.
Conclusion
As you can see, the preparation for the technical interview isn't that hard.
You just need to be professional and spend some time before, and after the interview to maximize your chances of success.
Good luck with your interviews, and see you next week!
SEO
0 Σχόλια