The big thing wasn't exact coding skills; it was ALL problem solving and worthing with a client. IE, you are the engineer, the interviewer is the client, how do you design and lay out what they need their software to do etc. The big thing was how do you build a system; I focused on making cheap, easily maintainable systems, and that was impressive to them. I also point out some flaws with the assumptions of the questions (this isn't how all users act, etc) and that helped out a lot as well. Even when I didn't fully understand the problem, I kept asking and figuring, trying to learn what it is that they wanted, and how I could build it. You should always talk out your thought processes, to show them they are happening, and to get them to talk as well! TALK TO GET THEM TO TALK!!

It was a 2-3 round process, depending on how your interview went, with increasingly hard DSA questions followed by some HR and behavioural questions. First round was mostly easy and medium leetcode, followed by medium and hard questions in the second round and above on more complex topics.