The interview consisted of 7 parts or maybe more, each took 1-1.5 hours. Also, one codility task took 2 hours. The whole process from the first call till the final decision took 3 months. The technical part was quite easy I suppose for anyone having 5+ years of experience. Trivial Java and SQL questions like what is the complexity of insertion of the element to array list or linked list and so forth. What I did not like is so called 'system design' - that is usually also a trivial list of issues and possible solutions but only in case if the interviewer can express one's issues clear and comprehensive and also I would expect a bit of professionalism from this person. These two things were not found there.
First, the person had difficulties expressing the input info for the tasks. Second, the person was not ready to discuss any possible solutions but the one that the interviewer believed is the most correct. Third, discussion about suggested technologies just revealed the lack of knowledge from that person. Of course for the candidate in that case it can't be an easy challenge to go through it. I guess the best strategy here would be to kindly agree with any absurd thing that was said by the interviewer. That was quite expected that the feedback from that interview was negative.
Also, they complained about my soft skills and incorrect answer to the question about what would you do if the person is not performing well - I replied that I would try to help one if not I report all the possible risks of product delivery to my manager and it might be needed to replace the person.
What are positive things - from the technical point of view the interview was quite easy. Negative things - unnecessarily long interview, 7-8 hours? I cannot believe that you supposed this person was good for the first 6.5 hours of the interview and then you suddenly realized at 6 hours and 59 minutes moment that you do not want to work with this person. It is not working this way. Some interviewers are either not technically experienced or do not have adequate soft skills to do this work. Codility - useless trivial tasks that you never do in reality and you should waste at least 2 hours of your time Neutral things - soft-skill interviews are just a matter of good or bad luck either you are the nice guy for them or not, no matter how you behave and whatever you say.
I would suggest making the interview shorter just to respect the time of all who participate.
What are your weaknesses? What would you do with the problem if your colleague is not performing well? What is the difference between ArrayList and LinkedList?
The following metrics were computed from 1 interview experience for the Zalando Senior Developer, IT Applications role in Helsinki, Finland.
Zalando's interview process for their Senior Developer, IT Applications roles in Helsinki, Finland is extremely selective, failing the vast majority of engineers.
Candidates reported having very negative feelings for Zalando's Senior Developer, IT Applications interview process in Helsinki, Finland.