Remitly Software Engineer Interview Guide

Remitly Software Engineer candidates describe a process where coding carries the most weight, with behavioral and design conversations filling out the rest. The most recent technical screen on record began with a log-parsing problem that could be solved in a few lines of Python, then became a harder version in which records arrive from an event stream. The follow-up was mostly about time and space complexity, and why a streaming approach keeps memory bounded. That candidate was told the later coding rounds lean toward real-world engineering scenarios. It is worth practicing quick parsing logic and problems where you cannot hold the whole input at once.

The shape of the loop varies by account. One candidate started with a recruiter call. Next came a timed 60-minute online assessment with SQL and Python questions, then live coding with three to four LeetCode-style problems of easy to medium difficulty in about an hour. Another described a technical exercise followed by four one-hour live coding interviews. Others mention a coding round on Coderpad, system design discussions and object-oriented design questions. One candidate found a coding problem ambiguous: it had to pass specific test cases without following an obvious pattern. Asking clarifying questions early can help.

Behavioral questions show up throughout. Reported topics include disagreeing with coworkers, handling multiple urgent assignments, developing teammates, understanding customer needs and keeping systems running smoothly as they scale. One candidate was also asked about money laundering and what that process entails. Several candidates mention slow scheduling or little follow-up, so keep track of next steps yourself and prepare stories with a clear result.