Ridgeline Interview Questions
& Process

The interview process had about 5 rounds, finishing with an onsite interview. It went pretty well. There was an in-person technical screen where I had to explain a simple function. There were also screens focused on interpersonal skills and leadership with team members, peers, and other department leads. They said I would get an offer, but after two weeks of checking in with HR, they said they weren't moving forward. It was a really disappointing and confusing experience.

The people I spoke with were great, but the interview process was a bit strange. A major red flag was this really weird and confusing React CAPTCHA challenge. We spent a good chunk of time just figuring out the odd requirements. I wasn't sure if questioning the bizarre user experience was part of the test, but it didn't seem like it. I passed, but I'm unsure if it sent a positive signal. One of the later rounds involved a panel of three engineers who kept interrupting each other and phrasing questions differently. It was tough to figure out who to focus on while trying to address all of them, and I had no clue if my answers were good because I was reading the reactions of three people. While I get wanting multiple engineers involved, they usually act as shadows to keep the conversation focused, not like this. I didn't get the job in the final round, but the recruiters were nice and gave me a phone debrief. I brought up some of these issues, but the recruiters are limited in what they can change about the engineering team's hiring process. I hope someone reads this and improves parts of it because, besides that, the team was a pleasure to talk to.

It started with a recruiter phone screen, then a hiring manager screening which was mostly to get to know each other. After that was a coding round, a LeetCode medium style problem with a panel. The question was about a simple stock trading problem, a simple DSA was enough. Then came the interview loop with 5 back-to-back interviews with multiple teams on the same day. These mostly focused on partnership with the hiring team and other related teams, behavioral aspects, and informing about the company. One round was a technical interview about Spotify System Design. Even after the original loop went well, they added more rounds (another partnership and a final round with the SVP). They said it was a change in the interview process, but it felt like a stalling tactic. I had mentioned my salary expectations before these 'extra rounds', which were at the high end of the range. This might have influenced them to look for a 'cheaper' candidate. The recruiter was honest and admitted they liked me but preferred another candidate. I liked the people I interviewed with and was keen on joining the Reno team.

The interview started with a recruiter call, followed by a behavioral interview. Then there was a technical interview, and after that a bunch of on-site interviews. I initially focused on Python for LeetCode, but realized I was losing my Java/JavaScript skills, so I switched back. I asked for a take-home assignment instead of the technical round because my Python/LeetCode skills were rusty. I prefer working on real problems to showcase my strengths. They agreed to a CoderPad problem, and it didn't matter if I solved it. I was slow because I'd forgotten some Python specifics and kept thinking about the optimal solution and variable names. They mentioned wanting someone who can dive into code, and while I can, I need more LeetCode practice for this company. Luckily, I found another job that accepted a take-home and avoided the 5-hour on-site.