Remitly Software Engineer interview with a disputed coding solution

Remitly·Software Engineer·Reported Oct 2022
Technical ScreenOtherNo responseMedium

After a recruiter reached out, I entered the process with a decent amount of momentum. I had one technical interview that combined Q&A with a whiteboard-style coding task. The conceptual part focused on DSA and time complexity. Even when the conversation became tense, I felt I understood what they were asking me to do.

The process then moved into the loop. One technical interviewer kept insisting that my solution was wrong but couldn't produce a test case to contradict it. When I later validated my approach, it turned out to be correct. The technical interviews combined coding with light behavioral check-ins, and the interactions with people were generally pretty chill. I had a strong feeling the interviews were going well, so the result surprised me.

The hardest part wasn't the technical work. It was the silence afterward. The recruiter ghosted me instead of sending a clear rejection or feedback. I really wanted to work there, and I left feeling fairly confident. That lack of closure made the whole process feel unfair.

Location: Manila, Manila. Overall feedback: Negative. 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 → Other
Outcome
No response
Difficulty
Medium
Date
Reported Oct 2022

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