Ridgeline Software Engineer Interview Questions
& Process

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.

I interviewed for a software engineering role. They say they want to steer away from brain teasers, which I think is a red flag because it implies they believe they have a better way to assess candidates. Anyway, the challenge is to implement something in React with their given criteria. The idea is to simulate a real working environment, which I don't think works because in a real environment, you don't get penalized when you take the wrong turn in an implementation choice. You can simply revert your changes and restart where things were working. But in the interview, you must know the perfect path to implementation in one go. In short, be prepared to read the interviewer's mind and get the most optimal implementation from them within the time constraint and while they are watching you code. If you don't implement it the way they expect, you're out. So much for improving on the traditional way of asking brain teaser questions. While brain teasers aren't perfect, they're still around because they avoid this exact issue: the passing/failing of a candidate isn't solely dependent on the interviewer's opinion; there's a clear score that quantifies the candidate. The score certainly gauges competency, but at least it's a game with clear boundaries.

The engineers were really nice and understanding during the interview. I had a good conversation with them, and they even gave me more time to finish the problem. I definitely recommend interviewing with Ridgeline!