Quote:
Originally Posted by Dadhawk
Well, yea 11 interviews is excessive. I don't think I've ever had more that 3 for any job. Personally, I rarely call someone back for more than a second interview session (which could include more than 1 individual interview).
Hope things look up for you soon. We can't get candidates here, so when we do, we treat them gently!
|
Mentioned before, but she did find work finally a few months ago. I think that one was 11people, 7 interviews. Still nuts, but it seems to be the thing now
Quote:
Originally Posted by NoHaveMSG
After 3 I would have told them, "I don't think you are the right company for me."
|
It seems all the rage now. Been part of a chain where they're doing 5 for fairly junior roles.
Quote:
Originally Posted by spike021
For all you programmers out there, today I failed an interview for panicking and totally forgetting to question the value-types of the data I was working with.
i.e.
array: [["1230", "testing", ""], ["200", "testing3", ""], ["1230", "testing1", ""], ["2000", "testing", ""]]
Basically the first value is a timestamp in 2400 format. I had to sort first by the 2nd value (some word), and then sort by the first.
So I did a Python library sort with a lambda.
But I messed up one thing, I kept getting the list back in a different than expected order.
With that bug, I screwed up the rest of the interview.
The bug was... I was sorting the first values (the timestamps) as strings, not type-casting to integers.
|
24hr format it shouldn't matter unless it's not actually a proper timestamp, which would have to be 0200 not 200. That's an evil trick question. Not a good place to work anyway.
I'm not sure we have anything near you but would be happy to take a peek at your resume and dig through / keep an eye on postings.
I think other developers are half the problem. We've gotten into one-upping each other. Expecting candidates know exactly what we knew at a level and ignoring the guidelines.