Ideas from books, articles & podcasts.
I find that many students forget to apply the best practices they know from real-world coding to their interviews. They assume that coding interviews are totally different, so the things they’d do normally don’t apply. One of the things people forget all of the time is to test their interview solution. But would you ever commit code in the real world without testing it thoroughly first?
MORE IDEAS FROM THE SAME ARTICLE
While test interviews has merits, there is one fatal flaw: Companies are notoriously bad at giving you any meaningful feedback. “So,” you might say, “Who cares? I can just judge my own performance.” Well yes, that’s true, but it can be really hard to judge yourself. You don’t know what criteria y...
I’ll tell you that finding a brute force solution is 1000% better than not finding a solution at all. And if you start by immediately trying to find the optimal solution, it is easy to get stuck and end up without a complete solution by the end of the interview.
The key here is that while in some cases there may be one “best” solution, there are way more problems where you can make different trade-offs and you have to decide which ones to make. As an interviewer, I love to see candidates who weigh the different possibilities.
[0:00–0:05] Get settled & fully understand the problem. Work through example inputs.
The first step of the FAST Method is to find an initial brute force recursive solution. This is something that you need to be able to do on your own for the FAST Method to be of any use to you.
Often, people dive right into writing code as soon, until you’ve fully worked out the solution. Writing any more code than just for thinking is a critical mistake for two reasons.
The key here is simply to get more practice coding, and ideally do so in an environment where you are getting good feedback on your code. One of the best ways to do this is by contributing to open source projects. Not only is this a great way to show off your experience, but you will get the bene...
I love asking complicated interview problems. If a problem involves several different components, you as the interviewer get such great insights into how a candidate manages their thinking when there is so much to deal with all at once. The key to successfully solving these problems is to use abs...
Your thought process is non-linear when you’re solving problems, so you may have thought you needed a HashMap because of some other line of thinking that you have since abandoned.
created 1 idea
created 5 ideas
❤️ Brainstash Inc.