Remitly interview questions

Showing 1–11 of 11 results

• Behavioral Screen: Going Beyond Your Responsibility and a Time You FailedMedium

  Two behavioral questions from a software engineering technical screen: describe a time you went beyond your responsibility, and describe a time you failed. They test ownership, judgment about stepping outside your scope, candor about your own mistakes, and whether the lessons you learned changed your later behavior.

  RemitlySoftware EngineerBehavioral & LeadershipTechnical Screen
• Build a Transfer-Fee Comparison PrototypeMedium

  Design an extensible remittance fee-comparison engine that aggregates quotes across multiple providers, normalizes explicit fees and FX spreads, and gracefully surfaces provenance, staleness, and provider failures.

  RemitlyStaff AI-Native EngineerSystem DesignTechnical Screen
• Compute transfers to balance account debtsEasy

  This question evaluates a candidate's ability to convert per-account net balances into a set of transfers, testing algorithmic problem solving, data-structure manipulation, and correctness under conservation invariants in transactional systems.

  RemitlySoftware EngineerCoding & AlgorithmsTechnical Screen
• Describe how you prevent project delaysEasy

  This question evaluates a candidate's project management, leadership, risk mitigation, communication, and adaptability skills by probing methods for preventing delays and examples of changing approaches to complete work.

  RemitlySoftware EngineerBehavioral & LeadershipTechnical Screen
• Design a Production-Ready URL ShortenerHard

  This question evaluates competency in designing a scalable, reliable, and secure production URL shortening service, covering API design, link data modeling and analytics, ID/token generation, caching and read/write paths, partitioning/replication/consistency choices, rate limiting and abuse mitigation, TTL handling and cleanup, and HA/DR and monitoring. Commonly asked in system design interviews to probe architectural trade-offs for high-read consumer services, it belongs to the System Design domain and emphasizes practical application of distributed systems and operational concepts rather than only conceptual theory.

  RemitlySoftware EngineerSystem DesignOnsite
• Design an Elevator System and SchedulerMedium

  This question evaluates a candidate's object-oriented design and algorithmic scheduling competencies, focusing on concurrency control, fault tolerance, queue management, tie-breaking rules, and time/space complexity analysis within an elevator control system.

  RemitlySoftware EngineerCoding & AlgorithmsOnsite
• Design an IP Address Filtering ServiceEasy

  Design a low-latency service that allows or denies traffic using source or destination IP rules. Candidates must define conflict precedence, address normalization, versioned rollout, stale-state behavior, audit evidence, privacy-conscious logging, and safe rollback.

  RemitlySoftware EngineerSystem DesignOnsite
• How to prepare for a PM partnership roundEasy

  This question evaluates a software engineer's competency in cross-functional collaboration, communication with product managers, stakeholder alignment, prioritization, and trade-off reasoning when working with Product, Design, Data, QA, and other engineering teams.

  RemitlySoftware EngineerBehavioral & LeadershipTechnical Screen
• Solve k-Nearest Places by Latitude/LongitudeMedium

  This question evaluates geospatial algorithm and systems-design competencies, focusing on nearest-neighbor search, great-circle distance computation, spatial indexing, and runtime/memory trade-offs for scalable location queries.

  RemitlySoftware EngineerCoding & AlgorithmsOnsite
• Validate a Bijective Substitution CipherMedium

  Determine whether two printable ASCII strings form a valid one-to-one and onto (bijective) character substitution mapping.

  RemitlySoftware EngineerCoding & AlgorithmsOnsite
• Whiteboard and Deep Dive a Past ProjectHard

  This question evaluates a candidate's end-to-end system design skills, including architecture decomposition, trade-off analysis, data consistency choices, scalability and resiliency patterns, and integration of operational practices for a user-facing distributed service.

  RemitlySoftware EngineerSystem DesignOnsite