The problem as I see it is the difficulty in posing a problem that's interview-sized and still relevant to their actual workflow. I don't know how much whitebo

The problem as I see it is the difficulty in posing a problem that's interview-sized and still relevant to their actual workflow. I don't know how much whiteboard algorithm time you spend during your day to day, but for me it's vanishingly small. What is relevant in my day to day is dumb shit like "What do you name things?" "How do you control access to classes internals?" "How do you construct an API?" "How do you communicate your designs to people living outside your head?" Virtually none of which you can get done on a whiteboard with a problem set that you can define in five minutes or so.