Senior Software Engineer applicants have rated the interview process at Ripple with 2 out of 5 (where 5 is the highest level of difficulty) and assessed their interview experience as 40% positive. To compare, the company-average is 41.8% positive. This is according to Glassdoor user ratings.
Candidates applying for Senior Software Engineer roles take an average of 11 days to get hired, when considering 5 user submitted interviews for this role. To compare, the hiring process at Ripple overall takes an average of 29 days.
Common stages of the interview process at Ripple as a Senior Software Engineer according to 5 Glassdoor interviews include:
Phone interview: 80%
Skills test: 20%
Here are the most commonly searched roles for interview reports -
I applied through an employee referral. The process took 3 days. I interviewed at Ripple (Redding, CA) in May 2016
Interview
I was called by Ripple. We spoke about Ripple and my experience. As soon as I mentioned a time frame for a specific technology the interview turned sour. The interviewer didn't not value past experience in other technologies as a contribution to overall competency, but only the number of years experience in a specific stack. He was very nice, and we ended the call. They did try to fit me into other spots in the company which was very generous of them.
Good. Well organised. Enjoyed discussion. Process bit slow but well managed. Typical sde interview process with some system design and coding. Then behavioural and team fit. The process was cool and I guess enjoyed it.
I applied online. The process took 1 day. I interviewed at Ripple (Dublin, Dublin) in Apr 2026
Interview
first round was "tell me about a time when..." type interview which I answered fully. The Interviewer said I would herre back about the next round which was a take home test to complete.
Was ghosted at that point. chased up a week later but no reply.
Highly unprofessional and time wasters
I interviewed for a software engineering role at Ripple. The phone interview involved a coding problem based on a weighted graph traversal scenario (similar to a currency/crypto conversion problem where the goal is to find the path with the lowest loss).
I suggested using Dijkstra’s algorithm since the problem effectively required finding the minimum-cost path in a weighted graph. However, the interviewer repeatedly pushed for traversing the entire graph instead.
During implementation there were frequent interruptions and side questions while I was coding, which made it difficult to walk through the solution. I also suggested enforcing certain constraints during graph construction, but the interviewer insisted on validating them during traversal, which led to confusing directions.
At one point I had to explain how the graph construction would enforce those constraints. I also made a small typo during implementation; instead of allowing time to debug, the interviewer immediately suggested changing the algorithm. After fixing the typo, the code worked as expected.
Overall, the problem itself was interesting, but the interview felt unstructured and it was difficult to demonstrate the solution effectively.
Interview questions [1]
Question 1
coding problem based on a weighted graph traversal scenario (similar to a currency/crypto conversion problem where the goal is to find the path with the lowest loss).