Square software engineer candidates describe recruiter alignment, practical and collaborative coding, project discussion, and design-oriented technical interviews rather than a purely algorithmic process.
$152K
Avg. Base Comp
$216K
Avg. Total Comp
Not reported
Typical Rounds
3-6 weeks
Process Length
Square software engineer candidates describe a process that puts practical engineering alongside coding and design. One candidate began with a recruiter conversation about experience, role interests, location, compensation, and level. Another described a hiring-manager discussion of past work before a full-day onsite loop. Prepare to explain engineering decisions as you make them, not merely present a finished answer.
Technical work may be collaborative. A candidate reported incrementally building a transaction-processing solution while responding to added constraints involving multiple users, rolling windows, out-of-order events, memory limits, and edge cases. That account also emphasizes requirement clarification, trade-offs, clean code, testing, and adapting an implementation. A separate candidate encountered both a LeetCode-style question and a collaborative coding round, so applicants should be ready for either format.
Practical codebase work also appeared: one candidate added functionality to a partially implemented Java service and discussed error handling, API design, testing, maintainability, and production concerns. For design preparation, reported prompts included a disconnected point-of-sale scenario, banking and hotel-booking systems, and an object-oriented design exercise. Be ready to walk through a past project clearly, since that came up in the reported process. The available accounts do not establish one fixed sequence or total round count.
Synthesized from 2 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 an initial recruiter discussion covering experience, current role, interest in Square/Block, desired work, location, compensation, and level. Prepare a concise account of your background and the kind of engineering work you want.
Candidates report practical coding rather than exclusively LeetCode-style work. One account involved incrementally implementing transaction processing while explaining choices and adapting to new requirements such as timing, ordering, memory, and edge cases.
One candidate worked in a partially implemented Java service and added functionality. Discussion may cover where a change belongs, avoiding unrelated modifications, error handling, API design, testing, maintainability, and production concerns.
Candidates report architecture or system-design interviews, including product-oriented scenarios such as banking, booking, and offline point-of-sale behavior. A past-project walkthrough also appeared, so be ready to explain your role and technical decisions.
