Re:An inside look at Google’s data-driven job interview process
by vladimirralev on Thursday September 05, 2013 @03:12AM
(#6332651)
You must realize that your orchestra example doesn't apply here. What they did is clean-cut and simple removal of the gender bias. Provable.
Compare this with what google is doing. It would be the equivalent of having orchestra candidates write an "original" tune on paper in 20 minutes and then talk about select topics in music theory and then submit that to a figure skating judge panel.
Re:An inside look at Google’s data-driven job interview process
by jrockway on Thursday September 05, 2013 @01:27AM
(#6332335)
It's also worth pointing out that Google wants to hire people that will last for more than one project. It's great if you're hired for a specific project, but what about when that project's done?
The classic example is sexism in orchestras. Orchestra interviews used to consist of the candidate sitting on a stage and performing their piece for a panel of judges. The gender ratio of performers was terribly skewed, even worse than the software development field is today. Orchestra managers excused this by saying that women were simply not as good -- after all, the judges scores don't lie!
But a funny thing happens if you put the performers behind a screen. Suddenly, all the factors of their gender and race and grooming go away, and new performers start being a lot more diverse. There actually was a bias, a serious one, and it caused orchestras to lose who knows how many excellent candidates.
The current state of the art for programming interviews at big companies is to have the candidate solve actual programming problems, including whiteboard coding. It's not practical to put the candidate behind a screen or modulate their voice, so splitting up the tasks of "interview candidate" and "review interview feedback" is the best that Google has figured out.