Square Software Engineer interview typically runs 5 rounds: recruiter screen, technical assessment, hiring manager chat, onsite loop, project walkthrough. Timeline is several weeks and can stretch out; the process is practical and a bit hit-or-miss.
$138K
Avg. Base Comp
$225K
Avg. Total Comp
4-6
Typical Rounds
3-6 weeks
Process Length
We've seen Square lean toward candidates who can move comfortably between implementation and product thinking. The standout signal in this experience is that the technical work was practical rather than purely academic: one candidate faced an end-to-end banking system design, another had a hotel booking platform, and even the coding prompts included a poker-hand simulator and a collaborative problem-solving exercise. That mix tells us Square is looking for engineers who can reason through real systems and edge cases, not just recite patterns from memory.
A recurring theme across candidate reports is that the interviewers seem friendly and engaged, but the bar still depends heavily on how clearly you can explain tradeoffs while you work. We’ve seen rounds that felt like a vibe check paired with a deep dive into past work, which suggests the team pays close attention to whether your experience is coherent, hands-on, and technically grounded. The project walkthrough matters here because it gives interviewers a chance to test how you think about ownership, not just what you built.
The other non-obvious pattern is the variability. Our candidates report a process that can feel a bit hit-or-miss depending on the interviewer, so consistency matters: if your design answer is strong but your coding narration is shaky, that can stand out. Square seems to reward candidates who can stay calm in collaborative settings and make their reasoning easy to follow, especially when the prompt is intentionally more realistic than textbook.
Synthesized from 1 candidate report by our editorial team.
Had an interview recently?
Share your experience. Unlock the full guide.
Real interview reports from people who went through the Square process.
The hardest part for me was that the process kept stretching out longer than I expected. I started with a recruiter screen, then moved into a practical technical assessment that was not really LeetCode-style, which was a nice change of pace. After that I had a hiring manager chat that felt more like a vibe check and a discussion of past work, and then a full-day onsite loop. That final loop had two more technical interviews with different engineers, an architecture round, and a walkthrough of a past project. In total it felt like a pretty standard software engineer process, just with a lot of moving pieces and a lot of time invested.
The technical parts were a mix of coding and design. In the coding rounds, I was asked a LeetCode-style question in one interview, and in another round the coding was collaborative, with the engineers watching and interacting as I worked through it. The design questions were more practical than abstract: I had to design an end-to-end banking system of the process, and The interviewer asked me to design a hotel booking platform. I also got a simple object-oriented design challenge, and one question was to write a program that simulates poker hands. The behavioral part was straightforward and centered on talking through a project I had worked on. Overall the interviewers were usually nice and wanted me to do well, but the process still felt long and a bit hit-or-miss depending on who you got. I ended up not getting an offer, and after all that, the rejection was just a generic automated email, which was frustrating. My main takeaway is to be ready for practical coding, OOD-style design, and a solid project walkthrough, not just algorithm grinding.
Prep tip from this candidate
Be ready for practical, non-LeetCode technical screens plus collaborative coding where interviewers talk through your approach as you work. Also prepare a clear walkthrough of one past project and practice system design around end-to-end products like banking or booking flows.
Share your own interview experience to unlock all reports, or subscribe for full access.
Sourced from candidate reports and verified by our team.
Topics based on recent interview experiences.
Featured question at Square
Write a SQL query to create a histogram of the number of comments per user in the month of January 2020.
| Question | |
|---|---|
| Top 3 Users | |
| Cumulative Distribution | |
| P-value to a Layman | |
| Payments Received | |
| Hurdles In Data Projects | |
| Cross-Region Inventory Sync | |
| Customer Success vs. Free Trial | |
| Annual Retention | |
| Loan Model | |
| Inherited Model Evaluation | |
| Book Combinations | |
| Swipe Payment API | |
| Decision Tree Evaluation | |
| Azure Kubernetes Infrastructure | |
| Justify a Neural Network | |
| Decreasing Payments | |
| Your Strengths and Weaknesses | |
| Evaluate News | |
| Choosing Between Python and SQL | |
| 2nd Highest Salary | |
| Employee Salaries | |
| Closest SAT Scores | |
| Empty Neighborhoods | |
| Subscription Overlap | |
| Top Three Salaries | |
| Rolling Bank Transactions | |
| Merge Sorted Lists | |
| String Shift | |
| Bagging vs Boosting |
Synthesized from candidate reports. Individual experiences may vary.
The process starts with a recruiter screen to discuss your background, interest in Square, and overall fit for the Software Engineer role. This is the first filter before moving into the technical stages.
Candidates complete a technical assessment that is described as practical rather than purely LeetCode-style. The exercise appears to focus on applied coding and problem-solving, setting the tone for the more hands-on technical interviews that follow.
Next is a hiring manager conversation that feels like a mix of a vibe check and a discussion of past work. The interviewer spends time on your previous projects and general fit for the team.
The final stage is a full-day onsite loop with multiple interviews. It includes two technical interviews with different engineers, an architecture round, and a walkthrough of a past project, with technical questions spanning coding, collaborative problem-solving, object-oriented design, and system design.