A big problem of the industry is that a generation of developers has grown up who think that everyone should know the "modern stack". And now they're the ones making decisions on who to hire and who not to. Google did something there, and you, therefore, must keep up. Like if you don't know what the Kotlin compiler expands coroutines into or didn't play with Compose in your free time from work, then you're worthless. Nonsense. Well, like all polar sides, which I constantly talk about here. You can always come up with a counterexample.
This knowledge is a plus, of course, like any other knowledge. But it's silly, for example, to interview a person who worked for several years on a design system in XML, asking about what effects exist in Compose. Or listing coroutine context keys and Room annotations to a person who built a crazy offline-first system on rx + plain SQL. Moreover, the more senior you are, the more you dive into some specifics. Well, some infrastructure, tests, multi-modularity. And most interviews I've seen represent generic questions about the platform and the company's stack.
It's okay to ask generic questions, it's okay to discuss the modern stack, but you shouldn't draw far-reaching conclusions from this. If you're not ready to carry a discussion on comfortable territory for the candidate, then it's better to determine seniority by soft skills, I swear, talk about life. Knowledge of concepts is much more important than knowledge of technologies.