Theodo Interview Questions
& Process

Applied for a Tech Lead role at Theodo Morocco. It began with a phone call, then a 45-min HR interview where we talked about my background, why I want to move, and they presented the job and company. They said I was good to go. Next, I did a 2-hour code refactoring test. HR called after, saying I passed and was moving on. A meeting with a Senior Tech Lead was set up. I didn't get the link and had to ask, then it got postponed 'cause the Tech Lead had something urgent. A new date was set, but again, no link on the day. After emailing, HR called with the negative feedback from the Tech Lead. I already knew about these points and could explain them, especially considering the short time for the test. HR said a chat with the CTO would happen to go over things and decide if I passed the technical part. The next day, an email said they weren't moving forward. HR offered detailed feedback but never gave it, even though I said yes. It was tough emotionally, not just technically. The personal effort I put in wasn't met with clear, honest communication, which is frustrating when you're really motivated and engaged.

It's a pretty long interview process with five interviews. First, there's an HR interview, and it's in French. Then, you take a quiz to test your logic. After that, there's a technical test focusing on test-driven development. Next up is another technical interview with the CTO. The final round is with a manager who gives you the final decision on whether you get the internship.

The process has 4 parts: a first HR interview, a refactoring test, a debugging test, and an interview with a manager. All interviews are followed by a debrief which allows for constructive and quick feedback. The process is quite fast overall (even though it took place in July/August). Well organized overall, being natural and honest made the whole process go well and be 'easy'.

The interview process was quite extensive. It started with an initial HR conversation where I was told no preparation was necessary, but then they advised me to be more concise in discussing my background. After passing this, I completed a coding assessment that heavily featured LeetCode-style Data Structures and Algorithms (DSA) questions. I managed to solve two out of three, with the third being a Dynamic Programming (DP) problem. Following that, I participated in a TDD pair-programming exercise, a behavioral interview with the Agile Coach, and a math logic test. In the final round, the CTO reviewed my DSA answers and questioned my inability to solve the DP problem. I explained that my focus was on web development, leaving less time for advanced algorithmic topics like DP. The CTO mentioned the role doesn't involve algorithms but wanted to gauge my knowledge breadth. I then explained the logic behind DP and, with some guidance, solved it using pseudo-code. Despite this, I was rejected due to my non-Computer Science background, with an invitation to reapply after gaining 6 months of FullStack commercial experience. Throughout the process, the Agile Coach provided feedback at each stage, mostly positive, with constructive advice on being more pragmatic, which I feel I improved upon. The rejection felt arbitrary, especially since I was upfront about being a self-taught career switcher with a STEM Master's and was initially assured they welcome diverse backgrounds. The CTO's decision was based on concerns about my background and the required support, overriding the positive feedback from other interviewers. I was disappointed as I had a tour and was assigned a buddy. I shared my feedback on the assessment process, suggesting I was set up for failure, which wasn't well-received. Submitting my DSA assessment four weeks prior to the CTO interview made the rejection based on it and my credentials unexpected, as I had passed that stage. It appears there's a misalignment between the Agile coaches' and CTO's hiring metrics for junior roles. I'm sharing this in case the process has changed.