Squarespace Interview Questions
& Process

The interview process was okay, and the people I met were generally nice, but they tended to promise more than they could deliver. After the final interviews, I had a last chat with the recruiter about how I felt about the experience. The recruiter was open about when the team would discuss my candidacy and mentioned I was the only person they were considering due to my excellent performance. He also said he'd already gotten approval from everyone he'd spoken to. Getting rejected is fine, but stringing a candidate along and saying 'I think you'll get an offer' is not. What initially seemed like a great company to work for ended up being a disappointing process. If they contacted me for another role in the future, I don't think I'd go through their hiring process again because of how they treat candidates.

So, the whole experience was pretty wild. It started with a screening call, then went into a portfolio presentation. I had to show 3 case studies. They seemed to really like my work, pointing out my impact, how I dealt with stakeholders, my teamwork with developers, and my general design skills. They even said they loved my design craft. But, despite all the positive feedback and compliments, Squarespace ended up rejecting me. And to this day, they haven't given any reason why. It just goes to show, you can do great, get praised, maybe even connect well with the interviewers, and still get turned down. So, honestly, if I were you, I'd probably skip Squarespace.

The interview process is involved and with many steps, but it's not too long. They can set things up in consecutive days, if you're able to attend. It's even possible to do many interviews in the same day. The whole process took 1 month, but could have been faster if I had the time. The steps: - Phone screen with a recruiter - Leetcode-style (easy) DSA interview with an engineer. If successful, the real fun begins. There's 4 more interviews that, as stated, can happen in the same day or consecutive days. - Code analysis interview. They simulate a code review scenario with a very poorly written piece of code, and it's your job to point out the errors and suggest corrections/improvements. - Leetcode-style DSA Interview. Similar to the previous one, but harder. If the previous one was Leecode easy, this one is a medium. Brush up on your basic data structures, and be ready to talk about run-time complexity and so on. - System Design interview. Design a large scale application with its APIs, backend components, the database schema, etc. You should know about how to scale it to many users, etc. - Behavioral interview. The standard kind where they ask questions in the form of "Tell me about a time when..." and you should answer with the STAR format. Usually it's a hiring manager who conducts this one. The process was overall very good. People are respectful and nice, and after each interview feedback comes fast.

I went through 4 stages after the initial phone screening, each lasting around 50-60 minutes. These included implementing a front-end feature live, solving a LeetCode medium-level algorithm problem, a behavioral interview, and a system design round where I had to plan out an aspect of an app with many data points. Overall, the interviews themselves and the interviewers were great. The recruiter, though, seemed disengaged and didn't communicate well. Even though I passed all stages and got positive feedback from the interviewers, I didn't get an offer. I have a feeling they might be posting fake jobs or are just getting an overwhelming number of highly qualified applicants right now.