|
|
|
|
|
by pkukkapalli
2204 days ago
|
|
I have thought about this quite a bit recently as well. I think the main thing to look for in interviews is "does this person have a clear and sound thought process?" In theory, the whiteboard questions are meant to suss this out, but the prevalence of Leetcode and other interview prep websites blurs the signal. I wonder if just asking for a one or two page design doc on something would be a much better signal, since that's probably what you'll need to do on the job anyways. |
|
In fact, someone who is clear and sound in writing might get bogged down when writing code. Good writers are (obviously) not necessarily good coders.
I do think there is potential around the design doc. Design is a big part of a lot of roles. In addition, in a lot of these roles, having the "best" design isn't better than having a design that the rest of the team can understand. Still, I wouldn't do it for the purpose of identifying good "thinking". I would do it because I expect the people I hire to be good (or have potential) at what they will be expected to do.