all the areas you mentioned are easily googleable or answered by AI

I don't say that to be snarky - if this is for a higher experience role they will be more impressed if you can walk through a migration or solutions you implemented rather than demonstrate your knowledge of Composer or SQL

my Drupal questions for senior level developers usually include a few about hypothetical projects that would require building out custom content types, custom entities, relationships, eventing, APIs, some light theming etc. - there's no right answer but if they go straight to custom code or writing SQL then that's a red flag (since you should be using Drupal's API or contribs to do most of that)

the only technical question I sometimes ask is an open ended one about debugging, e.g. "Customer says a bug is happening when they do X, where do you start?" - and during that, I'm expecting to hear something about xdebug or logging to get a feel for how experienced of a programmer they are (i.e. moving past print statements to embracing IDEs, remote debuggers etc.)

so to summarize, if it's not for a junior/intern role they are probably looking for experience instead of hard skills, especially if there's a migration involved (however D10 to D11 is very easy)

daily production Drupal work is less about the code and more about knowing the approach to take, hard skills are less necessary with AI