Talking about previous projects: I like it! You get to show off a bit and also show what you learned and what your existing flaws are. It also gives the interviewer a good idea where you're at when they ask you how long something took. (Which for me, is longer than the average dev but i think the important part is figuring it out without giving up)
My current job I got through a series of background/how-do-you-deal-with-people interviews. I kept bracing for a code test but it didn't happen?
Take home tests: I've done the debug-this-problem thing.
I've also had conversational rapidfire q&a interviews just to quiz me on fundamentals, and those are a lot easier than being put on the spot, coding without internet. However after a handful of failures at the coding-sans-internet tests I felt like I had to get my rigour up, which was a good motivator.
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.
Talking about previous projects: I like it! You get to show off a bit and also show what you learned and what your existing flaws are. It also gives the interviewer a good idea where you're at when they ask you how long something took. (Which for me, is longer than the average dev but i think the important part is figuring it out without giving up)
My current job I got through a series of background/how-do-you-deal-with-people interviews. I kept bracing for a code test but it didn't happen?
Take home tests: I've done the debug-this-problem thing.
I've also had conversational rapidfire q&a interviews just to quiz me on fundamentals, and those are a lot easier than being put on the spot, coding without internet. However after a handful of failures at the coding-sans-internet tests I felt like I had to get my rigour up, which was a good motivator.