I met Square at an event and after talking to one recruiter he took my resume. I got an email from the recruiter asking me follow a link to do a simple coding challenge. There were two questions and I was able to complete one. 3 weeks later the recruiter invited me to a phone interview. My interviewer called from San Francisco and we solved a problem together using the coderpad.io platform. The question was fun and was a real world example of the problems they solve at Square. We run through tests and improved on the solution and added more features. My interviewer was extremely nice and helpful. He later asked if I had any questions for him and I did. I had another similar phone interview about 6 weeks later. After 2 weeks I was invited to interview with some engineers in Atlanta, Georgia. They paid for flight, food, hotel, etc. At the office, I had 2 technical interviews where I solved a problem together with an engineer (my interviewer). Square calls their technical interviews pair programming because you and your interviewer would have separate keyboards but would share a screen together and write your code together using coderpad.io. The questions were not that hard and the interviewer was always very nice and helpful. I loved these interviews as they were not harsh but smooth and realistic. After this I had lunch with I think a senior software engineer but there was another senior software engineer and a manager. It was fun talking to them and we all seemed to have a lot in common. The penultimate interview was with 2 senior engineers who asked me questions about one of my projects on my resume. The questions were very detailed as if they knew a lot about my project and the technology I used. It was very interesting and I actually underestimated this part of the interview process but I pulled through. The last interview was with one manager who asked me if I had any questions for him about Square or the Atlanta area in general. This conversation was very short so I felt less confident about the outcome. I flew back home and after a few emails back and forth between me and the recruiter, a phone call was scheduled for a workday. They called me to congratulate me and gave me the offer details. I was very happy with it and accepted it. Square's interview process is by far the best I have experienced anywhere. Just know how to use data structures, runtime complexity and you'll be fine. Also just be yourself! I wore some jean pants and long sleeved shirt with a pair of sneakers to the on site interview and I felt good about myself. It is more about what you say, how confident you are and how prepared you are.

My application was for Square. From application to offer took about 2.5 months so it is a fairly long process: 1. Code Signal assessment while applying for the job. They provide a link in the application and ask you to take it as part of your application. 2. Code Signal assessment from a recruiter. I was contacted by a recruiter to complete a Code Signal assessment again so that they could finish reviewing my application. I assume this means they didn't get the results of the first one? 3. 1 hour technical with a recruiter 4. 1 hour technical with a recruiter (a week later) 5. Virtual Onsite (another week later): a. 1 hour technical. This one was less like pair programming. It was similar to a LC Medium problem. b. 1 hour technical. Multiple parts revolve around designing/implementing a class. Each step adds complexity and is more difficult than the last. Got halfway through part 4. c. 1 hour for lunch (no interview) d. 45min Q&A past technical experience. Spend pretty much the whole time going in-depth on a project you've done. Choose one that you played a big role in. Ideally, one where you had some level of leadership and one where you can clearly express your impact. They will ask some technical stuff about the project and also about soft skills like how you approached solving problems or how you handled some conflict. They liked that I was able to give them a live demo of the project and said that most people aren't able to so I think it's good to have this prepared. e. 30min interview with the hiring manager. Talk about the role and about you. A good chance to sell yourself to the hiring manager and show why you're the best fit. Low stress and much more casual. f. 15min wrap-up chat with your recruiter. They give you more info, ask how you think you did, and mine told me how I was doing so far based on feedback from previous phone screens and interviews from earlier that day. Overall most technicals were not focused on LC style questions. I had a couple that were about implementing classes, so make sure you brush up on good class design. One of my phone screens was a pretty simple problem with multiple parts. Only one of my onsite technicals was like a LC medium. I can't reveal the problems I had because of the NDA they have you sign but both of my onsite questions happened to be related to matrices. 6 days after the onsite (was over the weekend so only 4 business days) the recruiter called me and said he got approval to make me an offer, but the hiring manager I interviewed with decided to go with a higher-level engineer instead (I'm guessing L4). We scheduled a meeting with a different hiring manager for the following morning. After interviewing with that hiring manager, I got a call from my recruiter that afternoon which is when I received my verbal offer. He went to get final approval and later that night I received the actual offer letter.