Remitly interview notes, page 1 of 2

“I started with the obvious classes and felt okay until they pushed on concurrency.” The rest of the author's notes on Software Engineer interview at Remitly, Onsite - System Design / Architecture round, covers how they worked through the question, what the panel pushed back on, and what they would do differently.

“This one sounds straightforward but I think a lot of people trip up by spending too long on what the original plan was instead of getting to the pivot.” The rest of the author's notes on Software Engineer interview at Remitly, Onsite - Behavioral / Leadership round, covers how they worked through the question, what the panel pushed back on, and what they would do differently.

“This is a meaty question and I underestimated how much they wanted the full arc, not just the happy path.” The rest of the author's notes on Product Manager interview at Remitly, Hiring Manager Screen round, covers how they worked through the question, what the panel pushed back on, and what they would do differently.

“Pretty open-ended and I kind of rambled.” The rest of the author's notes on Product Manager interview at Remitly, Hiring Manager Screen round, covers how they worked through the question, what the panel pushed back on, and what they would do differently.

“This question sounds scoped but it really isn't.” The rest of the author's notes on Software Engineer interview at Remitly, Onsite - System Design / Architecture round, covers how they worked through the question, what the panel pushed back on, and what they would do differently.

“I knew this problem from practice so I wasn't totally lost, but minimum transfers is where I slowed down.” The rest of the author's notes on Software Engineer interview at Remitly, Technical Phone Screen round, covers how they worked through the question, what the panel pushed back on, and what they would do differently.

“My first instinct was to just pair up positives and negatives greedily, which actually works fine for correctness.” The rest of the author's notes on Software Engineer interview at Remitly, Technical Phone Screen round, covers how they worked through the question, what the panel pushed back on, and what they would do differently.

“I kept treating this like a regular behavioral round and I think that was a mistake.” The rest of the author's notes on Software Engineer interview at Remitly, Onsite - Multi Round round, covers how they worked through the question, what the panel pushed back on, and what they would do differently.

“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.” The rest of the author's notes on Software Engineer interview at Remitly, Onsite - Behavioral / Leadership round, covers how they worked through the question, what the panel pushed back on, and what they would do differently.

“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.” The rest of the author's notes on Software Engineer interview at Remitly, Onsite - System Design / Architecture round, covers how they worked through the question, what the panel pushed back on, and what they would do differently.