One really interesting and effective (in my opinion) that I've encountered is pair programming. The interviewer would ask the interviewee to come in and come up with something to build/fix/hack. It could be an app from scratch, existing and sometimes an issue in a popular Github repo.
The interviewer is usually the observer while you do all the driving. And you are allowed to google or use SO. This gives the interviewer an idea on how you tackle problems and also shows a bit of your technical capabilities.
Yeah, that's a very good approach that I've heard of too. The problem is it takes time to get acquainted with a codebase, much longer than the 30-60 minutes you get in a traditional interview, anyway.
For further actions, you may consider blocking this person and/or reporting abuse
We're a place where coders share, stay up-to-date and grow their careers.
One really interesting and effective (in my opinion) that I've encountered is pair programming. The interviewer would ask the interviewee to come in and come up with something to build/fix/hack. It could be an app from scratch, existing and sometimes an issue in a popular Github repo.
The interviewer is usually the observer while you do all the driving. And you are allowed to google or use SO. This gives the interviewer an idea on how you tackle problems and also shows a bit of your technical capabilities.
Yeah, that's a very good approach that I've heard of too. The problem is it takes time to get acquainted with a codebase, much longer than the 30-60 minutes you get in a traditional interview, anyway.