Pretty common process: 0. HR (30m); 1. Technical + a very easy coding problem (60m); 2. System design (60m); 3. Behavioral (60m); 4. Bar raiser (check Amazon's bar raiser to grasp the idea; 60m)
The first interview was very easy, common technical questions and approaches, an extremely light coding problem, and further discussion because we still had plenty of room to discuss something. I am not very good at system design, so I got rejected after waiting for more than 1 week, despite following their good practices like understanding the problem, trying to dive into constraints, asking questions and listening to suggestions, constructing an API, and the diagrams, of course. Probably, I wasted too much time elaborating on the problem, so we had almost no time to delve into particular parts of the design.
The biggest downside: no feedback at all. This spoiled the whole experience, thus a negative experience.
Two sum (literally the first problem from LC).
Design a system that is a kind of middleware between our supply chain service and multiple third-party WMS (warehouse management systems)
The following metrics were computed from 21 interview experiences for the Delivery Hero Senior Software Engineer role in Berlin, Germany.
Delivery Hero's interview process for their Senior Software Engineer roles in Berlin, Germany is very selective, failing most engineers who go through it.
Candidates reported having very negative feelings for Delivery Hero's Senior Software Engineer interview process in Berlin, Germany.