InDebted Software Engineer Interview Questions
& Process

The interview process had 4 stages: an initial HR chat, then a live coding session, followed by a live systems design interview, and finally a leadership interview. All stages are manageable with proper preparation. The coding and design challenges are not as difficult as typical LeetCode problems, so candidates with substantial experience should find them solvable. I observed that the HR representative typically skips the personal introduction and immediately dives into explaining the interview structure before posing a series of questions.

First round was a 60 min call with the Engineering Manager. It was mostly Q&A about InDebted and how they do software development. They do a lot of pair programming, no code reviews, small frequent commits to main, and frequent deploys to production. They threw in one simple coding problem, mainly to check if I could code. The second round was a 90 min system design interview with 2 engineers. We had to design a system that connects with InDebted's current system. The third round was a 90 min coding test, not like LeetCode. It was a straightforward coding problem to see if I could break down a problem, write unit tests, and code it incrementally. I didn't pass this because I didn't use TDD, though it wasn't obvious I needed to. They require TDD for this stage, but the problem itself is easy.

The interview process involved three rounds: a coding interview, followed by a system design interview, and then another coding interview. Unfortunately, I didn't pass the system design round because the description in the interview invite was misleading. It suggested I should be familiar with the company's tech stack, including event sourcing, but I think I should have focused on typical system design principles with a tech stack I'm comfortable with. This company utilizes pair/mob programming, meaning most of the workday is spent collaborating on Google Meet, even when working from home, which ties everyone's schedule together.