What Is the Square Android Staff Engineer Interview Process Like?

Square is part of Block, and recruiters use both names. Candidates report a practical loop: a recruiter call, a technical screen, then several onsite rounds. Square's own developer blog describes its pairing round as writing and running real code with the interviewer.

Block does not publish a fixed Android loop. Treat any round count you read online as reported, not promised. The subject matter is far more certain, because Square's product is taking payments on a device.

Quick Overview

Square publishes advice for the pairing round itself. Everything about the wider loop comes from candidate reports, and it varies by team.

Square and Block Are the Same Company

Square is the seller business inside Block. Block also owns Cash App. Job boards list staff Android roles under both names, so search for both.

Recent Block postings named staff Android roles on Square Retail, Square Food and Beverage, Square Banking, and Cash App. Those postings ask for Kotlin and Jetpack Compose. Several also name Workflow, a state machine library that Square released as open source.

What Square's Own Blog Says About Pairing

Square's developer blog gives direct advice about the pairing round. You and the interviewer write and run code together in under an hour. It tells you to use the language and tools you know best.

Two more points from that post matter. Looking things up during the round is allowed. And a finished working solution beats a clever unfinished one.

The Android Design Question Is About Taking Money

Square accepts card payments on a phone or on a small dedicated device. That creates one hard client problem. A card is tapped, the network is gone, and the money must still be correct.

Square documents this feature in public. Offline mode lets a seller take card payments with no connection. Those payments are sent once the device reconnects.

Two details from Square's developer documents shape a strong answer. An offline payment has no server transaction id yet, so the client carries its own client transaction id. Square's payment API also takes an idempotency key, which is a unique string that stops one payment being charged twice.

So design the write path first. Every tap writes a record to a local database before anything else. A background worker sends the stored records when the network returns.

Then say what the seller sees. Square's documents say an offline payment can be declined if it is not processed within 24 hours. So the app must show pending payments, show the total value held offline, and cap that total.

Square Runs Android on Its Own Hardware

One Square staff posting described an Android Platform Apps team. That team builds system apps and services for Square's own Android devices. The posting named AOSP, the Android Open Source Project, as useful experience.

This changes the constraints worth naming out loud. The app may run all day on a fixed device with a card reader attached. Heat, long running processes, and device setup matter more than they do on a phone.

What Staff Adds Over Senior

A senior answer designs the offline queue and names what breaks. A staff answer sets the boundaries and plans the release.

Block's staff postings describe leading architecture, building shared components, and aligning other teams. Bring that into the round. Say who owns the payment queue module, and what its public interface is.

Then cover shipping. An app release cannot be rolled back like a server deploy. So put offline mode behind a feature flag, release it in stages, and keep a server switch that turns it off.

Finish with the cost of owning it. Name the metric for payments stuck in the queue. Name the alert, and name who is called when it fires.

How to Prepare

• Prepare the client design work. Grokking Modern Mobile System Design Interview covers payment flows, writes that must never apply twice, and offline queues as worked case studies.
• Practice writing code while you talk. The pairing round rewards clear narration and a working result. Grokking the Coding Interview drills the patterns behind most practical screens.
• Learn the offline write path until it is automatic. Local database, queue, client generated id, idempotency key, retry with backoff. What Is the Android System Design Interview Like? covers the structure this round expects.
• Read Square's public developer documents. The offline payments and idempotency pages are short, and they are the real source.
• Add the server side as background. Grokking the System Design Interview teaches the server design, which is useful background when the question reaches the API.
• Compare loops before you commit. Monzo publishes its mobile process in full, and Delivery Hero publishes its stages.
• Study the question families. See What Questions Are Asked in a Mobile System Design Interview? and this list of mobile system design interview questions.