Hacker Newsnew | past | comments | ask | show | jobs | submitlogin

I'm also a "well-calibrated interviewer" at Amazon. I'm an engineer and a 'bar raiser' with 700+ interviews. My thoughts are:

1. Interviewing and evaluating a candidate has very, very little to do with engineering. Yes, you have to be able to evaluate code but this just scratches the surface of what needs to happen during an interview.

2. As a corollary to #1 - just because you are a good engineer doesn't mean that you will be a good interviewer. Never mind whether or not you want to interview. It is just a different skill set.

3. Interviewing can take a lot of time. But it also has high value for the company. If you are passionate about the people that work with and really want to shape the company, then get involved in interviewing. There are very few activities that will influence things more.

4. A lot of the time that I spend in 'interviewing' is actually time that I spend with co-workers to make them better interviewers. For in-house interviews the breakdown is 15 minutes preparing, 45 minutes interview, 30 minutes writing debrief feedback, 30 minutes attending the debrief, and then 60 or more minutes working with the other interviewers on the loop or helping the hiring manager understand what they should be looking for.

5. In some ways the interviewing process is no different than any other process employed by a company. In particular there is almost always room for improvement. As an employee of a company you can spend time complaining about the process ('it is broken', 'it is unfair', 'it is too heavy weight', etc) or you can spend time fixing it. If you are working at a company where you are not empowered to fix things like this then you should consider working for a new company.

6. I like lists!



Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: