Remitly Software Engineer interview questions

9 Software Engineers have shared notes from their Remitly interviews, with the questions they were asked in each round. That is 75% of the 12 Remitly interview notes on Screna AI.

9 Software Engineer interview notes

Remitly·Software Engineer·Onsite - System Design / Architecture

Jul 2026
System design round at Remitly where they had me whiteboard a full past project from scratch. Pretty intense scope for a single session, covering everything from architecture to post-mortems.
  • Walk through the end-to-end architecture of a project you led. Cover the major components, how data flows through the system, your storage decisions, and any external dependencies you had to manage.
  • What were the key trade-offs in your design? For example, how did you think about consistency versus availability, or latency versus cost?
  • How did you handle scaling and failure recovery in this system?
  • How did you test, monitor, and iterate on the design over time?
  • If you were rebuilding this system from scratch today, what would you change?

“I picked a project I knew well but I think I front-loaded too much on the happy path and they had to keep nudging me toward the failure cases.”

View Post

Remitly·Software Engineer·Onsite - System Design / Architecture

Jun 2026
System design round at Remitly focused entirely on geospatial search. Pretty niche compared to the usual distributed systems stuff I'd prepped for, but it was a solid problem with a lot of moving parts once you dig in.
  • Given a set of geographic coordinates and a query point, design a system to return the k nearest locations. Walk through how you'd compute distances, what data structures or indexes you'd use, and how you'd handle scale.

“I started with Haversine for great-circle distance which was fine, but I fumbled a bit when they pushed on edge cases like antimeridian crossings.”

View Post

Remitly·Software Engineer·Onsite - Behavioral / Leadership

Jun 2026
Behavioral round at Remitly for a software engineer role. Two questions, both pretty standard delivery and adaptability territory. Nothing too surprising but worth prepping concrete stories for.
  • What specific habits or processes do you use to make sure a project stays on schedule?
  • Tell me about a time you had to change your approach mid-project to get it across the finish line.

“They wanted concrete mechanics, not just 'I communicate with stakeholders.' I talked about breaking work into smaller checkpoints and flagging blockers early, but I fumbled a bit when they pushed on what I actually do when a deadline starts slipping.”

View Post

Remitly·Software Engineer·Onsite - Multi Round

Jun 2026
Remitly's onsite for a software engineer role has four rounds: two coding, one system design, and a 'PM partnership' round that I wasn't totally sure how to prep for going in.
  • How does a 'PM partnership' interview differ from a standard behavioral interview, and what should you expect from it?
  • What specific competencies are evaluated when it comes to collaborating with product managers and other cross-functional partners?
  • How should you structure and prepare answers for a PM partnership round as a software engineer?

“I kept treating this like a regular behavioral round and I think that was a mistake.”

View Post

Remitly·Software Engineer·Technical Phone Screen

Jun 2026
Interviewed for a software engineering role at Remitly and got a coding problem that felt deceptively simple at first glance. The core challenge was about settling debts between accounts, which is the kind of thing you'd expect from a fintech company.
  • Given a map of account IDs to net balances (positive means owed money, negative means owes money, and the sum is guaranteed to be zero), produce a minimal list of transfers that settles all accounts to zero. Each transfer is a tuple of (sender, receiver, amount).

“My first instinct was to just pair up positives and negatives greedily, which actually works fine for correctness.”

View Post

Remitly·Software Engineer·Technical Phone Screen

Jun 2026
Remitly threw a classic debt-settlement problem at me, basically the same idea as LC 465. It was a coding round and the problem itself is well-known but getting to a minimum-transfer solution under pressure is a different thing.
  • Given a set of transactions or a map of accounts to net balances, write a function that produces the minimum number of transfers needed to settle all debts.

“I knew this problem from practice so I wasn't totally lost, but minimum transfers is where I slowed down.”

View Post

Remitly·Software Engineer·Onsite - System Design / Architecture

Jun 2026
System design round at Remitly for a software engineer role. The whole thing was basically one big URL shortener question but they expected you to go several layers deep across a lot of dimensions, not just sketch a box diagram and call it done.
  • Design a production-ready URL shortening service, covering the public API, database schema, ID generation with collision avoidance, caching strategy, partitioning and replication, rate limiting, analytics, TTL cleanup, high availability, and trade-offs under different traffic patterns.

“This question sounds scoped but it really isn't.”

View Post

Remitly·Software Engineer·Onsite - Behavioral / Leadership

May 2026
Behavioral question from Remitly, looks like it was for a mid-to-senior level role. Just the one question shared, but it's a meaty one about pivoting mid-project.
  • Tell me about a project where the original approach wasn't working. What made you realize it, what other options did you consider, and how did it turn out?

“This one sounds straightforward but I think a lot of people trip up by spending too long on what the original plan was instead of getting to the pivot.”

View Post

Remitly·Software Engineer·Onsite - System Design / Architecture

May 2026
System design round at Remitly for a software engineering role. The whole session was basically one big elevator question that kept branching into scheduling algorithms, concurrency, and multi-elevator scaling. Dense but kind of interesting if you're into that stuff.
  • Design an object-oriented elevator system. Walk through the core classes and interfaces you'd define (elevator, controller, request, floor, buttons, sensors), how they interact, and how you'd handle concurrency and faults.
  • Given pending requests for floors [1, 99, 2], how does your scheduler guarantee stopping at floor 2 before floor 99, using only a single internal queue? Describe the queue operations, tie-breaking rules, and the time and space complexity.
  • Propose a scheduling algorithm for the elevator system that optimizes for both travel time and fairness across requests.
  • How does your design scale to multiple elevators, and how would you support peak traffic modes?

“I started with the obvious classes and felt okay until they pushed on concurrency.”

View Post