Block (Square) Frontend Interview
What frontend candidates typically face at Block (Square) — fintech UI, coding quality, design, and prep. Composite/unofficial.
- interview-experience
- block
- square
Composite, unofficial guidance based on publicly shared candidate reports and common Block (Square, Cash App, Afterpay, TIDAL-adjacent, etc.) hiring patterns for frontend roles. Ecosystems differ by business unit — confirm with your recruiter. Not affiliated with Block.
Typical loop
| Stage | Focus | Format |
|---|---|---|
| Recruiter | Role, BU | Call |
| Technical screen | Coding | Shared editor |
| Onsite / virtual loop | Coding, design, behavioral / values | 4–5 interviews |
| Decision | Packet | Internal |
Block products touch money and trust. Frontend design should emphasize clarity, error recovery, and accessibility — not only visual polish.
Coding rounds
Solid medium DSA; high bar for correctness:
- Arrays, hashes, graphs
- Parsing / state-heavy exercises
- Clean tests and edge cases
Practice: Two Sum, Valid Parentheses, Binary Search, Merge Intervals, LRU Cache.
Frontend focus
- Payment / checkout style forms
- Seller dashboards and reporting charts (conceptual)
- Mobile-web performance
- Design systems and consistent craft
- a11y on critical money paths
Practice: Accessible Modal, Todo App, Autocomplete.
System design
- Seller home dashboard
- Payment flow UI (FE scope; PCI details stay high-level)
- Transaction history list with filters
- In-person vs online channel differences (conceptual)
Discuss: retry UX, idempotent submit buttons, offline failure messaging, security UX (XSS awareness — XSS).
Preparation plan (6–8 weeks)
- JS/TS + forms/a11y
- DSA timed
- Dashboard/checkout machine coding
- Design outlines
- Mocks + impact stories
Takeaways
- Fintech FE = correctness × trust UX × coding bar.
- Don’t invent backend PCI architecture unless asked.
- Confirm which Block company/team you’re interviewing for.