We switched from a random set of questions to a take home coding assignment (that we compensate for) and a discussion of said coding assignment.
It's pretty clear what kind of work someone will do when you can look at work they've done.
It's pretty clear what kind of work someone will do when you can look at work they've done.
I agree with the DRY intuition though: making coders repeat code challenges/assignments is stupid. Some sort of verification or credentialing after completion of assignment, signed by a 3rd party, would be really cool.
I typically want to see how people use resources and deliver with real IDEs and collaborative tools like git
I agree that the most valuable thing is not seeing how the solution was implemented (we want to keep the total hours expended to less than 20 for the senior engineer challenge and less than 5 for the junior challenge) but seeing how someone navigates their environment and how they talk through how they arrived at the solution. It's especially interesting to ask about alternatives, areas for extension and tradeoffs.
Candidates arguing about the amount?
Comp for a take home interview assignment isnt common yet so the social more doesnt exist.