How Kaggle Is Changing How We Work
theatlantic.com
theatlantic.com
>the Kaggle ranking has become an essential metric in the world of data science. Employers like American Express and the New York Times have begun listing a Kaggle rank as an essential qualification in their help wanted ads for data scientists
No, it hasn't, and the nytimes job posting they link to doesn't list it as an "essential" qualification (they didn't link to the amex posting). I know many people with experience in the data science space and very few of us have taken part in a Kaggle competition. It's not that there is anything wrong with Kaggle, but the pay is low for the required effort to differentiate yourself. Many modeling competitions I've seen require an inefficient use of time in the "diminishing returns" part of the process, which means winning requires a lot of free time. I worked with a guy who won a couple prominent data modeling competitions, and frankly I thought he was a mediocre data scientist (but a very hard worker).
I sometimes wonder who takes part in the competitions; and then I remember myself from six years ago, applying for jobs and looking for a way to make my resume stand out.
In fact, our conversations quickly turn to the Netflix Prize, where first place won the competition with an algorithm that could not be ported to production, and we discuss how poorly these competitions map to reality.
None of the data scientists I know hire based on Kaggle score. Several don't even think positively of Kaggle.
In a production environment, this is probably an insane amount of transformation, feature extraction, and classification for marginally little gains in precision (as defined here). But I'm only a year or two in to building production-environment classifiers, and nothing at Netflix's scale (though not tiny either-- it is a problem if I can't do feature extraction and high-precision/-recall* classification within a few milliseconds).
* - mid 90s, for a hard NLP/social graph problem.
Just like in research, it turns out that relaxing real-world constraints on a problem is often a great way to make progress. I would not have to search long or far to provide much worse uses of million-dollar grants/projects/big-data-software.
But, in the end, companies like Netflix or where I work are immediately looking for cheap ways to make X happen easier, better, and cheaper. But then hopefully the smart papers go on a shelf or are easily Googleable, and the rest of us get to learn from their efforts.
I can fit long-term and short-term goals in my brain, too, mister.
>If you followed the Prize competition, you might be wondering what happened with the final Grand Prize ensemble that won the $1M two years later. This is a truly impressive compilation and culmination of years of work, blending hundreds of predictive models to finally cross the finish line. We evaluated some of the new methods offline but the additional accuracy gains that we measured did not seem to justify the engineering effort needed to bring them into a production environment. Also, our focus on improving Netflix personalization had shifted to the next level by then.
From http://techblog.netflix.com/2012/04/netflix-recommendations-...
In the last week of a competition, you go into kitchen sink mode trying anything and everything to squeeze the last few points out of your models. The objective of the competition from the competitors standpoint is to win, not create a solution that could be deployed into the sponsor's production environment. On going maintenance of the model is not a consideration.
As far as the netflix competition goes though, the final solutions did help publicize the potential of ensembling and RBMs - I am grateful for that. My personal approach to the competitions is to use them as an opportunity to try out new modeling techniques (i.e. RMBs, deep beliefs etc...) on real world data. It has the added bonus of potentially paying off with prize money (as long as you don't get screwed[1]).
I would like to hear from past Kaggle sponsors and see what they have done with the winning models.
[1] http://www.gequest.com/c/flight/forums/t/4284/acknowledging-...
Look at how many people solve complex crossword and sudoku puzzles everyday for free...
The competitions are a good way to learn, practice, and get feedback on your methods. Kaggle Connect is where you can make a good living while doing a range of interesting work.
(I work for, and compete on Kaggle).
Also love the irony of explaining the importance of a data science competition host by citing Tom Friedman, the King Of Generalizing Anecdotes.
That said, I doubt more than a handful of people could make a living off competition winnings alone.
And those gigs pay hourly.
Besides the economic damage wrought by 99Designs, a lot of designers have gotten a sour taste in their mouth from the blatant copying/IP theft that often wins. If I come up with great idea A, and you do a nearly identical rendering of my idea but in what happens to be the buyer's favorite color.... who do you think will be selected as winner? Unfair outcomes are pretty common, especially because the people doing the choosing often wouldn't know a good design if it bit them in the face.
I should start providing prizes for the best start-up. I'll give you a $20k prize and then turn around and sell it for $1M or more. You can put it on your resume. Win win.
EDIT: Sure, it's good for various things, but it is so detached from the reality that it's a bit out in the thicket. The cynic in me just doesn't get over the value handed over by competitors to the sponsors.
I would think you don't have to hand over your algorithm, if you forego the prize money. Another way of looking at it... as alluded to by other posters, the "winning" data model may not be the best, so there might be less value handed over than you think.
In reference to a few comments here about the inefficiency of crowdsourcing, we're moving more of the work to the back-end (i.e. after an "expert" is guaranteed the bounty). Instead of awarding an expert on Flightfox, you now "hire" an expert based on an initial "pitch".
So, instead of receiving work from let's say 99 experts, we're aiming to provide great results from only 3 experts. To do this, we're working on segmenting and profiling both customers and experts. Think Uber/Amazon rather than eBay.
But don't get me wrong, lots of top notch results in the contests. It is just that it is testing only one facet of what is needed in a data scientist.
Credible people will do one or two competitions because they care about the problem, and because they want to establish themselves well enough to get better jobs, etc. If it works for them, great. If it doesn't, they'll get bored and quit. In that case, the best people leave and you have a ghetto.
Right now, Kaggle makes sense because "data science" is still an ill-defined field but a lot of people want to get into it, and no one knows what it means or takes to get in, so people will try things out to see what happens.
If Kaggle wants to stay in play for the long term, they'll need to get really good at connecting talented people with very high-quality jobs.
There is something that I don't think all of the hiring-related startups get yet: as things are, there's such a shortage of quality jobs. That's a 5-year existential threat to the whole business model. What happens when people realize that these sexy startup jobs are just corporate jobs with better marketing? What happens when the dream dies? Right now, high-quality jobs are too rare for the hiring startups (unless the genuinely change the economy) to prevent people from getting just as disillusioned with these new services as they are with headhunters. Now, that's not because there's an intrinsic limit on interesting work (see: Lump of Labor fallacy) but we'd have to overthrow the management of a whole industry to change that.
Now, data science. It is attractive right now because it carries with it a promise of what software engineering was supposed to deliver but, for most people, doesn't: interesting work, implicit respect, autonomy. I feel like data scientist in many companies means "software engineer who gets dibs on the most interesting projects". I'm afraid that title inflation into the data science field might dilute that, however.
What we really need is to fire 90+ percent of software managers and trust engineers to pick their own projects and call some shots. I don't know how to turn that into a specific startup idea, but it will solve a lot of problems.