The interview felt less like an assessment of Java engineering ability and more like a pub quiz for obscure syntax trivia. Instead of exploring problem-solving, design decisions, debugging skills, or real-world development experience, the focus seemed to be on recalling exact language details that most professional developers would simply look up in seconds.
It's a curious hiring strategy: rejecting people who know how to build software because they can't instantly recite syntax that modern IDEs autocomplete for them anyway
Overall, the process felt outdated, disconnected from how software is actually written, and more reflective of academic memorisation than professional engineering competence.
Initial CGPA based screening.
Three rounds in total post that.
First eliminatory round consisted of DSA and sql round for screening.
Difficulty Leet Code Medium.Strings question.
Pen paper DSA in person. Leet Code Easy. A sorting variant.
HR or behavioural round.
Final verdict: Selected
I arrived at the Barclays Munich office on Leopoldstraße. A friendly recruiter named Katharina welcomed me. We discussed Java microservices, Kubernetes deployments, and team culture. The atmosphere felt professional yet relaxed. Overall, a positive experience.
3 or 4 Rounds based on role and requirements.
1 or 2 Tech round about your skills and projects will be discussed.
Next is manager round where your inter personal or decision making ability will be discussed. Last HR round where your ctc will be discussed.
Interview questions [1]
Question 1
Skill - SQL
Few Topics - Joins, Windows Functions, Indexes, Partitions, XACT_ABORT, etc.
