3 ms·
The desire to create an 'objective' measure for programming capabilities is really sort of ridiculous. Given how much of a team sport software development is, i
by andrewvc 12y ago
The desire to create an 'objective' measure for programming capabilities is really sort of ridiculous. Given how much of a team sport software development is, it completely underestimates so many of the key factors that go into being an effective developer.
Unfortunately, as developers, we're keyed in toward quantifying everything, even if it's to our own detriment.
I cut my google interview short when I discovered that their process was to interview me, then bin me, then pick who I'd be working with after I'd gone through a pretty arduous process. I told them that I was interviewing them as much as they were interviewing me, and I had no interest in 'getting the job', then being told after the fact who I'd be working with. The idea that I'd keep interviewing them without even knowing who I'd be working with just seemed absurd to me.
- tptacek 12y agoThe idea that there is one single "objective" interview process is ridiculous. The idea that we should be vigilant about bias, subjectivity, and nondeterminism is the opposite of ridiculous.
- andrewvc 12y agoI fully agree! What I see is a rush toward quantifying everything that's quantifiable and discarding everything that isn't, which is terrible.
- cbhl 12y agoFor what it's worth, if you really wanted to interview Google, and you were in college, an internship is the way to go. If you get considered for full-time after an internship they usually give you the option to go back to the same team. But if you already have been in industry a while, then you don't qualify for an internship and that's a bit broken.