To stand out in the Remitly hiring process, you must prepare holistically. Technical brilliance alone is rarely enough; candidates are consistently evaluated on how they communicate, structure their thoughts, and align with the company's operating principles.

Technical Execution & Clean Code – You must write readable, maintainable code in your language of choice. Interviewers evaluate your naming conventions, modular design, handling of edge cases, and ability to write unit tests. Avoid over-complicating solutions; start with a working baseline and iterate.

System Design & Trade-off Analysis – When designing systems, avoid throwing buzzwords at the problem. You must justify every architectural choice, whether selecting a relational database over NoSQL, or choosing synchronous over asynchronous processing. Focus heavily on data consistency, failure modes, and system bottlenecks.

Product & Customer Empathy – Remitly engineers must understand the business context of their technical decisions. Be prepared to discuss how your past technical work improved the user experience, reduced transaction failures, or drove business metrics.

Cultural Alignment & Values – Study Remitly's core values before your loop. Be ready to demonstrate accountability, a bias for action, direct communication, and customer obsession. Frame your behavioral answers using the STAR method (Situation, Task, Action, Result) to keep your responses structured and impactful.

The interview loop for a Software Engineer at Remitly is structured to assess both your technical capabilities and your collaborative working style. The process typically spans three main stages: the initial recruiter screen, a technical assessment or phone screen, and a comprehensive virtual onsite loop often referred to as the Power Day.

While the exact steps can vary slightly by geographic location and team—for instance, European offices often utilize a take-home assignment, while North American teams lean toward live coding screens—the overall evaluation standards remain highly consistent. The company aims to simulate real-world working conditions, meaning you will often pair-program, discuss architectural trade-offs, and deep-dive into your past projects.

The visual timeline above outlines the typical progression from your initial application to the final decision. Candidates should use this sequence to pace their preparation, ensuring they master foundational coding before diving into complex system design and behavioral framing. Be aware that the transition between the technical screen and the onsite loop requires a shift from rapid problem-solving to high-level systemic thinking.

To pass the bar at Remitly, you must demonstrate competency across several distinct evaluation areas. Each round in the loop is mapped to specific competencies, and your interviewers will look for concrete evidence of your skills in these domains.

Coding & Problem Solving (Algorithms & DSA)

This area evaluates your ability to translate logical thinking into syntax. You will be expected to solve algorithmic challenges under the guidance of one or two engineers. The focus is less on memorizing obscure dynamic programming tricks and more on your approach to structured problem-solving.

Be ready to go over:

• Data structure selection – Knowing when to use maps, sets, queues, or trees to optimize time and space complexity.
• Complexity analysis – Articulating the Big-O time and space complexity of your solution immediately after writing it.
• Edge case handling – Proactively identifying null inputs, empty collections, integer overflows, and boundary conditions.
• Advanced concepts (less common) – Graph traversals (DFS/BFS), trie implementations, and sliding window optimizations.

Example scenarios:

• "Given an input stream of currency transfer requests, identify duplicate transactions submitted within a five-second window."
• "Write an algorithm to find the shortest path for routing money through a network of intermediary banks."

System Design & Architecture

In this round, you will partner with a senior or staff engineer to design a large-scale system. You are expected to lead the conversation, gather requirements, define API contracts, and map out the high-level architecture.

Be ready to go over:

• Scalability patterns – Horizontal scaling, load balancing, caching strategies, and database sharding.
• Data consistency models – Understanding ACID properties versus eventual consistency, especially in financial ledger systems.
• Resiliency and fault tolerance – Implementing retries, exponential backoff, circuit breakers, and dead-letter queues.
• Advanced concepts (less common) – Event sourcing, CQRS patterns, and distributed transaction management (Saga pattern).

Example scenarios:

• "Design a real-time transaction monitoring dashboard that processes thousands of events per second with sub-second latency."
• "Architect a system that manages dynamic payout corridors, adjusting fees in real-time based on currency volatility and liquidity."

Object-Oriented & Practical Design

This evaluation area tests your ability to write clean, maintainable, and extensible code. Unlike pure algorithmic rounds, the focus here is on software craftsmanship, design patterns, and your ability to refactor code as requirements evolve.

Be ready to go over:

• SOLID principles – Demonstrating clean class design, single responsibilities, and interface segregation.
• Design patterns – Applying factory, strategy, observer, or decorator patterns where appropriate.
• Refactoring under change – Showing how your initial design can easily accommodate new, unexpected requirements.

Example scenarios:

• "Design a class structure for a promotional discount engine that supports flat-rate, percentage, and regional discount rules."
• "Create an extensible framework for processing different payment methods (credit cards, bank transfers, mobile wallets) with unique validation steps."

Behavioral & Cultural Fit (Core Values)

This round assesses how you work, resolve conflict, and align with Remitly's operating principles. Expect deep dives into your resume and past projects. Interviewers will push past high-level summaries to understand your specific contributions and decision-making processes.

Be ready to go over:

• STAR method delivery – Structuring your answers with clear context, specific actions you took, and measurable results.
• Ownership and accountability – Demonstrating times you took responsibility for a failure or drove a project to completion against obstacles.
• Constructive disagreement – Showing how you handle professional conflict with data, empathy, and respect.

Example scenarios:

• "Tell me about a time you had to deliver a critical feature on a tight deadline while inheriting a highly unstable codebase."
• "Describe a situation where you realized a technical decision you made was wrong. How did you identify the error and pivot?"

As a Software Engineer at Remitly, your day-to-day work extends far beyond writing code. You will own features from conceptual design through deployment, monitoring, and maintenance.

• System Ownership – You will design, build, and maintain highly reliable microservices that handle financial transactions, user data, and compliance checks globally.
• Cross-Functional Collaboration – You will partner closely with Product Managers, UX Designers, Security Engineers, and Operations teams to translate customer needs into robust technical specifications.
• Technical Mentorship – Senior and staff-level engineers are expected to mentor junior team members, conduct thorough code reviews, and drive engineering excellence across the organization.
• Operational Excellence – You will participate in on-call rotations, monitor service health dashboards, write post-mortems for system incidents, and continuously work to reduce technical debt.
• Strategic Influence – You will help define the technical roadmap for your team, identifying areas where architectural refactoring or new technologies can unlock product velocity and scale.