https://arxiv.org/abs/2201.00650
I did a cursory browse through on few sections of this current book (namely the CV module), and I think the questions are on the easier end for actual ML interviews/whiteboarding. Normally, I would face some more depth (and equivalently as a tech lead, similarly ask more than surface-level questions to potential hires).
tldr: If you have gone through an introductory ML course like Andrew Ng's CS229 or CS230, these question banks seem obvious & trivial to solve.
Invest time creating your own pet projects rather than cutting corners with these books.
[0]https://huyenchip.com/ml-interviews-book/contents/3.1.1-base...
https://news.ycombinator.com/item?id=41084834
Note machine learning engineering is very different from model and data work, i.e. designing the experiments. There are plenty of jobs where you package Nvidia drivers and pytorch files into docker containers, or write low level C++ to e.g. implement a transformer network on a new device architecture. Those require nothing more than a cursory knowledge of machine learning, and you can essentially get away treating them as magical black box matrix multiplication formulas. Very few companies can actually afford the 7 figure salaries for actual frontier level machine learning research.
For example, if you want to run a GPT model on some obscure graphics chip, you are better off hiring a C++ computer graphics/embedded engineer to do it than a typical academic trained ML researcher. The engineer can implement a GPT model simply by building out the matrix multiplications, and can do a better job without even knowing what an activation function is.