Overall Square's interview process was fairly standard. They try to improve upon the process, and in some ways they do, but overall it falls short of what they're trying to do. For the most part it comes down to luck (who you get to interview you) and memorization. With 3 coding interviews and 2 technical discussion (and a talk with the manager) this is a test of endurance. Process: The interview process is "pair programming". The issue is they leave it up to the interviewer to determine how to implement that. Out of the four programming exercises I had I would say only one was true pair programming. The other mostly sat there taking notes and semi engaged (or slightly bored?). So expect more of a whiteboard session with an IDE and Google. After the coding you'll have open ended discussion with people on various teams. This isn't tough but after 3 hours of coding with 3 separate people it can be tough to be engaged. Questions: Despite what I read here most of my questions were variants of pretty standard interview questions. Design this, manipulate that, find this, etc, etc. Nothing was too difficult but they're not things you do in the real world and not something I can solve and implement while still entertaining the interviewer in the hour given. So memorize basic implementations of standard problems so you can spend your mental energy engaging the interviewer with your coding presentation. I would say my experience was fairly negative but I'll give props to a slightly better interview experience than other companies. I didn't get a confirmation of my onsite until the night before (but had been in contact with the recruiter so I knew things were still on). Out of the four coding interviewers I worked with one was fantastic, two were fine (took notes, not much feedback or engagement), and one was probably among my top worst interviewers. The interview is a full day which is pretty exhausting and works against most people (also makes it hard for people who already have a job).