At Gainlo, we allow people to practice mock interviews with employees from Google, Amazon, Linkedin etc. and get real feedback to improve. In the past, we have seen so many mistakes that candidates are making over and over again. At the same time, our users also like to ask us all kinds of questions regarding interview preparation and a lot of them are quite common.
So that’s why we decided to summarize all these tips and mistakes here and hopefully they can benefit others as well. For example, one of the most common questions is what I should do if I only have X days/weeks left. Therefore, we just published these two posts – How To Prepare For an Interview In One Month and 9 Tips to Prepare Your Coding Interviews In One Week. Both of them became quite popular, which is totally not what we expected!
In this series, we are trying to cover as many topics as possible, like preparation tips, mock interviews, common mistakes, behavior questions etc.. It’s also worth to mention that we only provide practical tips instead of something general that can hardly be acted on. For example, if we are telling you that you need to practice more with coding questions, then we’ll make it one step further by recommending books/sites for that.
If you have any question or suggestions, feel free to shoot us an email at info@gainlo.co.
A lot of people are asking whether coding speed matters in coding interviews. The short answer is – yes, it’s extremely important.
Over the past, Gainlo interviewers have seen so many candidates who came up with the right solution quickly but failed to complete the code in the end. This phenomenon has become more and more common and that’s why we decided to talk about it this week.
It starts with a simple question: does speed matter in coding interviews?
The short answer is: yes, definitely.
At Gainlo, we’ve helped many people analyze why they failed interviews based on their performances. One thing surprised me a lot is the huge percentage of slow programmers in these people. (more…)
Not everyone can be good at competitive programming In fact only few people are able to solve those complicated problems with time restriction.
Many people ask that is competitive programming useful to get a job in tech?
The short answer is that it’s not that necessary, but I encourage people to give it a try at least.
No one can underestimate the importance of a good resume. As a software engineer, your resume gives recruiters/interviewers the first impression and it also determines whether you can get interviews or not.
Do you know that Google receives more than 20,000 resumes a week, or two every minute?
It means that your resume will compete with millions of other resumes. So one may ask how could I make my resume stand out?
It starts with a simple question:
What should I do when I’m stuck in a coding interview?
Most people would suggest you go back and practice more, which can’t be more true.
But I’ll tell you that there are still a lot of things you can do during the interview. You might be nervous and your mind just goes blank, which is quite common when people are stuck.
As we always suggested in our previous posts, it’s extremely helpful to practice with coding questions when preparing an interview. Basically you can start with some very general questions from books like “Cracking the Coding Interview” or Website LeetCode. And then when it gets close to your interview date, questions from past interviews of your target company will be more helpful.
