Remitly Business Analyst interviews, as three candidates describe them, mix SQL and statistics screens, analytics assignments, presentations, pricing and campaign cases, and value-based conversations. Two candidates did not get offers and one accepted.
$149K
Avg. Base Comp
$185K
Avg. Total Comp
4-6 rounds
Typical Rounds
60 days
Process Length
Three candidates describe Remitly Business Analyst interviews that differ in length and format, so treat them as three separate experiences rather than one fixed process. Two of the accounts suggest interviewers value a clear recommendation over a tour of every possible interpretation.
One candidate had a 15-minute screen on SQL and statistics, a take-home, a three-hour analytics assignment, a technical deep-dive, a presentation to two managers, and a final conversation with product marketing leaders. The topics included campaign efficiency, which campaigns to continue or cut, median versus mean on right-tailed data, and how conversion rate, LTV and CAC connect. That candidate was rejected and was told the answers were not decisive enough. Practice ending every analysis with one recommended action and the evidence behind it, then mention nuance briefly.
A Senior Business Analyst candidate who accepted an offer reported about two months and six interviews, including a manager conversation and an HR conversation. One question asked them to compare several pricing strategies and pick one, with the trade-offs explained. They also said what they wanted in their next role came up in several meetings.
A third candidate reported four rounds, each tied to a company value, plus a project presentation and questions on data-driven decision making. The role was later cancelled after weeks of follow-up. Prepare behavioral examples that show how data changed a decision, and ask each interviewer about next steps and timing.
Synthesized from 3 candidate reports by our editorial team.
Had an interview recently?
Share your experience. Unlock the full guide.
Real interview reports from people who went through the Remitly process.
The process started with a phone screen where the recruiter asked about my current work and background. What caught me off guard was that they brought up a requirement during this call that wasn't actually listed in the job description — it felt like something that could have been clarified upfront to save everyone time. I moved past that and was scheduled for four formal interview rounds.
Each round was structured around one of Remitly's core values, and I interviewed with different stakeholders I'd potentially collaborate with if hired. The questions were grounded in behavioral scenarios and real-world applications. One that stood out asked how I'd used data-driven decision making in my work — they weren't looking for a textbook answer, but concrete examples of how I'd actually approached problems. I also prepared a presentation on a project I'd led, walking through the technical overview and business use cases, then fielded questions from the panel about how those scenarios might apply at Remitly. Another round dug into management practices and how I operate day-to-day.
All four rounds went well, or so I thought. The hiring manager even gave me verbal feedback that seemed positive. But then the follow-up stretched on for weeks — 1-2 months of back-and-forth without resolution. Eventually they told me the position had been cancelled. Coming from a NASDAQ-listed company, the communication and timeline felt unprofessional. It's a solid reminder that even strong interview performance doesn't guarantee closure.
Prep tip from this candidate
Be prepared to discuss data-driven decision making with concrete examples from your work, and ready a project presentation that ties technical decisions to business outcomes. Also, given the slow timeline, clarify next steps and expected timeline after each round to set expectations early.
Share your own interview experience to unlock all reports, or subscribe for full access.
Sourced from candidate reports and verified by our team.
Topics based on recent interview experiences.
Featured question at Remitly
How would you answer when an interviewer asks why you applied to their company?
| Question | |
|---|---|
| Ad Placement Value | |
| Empty Neighborhoods | |
| 2nd Highest Salary | |
| Rolling Bank Transactions | |
| Cumulative Distribution | |
| Payments Received | |
| Top 3 Users | |
| Total Spent on Products | |
| Paired Products | |
| Size of Joins | |
| Month Over Month | |
| Button AB Test | |
| Cumulative Reset | |
| Top Three Salaries | |
| Last Transaction | |
| Third Purchase | |
| Employee Salaries | |
| Google Maps Improvement | |
| Find the Missing Number | |
| Scrambled Tickets | |
| Comments Histogram | |
| Bagging vs Boosting | |
| Closest SAT Scores | |
| Get Top N Frequent Words | |
| Top 5 Turnover Risk | |
| Subscription Overlap | |
| Assumptions of Linear Regression | |
| Minimum Change | |
| Experiment Validity |
Synthesized from candidate reports. Individual experiences may vary.
Candidates report an initial call. One described a 15-minute screen with foundational SQL and statistics questions. Another said the recruiter asked about current work and raised a requirement not listed in the job description. A third mentioned a phone screen before meeting their manager. Expect background questions and possibly quick technical checks.
One candidate completed a take-home and then a three-hour analytics assignment on a dataset, justifying their reasoning. This step was not reported by the others, so it may vary by team or level. If you get one, plan to explain assumptions and finish with a clear recommendation.
Candidates report conversations with a senior team member for about 75 minutes, with a direct manager, and with other stakeholders. Topics included what the team does, what the role involves, and what the candidate wants next. Discussions were described as friendly rather than adversarial, though one included technical deep-diving.
Candidates report presenting analysis or a past project. One presented conclusions to two managers, who wanted crisp takeaways. Another presented a project's technical overview and business use cases. A senior candidate compared pricing strategies and chose one. Prepare to defend a single recommendation and discuss trade-offs.
Final steps reportedly included product marketing leaders covering campaign strategy, journey mapping and A/B testing, value-based interviews, and an HR conversation. Outcomes differed: one accepted offer, one rejection citing a lack of a decisive answer, and one role cancelled after a long follow-up. Timelines can be long, so ask about next steps.
