31–40 of 53 posts
This is my favorite because it made so much sense and clearly illustrated my problem solving skills. I said "Leave" as I got up and left.
I hate the "What is your greatest weakness?" question. It's a great question for a politician, not so much for a software developer. My answer is usually "heroin"...just to see their response.
"My honesty." "I don't think that's really a weakness." "Nobody cares what you think."
I hate the "What is your greatest weakness?" question. It's a great question for a politician, not so much for a software developer. My answer is usually "heroin"...just to see their response.
I find asking a developer to write code on a whiteboard or word document to make not much sense. I was asked how many bytes are there in x amount of space, which i find as not much to do with competence in software development. A follow up question is, whats the point in asking these questions, any idea on what the goal is? There has to be an intention behind it.
Sorry, you don't see the intention behind asking people to write code on a whiteboard? Being able to lay out ideas, code, and architecture on a whiteboard is a useful skill in and of itself for communicating with coworkers, let alone using it as a way to get insight into how an interviewee codes.
I find asking a developer to write code on a whiteboard or word document to make not much sense. I was asked how many bytes are there in x amount of space, which i find as not much to do with competence in software development. A follow up question is, whats the point in asking these questions, any idea on what the goal is? There has to be an intention behind it.
Sorry, you don't see the intention behind asking people to write code on a whiteboard? Being able to lay out ideas, code, and architecture on a whiteboard is a useful skill in and of itself for communicating with coworkers, let alone using it as a way to get insight into how an interviewee codes.
"If you are in a room with 100 good ninjas and 1 evil ninja and the lights go off, how do you save all of the ninjas?" This is my favorite because it made so much sense and clearly illustrated my problem solving skills. I said "Leave" as I got up and left.
I am not a fan of these types of questions. I'm more of a slow burn problem solver, but I've been presented these types of questions at places and it made it clear that those places were not a good fit for me and vice versa.
Earlier quoted context omitted.
Sorry, you don't see the intention behind asking people to write code on a whiteboard? Being able to lay out ideas, code, and architecture on a whiteboard is a useful skill in and of itself for communicating with coworkers, let alone using it as a way to get insight into how an interviewee codes.
If you want to see how someone codes, ask them for a sample of code that they wrote under realistic circumstances. On a white board in front of strangers who are only there to judge is not a realistic circumstance. A realistic circumstance involves the candidate's preferred development environment and tools. It is not always possible for job seekers to share code they've written in the past, not everyone has time or…
Earlier quoted context omitted.
If you want to see how someone codes, ask them for a sample of code that they wrote under realistic circumstances. On a white board in front of strangers who are only there to judge is not a realistic circumstance. A realistic circumstance involves the candidate's preferred development environment and tools. It is not always possible for job seekers to share code they've written in the past, not everyone has time or…
One good way would be to make the person come for a week and give them the chance to do a couple of simple initial coding tasks. Something self-contained that you would normally give to a newcomer in the team.
Just who is willing to put up with a week long interview? If someone is searching for a job while they already have one, this is completely untenable.
Earlier quoted context omitted.
Sorry, you don't see the intention behind asking people to write code on a whiteboard? Being able to lay out ideas, code, and architecture on a whiteboard is a useful skill in and of itself for communicating with coworkers, let alone using it as a way to get insight into how an interviewee codes.
Its not useful skill to code in a whiteboard, drawing diagrams maybe? Even that how often does it happen.
Earlier quoted context omitted.
One good way would be to make the person come for a week and give them the chance to do a couple of simple initial coding tasks. Something self-contained that you would normally give to a newcomer in the team.
>come for a week Just who is willing to put up with a week long interview? If someone is searching for a job while they already have one, this is completely untenable.
Not ideal but probably much more useful than the current interview formats commonly used.