
Squarespace Frontend Engineer Interview Questions
& Process
Real candidates share what happened, how many rounds they had,
and how the experience turned out.
Based on 15 interview experiences · FREE TO READ
Candidate interview experiences
First-hand accounts from people who interviewed at Squarespace.
Front End Developer
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.
- Could you build a live image carousel that includes buttons for cycling through images and also has an automatic timer for transitions?
Frontend Developer
My interview experience with Squarespace was mostly positive, with polite and respectful interactions, and what seemed like a good environment. The technical interview was tough, which is good, and I spent a lot of time prepping based on their guides. The whole thing took about six hours and involved several rounds. What was disappointing, though, was that after all that, I didn't get any feedback, even though they said I would at the beginning. When I asked about it, they explained that their summer internship program was really busy, so they couldn't provide feedback. I get that companies get swamped, especially during internship season, but I was really hoping for some insights after investing so much time and effort. Even a little feedback would have been useful for knowing how to improve. It would have been a nice way to wrap things up, considering all the work from both sides. Honestly, it felt a bit inconsiderate of my time and effort. When you put in hours for an interview, you should at least get the promised feedback, even if it's short. I hope Squarespace will think about this for future candidates.
No confirmed questions were included in this interview report.
Frontend Software Engineer
I applied online via LinkedIn and got a 3-hour take-home coding challenge on HackerRank. After passing that, I moved to virtual onsite interviews. I could split them over days but did them all in one day. There were 4 rounds plus a quick chat with the recruiter. The first round was a JavaScript coding challenge on CodePair. The second was a system design interview using CodePair's whiteboard feature. The third was a behavioral/conversational interview. The fourth was another coding challenge on CodePair, focusing on Data Structures and Algorithms. It was a great experience, not stressful because the recruiter gave good details. The interviewers were chill and knew what they wanted.
- Could you build a carousel UI with CSS & JS, given the HTML?
- How would you design a dashboard featuring graphs, a data table, and search/sort functionality?
- Implement the search component logic to find items based on searchTerm matching tags, categories, and name.
Squarespace Frontend Engineer Interview Questions
Quoted word for word from Squarespace interview reports.
“Implement the search component logic to find items based on searchTerm matching tags, categories, and name.”
Read reports →“Create a slider using JavaScript, HTML, and CSS.”
Read reports →“Could you fix this bug in the provided JavaScript code?”
Read reports →“Could you write some correct JavaScript code that uses closure?”
Read reports →“Could you write a basic template engine class?”
Read report →“How do you approach debugging in a VSCode-like IDE with limited go-to-definition and no TypeScript?”
Read report →“Could you build a live image carousel that includes buttons for cycling through images and also has an automatic timer for transitions?”
Read report →“Given the IDE limitations, how would you find call sites to fix bugs?”
Read report →“Can you explain Closures and Curry?”
Read report →Formats, difficulty and experience
Across all 15 Squarespace interview reports.