I think it's fine to expect engineers to know graph algorithms in terms of what they do and when to use them, but knowing how to implement them on the spot on a

I think it's fine to expect engineers to know graph algorithms in terms of what they do and when to use them, but knowing how to implement them on the spot on a whiteboard is stupid. This one company had an interesting problem that I identified quickly as an application of A* with some interesting edge cases on top. Working through those cases and coming up with the heuristic was clearly the main point of the interview, or so I thought. The interviewer asked me to write out A* on the whiteboard...