I went through the recruitment process at this company to the final stage: the technical interview. Like other software engineer candidates in the company that I see here, my experience was far from positive. The process was extremely long, with multiple interviews, but the main one was the project to do at home. They require a fully functional project with many features, which would take at least 10 hours for a senior frontend developer—a huge demand for someone with a full-time job and to keep time for personal life activities. I completed 100% of the project, including the bonus tasks, and at least found it somewhat interesting. The final interview involved presenting the project for an hour to three developers, with most of the questions coming from a senior engineer. Questions were not so complex, even if somehow I had a feeling that the senior was never fully happy with my answers. Even if they were correct, he had to say "Yes that's one of the solution but...". Overall, I would say that their opinion was positive on me, they asked me questions that I answered and I presented them a project fully functionnal with bonuses. However, here come the most frustrating part: when they gave me the results, it was negative and they didn't even bother to provide any feedback on what they found lacking and why they didn’t make an offer. I asked later to the HR who was in charge and I am still waiting for her reply to my message 1 week ago after final decision. I will never recommend this company for IT job. Don't waste your time with this company; they have no respect for their candidates.

I recently interviewed for a Senior Software Engineer position at Media Markt Germany, and my experience was far from positive. The entire process took over a month, with multiple lengthy interview stages. The second interview required completing an extensive take-home project, where they asked for two fully functional microservices in less than a week. Even for someone experienced, this would take at least 10-20 hours, which is extremely demanding for candidates who already have full-time jobs and can only work on it in their limited free time. During the third interview, I had to present my solution to a panel of five interviewers. They had no real objections to my work, but one interviewer questioned my approach to structuring controllers. Specifically, he asked why I created a controller per use case rather than grouping everything into a single controller. I explained that I followed the Single Responsibility Principle (SRP), only to be met with a bizarre counterargument—that SRP means each file should contain only one function. I had to explain what SRP actually meant, which raised concerns about their technical knowledge and engineering culture. Despite the lack of valid criticism on my solution, I was ultimately rejected with the vague reason that I was "not open to feedback." This experience left me with the impression that challenging their opinions, even with well-founded reasoning, is not welcome. If there's one lesson I took from this, it’s that questioning someone who feels insecure about their position can cost you the opportunity. I wouldn’t recommend this interview process to anyone looking for a fair and reasonable hiring experience.