3 ms·
I try to ask some general questions about what they like, what part of the stack they find themselves most proficient in. If they claim to be full stack still f
by bryanrasmussen 9y ago
I try to ask some general questions about what they like, what part of the stack they find themselves most proficient in. If they claim to be full stack still find out what they're most proficient in. Then take them through some of our code that needs refactoring, from obvious to deeper refactoring, have them ask me questions about it, make suggestions and so forth. But I haven't done that for nearly a year because I'm just consulting now.
I was at a thing last night waiting in line, and someone behind me was talking about an interview they had given. They had the guy explain what quicksort was and do some whiteboard coding etc. etc. and he did everything perfect and he had an outrageous cv and they were wondering why he wanted to work there ( this was half overheard so I didn't get everything) I was surprised because I've never actually been anywhere were people ask me to explain quicksort...
I was at one really good interview one time where I had to suggest refactors to a little game in a language I didn't know and the suggestion should have been binary search - but I had a brain problem at the moment and couldn't remember the name of the algorithm so I hesitated (uh how do I say what to do here when I can't remember the name of that big array algorithm) after I had gotten the code down from taking half an hour to run to taking 8 minutes (saving different states so I could just look them up when needed) and the interviewer got bored, did the solution and showed me out (politely)