[bane]

Well, 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?

[irahul]

> 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.

[bane]

Matasano's publicly stated process is basically to call them up on the phone, then begin a multi-week technical interview process consisting of several technical screens and some project work.

It's a first come first serve, but only if you are this tall, process.

It's intriguing, and the technical interview process isn't entirely unlike others I've seen, and does a good job weeding out persons that have no business working for Matasano.

Like anything there is an upside and a downside:

Downside first (because I'd like to end on a positive note)

As an applicant, you really want to have that job, because you just dropped applying for anything else for a few weeks while you run this gauntlet.

Good side:

Matasano ends up with qualified, eager employees who really want to be there.

The biggest problem for me in both of your examples is that, taken literally, you know only the functional capabilities of the candidate, but virtually nothing else.

People who can answer moderately deep technical questions are a dime-a-dozen in certain parts of the country. So while passing an intensive technical screen will generally yield solid employees, it can sometimes fail in interesting ways.

I remember a guy my friend hired just this year who passed all of the technical screens (all done remotely via phone interviews, webex and email) with flying colors, but had two problems: once employed, he just froze unless given explicit direction every 5 minutes, he had atrocious personal hygiene that was so bad it sent half a dozen people home ill. On his resume? Didn't finish his schooling, <1 year work histories at a half dozen companies plus some other warning signs I can't go into. An in-person non-technical interview would have revealed his other issues.

Unanswered questions for the Matasano process:

1) Can they actually finish an extended task or are they just good test takers?

2) Are they self motivated?

3) Do they tend to move about employers very quickly? (ladder jumpers, flaky personalities)

4) Have they performed well on teams?

5) Do they have a violent criminal history or dangerous psychological issues you should be aware of?

6) Do they have other skills you might be able to take advantage of in the future?

etc.

Hiring people is hard. Hiring good people doubly so. But a good hiring process should be well rounded so that you understand where you can use a person in your organization if you choose to hire them, and set expectations of performance up front. An anti-social super tech type might only be usable in development, while somebody with good presentation skills and strong technical skills might be more valuable in a variety of roles.

I'm not saying mine is the best and greatest in the world, but it's pretty good, and more or less what you'll find just about any place. Some places have oddball or one-off hiring systems that work well for them and provide them with their own desired metrics on an employee. I think that's great also.

Going back to the original point that drug us down into this conversational morass, resumes are fairly standard, and have certain things most companies expect to see. Building a resume based on the hiring practices of just one company is not something I'd particularly recommend unless you only care about getting hired at that one place and nowhere else.

Important! The resume won't get you hired, but it will get you an interview. Otherwise you need some selection mechanism to determine whom to interview or you'll spend every waking moment in interview hell.

[tptacek]

We do not have candidates perform "project work".

The amount of time people spend on our tech challenges is (a) calibrated to be less than the amount of time one spends on an all-day tech interview and (b) designed to be broken up into three short chunks (by short we mean "an hour or so") so people can do them at their convenience, rather than having to take a personal day from work to "run a gauntlet".

We go way out of our way to respect people's time; in fact, after interviewing candidates from our earlier process, we designed this process with that as a primary goal. Which is why we say that over and over again on the Careers page.

"Drop everything for a few weeks" is disingenuous hyperbole. As is the idea that --- working in information security for Fortune 500 companies --- are hiring violent felons. I understand that you're irritated with how I've responded to your comments and I don't blame you for being uncivil, but please constrain your irritation at me, not my company.

[bane]

I apologize if I mischaracterized your company's hiring process -- there was no disparagement intended. On the contrary I believe it is intriguing, and given your company's excellent reputation it appears to work well.

It also appears that we're definitely at a communications impasse. By "project work" I was referring to steps 3, 4 and 5 from the career page you referenced:

3. Web app challenge

4. Custom protocol challenge

5. Write a fuzzer (including automated testing)

I'm open to any other descriptor for those steps that you care to use. I most sincerely apologize if "project" implies too heavy a meaning.

And by length of time I was referring to the answer to question #1 directly below those steps

"This looks complicated. How long does it take?

Not that long! We work hard to minimize the amount of time we demand from candidates. We'll be 80% of the way through before you're ever asked to come on-site. We can usually wrap things up inside a few weeks. "

I personally think it sounds like your process is designed to optimize around keeping the technical screening as short as possible while still maximizing the information you retrieve -- which I think is great. It's certainly a much better use of everybody's time than say, Google's multiple all-day committee interview/quiz show extravaganzas are. If I misunderstood the FAQ and the process does not, in fact, take a few weeks, I apologize.

I'm not sure if it's you or I that's going out of our way to be obtuse regarding best hiring practices, but I apologize if I brought any offense or disparagement to you or your company. It wasn't intended.

[tptacek]

No big thing. It's my fault this got so heated. I could go on and on about what we've learned about recruiting process over the last 5 years, but we're pretty deeply nested here; some other time.

[saturdayplace]

I mostly lurk, and I watched this exchange with interest. If anonymous internet votes count for anything, please count this as one for the writeup you just mentioned.

[tptacek]

Our 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.

But: that isn't the entirety of our recruiting process; it's just the portion most visible to applicants.