4 ms·
Yes, I have some technical chops - started coding on a TRS-80 Color Computer II in the 80s and never stopped. It's not something I do much of anymore (sadly) as
by bane 15y ago
Yes, I have some technical chops - started coding on a TRS-80 Color Computer II in the 80s and never stopped. It's not something I do much of anymore (sadly) as a growing crop of grey hair has convinced my day job c-levels to shovel me into managing groups of technical people.
I also do lots of work outside of pure development in my day job, and it has wildly different sets of requirements, but the process is more of less the same. I've hired and managed a few more of these types than straight developers. But I've managed to have about the same success with both, or if we did hire duds for some reason (CFOs cousin or whatever), I noted the potential problems in their file and came out reasonably accurate.
The problem with trying to hire the next legend in the field is that more often than not, you are not hiring the next legend in the field no matter how they feel about themselves.
That's why legends are notable, they're unique and rare. If they are really that awesome, they'll become legends in their own time and you'll know about them before their resume hits your inbox. Building a hiring process for legends is fraught with peril. Legends are almost by definition not hire-able around repeatable hiring processes. So companies fake a process. Some companies select for specific schools -- like the too often true stereotype of top finance firms only hiring Harvard/Yale grads or top tech firms only hiring Stanford/MIT types. I've even heard of some hiring with a heavy weight on SAT scores or average KLOC per month!
As much as we all like to think of the lone swashbuckler programmer, coding his way to greatness in the fewest undocumented KLOCs possible, I'm hiring people to build actual things that other programmers of various talent levels from other organizations might have to work on months or years later long after my rockstar has moved on to greener pastures because we didn't offer him the office chair he wanted or whatever. In other words, I'm hiring for the best of typical. I need engineers, not crusading nights. I'm building the Golden Gate Bridge or the Empire State Building, not the Pioneer Space probe or filming and episode of MacGuyver. I've hired the rockstars before, there's a reason organizations tend to eventually move on to other processes.
I've worked with some absolutely unknown solid developers who I'd put up against the best in the field any day of the week, because they produced miracles on time and within budget. Absolutely stunning, elegant, rock solid software. But I'd rather focus on their steady solid performance over time. Rather than have a rockstar come in and dump down a few thousand lines of impenetrable code then flame out. I've found that solid, steady developers will ultimately outperform those guys every time. They'll do it right, and the bridge won't fall down or the building won't fall over.
If you are looking at tremendous number of resumes per week, you have to build a hiring process that selects for the best of typical. If you spot a super star in the pile, by all means talk to them, but you'll eventually find that most of the time they have overinflated egos. Hiring people is almost exactly like American Idol. 90% of all the candidates you see are bad, often spectacularly, often embarrassingly. The worst suffer from some of the most intense Dunning-Kruger effects I've ever seen. But you might find an honest to gosh amazing developer every once in a while and it's worth it to hire them. But don't build a process trying to find them, they'll find you.
If you don't build this kind of selective process, you'll spend literally all of your waking hours interviewing people. If you like this kind of thing, and your company is willing to let you do this, awesome. I have other things to do.
An all day technical interview sounds great, but now do this with 30+ candidates. Bye bye month of November. You need to weed people out and get it down to a manageable pool that you can then focus your time on.
I'm know what I'm saying may sound harsh or overly selective based on some arbitrary metric but it's all there for very good, repeatable reasons. But in practice these are only guidelines. If you went to school, awesome for you, I don't care where, be prepared to talk intelligently about the experience, be proud that you demonstrated the ability to complete a grueling, often mindless multi-year project on your own. If you didn't, but managed to autodidact your way to a great skill set, fantastic, be prepared to show and talk about why that worked better for you than going to school.
- tptacek 15y agoTwo things. First, I wish you'd stop caricaturing everyone hired through a process other than yours as "lone swashbuckling MacGuyvers" or whatnot. I am not laying out a method for hiring "the next legend". Second, it is incumbent on you to get better and more efficient at hiring people, and if you're stuck with "resume, phone screen, all-day interview", you've got your hands tied behind your back. There are so many ways to control and accelerate a recruiting funnel that it's tragic to be running one for a high-tech company the same way that Northern Trust runs them for junior bankers.
- bane 15y agoWell, not that I was talking to you (I was talking to cookiecaper) But I appreciate the interest even if your reply is a little bit of a response to something I didn't say. Near as I can tell your process appears to be first come first serve. By your own statements, you don't look at resumes, and you apparently don't ask any particular questions about work history or education during your interview process. I'm guessing you have some sort of technical screen since you've alluded to having some sort of highly specialized selection process of some sort. But I've illuminated you enough with what I've learned to be a solid and reliable process, and I know I must be unfairly characterizing your process above or you wouldn't be in business, so what's yours?
- tptacek 15y agoOur process is obviously not "first come first serve" (we would not be "very good" at screening candidates if it was), but we're pretty deeply nested in this thread to get into details. A good starting point is http://www.matasano.com/careers http://www.matasano.com/careers. But: that isn't the entirety of our recruiting process; it's just the portion most visible to applicants.
- irahul 15y ago> By your own statements, you don't look at resumes, and you apparently don't ask any particular questions about work history or education during your interview process. This thread is already a bit too long, and I haven't read through tptacek's link about his hiring process, but: 1. you don't look at resumes, If I am hiring for a ruby on rails position specifically, the only thing I need to check is if you know ruby on rails. I know RoR, I know my requirements, I can evaluate if you are suited to this current role. If I am hiring for RoR, but I am looking for a generalist - someone who might not know RoR but can pick it up on the run, then looking up at the resume for RoR isn't required. I will just talk general algorithms, design problems, code snippets. 2. and you apparently don't ask any particular questions about work history or education during your interview Me: Let's say we need to have a threaded discussion forum. You know, like HN. Where replies can have replies. Joe: Yes, I got that. Me: Let's see how you go about deciding upon the models for that. I need upvote/downvote/recall vote on all posts. Here, take this piece of blank paper, and run me through how are you storing posts, and comments. And when loading a particular post, how are you going to load the posts and comments associated with them. Joe: works through it Me: That looks great, but I am concerned about the number of db hits. Joe: suggests some kv store suitable for it, talks about storing graphs Me: I think that's good enough. How about implementing upvote/downvote/recall vote. Joe: Need to change the db models. I skipped them in the first iteration. Me: Let's skip it. You know about closures? Care to quote me a particular example of closures? Joe: function translator(el) { return function(text) { $(el).text(text); } } // Translate all i18n elements $('.i18n').each(function() { // Text and callback AJAX_API.translate($(this).text(), translator(this)); } And so on and on. I don't see why I need to specifically ask about your education. I might ask about your work experience, but not necessarily.