Mojo (UK) interview questions

The screening round included a chat with the founder. It was a straightforward interview speaking about motivations, strengths, and weaknesses. They were quite intent on hiring someone with startup experience because they immediately made it clear on the call that I would not be progressing to the next round due to the lack of startup experience.

The process began on a positive note with an engaging and insightful conversation with one of the founders — one of the most enjoyable interviews I’ve had. However, the experience became less positive as it progressed. I was given a technical task that lacked clarity and specificity. The brief required making fixes and rendering data on both mobile and web. I was advised by the recruiter to stick strictly to the instructions, as candidates had previously been rejected for adding elements outside the scope, such as tests or other enhancements. I followed this guidance carefully and completed the task accordingly. Unfortunately, I was rejected shortly after submitting, and the feedback I received seemed to contradict the original instructions. For instance, I was advised not to go beyond the brief, yet the feedback focused on things that weren’t part of the task. My use of standard performance optimisations in React Native, such as memoization and flat lists (which were relevant to the large datasets involved), was also questioned. I requested clarification but did not receive a response. Even the recruiter I had been in contact with acknowledged the lack of follow-up. It was disappointing not to have the chance to discuss the feedback or clarify the reasoning behind the decision. While I respect every company’s approach to hiring, clearer communication and consistency in expectations would have made this a more positive experience.