← Back to Directory

Remitly

Large Enterprises

Screna has 12 Remitly interview write-ups. The most reported round is the system design round (4).

12 interview notes · updated Jul 2026

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·Product Manager·Onsite - Product Sense / Strategy

Jun 2026
Interviewed for a PM role at Remitly. Just one question I can remember clearly, product strategy flavor, pretty standard but it made me think harder than expected.
  • How would you decide whether launching a new product is worth pursuing?

“I went straight into market sizing and kind of forgot to talk about internal feasibility for a bit.”

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·Product Manager·Hiring Manager Screen

Jun 2026
One question from what seemed like a PM screen at Remitly. Not much to go on but it's a classic product sense angle that trips people up if they haven't thought about it before.
  • How do you gather feedback from users?

“Pretty open-ended and I kind of rambled.”

View Post

Remitly·Product Manager·Hiring Manager Screen

May 2026
Remitly PM interview, one big behavioral question about keeping projects on track. Pretty much the whole conversation was built around one detailed scenario.
  • Walk me through how you keep a project on schedule. Cover how you scoped the work, identified and tracked risks, kept stakeholders in the loop, and adapted when things went sideways.

“This is a meaty question and I underestimated how much they wanted the full arc, not just the happy path.”

View Post