Remitly Software Engineer interview with a high-frequency banking prompt

Remitly·Software Engineer·Reported Apr 2026
Technical ScreenHard

My first step was an early technical prompt that was much broader than I expected for an initial stage. I had to build something like a high-frequency banking system from scratch, which meant thinking beyond one algorithm and covering the moving parts end to end. It was comprehensive, but once I broke the problem down, I could see a way through it.

The next round was a live interview with behavioral and coding components. The coding portion didn't match the frontend expectation I'd been given. Instead, it focused heavily on DSA and then escalated into a hard LeetCode-style challenge. The technical bar felt real, and so did the time pressure.

If I had passed that stage, the process would have continued with several longer interviews, including multiple coding rounds, system design, and meetings with product and a hiring manager. The early rounds felt like they were filtering for someone who could handle that level of depth and pace. I didn't receive an offer, but the experience made it clear how demanding the later onsite would have been.

Location: Warsaw, Masovia. Overall feedback: Positive. Offer status: No offer.

Published

Curated and edited by PracHub

Discussion

Sign in to join the discussion. The author is notified of every comment.

Loading comments…

Interview at a glance

Company
Remitly
Role
Software Engineer
Rounds
Technical Screen
Difficulty
Hard
Date
Reported Apr 2026

Real Remitly interview experiences

First-hand reports from Remitly candidates — the rounds, the questions they were asked, and how it went.

All 9 Remitly interview experiences