Taro Logo

Senior Software Engineer Interview Experience - Berlin, Germany

September 1, 2022
Positive ExperienceNo Offer

Process

The interview process is very lengthy and takes more than one month. Round 1: screen by hr where they will go through your resume and check your skillset matches the role Round 2: Codility test where 3 problems will be provided- fix error in code, 2 LeetCode medium problem Round 3(Tech manager screening): tech manager round- it was like a rapid-fire round, the interviewer asked more than 30+ questions in 1 hour. question- CAP theorem, ACID, NoSql vs SQL, how to handle transactions, event-driven architecture, how ci/cd pipeline works, k8 basics, Kafka basics, thread basics, Rest architecture, OOPs concepts, Singleton, design patterns used in projects, objects of abstract class can be created?

Round 4(SSE Screening): String pool, immutability, GC, hashmap internals, problem-solving -> merge two sorted lists, the internal implementation of ArrayList Round 5(SSE Screening): JPA, annotations used in JPA, hibernate annotations, @Transaction, how to do transactions between 3 microservices, functional interfaces, used any functional interface, streams, CAP theorem, what is latency and how to reduce it, what all ways are available to communicate between two microservices, basic inheritance question--> can we implement multiple interfaces, is it possible to extend multiple abstract classes, when you will prefer to use an interface and when you will use an abstract class.

Round 6 (System design round): Streaming service.I had designed it for a large scale. Interviewer asked me if the additional service can be removed which i was using to do some very specific tasks can be removed. which I removed after picking the hint which was provided to me by the interviewer. you will not get any feedback in between rounds. in my case, I got it after the 6th round with Negative feedback round 6, in which I changed my initial design after getting a hint from the interviewer which contradicted my earlier design. I was completely shocked after seeing this feedback and was thinking about whether it would have been better if I had ignored his hint. The process is too lengthy and time-consuming for getting such weird feedback.

I will suggest if you're giving an interview for Zalando use it as a launchpad for other interviews.

Questions

CAP teorem, ACID, NoSql vs SQL, how to handle transactions,event driven architecture,how the ci/cd pipeline works, k8 basics, kafka basics, thread basics, Rest architecture, OOPs concepts, Singleton, design patterns used in projects, objects of abstract class can be created ?

Was this helpful?

Interview Statistics

The following metrics were computed from 38 interview experiences for the Zalando Senior Software Engineer role in Berlin, Germany.

Success Rate

8%
Pass Rate

Zalando's interview process for their Senior Software Engineer roles in Berlin, Germany is extremely selective, failing the vast majority of engineers.

Experience Rating

Positive34%
Neutral26%
Negative39%

Candidates reported having mixed feelings for Zalando's Senior Software Engineer interview process in Berlin, Germany.

Zalando Work Experiences