Real, anonymous reports from people who interviewed for Software Engineer at Squarespace, newest first and distilled into what to expect across the loop.
I went through a fairly standard but slightly extended sequence that still felt coherent: recruiter outreach, then two technical interviews, followed by a behavioral round after a coding assessment. The whole journey took about a month, and by the end I’d spoken to multiple interviewers across the loop.
I started with a recruiter phone call and then moved pretty quickly into a coding screen. The technical part felt like a typical LeetCode-style medium, and it was as much about how I communicated as it was about getting to the answer—I remember trying to talk through what I was thinking and asking questions when something was unclear. After that, the process shifted into an onsite-style loop that stayed very structured, with each stage taking about an hour.
The interview process typically begins with a recruiter call, followed by a coding screen, and then a structured loop of technical interviews including DSA, system design, and behavioral rounds. The entire process generally spans about a month, with multiple one-hour interviews that maintain a clear flow.
Candidates can expect a mix of coding challenges, data structures and algorithms (DSA), system design discussions, and sometimes code review scenarios. The technical questions are often framed to reflect real-world problem-solving rather than just theoretical knowledge.
Behavioral interviews are common and typically utilize the STAR format to assess teamwork, leadership, and communication skills. Interviewers focus on understanding candidates' thought processes and how they articulate their experiences.
The overall difficulty of the interviews is generally described as average to slightly above average, with a focus on core fundamentals. Candidates often report feeling prepared but sometimes find the expectations for performance unclear, especially in the final stages.
While many candidates report a friendly and supportive atmosphere, there are mixed experiences regarding communication and feedback throughout the process. Some candidates noted delays or a lack of follow-up after interviews, which can leave them feeling uncertain about their standing.
Candidates should prepare for a variety of technical topics, including data structures, algorithms, system design, and language-specific knowledge, particularly in JavaScript or Java. Practicing coding problems in a collaborative manner can also be beneficial.
