I'm not a fan of multiple rounds of interviews and I don't think I would ever be comfortable with a coding test during an interview.
In terms of questions I would ask, I like asking about something the person has made that they really enjoyed making. Ideally, that is something they programmed but I'm actually not that fussed if it isn't. There is no right or wrong way to answer (well, I guess not answering the question at all is "wrong") but really I just want to see how technical they can get into anything they are passionate about, trying to tap into their enthusiasm about any subject.
I do ask other questions like if they have any open source work but not to "grade" a person against someone that doesn't, purely just to see any code they have already written in the wild.
I do like the idea of "take home" tests and while I know people could 100% cheat, I do throw in a wide variety of problems. Basically, I build something the way we would for the company, rip out a bunch of things all over the place and see how someone else puts it back together. I give them relatively detailed information on what the functionality needs to be and off they go. I try and aim for this to be relatively short because time is valuable for both them and myself but I do find it a good insight into problem solving in a specific domain. I also don't require for it to be complete either, you focus on your strengths and that is all I am really wanting to see. If you can do it all though, great!
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.
I'm not a fan of multiple rounds of interviews and I don't think I would ever be comfortable with a coding test during an interview.
In terms of questions I would ask, I like asking about something the person has made that they really enjoyed making. Ideally, that is something they programmed but I'm actually not that fussed if it isn't. There is no right or wrong way to answer (well, I guess not answering the question at all is "wrong") but really I just want to see how technical they can get into anything they are passionate about, trying to tap into their enthusiasm about any subject.
I do ask other questions like if they have any open source work but not to "grade" a person against someone that doesn't, purely just to see any code they have already written in the wild.
I do like the idea of "take home" tests and while I know people could 100% cheat, I do throw in a wide variety of problems. Basically, I build something the way we would for the company, rip out a bunch of things all over the place and see how someone else puts it back together. I give them relatively detailed information on what the functionality needs to be and off they go. I try and aim for this to be relatively short because time is valuable for both them and myself but I do find it a good insight into problem solving in a specific domain. I also don't require for it to be complete either, you focus on your strengths and that is all I am really wanting to see. If you can do it all though, great!