When you work on a new coding interview question, you should start with finding a brute force solution. But how do you even do that?
Software engineer salary numbers can be crazy, but are you factoring in cost of living? Cost of living dramatically affects software engineering salaries and retirement savings.
It can be really hard to be productive when studying for coding interviews. And everyone has their own definition of productivity, which doesn’t make it any easier. In this article, you will learn three uber-actionable productivity tips for studying to ace your coding interview.
These days it seems like everyone wants to work at Google. But if this is your reasoning, you may want to rethink your career goals.
Do you find yourself getting stuck in your interview? Most people don’t fail interviews because they don’t know the material. They fail because they can’t get unstuck.
Cracking the Coding Interview may be the bible of coding interviews, but are you using it properly? Here’s how to take full advantage of CTCI.
If you study productively, you can get 10x done in the same amount of time. Or you can learn the same things in 1/10th the time. Here’s how to study productively.
Dynamic programming is hard enough when you know that you need to use it for a problem. But what if you don’t even know a coding interview question is a dynamic programming problem to begin with?
Getting stuck is never fun. Especially when you’re working really hard. And yet, I find that this happens to people preparing for coding interviews all the time.
Everyone always says you need to do mock interviews. But are you spending all this time on mock interviews for your Google interview and not making the progress you need?