I went through the Senior Engineer track, and frankly, it was one of the most inconsistent and poorly managed processes I’ve encountered.
The "Success" trap: I solved all three coding challenges perfectly, each in under 10 minutes. Because I was so efficient, we moved into System Design. I provided clear, senior-level signals across the board.
Despite clearly acing the interview, I was dismissed with a lazy, meaningless “fit” rejection. In a single one-hour interview, I was drilled on three coding problems, Python fundamentals, and system design, and handled all of it successfully. When a candidate clears every technical hurdle thrown at them and still gets rejected without a single concrete or technical reason, it becomes obvious that the process is no longer about skill or competence.
At that point, decisions are driven by subjective preference, gut feeling, or internal bias, not merit.
Final verdict:
If you are a high-performing engineer who values logic and objective evaluation, look elsewhere. This team seems more interested in finding reasons to reject people than in recognizing actual talent. They will waste your time, and then provide a "fit" rejection because the interviewer likely felt threatened or simply decided they didn't like you personally, regardless of your perfect technical score.
Advice to management:
Fix your scheduling systems and train your interviewers to use standardized rubrics. Rejecting a candidate who solves every problem in record time based on "gut feeling" is a surefire way to ensure you never hire top-tier senior talent.
Intro
Can you introduce yourself and your current role?
What is your current tech stack?
What kind of backend work do you primarily do?
Can you talk about a recent major project you worked on?
Why Flask or FastAPI?
What were the scalability expectations for this system?
What kind of traffic (RPS/RPM) were you expecting?
How do you handle async or unpredictable workloads in your system?
Framework & Design Decisions (Deep Dive)
Why is Django a better fit for your use case than FastAPI?
How does team size influence framework choice?
How do you handle authentication and authorization?
How did you migrate from single-tenant to multi-tenant?
How do you ensure tenant isolation?
What are the current bottlenecks or limits of your system?
What are *args and **kwargs in Python?
What is the difference between positional and keyword arguments?
What are decorators and why do we use them?
Difference between iterators and generators?
What is the Python GIL?
How does multithreading work in Python?
Does Python support true parallelism?
Coding
Find the maximum element in an array
Two Sum problem
Jump Game (can you reach the last index?)
System design (Triggered because I finished early)
How would you design a service that needs to scale from 1k to 10k+ requests?
How would you handle traffic spikes?
Would you use a queue? Why?
How does autoscaling fit into this design?
How would you avoid losing requests?
How would you design caching for this system?
When would you use Redis vs database caching?
How does geographic location affect caching?
What role does CDN play here?
How would you improve database performance?
How do indexes work in PostgreSQL?
What types of indexes are you aware of?
How do you analyze slow queries?
When would you consider NoSQL instead of PostgreSQL?
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.