Relatively standard interview questions (graph algorithm coding problem + basic ML questions), but the interview ended with an unexpected twist - my interviewer critiqued my interview skills in a constructive way and gave me career advice related to MLE. The interviewer pointed out that I approached things too slowly, i.e. too academically, too comprehensively, and too indirectly, when all they needed was a clear and efficient answer to their questions and coding problems. Since I'm relatively inexperienced, this observation was absolutely on point and really made me think about how to optimize my interviews to be more professional instead of just "winging it". One reason this is important is because all the time spent on non-essential details when answering problems or questions takes up time for asking more questions that help the interviewer gauge your skill and possibly make you more competitive. (To be fair, I definitely purposely took things slowly to promote clear communication and questions or discussion, but it's important to know when to take things slowly and when to take things quickly.) Really unique experience. I'm not sure if everyone else will have the same result, but this is definitely an interview you want to try since you might learn things that you don't from other interviews, i.e. Amazon, Google, etc.