None, but a) if you can't write that trivial code I don't want to be on a team with you anyway because I'm going to be teaching you how to basically think, and b) the part where you talk about the code, not the part where you write it, is the part where I try to detect if you're any good at communication or abstract thought.

(disclaimer: all of this is notwithstanding the fact that some people's brains shut down specifically during interviews/places where they feel under pressure, which I have nothing but sympathy for. Afaik that's an unsolved problem with coding interviews. I would always try to lower their stress but it is not a sure thing.)

I don't know what "elements from a matrix in spiral order" is supposed to mean. If it is that for the matrix

    A B 
    C D
    E F

you are supposed to return A B D C E F, then if you cannot do this, I don't care about how clean your code is.

I'm really against leet code interviews in general as a concept.

Having said this, I'd never hire a person that's not able to reason about this. Actually writing the implementation is really secondary