That's the point of the interview, to validate the resume by having in-depth conversation about the projects in it.
Note this doesn't mean trying to test for the skills that they must've applied to do those jobs. That's hopeless to achieve in an interview for all the reasons endlessly documented in these threads. Instead, assume that if they did the jobs listed in the resume, obviously they must have the skills to have done them. So now the interview is about validating they did those jobs, not the technical detail itself.
Based on more than two decades of hiring, this works very well.
Note this doesn't mean trying to test for the skills that they must've applied to do those jobs. That's hopeless to achieve in an interview for all the reasons endlessly documented in these threads. Instead, assume that if they did the jobs listed in the resume, obviously they must have the skills to have done them. So now the interview is about validating they did those jobs, not the technical detail itself.
Based on more than two decades of hiring, this works very well.