3 ms·
I don't know about google, but on my first proper job after graduating (the actual first lasted only two months) I was given a coding problem that involved writ
by YeGoblynQueenne 9y ago
I don't know about google, but on my first proper job after graduating (the actual first lasted only two months) I was given a coding problem that involved writing a parser. After I got hired in the company I spent about seven months gluing APIs and adding one-liners etc, but in those seven months I once actually had to write a parser (for Tag-Length-Values). And in the seventh month, another engineer had a problem that was almost identical to my interview question- we were all gathered together around their monitor laughing about it.
So I'm guessing, it's not for the everyday stuff that google thinks you need to know how to invert binary trees etc, it's for that one time when you'll really need to do it.
... of course, at that point you can just look up the solution, but I guess they want to make sure you can understand it.
- jjoonathan 9y agoI think the real value is in the ability to recognize the opportunity to apply an algorithm when it arises. You can't just look that up on stack overflow and the alternative is usually spending 10x as long to write a large logic hairball filled with bugs and missing edge cases. Apply another 10x multiplier for the maintenance. I've inherited enough of these (deeply nested code hairballs that can be replaced by a comparatively miniscule set of tree traversals or something) to change my view from "algo is just programmer status signalling" to "algo is a core competency that matters."