> It felt like a massively unfair way to evaluate me. My advice to someone in a similar situation is to start talking and ask about what we want to really achi

> It felt like a massively unfair way to evaluate me. My advice to someone in a similar situation is to start talking and ask about what we want to really achieve here. Not what the task description literally says (SPA or whatever - that's "how" but not "what for"), but what's the real business purpose for it. For the interview purposes - what do they want to see during or after those 50 minutes. Then making a guess whenever this objective can be realistically delivered within the provided constraints, and communicating how do you feel about it. If they provide their real expectations (e.g. "we want to see how you tackle a problem outside of your immediate expertise domain, we recognize harsh time constraints and it is okay if you won't complete it, although we'd appreciate trying your best") it's all fair game. If they don'tjust insist they want this specific JS SPA done in 50 minutes - well, that says something about their project management habits. In such case, I'd start asking questions about the role responsibilities.