The purposes of these interviews is not (usually) to see if you know the answer. It&#x27;s to see how you problem solve.<p>If you knew the correct answer to e.g. the BFS algorithm, you&#x27;ll get thrown another question that they hope you <i>don&#x27;t</i> know.<p>When interviewing, the thing I want to see most is how someone works through a problem: can they solve from first principles? do they go via trial and error? do they ask for a computer to google things up&#x2F;a book?<p>Picking raw CS problems is an easy option, as its something that you <i>should</i> be able to solve, and it means I don&#x27;t have to require you to know Angular&#x2F;React&#x2F;Flavour of the month (new tools are easy to teach the right candidate).<p>You&#x27;re <i>not</i> going to immediately know the answer to everything that comes up in your job; so evaluating how you solve the unfamiliar is very important.