Reverb Software Engineer Interview Questions
& Process

The whole thing took more than two months. First up was a call with the recruiter, where we chatted about some behavioral stuff and they gave me the lowdown on the rest of the interviews. After that, I had a one-hour HackerRank challenge. Then I talked to the hiring manager about my technical chops and more behavioral questions. The last interview was with the hiring manager and another engineer, and we worked through HackerRank problems using test-driven development. It all went pretty smoothly, but here's the kicker: the job ad said remote, but after the final interview, they told me I didn't get it because they want new hires in the Chicago office a few days a week, even though they said I interviewed well. They should really update their job postings.

The interview process began with a recruiter screening call, which was pleasant. Following that, I had a one-hour interview with an engineering director. During this interview, we worked through a HackerRank-style coding problem on Codepen. I found the problem to be irrelevant to real-world scenarios, which was disappointing given my prior communication with the recruiter expressing a preference for practical challenges over typical online coding assessments. Despite this mismatch, all interactions were with nice and friendly people, and the company emphasizes inclusion.

It was a really fair process, and everyone I interacted with was super helpful and genuinely wanted me to succeed. They were all incredibly nice people, and I'd gladly go through it again. The systems design part was likely the most challenging. Everything else is pretty straightforward for a developer who can articulate the pros and cons of different approaches and has relevant experience.