After an initial chat with the CTO, I was tasked with completing a short coding project in my personal time. (This was by far better than coding during the interview, which is just not a realistic test of a candidate’s skills and is something I never ask a candidate to do.) There was then a session to discuss my code and consider shortcomings and improvements. Next, there were several other interview stages which were a mix of technical, situational, and softer skills. The interview process was spread over several days, so it was a little long, but no one session was too long, and like they say, it’s just as much about you finding out about them as them finding out about you. On balance, this was a positive process with some robust challenges from what appears to be genuinely friendly people.

It started with a great conversation with the CTO followed by a take-home test. After I submitted my solution, I had a one-hour session with two engineers to discuss my implementation. During this interview, I was asked to walk them through the code and explain the reasoning behind my decisions. Then, I went on to another interview with two other engineers in which I was asked more general engineering questions. The last round was a chat about Odeko core values followed by a final meeting with the CTO.