The short answer: Block, the company behind Square and Cash App, publishes one live page on how it hires: its AI hiring principles. That page says interviewers evaluate technical skills, collaboration, communication and leadership, that people make every hiring decision, and that pasting AI output into a live exercise is not allowed unless your interviewer or recruiter says so. Cash App's interview guides, as published in 2025 and since taken down, describe a recruiter chat, a 60-minute pairing interview in your own language and a virtual onsite of coding and behavioral interviews. The current loop may differ from those guides. Last reviewed October 2026.
Block Software Engineer at a Glance
Base Salary (US postings)
$142k - $395k/yr
Interview Rounds
6 to 7 rounds
Levels
Builder Fellow - Staff Software Engineer
Block software engineer interview: quick answers
| Question | Short answer |
|---|---|
| How many interview rounds? | Cash App's 2025 guides describe a recruiter chat, a 60-minute pairing screen and a virtual onsite whose length depends on level. For mobile roles the onsite was 2 coding plus 2 to 3 behavioral interviews. Candidate guides describe 4 to 6 onsite rounds that add system design and a domain round. |
| What do the rounds test? | Block says interviewers evaluate technical skills, collaboration, communication and leadership. Cash App's 2025 pairing guide said problems are rooted in algorithms and real production work, with no trick questions, and are judged on collaboration, thought process, code quality and problem solving. |
| Can I use AI tools? | Only where Block allows it. Some roles have assessments that involve AI tools, and your recruiter tells you what is permitted. Pasting AI output into a live exercise is not allowed unless the interviewer or recruiter says so. Only Block's own recording tool may record interviews, and you can opt out of it. |
| Is the pairing interview open book? | In Cash App's 2025 pairing guide, yes. You could use the internet, code in the language you know best and run your code often, and compiler errors did not count against you. The current loop may differ. |
| How long does it take? | Block does not publish a timeline. Its US postings say roles stay open for an average of 55 days before they are filled. |
| What does Block pay software engineers? | Zone A postings (New York, San Francisco and Seattle areas) print starting base pay of $142K to $213K or $180K to $270K for most Software Engineer postings, $217.8K to $326.8K for Senior and $263.6K to $395.4K for Staff. |
The Block software engineer role
What Block engineers work on, the skills its job postings ask for, and what a normal week looks like.
Primary Focus
What You Need
- 3+ years for Software Engineer, 5 to 8 for Senior and 10 to 12+ for Staff
- Designing, building and owning features end to end, including testing, rollout and maintenance
- Operating production systems through on-call, incident response and follow-up fixes
- AI fluency: using AI tools across design, coding, testing and debugging while checking their output
- Design reviews, code reviews, documentation and mentoring
- Turning domain rules from tax, compliance or finance partners into reliable software
- Java, Kotlin, Go, Ruby or Python, depending on the team
Nice to Have
- Payments experience (a hard requirement on some payments teams)
- gRPC, Protocol Buffers and event-driven services on Kafka
- MySQL, Aurora, Vitess, DynamoDB and Redis at scale
- AWS, with GCP on some Cash App teams
- Large monorepo builds with Bazel, Gradle and Buildkite (Developer Experience)
- Snowflake, Databricks, Airflow and dbt (Data Platform)
Languages
Tools & Technologies
Want to ace the interview?
Practice with real questions.
A Week in the Life of a Block Software Engineer
Illustrative mid-level week · Block
An illustrative week for a mid-level engineer, built from practices Block describes in its own publications and job postings. Real weeks vary a lot by team.
Culture notes
- Employees choose home, office or hybrid unless the role needs a specific location, and Cash App calls itself a distributed team since day one.
- AI is part of daily engineering: Block reported over 90% of code submissions authored partly or fully with AI and a 30% rise in weekly code changes.
- Engineers own what they build, including on-call, incident response and postmortems.
- Block's Developer Experience team runs the largest monorepos and works on Bazel builds, CI speed and agentic workflows.
Key takeaway: Expect to own a service from design review to on-call, with AI tools in the loop and people approving every change.
Block software engineer levels and pay
Your level sets the bar you are interviewed against and the pay band of the offer.
Block Software Engineer Levels
Each level has different expectations, compensation, and interview focus.
What This Level Looks Like
A paid six-month fellowship for ten builders on design and engineering teams across Block brands, with possible conversion to full time.
Interview Focus at This Level
Block judges fellows on proof of building; applications were closed in October 2026.
Find your level
Practice with questions tailored to your target level.
Block's software engineer postings state no level code, so the rows below use posting titles. Titles and pay bands do not line up neatly: two postings titled Software Engineer carry the same band as the Senior postings. A candidate guide maps Software Engineer, Senior and Staff to L4, L5 and L6; Block does not publish that mapping.
Pay in Block's US job postings
Block's postings print a starting base pay range for each of four US pay zones, and each posting carries a brand: Square, Cash App or Block. No software engineer posting mentions a bonus or equity, but Block's benefits page says every employee receives equity and can join a stock purchase plan at a 15% discount.
| Posting | Location | US base salary range |
|---|---|---|
| Software Engineer, Reconciliation & Reporting (Square) | Bay Area, CA (Zone A) | $142K to $213K |
| Software Engineer, Cash App Taxes (Cash App) | New York, NY (Zone A) | $180K to $270K |
| Software Engineer, Privacy Engineering (Cash App) | Bay Area, CA (Zone A) | $180K to $270K |
| Software Engineer, Data Platform (Cash App) | Bay Area, CA (Zone A) | $180K to $270K |
| Software Engineer: Program Engineering (Block) and Payment Interfaces (Square) | Bay Area, CA (Zone A) | $217.8K to $326.8K |
| Senior Software Engineer: Product Platform (Cash App) and Developer Experience (Block) | Bay Area, CA (Zone A) | $217.8K to $326.8K |
| Staff Software Engineer, Cash App Banking (Cash App) | Bay Area, CA (Zone A) | $263.6K to $395.4K |
| Staff Software Engineer, Payments Acquiring (Square) | Bay Area, CA (Zone A) | $263.6K to $395.4K |
| Staff iOS Software Engineer, Bitcoin (Cash App) | Bay Area, CA (Zone A) | $263.6K to $395.4K |
Rows show Zone A, which covers New York, San Francisco, Oakland, San Jose and Seattle. Zone B (Austin, Chicago, Denver, Los Angeles, Portland, Washington DC), Zone C (Atlanta, Dallas, Houston, Scottsdale, Salt Lake City) and Zone D (Detroit, Indianapolis, Nashville, St Louis) pay less: the Senior band, for example, drops to $185.2K to $277.8K in Zone D. Staff postings show the same range in every zone. Postings state no level, so rows use posting titles, and no entry-level US posting was open. Ranges seen October 27, 2026.
Block software engineer interview process
The stages below follow Cash App's interview guides, as published in 2025 and since taken down, so the current loop may differ. Block's live AI hiring principles page covers how decisions are made, and candidate guides fill in the system design round.
6 to 7 rounds
Screen
2 roundsRecruiter chat
Your background, what you are looking for and which team might fit. Cash App's 2025 guide asked candidates to be open about what excites them so recruiting could match them to a team.
Tips for this round
- Say which products and problems interest you so the recruiter can match you to a team.
- Ask what AI use is permitted in each stage of your process.
Technical pairing interview
Live pairing with an engineer on a multi-part problem, in the language of your choice. Cash App's 2025 guide allowed internet use, encouraged running code every couple of minutes and said compiler errors cost nothing.
Take-home
1 roundTake-home project (some mobile roles, instead of the pairing screen)
Build a small mobile app to a spec. Cash App's 2025 mobile guide said it was reviewed for architecture, UI craft, testing and how well you followed the spec.
Tips for this round
- Follow the spec closely; it was part of the review.
- Structure the app so you can add features to it in the onsite.
Onsite
3 roundsVirtual onsite: coding
More pairing problems like the screen. Take-home candidates instead extend their own project with new features.
Tips for this round
- Write code you would ship: clean names, no leftover experiments, tests where they help.
- Treat the interviewer as a partner who may give hints or join in the code.
Virtual onsite: system design
Architecture for the business unit you are joining. Candidate guides mention prompts such as peer-to-peer payments or an offline-first point of sale. In Cash App's 2025 mobile loop, design was folded into the behavioral interviews.
Virtual onsite: behavioral and past experience
Past projects, cross-functional work, how you like to work, mentoring and technical leadership. Block says some candidates also meet several hiring managers and leaders.
Tips to Stand Out
- Cash App's 2025 pairing guide said to code in the language you know best and to know its standard library well.
- Talk through your thinking, since the pairing interview was described as a check on what you are like as a teammate.
- Break the problem up and run your code every couple of minutes; the 2025 guide said compiler errors cost nothing and print debugging is fine.
- Treat the code as production code: remove abandoned ideas, avoid unused variables and explain any shortcut you take.
- Ask clarifying questions about what the problem needs, and if you ask how to solve it, bring your own options to discuss.
- Bring several project stories with your own contribution spelled out, and be ready to say why Block and why Square or Cash App.
Common Reasons Candidates Don't Pass
- ✗Block says work that does not reflect a candidate's own skills, such as AI substitutes, may not be considered.
- ✗A candidate report on a senior Cash App loop said the behavioral round was the hardest part, with probing in several directions.
- ✗Candidate guides say candidates struggle when they ignore the existing code's patterns in multi-part tasks or cannot justify data structure choices.
- ✗Candidate guides flag generic system design that ignores the business unit, such as hand-waving on payment rails or fraud.
Based on Block's own pages and candidate reports.
Block does not publish a timeline, though its postings say US roles stay open about 55 days on average. People make every hiring decision, with AI summaries and scorecard support, according to Block. Last reviewed October 2026.
What is different at Block
- Pair programming as the core format. Cash App's 2025 guides described live pairing in your own language with internet use allowed, frequent code runs and print debugging viewed positively. It is closer to a work session than a closed-book quiz.
- Written AI rules for candidates. Some roles have assessments that involve AI tools, live copy-paste from AI is banned unless allowed, take-home work may use AI the way you would at work if the instructions allow it, and personal recording or transcription tools are never allowed.
- AI fluency in the rubric. Block's engineering lead said at its 2025 investor day that AI fluency was added to the job ladder and interview rubrics, and software engineer postings ask you to use AI tools while checking their output.
- One board, many brands. Square, Cash App, Afterpay, TIDAL, Bitkey, Proto and Block platform teams hire on the same board, so the domain (payments, banking, taxes or bitcoin) depends on the team.
- A take-home option for some mobile roles. Cash App's 2025 mobile guide let candidates choose a take-home app over the live screen, then extend that app in the onsite.
- Payments experience is usually optional. Cash App's 2025 guide said most backend roles did not need it, but some payments teams make it a hard requirement.
Block software engineer interview questions
Coding problems from our bank tagged to Block, then design, fundamentals and behavioral prompts we wrote for this guide.
Coding problems from our bank
From the DataInterview coding bank: the problems tagged to Block first, then classic problems on the topics most loops cover. Open one to solve it in the code editor.
Fix Broken Idempotency Check
Fix Broken Revenue Reconciliation
Data Reconciliation Checker
Two Sum
Valid Parentheses
Insert Interval
System design practice
Practice prompts we wrote around Block's products. They are not reported interview questions. Each answer is an outline of what a strong answer covers.
Design peer-to-peer payments for a consumer money app, where one user sends money to another by username.
Sample Answer
Clarify volume, latency, funding sources (balance, debit card) and limits. Accept each request with an idempotency key, run risk checks, then record the transfer as balanced entries in a ledger in one transaction. Notify both users after the ledger commits, through an event stream, so the money movement never depends on a notification succeeding. Discuss retries when the card network times out, reversals, and how to rebuild any balance from the ledger. A weak answer updates two balance columns with no audit trail.
Design card acquiring for a seller payments platform that processes card payments across several brands.
Design a reconciliation service that matches card network settlement files against internal payment records.
Design an offline-first point of sale app that keeps taking payments when the network drops.
Design an LLM-based financial assistant inside a consumer money app, including how bugs get fixed.
Fundamentals practice
Concept questions on the topics Block's rounds lean on, with short model answers. We wrote these for practice.
What is an idempotency key and why do payment APIs need one?
Sample Answer
It is a unique ID the client sends with a request. The server stores the key with the result, and a retry with the same key returns the stored result instead of charging again. It matters because networks time out, and the client cannot tell whether the first request went through. Reusing a key with a different payload should be rejected.
Why store money as integer minor units instead of floating point?
What is double-entry bookkeeping in a payments ledger?
How do you change a Protocol Buffers message without breaking older clients?
Behavioral practice
Practice prompts we wrote for the behavioral rounds. They are not reported interview questions.
Tell me about a project you led from problem framing to rollout and operation.
Sample Answer
Block postings describe owning work through testing, rollout and on-call. Cover the problem, your own decisions, how you validated the result and what operating it taught you.
Describe a time you worked with non-engineers to turn complex rules into software.
Tell me about a time you used AI tools and had to catch a mistake in their output.
Walk me through an incident you were part of and what changed after it.
Why Block, and why Square or Cash App in particular?
Practice problem: idempotent transfers
pythonA payments service receives transfer requests as (key, sender, receiver, amount) tuples, with amounts in cents. Starting from a dict of balances (missing accounts have 0), process the requests in order and return (statuses, final_balances). A request with a new key moves the money and returns "ok" if the sender has at least the amount, otherwise it changes nothing and returns "declined". A request whose key was seen before changes nothing: it returns the first request's status if the sender, receiver and amount match, and "conflict" if they differ. Example: balances {'ann': 500}, requests [('k1', 'ann', 'bo', 300), ('k1', 'ann', 'bo', 300), ('k2', 'ann', 'bo', 300), ('k2', 'ann', 'cy', 300)] returns (['ok', 'ok', 'declined', 'conflict'], {'ann': 200, 'bo': 300}).
1from typing import Dict, List, Tuple
2
3def process_transfers(balances: Dict[str, int],
4 requests: List[Tuple[str, str, str, int]]) -> Tuple[List[str], Dict[str, int]]:
5 """Return (statuses, final_balances) after processing requests in order."""
6 pass700+ coding problems with a live code executor.
Practice in the EngineHow to prepare
A plan for the Block loop, most important first:
- Practice multi-part pairing problems in the language you know best, running code often and talking through each step with a partner.
- Know your language's standard library and testing tools well, since Cash App's 2025 guide stressed using them in the pairing interview.
- Ask your recruiter which stages allow AI tools, and read Block's AI hiring principles before the first interview.
- Practice system design for payments problems: idempotent transfers, ledgers, card acquiring, reconciliation and offline payments.
- Prepare several project stories with your own contribution clear, and rehearse them on someone with no context to catch jargon.
- Pick the brand and team you want (Square, Cash App or a Block platform team) and prepare a business or technical reason for it.
Practice path
Courses that cover the rounds above:
Are you ready for the Block software engineer interview?
1 / 7Can you solve a medium problem (graphs, intervals, heaps or sliding window) in about 25 minutes while explaining your approach?
Frequently Asked Questions
How many rounds is the Block software engineer interview?
Cash App's interview guides, as published in 2025 and since taken down, describe a recruiter chat, a 60-minute pairing screen and a virtual onsite. For mobile roles the onsite was 2 coding plus 2 to 3 behavioral interviews depending on level. Candidate guides describe 4 to 6 onsite rounds including system design. The current loop may differ, so ask your recruiter.
Can I use AI in a Block interview?
Only as Block allows. Block's AI hiring principles say some roles have assessments that involve AI tools, and your recruiter says what is permitted. Pasting AI output into a live chat, shared document or technical exercise is not allowed unless the interviewer or recruiter says so. You may use AI to prepare, and people make every hiring decision.
Are Block interviews recorded?
They can be. Block says it records interviews only with its own recording tool and you can opt out. Personal recording or transcription tools are never allowed.
What is the Block pairing interview like?
In Cash App's 2025 guide it was a 60-minute live pairing session with an engineer on a multi-part problem, in your own language. Internet use was allowed, compiler errors did not count against you, and the interviewer often asked afterward whether the problem could be solved another way.
How much do Block software engineers make?
Zone A postings in October 2026 printed starting base pay of $142K to $213K (Square, Reconciliation and Reporting), $180K to $270K for three Cash App Software Engineer roles, $217.8K to $326.8K for the Senior band and $263.6K to $395.4K for Staff. Block's benefits page says every employee gets equity.
What are the software engineer levels at Block?
Block's postings state no level code. Titles run Software Engineer, Senior Software Engineer and Staff Software Engineer, asking for about 3+, 5+ and 10+ years. No entry-level US software engineer posting was open in October 2026.
Can Block engineers work remotely?
Often. Block lets employees choose home, office or hybrid unless a role needs a specific location or time zone, and offers up to 45 days a year of international work. Some postings are still marked not open to remote.




