Let’s admit, the job search and related interviews are not the most pleasant, to say the least, things in the world. Many people look for various tips and tricks before interviews (yes, we will also share a few), but it is more about the professional and psychological shape you are in.
Starting the meeting in the right frame of mind, you are more likely to be able to deal with all the problems. What is the right state of mind for an interview? What types of interviews are there? What are the basic recommendations for passing technical interviews? Let’s find out.
YOU ARE ALSO THE INTERVIEWER
One thing that most people often forget is that you are also the interviewer.
Yes, during interviews, the company evaluates you, but you also evaluate the company to understand if it suits you. What are the values of this company? How are people treated here? Would you really want to end up working for this company?
Sometimes we just need a job — any job. But, if possible, try to estimate how this work will affect your career in the long run. Because, if you say "yes" to this company, you are turning down ten others.
Please remember that the interview is not a one-way road. Sometimes it seems so, but you also have some control over the situation and options.
WHAT ARE THE MAIN TYPES OF TECHNICAL INTERVIEW?
There are several types of technical interviews. They can tell us a lot about how the company works and what it would be like to work there.
WHAT ARE THE BASIC RECOMMENDATIONS FOR TECH INTERVIEWS?
1) ASK CLARIFYING QUESTIONS
Even if you think that you have understood the task 100% right, articulate your understanding to the interviewer so that he can correct you or point you in the right direction.
2) HARDCODE, MAKE A CLUMSY SOLUTION, THEN AN IMPROVED ONE
When you are faced with a coding challenge, first create a working solution, and then improve it.
3) SPEAK UP. LOUD AND CLEAR
You must talk all the time while solving the given problem. Speak out loud.
Here's the thing here. Getting to the result is important, but just as important (if not more) is showing your thinking process. The interviewer wants to know how you approach problems.
4) DON'T BREAK THE FLOW
When you realize that there is a bug or some other problem in your code, your brain naturally starts to panic. Please, don't be so desperate to start breaking your code or breaking your thought process.
If everything goes well:
So, you have a solution. You have easily dealt with the main problem. Now what?
This is a very important part of the interview, because at this stage you can get leverage for further negotiations regarding the position and salary.
5) SHOW OFF YOUR KNOWLEDGE
Look for an appropriate opportunity to show your knowledge and experience.
How do you feel about the logic of the model? What indexes would you add? How would you deploy migrations to avoid downtime?
WHAT ARE THE ADDITIONAL TIPS?
There are a few common places that often appear in interviews (especially in whiteboard ones). The two main challenges in this regard are FizzBuzz and the Fibonacci sequence.
Please remember that you don't have to memorize solutions. You just need to familiarize yourself with the solution and be able to reproduce it from scratch.
Normally during interviews, it is acceptable for a candidate to look for the standard library or package documentation. But interviewers will most probably object if you decide to look for a ready-made answer (don’t go to StackOverflow).
If you have any doubts about where you can peek and where you can’t, see Recommendation 1 (ask clarifying questions).
If you have a remote interview, take a glance at the interviewer's face in the top right corner. When you write code and notice the interviewer nodding, it can be a visual cue to confirm that you are on the right track.
Note: this might not always work, but definitely can come in handy.
When it comes to remote interviews, try to set everything as best you can. The camera is turned on (position yourself so that you look directly into it), the internet is good, the laptop is charged, the room is quiet, there is a glass of water nearby, etc.
Things like that are not affecting your interview results directly, but you shouldn't annoy the interviewer and stress yourself over the little things.
IN A NUTSHELL
It's okay to be nervous. Most people get nervous before or during interviews. It’s ok. Your body is preparing for combat. Basic emotion, response to fear. Pure biology. So just accept your nerves as a fact. This is just a preparation to show your best.
Finally, this is just an interview. You can take it as a skill that can be acquired and perfected through practice. Don’t be hard at yourself if the interview results are not what you expect. Keep practicing and you will succeed.
Starting the meeting in the right frame of mind, you are more likely to be able to deal with all the problems. What is the right state of mind for an interview? What types of interviews are there? What are the basic recommendations for passing technical interviews? Let’s find out.
YOU ARE ALSO THE INTERVIEWER
One thing that most people often forget is that you are also the interviewer.
Yes, during interviews, the company evaluates you, but you also evaluate the company to understand if it suits you. What are the values of this company? How are people treated here? Would you really want to end up working for this company?
Sometimes we just need a job — any job. But, if possible, try to estimate how this work will affect your career in the long run. Because, if you say "yes" to this company, you are turning down ten others.
Please remember that the interview is not a one-way road. Sometimes it seems so, but you also have some control over the situation and options.
WHAT ARE THE MAIN TYPES OF TECHNICAL INTERVIEW?
There are several types of technical interviews. They can tell us a lot about how the company works and what it would be like to work there.
- Whiteboard (interviews with the use of a white board);
- Coding tasks (questions on computer science or algorithms);
- Practical coding (solving a particular problem);
- A project given to the candidate as homework.
WHAT ARE THE BASIC RECOMMENDATIONS FOR TECH INTERVIEWS?
1) ASK CLARIFYING QUESTIONS
Even if you think that you have understood the task 100% right, articulate your understanding to the interviewer so that he can correct you or point you in the right direction.
2) HARDCODE, MAKE A CLUMSY SOLUTION, THEN AN IMPROVED ONE
When you are faced with a coding challenge, first create a working solution, and then improve it.
3) SPEAK UP. LOUD AND CLEAR
You must talk all the time while solving the given problem. Speak out loud.
Here's the thing here. Getting to the result is important, but just as important (if not more) is showing your thinking process. The interviewer wants to know how you approach problems.
4) DON'T BREAK THE FLOW
When you realize that there is a bug or some other problem in your code, your brain naturally starts to panic. Please, don't be so desperate to start breaking your code or breaking your thought process.
If everything goes well:
So, you have a solution. You have easily dealt with the main problem. Now what?
This is a very important part of the interview, because at this stage you can get leverage for further negotiations regarding the position and salary.
5) SHOW OFF YOUR KNOWLEDGE
Look for an appropriate opportunity to show your knowledge and experience.
How do you feel about the logic of the model? What indexes would you add? How would you deploy migrations to avoid downtime?
WHAT ARE THE ADDITIONAL TIPS?
- FAMILIARIZE YOURSELF WITH COMMON TASKS
There are a few common places that often appear in interviews (especially in whiteboard ones). The two main challenges in this regard are FizzBuzz and the Fibonacci sequence.
Please remember that you don't have to memorize solutions. You just need to familiarize yourself with the solution and be able to reproduce it from scratch.
- USUALLY, YOU CAN PEEP INTO THE DOCUMENTATION
Normally during interviews, it is acceptable for a candidate to look for the standard library or package documentation. But interviewers will most probably object if you decide to look for a ready-made answer (don’t go to StackOverflow).
If you have any doubts about where you can peek and where you can’t, see Recommendation 1 (ask clarifying questions).
- FOLLOW VISUAL CUES
If you have a remote interview, take a glance at the interviewer's face in the top right corner. When you write code and notice the interviewer nodding, it can be a visual cue to confirm that you are on the right track.
Note: this might not always work, but definitely can come in handy.
- IF YOU'RE BEING INTERVIEWED REMOTELY, SET THINGS UP NICELY
When it comes to remote interviews, try to set everything as best you can. The camera is turned on (position yourself so that you look directly into it), the internet is good, the laptop is charged, the room is quiet, there is a glass of water nearby, etc.
Things like that are not affecting your interview results directly, but you shouldn't annoy the interviewer and stress yourself over the little things.
IN A NUTSHELL
It's okay to be nervous. Most people get nervous before or during interviews. It’s ok. Your body is preparing for combat. Basic emotion, response to fear. Pure biology. So just accept your nerves as a fact. This is just a preparation to show your best.
Finally, this is just an interview. You can take it as a skill that can be acquired and perfected through practice. Don’t be hard at yourself if the interview results are not what you expect. Keep practicing and you will succeed.
