I interviewed at six top companies in Silicon Valley in six days

Re:I interviewed at six top companies in Silicon Valley in s... by brabel on Saturday January 19, 2019 @05:02AM (#18946239)

> Wouldn't it be better to hire somebody who thought that was lame and who spent 100s of hours learning performance testing, new libraries, design patterns, or just working on projects?

I would hope so, because I do all those things and, after over a decade writing software, find the ability to solve puzzles almost completely useless for most coding I've ever done. But reality doesn't need to make sense. So, if you want to work for Google or Facebook, learn puzzles anyway :)

[ Parent | on HN ]

Re:I interviewed at six top companies in Silicon Valley in s... by BossingAround on Saturday January 19, 2019 @05:18AM (#18946293)

I really think it depends on the quality of the project. If I'm looking at a candidate, and see 3 projects, each pushed in one commit, each project has 3 classes in one package, and I see pushed compiled classes as well as source classes, that's a clear sign that this person doesn't know what he or she's doing.

That may not be necessarily a bad thing, depending on the position of course. But projects are not the be all end all, at least not in my company, and where I interviewed.

[ Parent | on HN ]