ShowMax Backend Developer interview questions

First call just to meet each other with the dev leader. Second call with the dev leader and another developer with technical interview. Third call to confirm technical interview and feedbacks for async exercises from the second call. Final feedback in few days via email

Saying that the interview process in this company is terrible would be an understatement. I would STRONGLY recommend never to apply here. Firstly, it took them five months to get in touch with me after my initial application, which is completely unacceptable. The interviews were conducted remotely, all via Google Meet. The initial call with the recruiter mostly went well, and thereafter I was scheduled for a call with a tech lead and one other engineer. The second call was mostly fine, with no coding involved. It was just a briefing on their tech stack, plus them answering any questions I had. Where things became bizarre was in the third call, in which I was asked to do a live coding challenge (which they lied would be a simple one) featuring a tech lead from the previous interview, plus two other engineers. I later found out it was a copy pasted LeetCode medium challenge. The panel in this interview did not explain the rationale for the problem. Also the problem does not correspond to the actual work you'd have to do. Once I completed the challenge, I was immediately told I wasn't a good fit for the company, and that at best I would be a junior programmer there (despite having more than 10 years of experience) - which is quite insulting. It seems that no real thought went into the technical interview - they simply copy pasted problem definitions plus corresponding answers from LeetCode, then expect candidates to regurgitate answers on the fly. If as a candidate you hesitate, or don't write code as fast as they expect, they automatically disqualify you, with no real explanation as to what you did wrong. The languages they expect you to code in are: ruby, javascript, go and python. For all the mentioned programming languages, you'll be given the same algorithmic challenge, in which the panel already has the answer to. The panel also did not seem interested in my thought process or approach to solving the problem. It seemed that unless you write code that matches exactly what they have on file, you fail. Once again, avoid this place.