[borbulon]

I went on an interview some years ago and was asked how I'd architect a certain situation with Models and Controllers. I spent some time discussing why that wasn't the right solution for what they were trying to do, and they said thanks but no thanks.

Now to be fair to them, I was asked to do a certain task and I failed to do that task. It's pretty cut and dry.

But I also walked away glad they turned me down, because if they're going to try and force me to do something a specific way when that way is inefficient, or troublesome or just plain not the best answer, then I wouldn't really want to be working there anyway.

[nerdponx]

I've handled interviews like this before by saying "normally I wouldn't use Models and Controllers for this task because X, but since you asked, I assume you just want me to demonstrate that I know what Models and Controllers are, and that's what I'll do".

How they react to that is telling. I've had interviews where they say "great point, that's exactly the kind of thinking we need!" and other interviews where they take it as a challenge to their authority. The latter is of course a red flag and you should excuse yourself from any further interviews.

[thomastjeffery]

> Now to be fair to them, I was asked to do a certain task and I failed to do that task. It's pretty cut and dry.

Being that cut and dry (read: binary) is a problem of its own; and it's probably the more important one to solve.