4 ms·

Interviewing these days is not a technical challenge. It’s a fraternity/sorority rushing week. Technically I was qualified and able to answer their questions.

by xyst 5y ago

Interviewing these days is not a technical challenge. It’s a fraternity/sorority rushing week. Technically I was qualified and able to answer their questions. But ultimately was turned down after 6 rounds of interviewing. I think I was heavily dinged because I wasn’t entirely familiar with their product in the wild, and was never given any hint as to what product I would be working on.

bufferoverflow 5y ago
I'm surprised good programmers have the time/patience for 6 interviews. I think 3, maybe 4 is my max. If you can't figure out my skills in that amount of time, your process is broken. I also disagree that interviewing is not a technical challenge. For most programmers it is. There are very few who can breeze through FAANG-level technical interviews.
- bb88 5y ago
  2 total interviews. Maybe 3 if they have questions. But if they have questions, they should have figured it out between the first and second interview.
- knuthsat 5y ago
  For me, if the 2nd interview is not me talking to someone from their company that I might work with and if I cannot ask questions about the problems they solved, their approach to programming or building teams (depending on their role), I just say to the recruiter that I'm not interested. The only reason why I'd come somewhere is if I like the engineers or if I'm in need of money. If I need the money, I won't ask a thing.
MarkSweep 5y ago
At one startup I did a couple rounds of phone interviews and a full day of in person interviews. Lastly I got to chatting with the co-founder. I can't remember the precise question I asked about how they were building out the team, but I clearly remember the answer. They made the interview process longer and more involved in an effort to narrow the field of candidates. I understand the reasoning: if you think you have a special mission and want people dedicated to that mission, filter by dedication. But I'm not really sure there is a way for any one candidate to consume as much time interviewing for a role as that company could consume out of a pool of candidates. And that includes my smart-ass idea of trying to interview at Pinterest and stopping in the middle of the interview saying "please sign up to see the rest of this whiteboard solution".

by xyst 5y ago

bufferoverflow 5y ago

I'm surprised good programmers have the time/patience for 6 interviews. I think 3, maybe 4 is my max. If you can't figure out my skills in that amount of time, your process is broken. I also disagree that interviewing is not a technical challenge. For most programmers it is. There are very few who can breeze through FAANG-level technical interviews.

bb88 5y ago
2 total interviews. Maybe 3 if they have questions. But if they have questions, they should have figured it out between the first and second interview.
knuthsat 5y ago
For me, if the 2nd interview is not me talking to someone from their company that I might work with and if I cannot ask questions about the problems they solved, their approach to programming or building teams (depending on their role), I just say to the recruiter that I'm not interested. The only reason why I'd come somewhere is if I like the engineers or if I'm in need of money. If I need the money, I won't ask a thing.

MarkSweep 5y ago

At one startup I did a couple rounds of phone interviews and a full day of in person interviews. Lastly I got to chatting with the co-founder. I can't remember the precise question I asked about how they were building out the team, but I clearly remember the answer. They made the interview process longer and more involved in an effort to narrow the field of candidates. I understand the reasoning: if you think you have a special mission and want people dedicated to that mission, filter by dedication. But I'm not really sure there is a way for any one candidate to consume as much time interviewing for a role as that company could consume out of a pool of candidates. And that includes my smart-ass idea of trying to interview at Pinterest and stopping in the middle of the interview saying "please sign up to see the rest of this whiteboard solution".