Remitly Software Engineer candidates describe a recruiter screen, coding rounds that range from LeetCode-style to streaming problems, and design and behavioral conversations. The loop varies by account.
$163K
Avg. Base Comp
$260K
Avg. Total Comp
Not reported
Typical Rounds
Not reported
Process Length
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.
Synthesized from 15 candidate reports by our editorial team.
Had an interview recently?
Share your experience. Unlock the full guide.
Real interview reports from people who went through the Remitly process.
The tech screen was the part that stuck with me most. The first question started deceptively simple: a log problem I could solve in about three lines of Python. Once that was done, the interviewer moved to a harder version where I had to parse log entries coming off an event stream, which meant thinking about processing records as they arrive rather than loading everything at once. It was clearly meant as an advanced problem, not just a warm-up, so I had to slow down and talk through my approach before writing code.
Most of the discussion after the code was about complexity. I was asked for the time and space cost of my solution, and then to consider how those costs change when the input is a continuous stream instead of a fixed list. Being able to explain why a streaming approach keeps memory bounded mattered more than producing a perfectly clever implementation.
As far as structure goes, I understood the full process to be an HR conversation, this technical screen, and then a four-round interview loop. The coding rounds were described to me as leaning toward real-world engineering scenarios, so the LeetCode-style problem I got may not be typical of the whole loop, though I'd prepare for it either way.
The process ended with a declined offer, so I can't speak to how the later rounds went from my own experience. The screen did give me a clear sense of what Remitly looks for: working code first, then the ability to reason out loud about scale and complexity. If you're preparing, get comfortable writing parsing logic quickly and practice describing your complexity in terms of both time and memory.
Prep tip from this candidate
Practice writing a quick parser for log lines, then extend it to handle a continuous event stream, and be ready to state time and space complexity for both versions. The screen moved from a trivial solution to a streaming problem, so the follow-up is where candidates get tested.
Share your own interview experience to unlock all reports, or subscribe for full access.
Sourced from candidate reports and verified by our team.
Topics based on recent interview experiences.
Featured question at Remitly
How would you answer when an interviewer asks why you applied to their company?
| Question | |
|---|---|
| 2nd Highest Salary | |
| Empty Neighborhoods | |
| Top Three Salaries | |
| Employee Salaries | |
| Closest SAT Scores | |
| Rolling Bank Transactions | |
| Top 5 Turnover Risk | |
| Subscription Overlap | |
| Payments Received | |
| Top 3 Users | |
| Total Spent on Products | |
| Size of Joins | |
| Merge Sorted Lists | |
| Last Transaction | |
| Like Tracker | |
| Find the First Non-Repeating Character in a String | |
| String Shift | |
| Google Maps Improvement | |
| Largest Salary by Department | |
| Find the Missing Number | |
| Scrambled Tickets | |
| Comments Histogram | |
| Bagging vs Boosting | |
| Get Top N Frequent Words | |
| Cumulative Distribution | |
| Minimum Change | |
| Maximum Profit | |
| P-value to a Layman | |
| Prime to N |
Synthesized from candidate reports. Individual experiences may vary.
Candidates describe an opening call with a recruiter or HR representative. Reports describe a short conversation about background and fit. Prepare a concise story about your experience and why Remitly.
Accounts differ here. One candidate took a timed 60-minute online assessment with SQL and Python questions, and found the platform's layout easy to misread. Another had a live tech screen that began with a log-parsing problem and moved to an event-stream version, with questions on time and space complexity. Practice explaining your approach before you write code.
Candidates report coding sessions of roughly an hour, some on Coderpad, with LeetCode-style problems from easy to medium. One described a more ambiguous problem that had to pass specific test cases without an obvious pattern. Expect complexity follow-ups, and ask clarifying questions early.
Two candidates mention system design in the later stages, and one mentions object-oriented design questions. One hiring manager asked how to improve systems or keep them running smoothly as they scale. Prepare to talk through scaling, reliability and trade-offs in plain terms.
Behavioral questions appear in dedicated conversations and inside technical rounds. Reported themes include disagreeing with coworkers, handling multiple urgent assignments, developing teammates, understanding customer needs and company values. One candidate interviewed with several different managers using the STAR format. Bring examples with a clear outcome.
