First, a call with a recruiter, basic, down-to-earth questions, no "where do you see yourself in 5 years" nonsense, they tell you what the next steps are and you also get to ask a couple of questions regarding the company, so it's a 2-way exchange. Following that, a technical interview, designed around 2 phases: the first one, probing the extent of your theoretical knowledge of concepts, tools and components required in your field (no, you don't need to know Python's C implementation details for that), followed by a second phase, where some live coding has you propose practical solutions, find issues with current code and write your own solutions. The tasks here are very down-to-earth and I found them to be real-world scenarios. All in all, I thought the technical challenge was designed around you being enabled to easily show both what you know and how you think. At the end, I got a very comprehensive review of how I did, including strengths, but, most importantly, points to improve on and recommendations for doing just that.