Block Interview Questions
& Process for Software Engineers

You are allowed to look things up. The technical phone screen runs as a pair-programming session on CoderPad, and reaching for the docs or Stack Overflow mid-problem costs you nothing, because the round is built to watch you work the way you work on an ordinary Tuesday. Code that compiles and runs beats code that is theoretically optimal and half-finished. Several stages over a few weeks: a recruiter screen sets up that phone screen, then you move into a virtual onsite of four to five rounds spanning coding, system design, object-oriented design, and behavioral.

Most rounds outside the coding sessions and the hiring-manager conversation are run by two interviewers at once, so more pens land on the written feedback than the round count suggests. That feedback is what the debrief works from, and the debrief settles the hire and the level in one sitting rather than deciding your level later. The hiring manager carries real weight on the call. Once it goes your way, you move to the offer.

Which business you join changes the questions before you have answered one. Square hires for merchant payments, Cash App for consumer money movement, Afterpay for installment credit, Bitkey for Bitcoin self-custody, and each runs its own hiring with its own stack and its own house style of problem. The onsite shape holds across them: a practical coding round, an object-oriented design round, a payments-shaped system design, and a behavioral round anchored in Block's mission, with the exact split turning on level and which business you are joining.

The weighting favors engineering judgment over puzzle speed. A round can turn on whether your class boundaries would survive the next feature request, or on whether you noticed that two services can disagree about the same balance. Interviewers are deciding whether they would hand you code that moves other people's money.

CodingDS&A

Medium-centered data-structures and algorithms problems (arrays, strings and hashing, graphs and trees) written and run live

Object-oriented designOOD

Model and implement a real module in code: clean class design, extensible interfaces, and the edge cases you cover, not algorithmic tricks

Practical / integrationHands-on

Build against a real API or wire a small end-to-end feature: graded on production judgment and how you handle failure and retries

System design

Payments-shaped problems: a double-entry ledger, Cash App P2P transfer, an idempotent payments API, real-time fraud detection, API rate limiting

BehavioralValues

Anchored in Block’s mission of economic empowerment and how you work across its businesses: Square, Cash App, Afterpay, TIDAL, Bitkey

Finishing early does not end the round. The coding questions are built in layers, and a clean answer to part one is the interviewer's cue to add the constraint that breaks it. Problems sit around medium, with arrays, strings, and hashing carrying most of the load and graphs and trees close behind, but the grade lands on clean, correct, running code rather than obscure tricks.

So drilling for speed is the wrong preparation. Complexity called out unprompted still helps, and so do edge cases you name before anyone asks. The bigger win is code you would not be embarrassed to leave in a pull request: real names, small functions, nothing clever you could not defend in review. And the algorithms are only part of the coding bar, since an object-oriented design round and a practical / integration round sit alongside them.

These are the rounds where candidates who trained on contest problems come apart. In the object-oriented design round you model a real module in code, and you are graded on design quality and the edge cases you cover: classes with honest boundaries, interfaces that survive a feature nobody has asked for yet. Nobody is timing you against a clever algorithm.

The practical / integration round asks you to build a small end-to-end feature, often against a real API. Production judgment is the signal, and it lives in unglamorous places: what the code does when the call times out, how the retry behaves, whether a request that arrives twice charges the customer once. At a payments company none of that is hypothetical. The retry and timeout behavior these rounds probe is the same problem Square solved in OkHttp, its widely used open-source HTTP client.

Both rounds go better if you treat them as a pull request rather than an exam. Say your assumptions out loud, since an assumption you never voiced reads as one you never noticed, and stay on the hook for whether the thing you built is actually correct.

Block lets you take equity as cash. US employees can convert any portion of an RSU grant into money that arrives through regular payroll, a program that exists because XYZ stock swings hard enough to leave grants underwater. It does not raise your total, but it changes what you are actually negotiating over. The offer itself is base salary, equity, and a possible sign-on, and which parts flex depends on level and how strong your case is.

Equity is where the growth lives. Bonus is close to nothing on the IC rungs, so pushing on a bonus percentage spends the conversation on the smallest number in the offer. Most of the negotiation is really the case you make for your level and your scope, and a competing offer remains the strongest thing you can put on the table.

Average total compensation by level, per Levels.fyi (US, as of Aug 2026); self-reported and rounded. Block labels these levels by number only; the Entry, Senior, Staff, and Principal mappings are the market-standard reading by years of experience. Equity is public XYZ stock (convertible to cash), and the overall median is about $363K. Levels 8 and above have too little public data to show.

Have the conversation after the decision goes your way and before the paperwork hardens. Asking what the top of the band looks like is a normal question and recruiters answer it. Point the ask at equity, which is the component that actually scales with level here.