4 ms·

I've honestly simplified my approach to interviewing over the last few years and I'm pretty happy with the results. I just have a conversation and ask them to

I've honestly simplified my approach to interviewing over the last few years and I'm pretty happy with the results. I just have a conversation and ask them to tell me about a favorite code project they've worked on. Could be school project, previous job, whatever. And just let them talk about it. I'll prod for more detail if I need to give a little nudge. Ask about problems they solved when doing it, etc. The _only_ thing that I'm looking for in this process is whether or not the person is truly interested what they're doing. This comes through when talking about something they're excited to have worked on, seemingly small problems that they had to really work to solve, etc. Geeking out, if you will. The single most important trait I've seen in programmers that I've worked with over the years is "level of interest". There's too much that you have to learn on a daily basis to be successful in this field. If you're not interested in learning new things and finding solutions to the problems that you encounter, you're not going to make it very far. Beyond that and basic competence in the core skills that the job requires, I don't look for much more. Thus far, everybody I've ever hired who has passed this little conversational test has been an excellent team member.

ChrisMarshallNY 6y ago
This. I was a hiring manager for 25 years, and this was exactly what I did. I made very, very few mistakes, and actually had some pleasant surprises.
- thaumasiotes 6y ago
  > I made very, very few mistakes How do you know? How often did you follow up on rejections to see whether they should have been hires?
  - ChrisMarshallNY 6y ago
    Actually, for the company that I worked at, and the level of folks we hired, I often heard about how they went. The only one that made me sad, was a chap who used to show up on the Adobe Photoshop splash page. We offered, he declined. In the aggregate, I think things turned out OK for all of us. There are some folks that I have to admit, probably did best by not accepting us.
    - geoduck14 6y ago
      >There are some folks that I have to admit, probably did best by not accepting us. Yeah, I hear that. I remember interviewing someone who was _good_, but not at this narrow thing that we were hiring for. She seemed SO hopeful that we would give her an offer, I wanted to tell her directly "this job is going to waste 6 mo of your life and offer you nothing I return"
      - ChrisMarshallNY 6y ago
        My most fond recollection was a young chap that was a "second choice." The first declined, and this guy had very little of the exact skills we needed, but he had a real eagerness. He turned out to be an amazing hire. I think that he far outstripped the first choice, and he has gone on to do quite well, after leaving our company. I like to think that I ran a fairly good shop. We kept people for decades. When they finally rolled up our shop (after 27 years), the person with the least seniority had ten years.
lordnacho 6y ago
Same here. There's no silver bullet question, and no high pressure situation with me. My approach has just been to have a conversation, and try to move it along naturally. What do you think of concepts? What useful STL did they add? Why did you go with this design? Ask me something. If the person doesn't really have the level of interest required, they will run out of things to say. Like a cave left unexplored. The good candidates will go down all the caves with you, even if they don't quite know what's there. In particular, the times I've had dud hires it was not possible to know from the standard fare of coding questions and IQ questions. When I was doing that obviously the people I hired passed. But for instance one guy really didn't want to be a programmer, he just knew how to answer the questions. He ended up stalling on his first assignment, and eventually decided to change careers. Another dud also lacked motivation, perhaps because he was asked to do something not quite in his area to begin with. He ended up not doing anything at all. Apart from those two, dozens of others have turned out ok. I never ran into that guy who couldn't do FizzBuzz, despite not asking. I also don't think it was all that bad to let go of the duds within a quarter, they never got so ingrained in the team that we depended on them, and they could plausibly move on to another job without mentioning us on their CV.
- pocketgrok 6y ago
  I’ve been job searching lately and it is brutal. I’m fairly social normally but interviews terrify me. I freeze up, lose my train of thought and I don’t think my enthusiasm for my work really comes though. It’s probably not as bad as I imagine but it’s really frustrating.
  - bitexploder 6y ago
    If you will permit me some trite but genuine advice: I have been interviewing and hiring people for well over a decade and it's not much more fun as the interviewer. Just pretend you are having a conversation with a friend about a project you really enjoy. It's kind of like worrying about how you will perform in a race. The training is already done when you show up to the starting line. The race is the easy part. You know what you know, just demonstrate it. Let the chips fall where they may, as they say. If you fall short, so be it. It's kind of the Zen approach to interviews. Don't try to hard, just do what you know how to do and find that place where you can be genuine.
