Ripple Interview Questions
& Process

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.

It started with a recruiter screen and then a hiring manager screen. The process is organized, but the hiring managers seem to lack clarity on what they are looking for, which makes the decision-making process appear chaotic. I've been considered for four different roles internally over the past nine months. The feedback suggests a lack of communication among them, as one person found me too focused on crypto, which is odd given my limited experience in that area compared to my 20 years overall. Another feedback was that I was too sales-oriented and lacked relationship management skills, which is also strange as I've primarily been in business development. Conversely, when I was considered for a different team, the feedback was that I wasn't 'crypto enough' or 'salesy enough.' It seems they are unsure of their requirements. The fact that roles at Ripple remain open for over six months implies a lack of urgent hiring needs.

The hiring process was pretty involved, covering both technical and strategic aspects of product management. It started with a 30-min recruiter chat about my background and interest, plus role details and salary. Then, I interviewed with the hiring manager, who dug into my product experience, prioritization methods, teamwork, and vision, using behavioral and situational questions. Finally, I had a take-home case study where I needed to design a new feature or improve an existing one, detailing the problem, solution, and success metrics. This really tested my practical PM skills.

The interview process was incredibly straightforward. The recruiter was excellent, and the people I spoke with were incredibly friendly. Despite driving an eight-hour roundtrip to San Francisco to meet with the team, I ended up having three Zoom interviews. The team’s positive energy made the long commute worth it, and I was eager to secure the role. Unfortunately, after driving to the office and assuring them that my hybrid status was acceptable, they decided not to proceed due to my distance. This hadn’t been a concern until the day of my last interview, and it was well-known how far I lived before that. Apart from the last-minute decision to inform me I wouldn’t be hired due to my distance, everything else was perfect. The recruiter was excellent, and I thoroughly enjoyed working with the team.