|
|
|
|
|
|
by ZhL
2309 days ago
|
|
|
Yeah, that would require a whiteboard and a programmer friend who is kind of enough to endure the misery of watching me struggle with a marker, trying to remember how to write by hand again.. I have very little experience interviewing (my previous job lasted 10+ years, my current one - almost 6). But I thought that solving problems on a whiteboard is fairly common, if not a golden standard for an on-site. At least both of the on-sites I had recently had a whiteboard component. I think certain problems are a good _partial_ fit for a whiteboard interview: math/geometry, graphs and trees, combinatorics, system design. However, it does not feel natural to solve the _entire_ problem on a whiteboard. Additionally, I was also expecting whiteboard sessions to be a collaboration and a discussion. That hasn't been my experience so far.. I had either very little feedback, or a feedback that was more confusing than helpful (to me at least). Hence the question if I can do anything at an interview to increase the chances of a positive outcome. Or if there is a systematic approach to this problem. |
|
|
There is.
The whiteboard firing squad questions are pretty predictable once you do enough of them.
The very bad ones will ask directly from one of the popular sites. DFS/BFS/Invert Binary Tree/Coin Change/Hop Jump Skip/you know.
You have to learn it once and can regurgitate until you forget them again.
I am happy to help a fellow HN'er and work out some trial whiteboard interviews with you if you feel that would help.