The process is decent. First you will get to interact with CTO. If you are through then you are put for 2 hours of grueling coding, designing and code review exercises. If this is through then 2 more rounds with founders. My experience with CTO was good. However the next 2 hour round was simply put - bad. They will put you through Software Engineers as interviewers. The HR says that they need someone who can handle People, Process and Technology. I doubt if the interviewers in round 2 really understand this. They would expect every prospect to be like them and completely forget that EM is a senior role will lots of other responsibilities. They gave a lengthy problem statement and when I asked meaning of certain statements, I was told that don't worry about it, its not relevant for the problem. Then why on earth it's there? After a bit of struggle I could come up with some basic algo to solve problem. Then in code review they gave me a choice of js, kotlin and python. None I have worked on. I chose kotlin bcoz they told it's the closest to java. I was asked to be prepared with an ide. I was ready with eclipse for java. Now their code was not importing in eclipse. Then again they said we just need the files. Now anyone who has worked with an ide will appreciate the color coding. So with no color coding help I was reviewing a stupid code where everything was written in a single file. I pointed out a restructuring of the code. There were no tests at all. I suggested and offered to demo that. The 'intelligent' software engineers were not interested in seeing it. Then came the design. I was asked to use the whiteboard in google meet for system design problem. With no comfort I continued. However at one point this caused a lot of inconvenience I switched to paper pen format and prepared the design with microservices framework. The provided the solution. Read more in Question and Answers...