Square Interview preparation

You don't need to solve all parts of the problem to "win" the interview. We're looking for holistic feedback about how you approach the problem, from the perspective of things like analysis, technical design, maintainability, fluency in your chosen language. Do you test, do you think of good cases to test, how well do you troubleshoot. A good solution to parts 1-2 is probably better than a bad solution to parts 1-3.

I interviewed with square 2 times and both the times I got rejected in phone interview. Both the times, the template was same. First time it took me a while to understand the question so couldn't manage my time well. Second time, even though question was fairly easy, I couldn't solve all the parts of it. Interviewer just pasted the next part once I solved it's previous part. It was verbose and took some time to read and understand requirements. I am pretty sure the terms like "technical design", "maintainability" doesn't apply to all kinds of questions. Also, most often interviewers don't show all the three parts of the question upfront which makes things even more difficult. This is my experience. Not generalizing anything. It depends on the kind of question the interviewer asks.