Leapsome Software Engineer Interview Questions
& Process

The interview process was the most hectic interview I have ever done. So many unnecessary steps that at a point they all started to repeat questions already asked and answered in previous steps. The sad thing is that they will reject you at the last step with a generic rejection mail. It is hands down my worst interview experience. For a company that is trying to streamline employee enablement, I found it weird that their recruitment process was filled with unnecessary steps. Also the take home task is divided into three. The product development, the code review, and feature implementation.

The whole thing took me about 1.5 months. First was a call with HR, then a technical chat with the Engineering Manager. After that, I had a take-home assignment to do. Then there was a culture fit interview, and finally, an interview with the Cofounder. For the take-home, I had to work on a Git repo, fix an existing issue, and make a PR. I also had to review a PR that was already open. On top of that, there was a product case study. The other rounds were pretty straightforward. It was a good experience with the team overall, but the Cofounder's interview was rough. He kept dropping off the call and ending it because his internet was bad. It's pretty surprising for a cofounder hiring a senior engineer that he wouldn't have his internet sorted. It caused some communication issues. We ended up turning off video to see if the rest of the interview could go okay. I'm giving it a negative rating because after nearly two months of interviewing, just getting a "we decided not to proceed with your application process as we're going forward with other candidates" is disappointing. Companies really need to step up their feedback game for candidates.

Had a really nice chat with the HR person, it felt natural. She asked some good questions to see how you'd fit the team and your general work attitude. There were also questions about your experience and the tool itself, it's a bonus if you know it a little. Then we moved on to a case study involving product-focused thinking, a PR review, and fixing a bug in a very old codebase. They were quick to give feedback and explained in detail what was good and what could be improved.