When I'm the interviewer, I don't do whiteboard/CoderPad exercises. As a candidate, they make me nervous.
But, I do think they can be a decent part of a larger interview process.
I've had some very reasonable whiteboard exercises where the interviewers were very clear that the problem was tricky and I wasn't necessarily expected to solve it - the emphasis was on conversation and hearing my thought process. I actually enjoyed some of them.
If you can start off on a contract, do that. It is
the best way to even out the power dynamic of the
interview process.
I agree in principle but in practicality, there are some difficulties such as needing healthcare coverage for my family. (Yes, the US system of employer-subsidized healthcare is utterly broken, but that's what I'm dealing with)
Counterpoint: why not just just take a fulltime job and quit / move on if it's not a good fit?
But, I do think they can be a decent part of a larger interview process.
I've had some very reasonable whiteboard exercises where the interviewers were very clear that the problem was tricky and I wasn't necessarily expected to solve it - the emphasis was on conversation and hearing my thought process. I actually enjoyed some of them.
I agree in principle but in practicality, there are some difficulties such as needing healthcare coverage for my family. (Yes, the US system of employer-subsidized healthcare is utterly broken, but that's what I'm dealing with)Counterpoint: why not just just take a fulltime job and quit / move on if it's not a good fit?