|
|
|
|
|
by lovich
3138 days ago
|
|
Exactly, my favorite flavor of those are the ones where the interviewer appears to not stop until they find what you cannot solve, which is perfectly fine for an interview, but they still seem to treat that failure as an inability to program. One place I interviewed at wasn't doing much more than crud, and we got into our 4th cs question of that day, and my 6th with the company so far after their phone screen. They gave me some question that was solved with a flood fill. I admitted I had never encountered that before and muddled through it getting an answer that could not handle a few edge cases which I pointed out before they even brought it up. After that point they cut that phase of the interview short and the next guy asked me some things that were answered off my resume and they said they'd call me back which of course they didnt. I could easily have been denied for other reasons but it's one of numerous interviews where I go through 1-n cs questions and whenever I get to the first one I can't solve the interview is cut short. It's just a giant waste of everyone's time |
|