Oh, if we're talking about 10+ years, then I definitely want to test that they can code, and make sure I get a good read on their attitude. You get a lot of "architect" types who think they are too good for coding now and can hand down their glorious wisdom from above, when in reality they were kind of mediocre engineers to begin with, are now even more divorced from the reality of their decisions, and come up with worse designs than if you had just left it to some juniors to figure out themselves.

But yes, for senior candidates, I'm doing a lot less coding and a lot more design and architecture, because that should be what they can offer differentiated from their less experienced peers. And I'm also going to be looking for their interviewing skills and philosophy, because they will probably end up doing more of the interviewing and thus team-building, not to mention the culture they set by all the juniors looking up to them.