This is the same company that caused all that fuss a few weeks back with their arrogance about who they would hire and for posting a cover letter to belittle a candidate. (http://news.ycombinator.com/item?id=360574)
Cut 'em some slack. They screwed up, hopefully they've learned their lesson, apparently they've found someone (so it doesn't look like they were hurt too badly), and the data they post here may help other startups find people.
You almost make this sound like a bad thing. While hiring someone based entirely on any single criterion is a bad idea, but someone's degree is not a horrible heuristic for doing some quick review of potential candidates, or when comparing the quality of candidates. Graduating with a Computer Science or Engineering degree from MIT does mean something, particularly if you're looking for more junior developers.
My thoughts exactly. Problem with a lot of inexperienced startups is their failure to look at people's potential and not their credentials. While a degree helps, people are more likely to prove their quality through great work and amazing reliability. When I start hiring--which hopefully is soon--I'm not going to give a rat's ass about people's credentials, I'll know they're good when I see their work and how they work.
Sorry, I should've defined "work". In the web world, work is the designs you've done, the projects you've developed, and the communities you've helped. I'm sure building a financial library would fit perfectly in that category.
I wasn't busting your chops. I wanted to know because next year I will be completing my MSFE. My plans are to work long enough to pay off my debt and get a nice cash cushion and then move out to SV. I haven't built anything yet, but I am starting to get a financial library laid out in planning.
We didn't actually take a college degree into consideration when hiring.
I simply thought it would be nice to include, because some people do take college education into consideration when looking to follow up with applicants.
I understand, in some cases it can be helpful. But the way you worded it, you dropped the college degree reference many times.
I don't want to sound like a cynnical person when writing on this. I think it's cool that you published your results, I just felt like pointing out that it seemed like a lot of emphasis was put on college degrees as a qualifying factor. I would really like to hear about your reasoning for why you selected the applicants in the final round.
Some possible things to consider writing about next time:
Did they contribute to open source projects? If so, which ones?
Did they write some cool apps in the past? If so, what were they?
Do they have an interesting philosophy on life, code, or hackers? If so, what was it?
"waded through 85+ applicants, calling about 25 of those people, and interviewing about 10 candidates."
--For ONE position. It feels like this guy is running "American Idol" contest. Really, you bring in 10 candidates, to hire one, then you are not doing enough of a good phone screening.
This post doesn't talk about what happens when you've actually got a candidate in front of you. That too is hard.
We're using extensive testing of candidates to make sure that we understand their technical knowledge as well as traditional interviews.
All our candidates have to do a programming test before they even get considered for an interview (we made up a test that we think captures the sort of programming that they would have to do here).
Then when they come in they sit a programming knowledge test before they get to the first interview.
Another consideration is how you actually convince your prospective hire to join the company: particularly in a startup, the sort of person you want to hire is very likely to have multiple offers to choose amongst. When interviewing someone like that, I think it's important to realize the person's calibre quickly, and then to try to use the interview to show them why they ought to work for you -- in that situation, routine written programming tests probably work to your disadvantage.
You do have a point there. first of all, I work with Auston, the one who posted this threat. I think that making the decision to join a company has to do more with the people and vision of the company I'm interviewing with. At the same time I think it would be nice to show them my skill set. I'm have been a consultant for a long time now and there have been times when I didn't want to do business with the other company after the initial meeting and other times where I had to proof myself to the company before we could have a deal together. I think we approached the interviews pretty good. We set up a very relax atmosphere and talk about more than just programming and skill stuff.
You could also consider using a recruiter. I realize it's painful to pay a large chunk of salary and you really want to conserve cash in a start-up.
But you also have to trade off the speed of finding someone against the recruitment cost. I'm using both recruiters and social techniques (including giving a bonus to any engineer on my team who brings in a candidate that we actually hire).
If hiring is hard, finding a decent recruiter is even harder. My experience, with recuriters, has been signing a contract to cough up 15% of annual salary to a recruiter who does nothing more than list the ad on job sites and pass along resumes. I know there are some recruiters that actually do recruit, and add value, but they are very hard to find.
> I know there are some recruiters that actually do recruit, and add value, but they are very hard to find.
Indeed so. I've been on the other side of the fence -- i.e. as an employee -- and the vast majority of the recruitment agencies I dealt with were idiots. 99% of them have no ability to sort of competent from incompetent candidates.
15% seems like a low fee. Perhaps the recruiters willing to work at that rate are not the best? The mid-sized company I used to work for would pay more like 33%. That company was able to build quite an impressive staff for a larger mid-sized company. (Also, they paid staff noticeably higher than industry average which was probably the real key.)
I do agree that it's hard to get a good recruiter and you do have to work with them to make sure they understand your requirements, but it is possible.
I've worked with a few over the years who do a really good job of screening candidates and if you give them a test that they can pass on to candidates as well then you waste less of your time.
Are you writing controls for the space shuttle or building a web based lead manager? How come nobody is good enough? My guess is you probably don't know what to look for in a candidate.
No wonder they're finding hiring hard.