So far its been pretty solid. My key approach is to ask about the last task they were working on. Then keep asking further questions on it to gauge their depth

So far its been pretty solid. My key approach is to ask about the last task they were working on. Then keep asking further questions on it to gauge their depth of understanding. For someone I want to hire there is almost always a "Beautiful Mind" moment. They stop trying to distill information and start just start talking about all the little details they needed to iron out to get it working right. That when I know they actually did the work and are not just a taking credit for being on a project. Why did you choose that over other approaches? Did you use an ORM or raw queries? What was the O(n) on that operation? What kind of database did you access? How did you add that to the CI/CD pipeline? Just flex the questions for whatever and the people that did not do the work fall apart. Then you have solid devs that show up every day and do the work. You also get the bonus of the dev knowing their new boss knows their shit.