4 ms·

Frankly, I think you're out of your mind. You should hire people based on absolutely as much useful information as you can ethically get your hands on. Why was

Frankly, I think you're out of your mind. You should hire people based on absolutely as much useful information as you can ethically get your hands on. Why waste the information in a person's github profile? Resumes suck, and are damned near useless. Bringing people in based on resumes wastes your lead engineer's time because the % hit rate on them will be very low. You will, at the very least, need to phone screen somebody that you only know from a resume, a process which takes a surprising amount of time. Talking to people is totally useful, and necessary, but not sufficient. It's prone to passing bullshitters (esp since you have your best technical person interviewing) and useless smart people (who don't get shit done), and to failing good employees who don't speak well or are having a bad hair/brain day or are very nervous. When you go to hire, use all the information you can. Look at their github, interview, have the person write code, have lunch with them to see if they get along with the team. Don't fail them for missing any one part of the interview, but take it all into account. Especially in a small team, you're making an decision with an enormous impact on the future of your company which is difficult and painful to undo. Don't waste any information.

econgeeker 15y ago
I find it interesting that you presume the hit rate on bringing people in based on resumes would be very low. I can tell a good engineer from a bad one, pretty well, using resumes. Phone screens, however are a waste of time. It is difficult to establish rapport with someone over the phone, for both parties, and I've seen some people actually ask programming questions over the phone. One very good engineer I hired, back before I was running my own show, did terrible on the phone screen. I brought her in, though, because I saw something in the resume. She's asian and had a real problem talking on the phone, but eventually got the job and was great. You are making a decision with an enormous impact. Therefore, it is critical that you do it based on a truthful assessment of the candidate-- not ideological prejudice.
- raganwald 15y ago
  I can tell a good engineer from a bad one, pretty well, using resumes. I am reminded of a cartoon I once saw. It showed a businessperson meeting another in a typical office. The caption read "We really liked your resume and would be interested in meeting the person it describes." Obviously you can select the good engineers a resume describes from the bad engineers a resume describes. What you cannot do from the resume alone is deal with false positives in the form of misrepresentations, nor with false negatives from people who are better at programming than they are at writing resumes. You already know this, that's why you still have interviews. But I hope you can appreciate that additional information can help you pick out some red flags for the "good" resumes, thing you will want to ask about in an interview, and likewise a resume that doesn't seem all that great but is associated with good work on github.... Maybe that's a false negative and you want to interview them anyways to see if they simply suck at resume-writing.
- tjr 15y ago
  I once was given a phone interview because a friend of mine knew the hiring manager. The manager really didn't want to waste time with me, he said, because I had just graduated from school, and thus I couldn't possibly be useful to him. But at my friend's insisting, he gave me the interview, and summarily dismissed me. A few weeks later the manager was fired from the company for some sort of unprofessional behavior, and replaced by someone who had just graduated from school.
  - econgeeker 15y ago
    I'm not sure the point you're making, but I should have said "phone interviews, at least for me, are a waste of time." I would have brought you in face to face... a recommendation from someone already working there is a very valid positive signal.
    - deleted 15y ago
      [deleted]
- eropple 15y ago
  Phone interviews aren't that bad, IMO, with proper use of http://i.seemikecode.com http://i.seemikecode.com or something similar. But when there's a language barrier of some kind, they're definitely not going to be as useful.

econgeeker 15y ago

I find it interesting that you presume the hit rate on bringing people in based on resumes would be very low. I can tell a good engineer from a bad one, pretty well, using resumes. Phone screens, however are a waste of time. It is difficult to establish rapport with someone over the phone, for both parties, and I've seen some people actually ask programming questions over the phone. One very good engineer I hired, back before I was running my own show, did terrible on the phone screen. I brought her in, though, because I saw something in the resume. She's asian and had a real problem talking on the phone, but eventually got the job and was great. You are making a decision with an enormous impact. Therefore, it is critical that you do it based on a truthful assessment of the candidate-- not ideological prejudice.

raganwald 15y ago
I can tell a good engineer from a bad one, pretty well, using resumes. I am reminded of a cartoon I once saw. It showed a businessperson meeting another in a typical office. The caption read "We really liked your resume and would be interested in meeting the person it describes." Obviously you can select the good engineers a resume describes from the bad engineers a resume describes. What you cannot do from the resume alone is deal with false positives in the form of misrepresentations, nor with false negatives from people who are better at programming than they are at writing resumes. You already know this, that's why you still have interviews. But I hope you can appreciate that additional information can help you pick out some red flags for the "good" resumes, thing you will want to ask about in an interview, and likewise a resume that doesn't seem all that great but is associated with good work on github.... Maybe that's a false negative and you want to interview them anyways to see if they simply suck at resume-writing.
tjr 15y ago
I once was given a phone interview because a friend of mine knew the hiring manager. The manager really didn't want to waste time with me, he said, because I had just graduated from school, and thus I couldn't possibly be useful to him. But at my friend's insisting, he gave me the interview, and summarily dismissed me. A few weeks later the manager was fired from the company for some sort of unprofessional behavior, and replaced by someone who had just graduated from school.
- econgeeker 15y ago
  I'm not sure the point you're making, but I should have said "phone interviews, at least for me, are a waste of time." I would have brought you in face to face... a recommendation from someone already working there is a very valid positive signal.
  - deleted 15y ago
    [deleted]
eropple 15y ago
Phone interviews aren't that bad, IMO, with proper use of http://i.seemikecode.com http://i.seemikecode.com or something similar. But when there's a language barrier of some kind, they're definitely not going to be as useful.