← Remitly Interview Insights

Remitly·Software Engineer·Hiring Manager Screen·Intermediate

Intermediate
May 2026

Summary

Behavioral question from Remitly, just the one prompt about pivoting mid-project. Short and focused, felt more like a screen than a full loop.

Questions Asked (1)

Q1

Tell me about a project where the original approach wasn't working and you had to switch course. What made you realize it wasn't working, what other options did you consider, and how did it turn out?

Adaptability & AmbiguityTechnical Trade-offs
Author's notes

This one sounds straightforward but I fumbled the middle part, the 'alternatives you considered' bit.

Create a free account to read the full note

AI HintsAI Generated

Suggested Approach

Choose a project where you identified early warning signs that the original approach was failing, and you proactively pivoted. Structure your answer using a clear narrative: context, problem detection, options considered, decision criteria, and outcome. Emphasize the technical trade-offs and how you balanced them to deliver value.

Pro tip: Quantify the impact of the pivot—e.g., 'reduced latency by 40%' or 'cut development time by two weeks'—to show that your decision was data-driven and beneficial. Also, briefly mention what you learned from the experience to demonstrate growth.

1. Set the Context

Briefly describe the project, your role, and the original approach. Keep it concise to focus on the pivot.

2. Identify the Problem

Explain the specific signs that indicated the original approach wasn't working, such as performance metrics, missed deadlines, or scalability issues.

3. Explore Alternatives

Discuss the alternative approaches you considered, including their pros and cons, and how you evaluated them.

4. Make the Decision

Describe the decision-making process, including any trade-offs, and how you got buy-in from stakeholders.

5. Show the Outcome

Share the results of the pivot, including metrics and lessons learned, and how it positively impacted the project or team.

Key Points to Mention

  • Early warning signs: specific metrics or feedback that indicated the approach was failing
  • Alternative solutions: at least two other options you considered and why they were viable
  • Decision criteria: technical trade-offs (e.g., time, cost, scalability) and how you prioritized them
  • Stakeholder communication: how you aligned the team and managed expectations during the pivot
  • Quantifiable results: metrics showing improvement after the pivot
  • Lessons learned: what you would do differently or how this experience improved your approach

AI-generated suggestions, not part of the candidate's original notes. May be inaccurate — verify before relying on them.