The interview experience was very fast and time consuming for me. This was good because it helped make a decision quickly within a week. First, the onsite interview directly. The recruiter was really friendly and gave me a tour of the place. Then we had lunch with the Director of Engineering, the CTO, and a few engineers where it was a general get to know you type of interview while eating a good meal. This was for about half an hour to 45 min. Then, afterward there were two technical interviews. Each 45 min long with a different interviewer. The first was very interesting. It was to analyze code (happened to be the language I was comfortable with) and figure out what it was doing, what was wrong with it, and how to improve it. This can very intimidating and difficult for those who don't code often or those who don't have experience in the field in question. They really want to see how you think and analyze the code even if it uses a strange API that you have not seen. It was on paper too so you can just point on the paper what you need to do. For me, this was just medium difficulty and a lot of experience and intuition played a part for me in this interview, but it was very interesting and educational. I don't think I got everything right, but it was certainly enough and the interviewer was very encouraging all the way. The second was just a coding challenge on the whiteboard, standard algorithm/data structure problem (medium/hard difficulty on leetcode). Very nice interviewers overall. Talked a lot about what they did and do for Nauto and it was very informational and nice to talk with. Then, had two half hour interviews with the recruiter and Director of Engineering, both very friendly and it was just your average HR interview questions. So overall, great. Afterwards, I met a few more engineers to talk with, no technical stuff. Got an offer within a week.

Phone call with Recruiter, engineer of team, take home coding challenge and finally an on-site. Each person seemed very hesitant until they reviewed the actual code. I prefer real world demonstration instead of knowledge based questions or non-practical problems. One thing I didn't like was interviewing with an engineer who wasn't part of the company. He bragged about working at Google for many years but at the same time, mentioned how much he hated working there. The other thing that got me was him stating that he's older and knows more than me, kind of putting me down at that point. Somewhat neutral to the whole process. It was somewhat quick.