Ripple Software Engineer Interview Questions
& Process

After passing the initial phone screening, I had 3 upcoming interviews scheduled for the following week, each lasting 45 minutes. These consisted of one technical interview and two behavioral interviews. Honestly, they felt more like casual conversations rather than formal interviews. During the technical part, there was just one question about optimizing something. The behavioral part really focused on accountability and leadership.

I interviewed for a software engineering role at Ripple. The phone interview was a coding challenge involving a weighted graph traversal, akin to a currency conversion problem where the goal is to minimize loss. I suggested Dijkstra's algorithm for the minimum-cost path, but the interviewer pushed for full graph traversal. Coding was interrupted by frequent side questions. I also suggested validating constraints during graph construction, but the interviewer wanted validation during traversal, leading to confusion. I had to explain how graph construction would handle constraints. A typo during coding, instead of allowing debugging, led to an immediate suggestion to change the algorithm. After fixing the typo, the code worked. The problem was interesting, but the interview felt disorganized, making it hard to showcase the solution.

A recruiter reached out for a Staff Engineer role, though I was open to a senior position if the bar was too high. The first round was with the hiring manager, which was okay. Next, I had a technical assessment where I needed to implement a stock-update problem. I discussed my solution, which I thought would work even if not optimal. The problem description was wordy, and I had to define all function signatures and assumptions myself. I started talking and coding simultaneously. Before I could run my code, time ran out. The interviewer seemed to accept it as a solution during the call, but I eventually got rejected. I'm unsure if they expected fully production-ready code. My advice to future candidates is to code faster to finish. I also suggest the interview panel set realistic expectations.