Went through Chime's final round loop earlier this year for a senior SWE role, backend/platform track. All virtual. Sharing the shape of it because the prep I found online was outdated.
Number of rounds: five interviews across two days. One hour each.
What they covered: Coding #1: Medium-difficulty algorithm problem. Classic interview fare. I got a dynamic programming variant that was approachable if you've done a few DP problems. They want you to think out loud. Getting to optimal solution matters but the path there is scored too. Coding #2: More practical, closer to a real engineering task. Mine involved designing a data structure for a simple use case and then extending it. This felt more representative of actual work. System design: Distributed systems flavor. I was asked to design a payment processing pipeline with reliability and idempotency requirements. Makes sense for Chime. Brush up on: message queues, retry semantics, exactly-once delivery, graceful degradation. They asked specific questions about failure modes. Behavioral: Two interviewers in this round, which was unusual. Lots of leadership-style questions even for an IC role. They care about how you handle conflict, how you communicate technical decisions to non-engineers, and what you've shipped end-to-end. Hiring manager chat: More conversational. They explained the team, asked what I was optimizing for in my next role, gave space for my questions. Not secretly scored on coding but definitely matters for culture fit signal.
Debrief timeline: I got feedback 8 days after the final round. That felt long but wasn't a rejection signal, they just move carefully on leveling decisions.
Overall it was a fair, well-organized loop. Not FAANG-hard, but not a checkbox exercise either.