3 ms·
It is nice to hear a defense of this style since there’s often so much complaining about it, and the tips to mitigate the downsides are useful. Personally I do
by drewrv 4y ago
It is nice to hear a defense of this style since there’s often so much complaining about it, and the tips to mitigate the downsides are useful.
Personally I don’t mind a whiteboard session or two during a loop but what’s wild to me is how, especially at big companies, you’re expected to do four or five of these to get an offer.
How often do these companies decide “well they understand when to use DFS and they can merge-sort a linked-list and they knew to use dynamic programming but we can’t hire them because they couldn’t remember how to implement a heap”?
- Apocryphon 4y agoThe problem is that these problems are not even whiteboard problems anymore. They’re often strictly timed coding exercises on Coderpad or Karat with actual mock IDEs and REPLs expecting running code under strict expectations. The more casual, flexible, subjective coding interview described by the OP is not the prevalent form of whiteboarding interviews, which has been superseded by the weeder version.
- nogridbag 4y agoDo you have any suggestions for a simple online coding portal? I know some companies have used a simple Google Doc for this reason, but that seems far from ideal.
- Apocryphon 4y agoCoderpad and Hackerrank are pretty de rigeur
- ergocoder 4y ago> you’re expected to do four or five of these to get an offer. I agree that this is unreasonable but not for the reason that you mention. Once you can pass this kind of interview, you can throw me 10 more and I will still pass them.