Square software engineer candidates describe a recruiter screen, practical coding that is often not standard LeetCode, design or existing-codebase work, and a project walkthrough. All three reports ended without an offer.
$192K
Avg. Base Comp
$266K
Avg. Total Comp
3-4 rounds
Typical Rounds
Not reported
Process Length
Candidates describe the Square software engineer interview as practical rather than a pure algorithm test. Two of three reports say the coding was not standard LeetCode-style. One candidate got a transaction-processing pair-programming problem, and the interviewer kept adding requirements. Those included multiple users, a rolling time window, out-of-order transactions and memory limits. Another candidate faced a remote screen with two follow-ups that escalated in complexity, and struggled to finish in time. Expect problems that grow after the first working solution, so practice clarifying requirements, explaining trade-offs and testing as you go.
The other recurring theme is design and real-code work. One candidate extended a partially built Java service and discussed error handling, API design, maintainability and production concerns. Another was asked to design an end-to-end banking system and a hotel booking platform, and also got a small object-oriented design task, a poker-hands simulation. Two candidates mention a walkthrough or deep dive of past work, so prepare one or two projects with specific technical decisions and results.
All three candidates were rejected. One described a generic automated rejection email, and another never heard back after the onsite. One candidate also said the process dragged on longer than expected. With only three reports, treat the details above as examples of what has come up rather than a fixed format, and expect your loop to vary by team and level.
Synthesized from 3 candidate reports 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 | |
| Loan Model | |
| Inherited Model Evaluation | |
| Annual Retention | |
| 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 | |
| Closest SAT Scores | |
| Employee Salaries | |
| Subscription Overlap | |
| Empty Neighborhoods | |
| Top Three Salaries | |
| Rolling Bank Transactions | |
| Monthly Customer Report | |
| Merge Sorted Lists | |
| String Shift |
Synthesized from candidate reports. Individual experiences may vary.
Candidates report starting with a recruiter conversation. One senior-level candidate describes about 30 minutes covering experience, motivation for Square, location, compensation and level. It typically works as a fit and logistics check, so prepare a concise story of your background and a clear reason for wanting the role.
Candidates describe a technical screen that was not standard LeetCode. One had a remote coding screen with two escalating follow-ups and ran short on time. Another had pair programming on transaction processing, where requirements kept changing. Practice building incrementally, clarifying assumptions and testing while you talk.
One candidate reports a hiring manager chat that felt like a vibe check plus a discussion of past work, placed after the technical assessment. Not every report mentions this step, so it may vary by team. Be ready to explain what you built, your decisions and how you work with others.
Candidates report coding rounds, an architecture or design round, and in one case work in an existing Java codebase. Design prompts included a banking system, a hotel booking platform and a poker-hands simulation. Interviewers often talk through the approach with you as you work, so practice thinking aloud on practical problems.
Two candidates mention a project walkthrough or deep dive during the final stages, and one felt the interviewers were probing for something specific. All three reports ended without an offer, with an automated rejection email in one case and no response in another. Prepare a tight project narrative and expect decision timing to vary.
