KOHO Software Engineer Interview Questions
& Process

Applied on their website and had a recruiter call 2 days later. The recruiter was really nice and the call went well, it was just a basic intro to get to know me and my background. Then I had to do 2 algos on Codility within 5 days. After that, I had a technical interview with 2 senior devs. I had some trouble understanding one of them at first, which I think might have given them the wrong impression, but it was generally okay. Even though I didn't get an offer, it was a really good interview experience and they were fast. The whole thing took me 1 week and the recruiter kept me updated. They also gave me good feedback so I know what to focus on for next time.

I got a message from a recruiter on LinkedIn, and they replied super fast and set up the first chat right away. First, there was a 30-minute HR call. Then, the HR sent over a coding challenge on Codility that I had two weeks to complete, which was really flexible. After I sent it back, the HR got in touch again in about 30 minutes to set up the next interview. This next round was a technical deep-dive and designing a part of Koho's system. They were really open and the interviewers were nice and helped guide me. The HR messaged me again in under an hour after the technical interview to schedule the cultural interview, which asked behavioral questions based on Koho's principles. After that, it was just team fit and then the offer.

I was reached by a recruiter over email. The interview process consists of three 4 parts. 1 - Initial screaming from HR over the phone 2 - Take-home assignment with a real-world case from KOHO to be complete in 5 days 3 - System design and pair programming with two random engineers with Excalidraw and Visual Studio Code (you need to authenticate on VS) 4 - Behavioral interview Although at first glance the interview process seems pretty fair and straightforward, it is totally nonsense and unfair. They ask you to create a production-like application for parsing and validating a file with multiple transactions. I spent over 20hs creating a microservice using SOLID and DDD with 27 unit tests and APIs deployed on a public cloud provider so anyone could test it out. I also created extensive documentation using both readme.md and Swagger web pages. Usually, when companies ask candidates to do take-home assignments, they expect them to discuss their approach and solution over the interview, and KOHO chains that they follow this approach. However, this is not the case. My second interview was with two random engineers which did now know about my take-home assignment at all, the one I spent 20hs on. To add to that, most of the system design interview is spent testing your ability of programming in Go, which was not mentioned during the process since they claim they were tech agnostic and did not require experience with Go. To sum up, do not waste your time if they ask you do to any take-home challenge since no one, absolutely no one, will see your submission (apart from the HR). Also, make sure your know Go pretty well if applying for KAHO.