I applied through a recruiter. The process took 2 months. I interviewed at Remitly (Seattle, WA) in Sept 2022
Interview
Here was the process:
1 Recruiter Screen
1 Phone Screen - LC Medium/Hard
5 Onsite Interviews
Breakdown
3 - LC
1 - System Design
1 - Behavioral
Mostly LC Mediums and all tech loops had 1/2 behavioral questions.
**Experience**
Overall great people.
One tech interviewer kept on saying my solution is wrong but couldn't come with a test case to break my code. Tested my solution later it was correct.
Apart from that everyone was super chill to talk too. Really wanted to work there and I was feeling fairly confident after loops too but got ghosted.
Also, as echoed by many people here please don't ghost your candidates. Please give feedback to people who invested so much time in you. A simple "Improve Design" "Improve Problem solving"can help the candidates a lot.
Thank you for taking the time to write this review and we are so glad that you enjoyed meeting everyone at Remitly. I am very sorry you didn't hear back from the recruiter after your interviews were completed. We aim for a great candidate experience with every interview and it is clear we missed the mark here. If you'd like to chat further about what we can improve upon, please don't hesitate to reach out to your recruiting contact at Remitly.
Other Senior Software Engineer interview reviews for Remitly
I applied through a recruiter. The process took 8 weeks. I interviewed at Remitly (New Westminster, BC) in Sept 2025
Interview
Recruiter schedules, cancels, reschedules, cancels again. It's a chaos to get an interview in this company. It took more than six weeks to finally talk to the recruiter for the first time. Same experience in scheduling a technical interview. Then they disappear. No feedback, no rejection.
I applied through a recruiter. The process took 3 weeks. I interviewed at Remitly
Interview
Typical interview process: screening with HM, 3 technical interviews, another screening with the HM. Overall it was okay, except for the interviews with the HM. For the first one, he was late and hadn't seem to have read my resume, needing to read it as the meeting started. For the second one, he asked all the same questions he had a week or so before. He seemed unengaged and was asking such highly specific questions about solving their specific technical problems that it made me wonder if the listing is even real at all, especially given how old it was. In either case, he didn't communicate what he was asking well and I was frustrated that it seemed like he didn't understand what I was saying. All the other interviewers were top notch and well prepared.
Interview questions [1]
Question 1
Typical STAR questions (which by the way, always expect a certain answer, which is why they are widely considered poor and outdated practice). Don't ask "tell me a time when X" when X is not a usual thing most people will have experienced. You'll just get lies as responses! And no, you won't be able to tell!
Recruiter call, asked a bit about my experience and explained what the team is currently doing on. They are planning to expand in Vancouver seems like. After the call, didnt hear back from the recruiter. And after a while got a rejection email.
Interview questions [1]
Question 1
Basic Questions like what is your day to day job etc etc
