This guide tracks 7 patterns (1 of them typically hard), 5 commonly reported questions, and a 4-round loop that usually runs 2-3 weeks.
Key patterns
Showing 3 of 7Common questions
Showing 3 of 5Interview process
Showing 1 of 4 roundsStart studying now, without an account
Every lesson below is a free public reading page. No sign-up, no install, and the worked examples run in the tab.
The Python behind Square (Block)'s top patterns
These lessons do not teach the patterns themselves. They teach the language mechanics each pattern is built from, which is the part you have to have in your hands before the pattern is worth practicing.
- Arrays & HashingPython10 min readTuples & setsGroup fixed records with tuples and track uniqueness with sets.
- Arrays & HashingPython10 min readDictionariesMap keys to values: read safely, assign, and merge dictionaries.
- TreesPython11 min readRecursion: a function that calls itselfSolve a problem in terms of a smaller version of itself, with a base case to stop.
- Dynamic Programming (1D)Python20 min readProfiling, complexity & cachingFind the hot path, fix complexity, and memoize repeated work with lru_cache.
- Dynamic Programming (1D)Python24 min readThe cost you asked for is not the cost you gotCorrect output, wrong cost. Learn to read a body for the work it hides, and to count that work exactly rather than guess at it.
- StringPython9 min readString indexing & slicingReach into text by position, take slices, and measure length.
Square (Block) runs a system design round
The System Design course opens with the method itself: how to scope a vague prompt, turn it into requirements you can defend, and budget the clock. You write your own answer first, then reveal a model answer to compare against.
- System design roundSystem Design25 min readClarifying a Vague PromptTurn a one-line prompt into a scoped problem with three to five sharp questions and explicit out-of-scope.
- System design roundSystem Design20 min readFunctional RequirementsPick the three user capabilities that define the core loop, phrase them as 'users can X', and defer the rest with a reason.
- System design roundSystem Design25 min readNon-Functional Requirements, QuantifiedTurn 'scalable and reliable' into quantified, testable targets (p99, nines, QPS) and name the design lever each one forces.
How Square (Block) judges you outside the code
The values and engineering norms the interviewers are calibrated against. Useful for the behavioral round, and useful for deciding which trade-off to argue for in the technical one.
Values they name
- Inclusion - economic empowerment for all
- Purpose - build products that matter
- Discipline - do more with less
- Collaboration - work together effectively
- Excellence - strive for the highest quality
What they look for in behavioral rounds
- Demonstrate passion for economic empowerment
- Show understanding of payments and fintech
- Exhibit reliability and fault tolerance mindset
- Display customer-focused problem solving
- Show you can work across multiple products/domains
How the team builds
- Payments and fintech expertise
- Multiple products - Square, Cash App, Bitcoin
- Reliability and fault tolerance paramount
- Economic empowerment mission
- Mobile-first for many products
Primary stack
- Java
- Kotlin
- Ruby
- Go
- React
- MySQL
- Kubernetes
- Code review
- thorough reviews focused on reliability
- Deployment
- staged rollouts with extensive testing
- Documentation
- comprehensive documentation for payment flows
Reading the guide is the easy part. Square (Block) will ask you to perform.
CodeSparring is a practice environment, not a question bank. You sit a full round against an AI interviewer, in an editor that runs your code, and you leave with a score and a specific next rep.
An interviewer that reacts
Carry one problem from clarifying questions through to working code while an AI interviewer responds to what you say and what you type, by voice or by text.
Code that actually runs
An editor in the page with a real runtime and real test cases. You run your solution and read the output, the same way you would in a shared editor on the day.
A scored round, not a vibe
Every session ends with a rubric covering problem solving, communication, and code quality, so you can see which part of the round is costing you the offer.
And 364 lessons you can read right now, free
The whole curriculum is public. Read the concept, run the worked example in the tab, and only sign in when you want the graded exercise at the end of a lesson.