11 ms·
For getting a job at Google/Facebook/Amazon/X cool startup, it's a lot more important to do some narrow-minded rote-memorization of algorithms and data structur
by majormajor 10y ago
For getting a job at Google/Facebook/Amazon/X cool startup, it's a lot more important to do some narrow-minded rote-memorization of algorithms and data structures and hone the skills talked about in a small set of books like Cracking the Coding Interview than to learn something really interesting, or become good at a certain thing, or build some cool shit.
Most interviewers aren't really interested in figuring out "is it worthwhile that you built this thing / did you do it right / why do you think this was something worth learning?" when it's so much easier to evaluate your whiteboard code on a narrow problem against some ideal standard solution.
You can tell them about how you were able to learn enough about a particular database in a couple weeks to be able to cut 90% of the runtime out of a hot query in your first few months at a job, since that was an area that wasn't scaling well and it was something your boss asked if you could take a look at, and they'll be like "ok that's nice, now implement a trie." What's the point of even having experience building and running real systems if that's the process?
If you'd rather be building than practicing whiteboard questions, your best path to success is probably going to be a less predictable one where you need to come across one of the right companies willing to work harder at interviewing because they have to find the best candidates who fall through the cracks at the places with the name recognition.
- FT_intern 10y agoThat kind of evaluation can't be standardized and is very prone to personal biases and opinions though
- majormajor 10y ago"Can't be standardized" is something of a red-herring, as I've encountered a huge variety in how even algorithmic questions are presented and judged. [More] prone to biases and opinions? Let's assume this is true (I'm not convinced that it's such a slam dunk - someone who wants to say no to a candidate can find a way, especially if they aren't being shadowed or recorded (which would feel pretty draconian for the interviewee too)). Isn't it still just a way of making a lazy complaint, "but that's harder!" You as hiring manager are responsible for knowing yourself, knowing your interviewers, knowing their strengths and weaknesses, and knowing your own. That makes it hard to assembly-line interview fresh graduates, but maybe you should have a separate process there anyway because they won't have much in the way of useful experience yet anyway.
- peter422 10y agoPeople lie, people embellish. If you are a good developer who sucks at whiteboard interviews, write open source code that everybody can see. Otherwise there is no reason an interviewer can or should trust whatever story you tell of past successes.
- bluebknight 10y agoThen, these supposedly "good" developers complain how they have a life and a family so they don't have free time for open source.
- peter422 10y agoI'm not saying you have to write open source code on your own time. I'm saying that you can't complain that an interview doesn't show you are good coder if there is no other way for somebody to look at a project you've done. Saying you did X/Y/Z at your last company but can't share the code since it belongs to them isn't a valid excuse for why you have no code out in the world to show off.
- loup-vaillant 10y agoIn other words, you have to have written code on your own time.
- unoti 10y agoYeah, you do. You can't rely on your employer to continuously retrain you through your whole career. Show me an engineer with 10+ years of experience who refuses to ever learn anything away from work, and I'll show you somebody working on old tech.
- vonmoltke 10y agoThere is a difference between learning things away from work and having open-source projects. Also, some people have enough flexibility to learn new languages, technologies, frameworks, and such within the context of their day jobs.