1. I ask about prior experience, following up on any interesting resume items or comments. I try to act like a "biographer" (per the book "Who") and just learn their story.
2. I ask them to describe data flow in a basic web app. If I push this UI submit button, explain the progression of data from the client to the database.
3. I ask for an explanation of core concepts of the framework I'm interviewing for or any one they've used.
4. I ask about version control concepts and some specific git commands.
5. I ask about prior team practices, e.g. what types of meetings they have and what the interviewee thinks of their effectiveness.
6. I ask about their knowledge of ops/DevOps, e.g. explain how a pipeline works.
7. I ask about basic CS/object orientation/language concepts, e.g. static vs. dynamic typing.
8. I ask what their most interesting project or story was and why it resonated with them.
9. I ask what their toughest debug was and how they solved it.
10. I ask about their experience with testing and opinions on how best to do it.
Between all that you get a pretty decent picture of what level they're at and what is their capacity to learn.