> not to come up with a BFS
But it's not about whether they solve the problem, it's about observing their problem-solving process... right? ;)
> But it's not about whether they solve the problem, it's about observing their problem-solving process... right? ;)
I did not say that the interview process at that company was my favorite or was the same as the one in the OP.
That said, my experience as a candidate at FAANG and smaller-but-not-super-small companies has generally been that I must at a minimum solve the problem, and that sometimes I must also solve it exactly the way some rubric says it is to be solved, so that providing an unusual approach that uses half the space and just as much time as the best approach the department has heard of also causes one to fail.
It seems like you might accidentally be testing your ability to predict their ability to solve the whiteboarding problems given their resume.
As an example, at one company we noticed that applicants with a certain level of educational achievement were dramatically less likely to be able to solve the problems we used than candidates with slightly higher or slightly lower levels of academic achievement. So if I made predictions about candidates, that's one factor that would influence my prediction, but it wouldn't necessarily mean that my subconscious bias was causing the candidates not to come up with a BFS.