First call was basic SQL questions. The technical SQL interview was a joke. They ask you to first say how you would go about completing a problem mathematically (your answer can range anywhere from something as basic as counting the number of times of X, or you can talk more about statistics and distributions). They then ask you to code it after giving your answer, so in a way, providing a better answer to the first question makes it harder for yourself later.

Firstly, the recruiter emailed me some questions, including basic inquiries about my background, projects I've worked on, and how I approach product cases. The interview process consisted of two rounds, each comprising a mix of technical questions, behavioral assessments, and product case studies. In the initial round, the focus was on technical proficiency, evaluating my knowledge and skills relevant to the role. This involved discussing past projects in detail, demonstrating problem-solving abilities, and assessing my understanding of key concepts within the field. The second round delved deeper into behavioral questions, aiming to gauge my interpersonal skills, communication abilities, and how I approach challenges in a team environment. Additionally, I was presented with more complex product cases, requiring me to analyze scenarios, propose solutions, and articulate my reasoning effectively. Overall, the interview process provided a comprehensive assessment of both my technical capabilities and my suitability for the role in terms of teamwork, problem-solving, and product understanding.