November 10th, 2022
Having been in both sides of the spectrum, the most valuable thing attained from my experiences as an interviewer is being able to understand how I looked like when I went to interviews as a candidate.
With that said, I found it to be a good idea to list some interview tips that impact us the most based on real life experiences.
This might be a little obvious but I think its useful to understand what happens if you blow it on even one question.
This is one of the most important things to not do in an interview. No matter how smart you are, the more you stutter the more you are taken less seriously. If you are a person that hardly stutters, consider yourself lucky. Those that have even some problem stuttering might impose this notion that they are either bulls**tting their answers or give the impression that they don't care about this job enough. This is the sad reality.
So what should you do if you have a tendency to stutter often even when all of the things you are telling the interviewer are the truth? You can try to practice speaking slower.
This is one of those mistakes that people probably have to experience themselves to be able to understand how this can easily backfire with negative impacts to the hiring decision if you were to slip. Logically it makes a lot of sense to overly provide the information asked for to show how intellectual you are. In some cases it holds true. But it can also backfire if overdoing it.
Have a look at this link and read the list of things on what is extracted from over explaining. You will find that they aren't exactly positive.
When there is a test in the interview it will most likely be about an algorithm that are commonly taught in every article you see.
I'm referring specifically to these:
In most interviews, the interviewer(s) just want to see how the candidate thinks and how they solve problems as well as evaluate their code writing style. They want you to succeed the interview. They are the people who gave the green light to bring you on to the next stage in the interview process so they're already in good terms with you as a candidate so they're not out to harm you or humiliate you. This is why most of them are sticking with common algorithms that every developer should already know.
Rest assured you don't have to worry about them asking you to implement the Jarnik-prim algorithm, the Kruscal's algorithm, prove how Dijkstra's algorithm performs Ω(2V) in worst case scenarios, etc. Remember, they want you to succeed but they still have to make sure you are at least capable working with common data structures.
I hope this helped shed some light on the Proxy pattern and how to take advantage of this concept using the now built-in
That concludes the end of this post :) I hope you found this article helpful to you, and make sure to follow me on medium for future posts!
© jsmanifest 2022