3 ms·
Honestly, I found the books (eg; Cracking the Coding Interview) to be decent at giving a quick overview. At the end of the day, doing a bunch of medium difficu
by alfalfasprout 10y ago
Honestly, I found the books (eg; Cracking the Coding Interview) to be decent at giving a quick overview.
At the end of the day, doing a bunch of medium difficulty and some hard difficulty questions on leetcode proved to be the best preparation. By the time you get to your interviews, you've probably seen a variation on what they're asking. I didn't find doing more interviews to be much more helpful than just doing a bunch of practice questions (if you're already good at interviewing in general).
Still, I think this garbage is annoying for senior developer positions or once you're at least a few years out of school. Having to practice implementing a topo-sort in 10 minutes or doing some tedious combinatorial problem gives zero insight into good software engineering practices. System design questions, on the other hand, are actually useful.
- bsvalley 10y agoIndeed, I'd be fine if it was only one algo question in the whole process. Unfortunately we're talking about one, sometimes 2 technical phone screens. Then 4-5 tehnical interviews onsite. You have to deal with data structures/algo crap the whole time (30 minute each) which is not only painful, but it's extremely annoying and pointless. Regarding books vs real world practice - I came a lot more confident by going through the process a few times talking to real interviewers. It's not only you and your laptop and zero stress. This make a big difference in boosting your confidence level.