Katkat

Company

Square interview questions

5 practice questions in the style of Square's interviews, covering Coding & Algorithms, Behavioral & Leadership.

Questions5

1 easy3 medium1 hard

Your progress0/5

Square interview questions by the numbers

Last updated

Katkat has 5 Square interview questions. The largest topics are Coding & Algorithms (60%) and Behavioral & Leadership (40%). By difficulty: 20% easy, 60% medium and 20% hard. The most common round is Onsite (60%). Frequent concepts include Arrays, Geometry, Grid and Hash Maps.

Topics

Difficulty

  • Easy20% · 1
  • Medium60% · 3
  • Hard20% · 1

Interview rounds

  • Onsite60% · 3
  • Technical Screen40% · 2

Roles

  • Software Engineer100% · 5

Frequent concepts

  • Arrays20% · 1
  • Geometry20% · 1
  • Grid20% · 1
  • Hash Maps20% · 1

Most mentioned in interview experiences

  1. 1.Build a Trust-Aware BIN Database1 report
  2. 2.Explain an AI-Assisted Engineering Workflow You Can Defend1 report
  3. 3.Implement transaction network queries1 report
  4. 4.Lead a High-Leverage Project in a Regulated Legacy System1 report

Counted from 2 candidate interview experiences on Katkat. How we collect and count

Showing 1–5 of 5 results

  • Build a Trust-Aware BIN DatabaseMedium

    Build an in-memory card-prefix database that resolves brand and card type independently across overlapping writes. Practice combining longest-prefix matching with trust and recency rules while preserving omitted fields and supporting heavy lookup traffic.

    SquareSoftware EngineerCoding & AlgorithmsOnsite
  • Explain an AI-Assisted Engineering Workflow You Can DefendMedium

    Use one real project to explain the path from ambiguous requirements through design, implementation, launch, and maintenance, with AI assistance treated as a bounded tool. Show stakeholder alignment, decision trade-offs, independent verification, rejected output, and post-launch learning.

    SquareSoftware EngineerBehavioral & LeadershipOnsite
  • Implement transaction network queriesHard

    This question evaluates the ability to model and query dynamic graph connectivity and reachability for pairwise transactions, testing competencies in graph representation, dynamic data structures, and reachability queries within the Coding & Algorithms domain and emphasizing practical application of algorithmic concepts.

    SquareSoftware EngineerCoding & AlgorithmsTechnical Screen
  • Lead a High-Leverage Project in a Regulated Legacy SystemMedium

    Prepare a senior project deep dive spanning business leverage, personal ownership, delegation, architecture, migration, performance, reliability, and cost. Extend the analysis to regulated legacy systems where reconciliation, auditability, controlled rollout, and silent correctness failures matter.

    SquareSoftware EngineerBehavioral & LeadershipOnsite
  • List the Two-by-Two Blocks Covering Each Black CellEasy

    This problem tests your ability to navigate grid coordinates, implement range boundaries, and perform efficient dictionary-based data collection.

    SquareSoftware EngineerCoding & AlgorithmsTechnical Screen

Square interview experiences

All 2 →
  • Two Same-Day Screens Then SilenceSquare · Staff Software Engineer · Senior+ · Technical Screen · Apr 2026
    No response

    Giving back to the forum. I interviewed for a Staff SWE role at Cash App — two technical screens back to back on the same day (one coding, one called an "AI Native" screen), then a separate HM phone screen later. All three were remote. Coding: 60 min, CoderPad AI Native: 30 min HM phone screen: 30 min It's been almost two weeks since I finished and I haven't heard anything — I'm guessing the posi…

  • Passed the Screen, Then Lost the HeadcountSquare · Software Engineer · Technical Screen · Oct 2025
    In progress

    It seems like at this company the hiring manager only looks at your resume after you pass the phone screen. First I talked with the recruiter, and then right there on that call they said they'd schedule the phone screen — a one-hour coding round. The interviewer didn't waste any time either. After about 5 minutes of introducing ourselves, we went straight into the problem. It was written on Coder…

More companies