Naked Financial Technology interview questions

The interview followed a Leetcode-style format, with multiple technical rounds that increased in difficulty. Initial rounds focused on standard data structures and algorithms, while later rounds included more complex problems and optimizations. The process was structured, and each round was time-limited. Expect to solve problems live or in a shared coding environment.

I was approached by Naked Insurance via LinkedIn and agreed to proceed with their interview process. Unfortunately, the experience was disorganized and left much to be desired. The process lacked structure, interviews were conducted out of sequence, with later stage interviews occurring before earlier ones. This inconsistency made it very challenging to follow and prepare appropriately. While the initial conversation with the hiring manager was positive, subsequent interactions with other interviewers were less so. There was a noticeable lack of basic courtesies, such as greetings at the start of interviews, which contributed to an unwelcoming atmosphere. Some interviewers exhibited a condescending demeanor, which was off-putting. The technical questions were easy and ranged from fundamental topics like closures and the differences between const and let, which I answered confidently, to vague and unhelpful hypotheticals like, “What is usually wrong when a website breaks?” Such questions lacked clarity and seemed designed to trip up rather than assess genuine understanding. Despite providing thorough and confident responses, I was informed that my answers didn’t align with their expectations. This feedback, combined with the overall tone of the interviews, suggested a culture that doesn't value diverse perspectives or approaches.