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.