3-4 stages of technical interviews, questions ranging from dashboard design to observability pipeline design to Kubernetes fundamentals.
The final stage was with somebody who was maybe an engineering director of sorts and seemed like they were the decision-maker, but they didn't even properly introduce themselves, so I'm not sure.
I felt that the technical interviewers were not knowledgeable enough to be able to understand the nuances of my answers, as they were all less experienced in the subject matter at hand than me. They were also all uncharismatic and seemed low-key depressed or angry at life.
I put interview difficulty as average because they were long and dry; the technical questions themselves were pretty easy.
Can we build a new observability system for Revolut with two engineers in nine months?
The following metrics were computed from 1 interview experience for the Revolut Observability Engineer role in London, England.
Revolut's interview process for their Observability Engineer roles in London, England is extremely selective, failing the vast majority of engineers.
Candidates reported having very negative feelings for Revolut's Observability Engineer interview process in London, England.