I applied online. I interviewed at Zego Insurance (London, England) in May 2026
Interview
Unfortunately, this was one of the weaker screening experiences I’ve had. The interviewer arrived late, asked a series of competency questions, but struggled to engage with the substance of my answers. Given the emphasis placed on Zego’s AI-first strategy, I expected more discussion around my experience leading AI products and the lessons learned, but the conversation never developed beyond surface-level questions. The interviewer also appeared disengaged throughout, including visibly yawning during the interview. Overall, it left the impression of a process focused on ticking boxes rather than understanding a candidate’s experience.
Interview questions [1]
Question 1
Do you use AI
How do you use AI
Tell me a time you’ve used AI in development
I applied online. I interviewed at Zego Insurance (London, England) in Mar 2026
Interview
The process was very clear from the beginning till the end. Everyone involved in the process was professional and provided me a very useful feedback. I didn't get an offer, but I received a very useful feedback that helped me discover what can I develop more
Interview questions [1]
Question 1
What methodologies do you use for risk assessment?
I applied through other source. I interviewed at Zego Insurance
Interview
I don't usually leave reviews, but I felt this was worth sharing in the hope it helps future candidates and gives the company useful feedback. This is about the process and my experience, not the outcome.
The process has multiple stages. The first stage is a call with the recruiter, covering a lot of standard screening questions, which was fine and as expected. Went well.
The second stage was a 45 minute conversation with a senior member of the team. For a process with multiple stages, 45 minutes is not enough time to properly evaluate a candidate or to give them a fair chance to answer in depth. Every second stage interview I've had with other companies has been at least an hour. A large portion of the start here was also taken up by an introduction to the interviewer and the company. While useful, it ran long enough that the rest of the interview felt rushed, and I was left with around three minutes to ask my own questions, which doesn't give a candidate a fair opportunity to assess fit in both directions.
The feedback I received was that I lacked sufficient A/B testing and experimentation experience. Based on my notes from the interview, A/B testing was not actually covered well. A/B testing spans areas like experiment design, hypothesis setting, sample size and significance, and reading test results. None of these were explored. The technical questions focused more on data querying, which is a separate skill set. Being rejected on a basis that wasn't directly assessed felt unfair, and a clearer or more accurate reason would have been more constructive.
I'd also note the communication. It took almost two weeks and multiple follow ups from me to receive a response after the interview. Companies rightly expect candidates to be respectful of their time and to communicate well, and candidates deserve the same in return. A simple note confirming the decision or timeline would have made a real difference and would have been more respectful of my time and effort that went into the preparation.
None of this is about not getting the role. It's feedback on interview experience and lack of communication, in the hope the process improves for others.
Interview questions [1]
Question 1
What is the achievement you most proud of?
What success metrics have you setup to make sure that things were working?
Data querying question