1st call with the recruiter, 15 minutes, asking some questions to understand if you have needed experience, also some questions about the motivation of joining the company. The recruiter doesn't seem to be interested in the motivation actually, just was asking because he has to ask it. 2nd - Root cause analysis (Problem solving). Recruiter meets with you beforehand to describe the upcoming interview process and sends the prep materials - this was useful. 3rd - Product sense. Recruiter meets with you beforehand to describe the upcoming interview process, but this time he was just reading the text from his screen with zero interaction with you, didn't send any prep materials. It was said that there are no right answers, what is important is to see how you think, approach a problem and solve it. Also, as the problem solving interview was focused on finding the root cause of problem, this one will focus more on product sense, design critique and the way I design the solution. During the practice I focused on designing solution on figma, analysing best UX/UI cases. The interviewer said that I can use him as a data scientist in the interview. But the interviewer focused on problem solving part mostly, for all my clarifying questions he answered as "I don't have information. how would you do it?" - to which I replied each time and lost couple minutes on each that kind of question. He could just say that "I'm NOT a data scientist and DON'T have any info, you just go with your assumptions/hypotheses". We had 5-10 minutes left for design critique, in which I was 100% confident, but as he didn't "get the certain answers" he was expecting to get, he didn't focused on how I did the design critique. Despite the fact that it was said that "there are no right answer, no right solutions, what is important is to see how you think, approach a problem and solve it" - the interviewer exactly wanted to get certain solutions that he had in mind or maybe they did. They even mentioned it in the feedback they gave after the interview.