For example, the company for which I work bills me out at $250 / hr. I get something like 15-30 job requests from other companies a week. It would not make any economic sense for me to pursue any of these other companies unless the interview process was dead simple, transparent, and easy (and the total compensation was _at least_ 15% higher than my current compensation). But, 99% of them will only offer modest pay adjustment (%2-3?), and then they expect me to sit through several hours of interviews. And, if I pass that nontransparent process, they ask me to sign a ridiculous employment agreement that signs away all my personal IP. Seriously?
The problem with recruiting today is that most companies who have good talent understand how valuable their best talent is. They treat them very well. And, the companies that want to obtain that talent completely under-offer their side of the deal.
Another problem is that most developers suck at negotiation. I see lots of anger on HN about not getting the 6-figure salary. Well, that's their fault for not asking for it. If they're a relatively good developer (top 25%), they should be making at least 6-figure, easy. And, if they're not, that's their fault, not the fault of others that know their value and how to demand a cut of it.
The problem is that hiring someone who can't code doesn't help me. And a bad engineer is worse than no engineer at all.
It's not like a grocery store where a bad employee is just really slow and a really bad employee steals things costing me a percent of a percent on my margins. A single bad engineer could theoretically destroy a company if they were savvy enough.
Pretty much anyone who does technical hiring will tell you that it's way worse to hire a bad candidate than to not hire a good one and interviews are tuned for that. It's the opposite of the American criminal justice system. A no-hire doesn't mean you're a bad candidate but a hire recommendation is very likely to mean that you're a good one.
This sentence does not compute.
Anyways, I think a big portion of the "hiring problem" is that companies are too afraid of hiring a "bad" developer. They somehow have this notion that if they fail to hire a great developer then its no big deal, but if they accidentally hire a bad developer, their company will all go to shit. This results in crazy interview multi-hour processes.
In the real world, the worst employees rarely ever negate the work of more experienced workers. Thats like saying if you hire a bad teacher, students will forget information rather than learn.
I've worked in organizations where the hiring process the OP is advocating for (short one hour, possibly non-technical, interviews) demonstrably led to serious problems in that organization. Have you ever sat in on technical software engineer interviews? It's beyond horrifying how many developers I've seen that have a great resume, a decent portfolio, talk a big game, but literally can't solve a fizzbuzz-style problem on a whiteboard. I'd say the percentage in my area of developers who fail at this is at least 80%!
Think about that... if your hiring procedures are lax, possibly 4 out of every 5 developers on your team will be ludicrously incompetent. I don't care how tight the hiring market gets; dumbing down interviews is simply not an option with those kinds of odds.
If you haven't already seen it, you should read Atwood's article on the same subject: "Why Can't Programmers.. Program?" [1].
[1] http://www.codinghorror.com/blog/2007/02/why-cant-programmer...
I'll tell you a secret. The first time I was asked to do fizzbuzz in an interview I got it wrong. It was about a year ago. I have been programming sine I was in middle school (I'm 29 now). Walking out of that interview was probably the worst day in my entire life.
Ever since then, two things have happened. First, the lines of fizzbuzz are forever etched into my mind. I can recite fizzbuzz verbally now. I don't even need any writing utensil. For i in xrange 1 comma 101 colon if i mod fifteen equals zero colon print "fizzbuzz" elif... [and so on]". This has come in handy in interviews since. All you have to say is "fizzbuzz" and I go ahead and write away. I don't even need the interviewer to explain the actual wording of the problem.
And the second thing is that I now have absolutly zero interrest in hiring a company that has fizzbuzz (or any other live coding portion) as part of it's hiring process. If I'm at an interview and the interviewer tells me "we're going to write code now", I'm done. If the problem is interesting I'll do it, but if it's fizzbuzz or anything having to do with reinventing something, I'm done. Not gonna work there.
I've struggled to put into words how to describe why I think live coding is such a terrible thing to ask candidates during interviews. Joel Spolsky makes a great point thats hard to argue against. If you're hiring a guitar player, you want to hear him play. If you're hiring a programmer, you'd first want to see them write code. I think the problem is that programming is kind of more like song writing. You can't ask a song writer to go the white board and bang out a new song. Even if you tell him exactly what the song should be about. Song writing is a process, and so is programming.
People also seem to minimize or ignore the cost of a no-hire. If your company has an open position it is trying to fill, it should be feeling pain. Work isn't getting done. Projects or clients can't be bid on. Current engineers are working overtime to meet commitments. If you can look at this situation, shrug your shoulders, and say, "Eh, we're going along fine. We can wait several months for a perfect fit.", then I think you need to re-evaluate why you have an open position in the first place.
I would like to see some actual data to back up this conception. Something that gives the actual statistical risk. As someone mentioned on another story here recently, humans tend to over-estimate the risks of negative events. I think the risk of bad hires in SV has been seriously over-estimated.
I.e. the incompetent new guy just has to fake it long enough that he gets promoted. Now his incompetence has leverage. He can most likely shove responsibility onto others, and eventually gets promoted again. More leverage.
If I were to start an organization, I would make damned sure that every single new hire could do what they were hired to do - and then some. Otherwise, the office dynamics may lead to a stagnant organization over time.
Meaning. Someone who is bad at programming but savvy about interacting with their coworkers, bosses, etc. Someone who might be able to keep a job long enough to really fuck stuff up even though they're bad at what they're doing.
Six months in you realize that they've built a bunch of terrible stuff into the system and now you need multiple people to tear it out and rebuild.
How does one know that one is a top developer?
I'd imagine it's easy to have a false knowledge of being in the top 25% (what with Dunning-Krueger and all) but how does a true top 25 percenter know that he is such?
Questions to ask yourself:
- Do you consistently get higher ratings than your peers?
- Do other developers come to you first if they want advice on the correct way to do something?
- Have you produced features that cause applause in sales teams or customers?
- Have all of your products been successful (maybe allowing for slips in schedule or budget)?
- Do people understand your code? (i.e. do you get a lot of emails from people asking to explain things?)
- Do features that you have created have significantly fewer bugs than other features?
- Do tech leads or product managers seek you out to help them build products or features?
Not that I would suggest replicating it mind you. The interviews are simple because they're literally just screening for people who can't have a converstaion about the weather. 95% of the substantive decision is just looking at the rank of your school and then your GPA. 90% of the candidate pool is excluded by arbitrary cutoffs from the get go. Which is an awful way to hire.
Most large firms draw their entry-level associates from their pool of summer interns, which they hire two years before they graduate law school and take the bar exam. They also usually give people a mulligan on failing the bar exam the first time, so people might work somewhere for 6+ months before passing the bar.
My toughest interview process involved driving 200 miles to spend a day doing psychological tests (after my interview). I got the job. Really, the hirer failed the interview, but I wanted out of my current job. Whose fault was that? Turned out to be a great job (my boss told me that he looked at my portfolio and CV and simply said "hire that guy" — the process was hoop jumping.
While I agree that the premed curriculum and med school are rigorous, attrition rates in engineering are very high. It's tough to get into med school, but it's tough to major in CS or engineering, and getting into a top grad school in engineering is very selective. Attrition rates at top med schools are typically below 1%. In engineering PhD programs, attrition rates are above 35%.
I've discussed this with people on HN before, and I really wish I could find better stats on MS attrition rates, especially at good schools.
I was once a PhD student at UC Berkeley, and I felt it was pretty much a horror show of failure and attrition (the experience caused me to view claims of a "shortage" of US grad students in a very different light). It's tough to get into med school (or a top law school), but looking at the numbers, it doesn't appear to be any worse than top engineering grad schools (where GPAs and GRE scores are sky high). But in the professional schools, once you're in, attrition rates are very low. Yale law school, for instance, has no 1L attrition. Columbia's 1L attrition rate is 0.3%. Attrition rates for elite med schools tend to be well below 1%. Something odd is going on when congress claims that there is such a severe shortage that we need to start awarding green cards to anyone who gets a grad degree in STEM from a US university [1], yet attrition rates start at 35% (in engineering) and only get worse from there.
I think that engineering, math, physical sciences are a pretty grueling path compared to the professions - a point of view supported (at least at the PhD level) by a RAND position paper:
http://www.rand.org/pubs/issue_papers/IP241.html
Anyway, none of this is meant to refute your point - you are right about the MS issue. Though I really do wish we had better info on MS attrition rates. When I was at UCB, there was some attrition from the MS program as well, though it was not anywhere close to as high as the PhD program.
[1] I support this, however, I don't support the reasoning behind it - that a poor educational system is the cause of the non-participation of US students in STEM grad programs. I believe the aversion is rational and market driven, and any policy to expand the engineering workforce at the graduate level should consider this carefully.
http://www.cgsnet.org/study-finds-completion-rates-stem-mast...
This was part of a study done by the council for graduate schools that recognized that attrition rates from MS programs were understudied compared to undergrad or PhD rates.
The full study is behind a pay wall, but still some interesting data.
STEM MS degrees appear to be completed within 4 years about 2/3 of the time - though that number drops to the low 40s within 2 years.
Unfortunately, there's only so much you can draw from this. MS programs aren't nearly as regulated as Law or Med school or PhD programs which tend to be offered only by very academically serious schools. Also, one of the big reasons for failing to finish a MS, according to the article, was work. So many students pursuing a MS are already employed in the field - something you can't do without a professional degree. Still, dropout rates were much higher than for MBA programs, so this data clearly means something.
It would be more interesting to know the attrition rates for MS students in STEM who are more like professional students at top colleges. In other words, what is the attrition rate for MS students who are enrolled full time at a top college.
Maybe these answers are behind the pay wall :(
Google gets thousands of resumes and they have to whittle them down. Some are easy to rule out just based on the resume. Others are easy to rule out in the phone interview.
But a large amount of them make it to the full in person interview. Now Google could just take it as first come first served and hire the first people that look decent. Or they could set the bar really high and whittle the pool down that way. They choose to set the bar really high. They can afford to because they get so many applicants.
As an employee I appreciate that. It means that every one of my coworkers is crazy smart. Any one of them can review my code and offer useful feedback. There are no unqualified developers that I'm aware of at Google and Google is a pretty big company so that's a little amazing. Out of thousands of developers there are thousands of amazing high quality developers.
It's partially market driven. When you get as many applicants as Google does and you are as awesome a place to work as Google is then you can afford to set the bar as high as Google does. And make no mistake they set the bar very very high.
I just want to say I interviewed at the Googleplex in June 2012 and it was an amazing experience. When I got the "rejection"(5 days later, which is standard in my experince), I didn't feel bummed or angry - I felt that I was defeated fairly in a challenging game of chess with people better than me. The programming questions I got weren't out-of-bonds ridiculous like I'm always hearing about. While the process took nearly 6hrs that day, it wasn't just for the sake of it. I had real discussions about real-world problems and I enjoyed it greatly. Those 6hrs flew by. Everyone should go through Google's interview process at least once; it will reveal limits that you didn't know you had. I'm a better person, career-wise, because of that experience. Also, I'm sure I was able to get the awesome job I have now only because I was still charged-up from Google-interview-preparing a few weeks before.
P.S., I'm sure I was close. I got a lot of smiles, nods, "yup, correct" and organic conversation that didn't seem rehearsed and they seemed happy to talk about so I suspect I did better than they expected but just... not... quite there yet... compared to some other candidates.
>>Everyone should go through Google's interview process at least once
No, and this is precisely the reason which gives them that 'We are super special so its our way or the highway' attitude.
What every person must do is stop what they are doing, and give themselves a brief moment of introspection. And they should ask, if they problems they are solving are most demanding, challenging or their times. Are those problems something important for which people are going to pay good money? Or at least they must ask how difficult the problem is on a technical scale. And then pick what is most important both in terms of learning technical stuff and money parts of it.
You must do this routinely. Probably every Saturday night. Based on what the outcome of that is, you must have one long term plan and one short term plan. Something that can be broken down to small parts, put in a todo list and tracked next Saturday night.
Getting into Google or any other big web company won't automagically catapult your career to the center of the universe. Its a good brand to carry on your resume, beyond that nothing much. Bulk of Google, is a large company. Its legacy systems + incremental development all over the place.
So any good to your career will come if you do something about it personally.
Days? I believe the median is 5 hours. The decision may then take days... but that's not the same thing.
Yeah, no thanks.
Presumably, you expect to hold the job for next few years of your life, at a minimum. If you can't budget 10 hours of your time, and you can't wait for a few weeks for an answer, it just doesn't sound like you really want to work there. Unless you're in desperate need for a job sooner... then I'd understand better.
But even if I was employed I'd be looking for an out much faster. I work with 4 week notice periods (max). A two month decision process is just messing you about.
--edit-- I'll add that the work sounded uninspiring, the location wasn't ideal and I was trying to go freelance/contract at the time (successful within a couple of weeks) so their goals and mine were completely misaligned...
Job interviews work fine if done properly. First, interview the right people (filter out hopeless candidates). Second, have the right people do the interview (hint: future colleagues). It's not perfect, but it's not "broken".
If you really knew the subject, you would have passed that exam.
Developers pass those exams and still hate the process. What now?
Standing in a room for a few hours writing on a wall is not exactly hazing; to say it is reeks of entitlement, especially when many software engineering jobs have a public trust: safety, privacy, reliability, and correctness standards that demand a certain level of rigor. Software engineering is a very hot field right now, and developers are in demand--but that doesn't mean you should turn up your nose at companies that maintain their own stringent standards of hiring.