After a recruiter call, I ended up doing a pretty long sequence that started with a take-home coding exercise. After that, the interview run got heavier: I had hands-on coding work plus system design style questions, and my final round ended up taking roughly 10–15 hours of total effort. The time investment felt enormous, and I kept expecting at least a more thoughtful follow-up.
When I finally finished the last round, the communication stopped almost immediately. I received a generic rejection email that felt impersonal given how much time I’d already put into the process. What stuck with me most was the contrast between the seriousness of the work—especially the final leg—and how little the ending felt like a real conversation about my performance.
> 1 year
Average Negative United States
After a recruiter stage, I went into a technical screen that felt more interesting than stressful. In my session, the interviewer asked a front-end coding question connected to rendering a merge sort, and it leaned into practical logic rather than pure memorization.
In the follow-up flow, I also experienced the kind of preparation-light technical setup that Square used elsewhere: an engineer introduced the round, talked about what the work tends to look like, and then walked me into the coding question on a coderpad-like environment. Across these technical screens, the vibe was friendly enough, but I still didn’t get a clear sense of what happened immediately afterward in my case. I never received a proper follow-up that explained how the interview went, which left the whole thing feeling open-ended.
> 1 year
Average Negative United States
I joined the process with a fairly standard structure at first: a technical round where I worked in a collaborative online IDE with an interviewer eva…
> 1 year
Average Positive Dublin, Dublin
My process centered on an online collaborative coding interview. I was paired with an engineer and worked in a coder-style environment to write and co…
> 1 year
Average Negative United States
My process started with a recruiter call that felt friendly and calm, and then I moved into a one-hour coding screen. The interviewer came back a bit …
Unlock every Software Engineer interview experience
Interviewed here recently? Add yours to help the next candidate. You'll appear as Anonymous.
What to expect
Distilled from the reports
Interview Structure & Timeline
The interview process typically begins with a recruiter call, followed by a technical screen and then an onsite phase that includes multiple rounds, often extending over several weeks. Candidates reported feeling strung along due to the lengthy timeline and multiple conversations with different interviewers.
Recruiter callTechnical screenOnsite phase
Technical Coding Screen
The technical coding screen often involves pair programming in a collaborative environment, where candidates are evaluated on their coding fluency, communication, and problem-solving approach. However, some candidates experienced interruptions or misalignment with the interviewer's expectations during this round.
Pair programmingCoding fluencyProblem-solving
System Design & Past Experience
Candidates can expect system design questions, often with specific themes provided in advance, as well as discussions about past technical experiences. These rounds are crucial, as some candidates found their performance in these areas significantly influenced the final decision.
System designPast experienceTechnical themes
Behavioral & Values Assessment
Behavioral interviews focus on communication, collaboration, and how candidates handle challenges, with a strong emphasis on fit with company values. Some candidates felt that these discussions were pivotal in the evaluation process, sometimes overshadowing technical performance.
Behavioral interviewCompany valuesCommunication
Feedback & Closure
Many candidates reported a lack of constructive feedback and closure after the interviews, often receiving generic rejection emails that left them uncertain about their performance. This absence of clear communication can lead to frustration and a feeling of unfairness.
FeedbackClosureRejection
Overall Difficulty & Experience
While the technical challenges are generally manageable, the overall experience can feel overwhelming due to the length of the process and the pressure of multiple rounds. Candidates noted that the experience varied widely depending on the interviewer's style and expectations.