Not to be gratuitously negative, but... All of these claims from Google that say competition performance hurts or that GPA doesn't matter are missing one huge thing: selection bias. Google only sees the performance of the employees that it hires, not the performance of the employees that it doesn't hire. Because of this, the data they analyze is statistically biased: all data is conditioned on being employed by Googl…
Programming competitions correlate negatively with being good on the job
61–70 of 112 posts
Re: Programming competitions correlate negatively with being good on the job
#62Earlier quoted context omitted.
Why must it be "how you work on a day to day basis"? Why must interviews only be about exactly what you're being hired to do?
I would like to think it is at least somewhat related to what I am doing, rather than a lucky dip of a question that I might get or might not. I am a way better software engineer than 15 years ago, yet I am worse at these sort of "challenges".
Perhaps you're not as good as you think.
Re: Programming competitions correlate negatively with being good on the job
#63I'd be interested to know what type of programming competition is being talked about here. There is a world of difference between Hackathons and Algorithmic style competitions.
Re: Programming competitions correlate negatively with being good on the job
#64Coming up with clever solutions is indeed very different from coming up with maintainable solutions.
Re: Programming competitions correlate negatively with being good on the job
#65Re: Programming competitions correlate negatively with being good on the job
#66The conclusion this article offers is drawn from a badly flawed study from over a decade ago, which Google decided neither to publish nor to use the conclusions from. A machine learning system was trained at Google as an attempt to do "scientific hiring." As their ground truth, the team used the performance reviews of people who had already been hired at Google . To optimistically give it the benefit of every doubt,…
Citation?
EDIT: To be clear, Ruberik is NOT an impostor, and it's sad that someone is now going around flagging his comments.
Re: Programming competitions correlate negatively with being good on the job
#67It's still a positive predictor in general. It just means that, beyond a certain point, it's a negative predictor. Just like a GPA of 3.5+ is probably positively correlated with getting tenure, but maybe getting 4.0 is worse than getting 3.9. Watch the actual video to get the real take away: I think what it meant was that, everybody who gets hired at Google is pretty good. If I just had to pick someone off the street…
programming contest winners are used to cranking solutions out fast and that you performed better at the job if you were more reflective and went slowly and made sure things were right.
The idea that a programmer can be very good at one level and have that goodness fail at other levels is important to consider. It is important to consider that a combination of skills, from cranking code to considering the impact of that code, matter. This consideration can lead to an entire team being valued rather than, say, the glorification of the "rock star" programmer.
Re: Programming competitions correlate negatively with being good on the job
#68It disagrees with every other data point I have, so I'm very skeptical with both the methodology (which is opaque) and the conclusion.
From all of my experience at Kaggle (we run machine learning competitions), with our community, and from being close to programming competition sites & understanding their communities, doing great at competitions is an unambiguously positive signal.
(It's worth noting that doing great at competitions is only a positive signal - the lack of competitions is by no means a negative signal).
Many of our customers have found that their best hires have come from competitions. In a lot of cases, this surfaces candidates that would normally be completely overlooked because they don't fit the "top tier CS school" mold that recruiters commonly overfit to.
Several companies have had a successful recruiting strategy built on poaching our top users (https://www.kaggle.com/users).
Peter Norvig's criticism that "programming contest winners are used to cranking solutions out fast and that you performed better at the job if you were more reflective and went slowly and made sure things were right" is specific to programming competitions with very short time durations (vs. the machine learning competitions that I'm used to running, which typically last months and incentivize solutions that generalize well).
However, we've seen that many programming competition winners also do well on machine learning competitions, and the same qualities that aid in competitive programming (creativity, efficiency, tenacity, fluidity with tools, and the ability to build something that works) help win machine learning competitions.
Re: Programming competitions correlate negatively with being good on the job
#69This is flat out wrong. It disagrees with every other data point I have, so I'm very skeptical with both the methodology (which is opaque) and the conclusion. From all of my experience at Kaggle (we run machine learning competitions), with our community, and from being close to programming competition sites & understanding their communities, doing great at competitions is an unambiguously positive signal. (It's worth…
Re: Programming competitions correlate negatively with being good on the job
#70The conclusion this article offers is drawn from a badly flawed study from over a decade ago, which Google decided neither to publish nor to use the conclusions from. A machine learning system was trained at Google as an attempt to do "scientific hiring." As their ground truth, the team used the performance reviews of people who had already been hired at Google . To optimistically give it the benefit of every doubt,…
Citation?
Also, as others have pointed out, Peter Norvig mentions some of this in his talk.