3 ms·
Unfortunately, "went to MIT" is both easily recognizable and easily verified. "Built a fusion reactor in my basement" is neither of those things. Similarly, "
by ender7 14y ago
Unfortunately, "went to MIT" is both easily recognizable and easily verified.
"Built a fusion reactor in my basement" is neither of those things.
Similarly, "check out my GitHub" has many of the same problems. I'm sorry, but most employers don't have time to look you up on GitHub to crawl through all your commits. That will happen if you get past the first cut, but it won't do anything beforehand.
Sure, you can put "Main developer for <some project>" on your resume. Hopefully the person who is in charge of culling applications has heard of <some project>. If they haven't, they will hopefully take the time to go look it up. Hopefully.
I'm not saying that this is the way it should be, but you have to understand that the average person in charge of hiring is constantly inundated with applications. They simply don't have the time to do research on each one. As with anything, you have to find some way to stand out, but in a way that doesn't require them to visit your basement.
- jshen 14y agoYou didn't make a clear point, but I want to say this incase people believe you are implying otherwise. I've worked at a few of the largest companies in the world, with the classic HR dept, and they have all had numerous good programmers with nothing more than a high school diploma. I've hired a few myself. It really isn't hard to show someone that you know what you're doing.
- Lednakashim 14y agoMy experience says otherwise, but it requires approaching the person and bragging for minutes. Its certainly possible to do this, but not via Internet or paper applications.
- kamaal 14y ago>>They simply don't have the time to do research on each one. As with anything, you have to find some way to stand out, but in a way that doesn't require them to visit your basement. In that case they shouldn't look too surprised if they end up hiring wrong people. Or they end up hiring a person with a lot of paper degrees but can't move a coin on the table. Because you ultimately get what your truly ask for. You asked for degrees, you got it. Why is this so surprising? Ask for innovation, creativity, hard work and productivity and you will get it. If you want to hire such people, you may to have to visit their basement or look at their github logs. If you can't do that you shouldn't complain you can't hire such people. People often ask why do great hackers, nerds and other geeks don't gel so well large heavy bureaucratic corporates. Its because the rewards vs performance incentives are all badly messed up. More often than not somebody who has a degree from X college, with Y GPA gets the money. We recently hired a guy straight out of college, extremely good marks on paper. He seems to know every other data structure and algorithm in the book. But doesn't last more than couple of hours. On the other hand, I've known people from ordinary background with medium exposure, able to last through tough deadlines and crisis situations with enthusiasm. The latter people make far more better hires than the previous ones. Your degrees are of no use if you can't perform. That fact doesn't change.
- andrewflnr 14y agoIn that case they shouldn't look too surprised if they end up hiring wrong people. They shouldn't, but they probably will anyway. I think you have to assume that lots of companies will be stupid and work with them or work around them.
- ender7 14y agoYeah, I'm not arguing that a degree is a good indicator of performance. You have to put yourself in the shoes of the person in charge of hiring. If you advertise a well-paid tech position, you will probably get thousands of applications. You can't read them all in elaborate detail. You can't visit everyone's Github. You just don't have time. So how do you cull? Just randomly select 10% and go with that? What if you happen to pick all the bad ones? That's not going to work. Industry experience? That's easy to fake and also doesn't really mean anything. Contact their previous employers? Those interviews are notoriously inaccurate and also way too time-consuming. If they graduate from a good college, that's possibly a good sign (but possibly not! easy to get a CS degree and have no work ethic). If their resume lists a bunch of personal projects and GitHub links, that's possibly a good sign (but possibly not! easy to push random crap to GitHub that no one will use). I'm afraid it all comes down to time. Either you hire an army of extremely well-trained HR people who are all capable of evaluating code quality and project performance (in which case, why aren't they off programming themselves?) or you come up with some heuristic for culling applications that doesn't take an inordinate amount of time. It's harder than it sounds, and that's why employers fall back on do-you-have-a-degree - because it sits at the sweet spot of sort-of-predictive and easy-to-cull. Or they end up asking their current employees who to hire, which means they hire their friends (which is not necessarily a bad thing).
- randomdata 14y agoUltimately, it boils down to filtering by reputation. The data says that most jobs are acquired through existing connections before it is ever advertised to the public, but in those outlier cases, a degree gives a nod to you from a known credible source. In the world of social networks and artificial intelligence, it is interesting that nothing has come up to provide better recommendations. Perhaps because it's not really needed in the software industry at this point (at least if you believe there is a shortage of talent), so it is not noticed as a problem by the programmers who are capable of making such a system a reality.
- tsotha 14y ago>Unfortunately, "went to MIT" is both easily recognizable and easily verified. Most people miss the point on why this is important. MIT doesn't teach its undergrads anything they couldn't learn at the local state school for a fraction of the price. But you have to be really smart to get in to MIT. That's what employers care about - not what you did when you were there, but that you got in. The root of the problem is Griggs v Duke Power. This problem isn't going to go away until companies can give IQ tests again without the legal peril, because otherwise employers don't have much to go on besides where you went to school.
- gaius 14y agoMIT doesn't teach its undergrads anything they couldn't learn at the local state school I think it's more subtle than that. If you start with people who are very good at learning (which is all you can know about them at college entry time) then you can teach them more in 4 years than you can the "average" person. So the MIT guys probably really do learn more. The question is of course the extent to which that translates to on-the-job performance, as good learner doesn't imply good doer.
- eli_gottlieb 14y agoMIT doesn't teach its undergrads anything they couldn't learn at the local state school for a fraction of the price. As a matter of fact, yes, UMass Amherst is quite competitive with MIT in STEM departments. Thanks for noticing.
- rsheridan6 14y agoThen there would seem to be an opportunity there to automate some of that work. Imagine an algorithm that could give an estimate of the impact factor of an open source project (sort of like the impact factor of an academic journal) and of a particular developer's contributions. You'd end up with a score kind of like karma at HN or reddit, which could be used by lazy HR departments to make the first cut. It could probably be gamed, but somebody's going to scrutinize you more closely for the second cut so gaming it might not be advantageous.