_the_inflator 6y ago
Same here. Motivation and will to learn beats almost everything in a ever changing world of IT. Look for curiosity, interests and blend them with your product.

ChrisMarshallNY 6y ago

This. I was a hiring manager for 25 years, and this was exactly what I did. I made very, very few mistakes, and actually had some pleasant surprises.

thaumasiotes 6y ago
> I made very, very few mistakes How do you know? How often did you follow up on rejections to see whether they should have been hires?
- ChrisMarshallNY 6y ago
  Actually, for the company that I worked at, and the level of folks we hired, I often heard about how they went. The only one that made me sad, was a chap who used to show up on the Adobe Photoshop splash page. We offered, he declined. In the aggregate, I think things turned out OK for all of us. There are some folks that I have to admit, probably did best by not accepting us.
  - geoduck14 6y ago
    >There are some folks that I have to admit, probably did best by not accepting us. Yeah, I hear that. I remember interviewing someone who was _good_, but not at this narrow thing that we were hiring for. She seemed SO hopeful that we would give her an offer, I wanted to tell her directly "this job is going to waste 6 mo of your life and offer you nothing I return"
    - ChrisMarshallNY 6y ago
      My most fond recollection was a young chap that was a "second choice." The first declined, and this guy had very little of the exact skills we needed, but he had a real eagerness. He turned out to be an amazing hire. I think that he far outstripped the first choice, and he has gone on to do quite well, after leaving our company. I like to think that I ran a fairly good shop. We kept people for decades. When they finally rolled up our shop (after 27 years), the person with the least seniority had ten years.

lordnacho 6y ago

Same here. There's no silver bullet question, and no high pressure situation with me. My approach has just been to have a conversation, and try to move it along naturally. What do you think of concepts? What useful STL did they add? Why did you go with this design? Ask me something. If the person doesn't really have the level of interest required, they will run out of things to say. Like a cave left unexplored. The good candidates will go down all the caves with you, even if they don't quite know what's there. In particular, the times I've had dud hires it was not possible to know from the standard fare of coding questions and IQ questions. When I was doing that obviously the people I hired passed. But for instance one guy really didn't want to be a programmer, he just knew how to answer the questions. He ended up stalling on his first assignment, and eventually decided to change careers. Another dud also lacked motivation, perhaps because he was asked to do something not quite in his area to begin with. He ended up not doing anything at all. Apart from those two, dozens of others have turned out ok. I never ran into that guy who couldn't do FizzBuzz, despite not asking. I also don't think it was all that bad to let go of the duds within a quarter, they never got so ingrained in the team that we depended on them, and they could plausibly move on to another job without mentioning us on their CV.

pocketgrok 6y ago
I’ve been job searching lately and it is brutal. I’m fairly social normally but interviews terrify me. I freeze up, lose my train of thought and I don’t think my enthusiasm for my work really comes though. It’s probably not as bad as I imagine but it’s really frustrating.
- bitexploder 6y ago
  If you will permit me some trite but genuine advice: I have been interviewing and hiring people for well over a decade and it's not much more fun as the interviewer. Just pretend you are having a conversation with a friend about a project you really enjoy. It's kind of like worrying about how you will perform in a race. The training is already done when you show up to the starting line. The race is the easy part. You know what you know, just demonstrate it. Let the chips fall where they may, as they say. If you fall short, so be it. It's kind of the Zen approach to interviews. Don't try to hard, just do what you know how to do and find that place where you can be genuine.

_the_inflator 6y ago

Same here. Motivation and will to learn beats almost everything in a ever changing world of IT. Look for curiosity, interests and blend them with your product.