Then the other side is giving you a "small project" that takes the better part of a day to implement. I just pass on those as well, and i'll do the short challenges but I don't really take the company seriously after that.
I found the most effective is whiteboard sessions that actually somewhat resemble reality as if I was the Product Owner and/or Architect with a problem. Then go through the design process, what database system would you use, would it have a a web service or be microservices or whatever, dig into the database design etc. May ask more specific technical questions along the way that are relevant to the design.
but the main thing is there is almost no actual coding done in the interview process at all.
With your experience you will likely know the right course of action to take immediately, but will still have to reach consensus with the team to keep them engaged as solving the problem is the fun part.
Get good a steering the conversation to your solution vs. just handing it down. You know the whole making it seem like it was their idea thing.
If your team perceives you as an authoritarian, they will be afraid to make any decisions on their own and you will become a constant roadblock.
I found the most effective is whiteboard sessions that actually somewhat resemble reality as if I was the Product Owner and/or Architect with a problem. Then go through the design process, what database system would you use, would it have a a web service or be microservices or whatever, dig into the database design etc. May ask more specific technical questions along the way that are relevant to the design.
but the main thing is there is almost no actual coding done in the interview process at all.