4 ms·

Interviewing skill is one way you get a job. After you've been doing this for long enough, and have a reputation, you tend to just get jobs by referrals. I dec

Interviewing skill is one way you get a job. After you've been doing this for long enough, and have a reputation, you tend to just get jobs by referrals. I decided in my last change of positions to try interviewing for jobs like most people without referrals, since I had several other referral positions open. And I was horrible. I was ridiculously bad, and couldn't get a job at jobs that paid less, and were for less skill. It was quite hilarious. Thankfully, all of the referral jobs were begging for me, and that was fine. There was no real loss, but it was a bit concerning that if I didn't have an extensive connection network that I would be in a significantly worse role.

alex_c 10y ago
Which parts of the interviews were you really bad at? How would you change the interviews you had so they don't reject qualified candidates? I've been interviewing a lot of developers lately, and while I'm fairly happy with my process (I've managed to avoid bad hires so far), I always have to wonder if I'm turning down people I shouldn't.
- chrshawkes 10y ago
  "I hate anything that asks me to design on the spot. That's asking to demonstrate a skill rarely required on the job in a high-stress environment, where it is difficult for a candidate to accurately prove their abilities. I think it's fundamentally an unfair thing to request of a candidate." Scott Meyers
- AndyNemmity 10y ago
  The technical question part. Because I work on so many different things at the edge of innovation, I have a wide array of experience for a short period of time, and then I move on. When I interview for jobs, I open up to any of the possible things in my background, of which it will take me perhaps 2 weeks to get back up to speed. But I am not going to take that 2 weeks for each job I interview for. I have trained my brain to learn things, and discard them keeping only the current tasks in memory. The rest I know how to obtain again. This means that I get asked questions I know that I've done repeatedly in the past, but can only vaguely explain without a refresher. To the interviewer, this means I am underqualified at best, and at worst, lying about my past skills. A lovely example of this during the process was that I was asked a fairly basic SQL question that I failed to explain when I had just landed from my second flight of the day. I didn't get the presales role for working with the database. (non referral job.) However, I did get offered a job working on development for that database, as well as product management for the database. So I couldn't get a presales role, that I've done in my past, because I couldn't answer a fairly basic sql question. I knew exactly how to answer it, the venn diagram of sql joins, a half second google, but in an interview, I blanked on the answer. That is indicative of my experience with non-referral positions. I've given training on sql joins a good 30 times in my life, and couldn't explain the join in an interview. Just the way it goes for me, thankfully it's not actually impactful in my life.
8a 10y ago
This is an important data point surveys like this ignore.

alex_c 10y ago

Which parts of the interviews were you really bad at? How would you change the interviews you had so they don't reject qualified candidates? I've been interviewing a lot of developers lately, and while I'm fairly happy with my process (I've managed to avoid bad hires so far), I always have to wonder if I'm turning down people I shouldn't.

chrshawkes 10y ago
"I hate anything that asks me to design on the spot. That's asking to demonstrate a skill rarely required on the job in a high-stress environment, where it is difficult for a candidate to accurately prove their abilities. I think it's fundamentally an unfair thing to request of a candidate." Scott Meyers
AndyNemmity 10y ago
The technical question part. Because I work on so many different things at the edge of innovation, I have a wide array of experience for a short period of time, and then I move on. When I interview for jobs, I open up to any of the possible things in my background, of which it will take me perhaps 2 weeks to get back up to speed. But I am not going to take that 2 weeks for each job I interview for. I have trained my brain to learn things, and discard them keeping only the current tasks in memory. The rest I know how to obtain again. This means that I get asked questions I know that I've done repeatedly in the past, but can only vaguely explain without a refresher. To the interviewer, this means I am underqualified at best, and at worst, lying about my past skills. A lovely example of this during the process was that I was asked a fairly basic SQL question that I failed to explain when I had just landed from my second flight of the day. I didn't get the presales role for working with the database. (non referral job.) However, I did get offered a job working on development for that database, as well as product management for the database. So I couldn't get a presales role, that I've done in my past, because I couldn't answer a fairly basic sql question. I knew exactly how to answer it, the venn diagram of sql joins, a half second google, but in an interview, I blanked on the answer. That is indicative of my experience with non-referral positions. I've given training on sql joins a good 30 times in my life, and couldn't explain the join in an interview. Just the way it goes for me, thankfully it's not actually impactful in my life.

8a 10y ago

This is an important data point surveys like this ignore.