My interview experience was extremely disappointing and felt like a complete waste of time. The environment came across as toxic from the very beginning and did not reflect well on the company’s culture.
After the initial call, I received a preparation document stating that my past projects would not be judged. However, during the interview, the interviewer did the opposite, criticizing decisions made by my previous company rather than focusing on my role or contributions. From that point on, it felt like they weren’t interested in anything I said. The conversation quickly shifted into detailed questions about internal implementations of Kafka and Postgres, which didn’t align with the preparation material at all.
What made the experience even worse was the interviewer’s attitude. They were visibly dismissive from the very first minute, which made the entire interview feel humiliating. Although it was clear I wasn’t moving forward, I was told I would hear back in a week. That update never came, and they simply ghosted me. Meanwhile, a friend who passed received a same-day response.
Overall, it was a disappointing and discouraging process. If the company doesn’t intend to move forward with a candidate, the least they could do is communicate respectfully and avoid misleading preparation materials or unnecessary humiliation. I invested a significant amount of time preparing, and it felt completely wasted.
How is idempotency implemented in Kafka and Postgres? How do you communicate progress to stakeholders?
The following metrics were computed from 48 interview experiences for the Monzo Software Engineer role.
Monzo's interview process for their Software Engineer roles is extremely selective, failing the vast majority of engineers.
Candidates reported having mixed feelings for Monzo's Software Engineer interview process.