Technical phone screen. Email from their recruiter who managed to get both the time wrong by an hour, and the interviewers' names wrong. I couldn't get any information from the recruiter on the nature of the interview which would assist me in preparing.
The actual role was a front end engineer position, but my interviewers just kept drilling me about threading, as they seemed to have identified, correctly mind, I am quite weak on it. I openly stated that I am no threading expert, most of my experience is building pages and CRUD endpoints. One replied that each time you hit a CRUD endpoint a thread will be spun up, so you need to be at least aware of threading. That is indeed true for their Microsoft backend stack, but not in NodeJS, in my current role I never have to worry about threading! They never bothered to email me a rejection. The whole process from start to finish seemed haphazard and chaotic, advice to DB would be maintain professionalism and raise the bar in how you treat candidates.
The interview included very theoretical textbook computer science questions, like asking you to explain the initialism SOLID to your understanding.
Describe how a deadlock comes about.
Describe in WPF how to spin up a thread off the GUI thread.
The following metrics were computed from 1 interview experience for the Deutsche Bank Frontend Engineer role in London, United Kingdom.
Deutsche Bank's interview process for their Frontend Engineer roles in London, United Kingdom is extremely selective, failing the vast majority of engineers.
Candidates reported having very negative feelings for Deutsche Bank's Frontend Engineer interview process in London, United Kingdom.