Block · Primly Community

Went through the Cash App backend loop last month, here's the breakdown

backend_bekah · 4 replies

Just finished my loop for a senior backend role on Cash App's money movement team. Sharing notes while they're fresh.

Rounds: Recruiter screen: 30 min, pretty standard. She was direct about timeline and comp range upfront, which I appreciated. Technical phone screen: 45 min, one coding problem (graph traversal, medium difficulty), plus 10 min at the end about a past system I built. Onsite: 5 rounds over two days. Two coding, one system design, one behavioral, one cross-functional with a PM.

The system design round was specifically about payments infrastructure. Like, they literally asked me to design a money transfer system that handles double-spend prevention. If you're coming from non-fintech you should spend real time on idempotency keys and distributed transactions before you go in.

The behavioral round surprised me. The interviewer had clearly read my resume. Questions were specific to my actual work history, not generic. She asked me to walk through a time I had to push back on a product decision, and then kept drilling in for specifics. No softball "tell me your strengths" stuff.

The cross-functional PM round was a 30 min product sense conversation. Not a case interview but they want to see you can think like a stakeholder. I almost blew this by being too technical.

Did not get an offer in the end (leveling mismatch, recruiter said). But the process itself was one of the cleaner ones I've been through this year.

4 replies

corp_refugee

the leveling mismatch thing at Block is real. they under-level almost everyone going in and then "level you up" if you crush it. it's a negotiating tactic, not an accident. ask your recruiter for a firm level range before you agree to the onsite.

backend_bekah

yeah looking back I should have pushed on that. recruiter said "we'll assess during the loop" which I now know is code for 'we'll figure out how little we can offer you.'

de_derek

the idempotency angle comes up in data infra interviews there too. they care a lot about exactly-once semantics in pipelines because money. if you're interviewing for anything adjacent to payments, practice talking about how you'd handle duplicate events.

tired_recruiter

the PM round catching you off guard is super common at fintech companies. they add it to the loop because there's so much cross-functional dependency in payments products. worth doing at least one mock where you practice explaining technical tradeoffs to a non-technical audience.