I'm sorry you didn't feel like you had a good experience interviewing with our company. We're always trying to learn from our mistakes and improve, so I appreciate you sharing immediate feedback after your experience. It sounds like we didn't do a great job in communicating how we were using the homework to inform ourselves about a potential candidate, and we will be changing our comms to future candidates so that it's very clear. To clarify, the purpose of the homework is not to create a production-ready app, but to show us a candidate's approach, their understanding of code and modern frameworks, affirming basic standards of code cleanliness, etc. If a candidate's homework shows some less than ideal decisionmaking due to a time constraint (which is very understandable), it's helpful if they are then able to articulate their process, what tradeoffs they made, what other factors (long-term and short-term) were considered, etc. when they are asked about it during the interview, especially for a senior-level candidate. When we gauge a candidate and whether we think they will be successful in a role, we consider the totality of what we saw, which includes both the homework and the interview. While this may not necessarily be an accurate indication of whether the candidate can do the job due to circumstantial factors (e.g. candidate was having an off-day), it's the best we have to go on and we try to make our process as fair as possible. There are times we do cut the interview short if we feel the interview is going very poorly, but that's primarily out of deference for the candidate's time. Apologies that you had such a negative experience interviewing with us this round, but we wish you the best of luck in finding a role that is a better fit.