I had three telephonic interviews (2 algorithm and one design). Somehow my telephonic coding didn't go that well (even though I felt it went pretty well) so they asked me to give another design round before the actual virtual onsite. For onsite, I had 1 presentation round, 1 coding, 2 system design, and 1 experience round. Pros: 1. Recuriter was able to schedule the interview promptly and in most of the cases they were very quick to respond. 2. They called me and provided feedback even when I was not selected. Very few companies do that and I really appreciate it. This helps candidates to improve on and get better for the next interview. Cons: 1. If you are not from Java background then they force you to take at least one telephonic interview in Java. They had some bad experiences with a candidate. When the candidate was hired he didn't like java. Hence they put this condition in place for telephonic round. I felt this is a really stupid condition and any good engineer will easily pick a new language. Anyways, I had to brushup my java knowledge before the interview. 2. They didn't keep update me about telephonic rounds and asked me for my availability. I thought it is for virtual onsite but when I got the calendar invite I realized that they have scheduled on design round. I had to clarify from them before confirming the interview. I felt they could have done a better job in giving me heads up. 3. In the presentation round all the interviewers were there which I didn't expect. They didn't even introduce themself and straight away jump to the interview. Probably set a better standard for interviews. Also, some of the interviewers were late. 4. Recruiter didn't care to give me enough heads up about the interviews and what I should expect. When I explicitly asked they just provided me the type of interview and their schedule. Generally, recruiters call and provide very detailed information about what to expect from each interview. 5. Regarding telephonic interviews, I had solved all the problems and didn't think that they would give me a negative feedback and I have to go through another round before virtual onsite. The second interviewer was not listening to me all the time. He was away from his laptop (I figured based on not responding to my questions and the voice quality indicated that he is not near his laptop). If you are not listening to the candidate all the time how can you even judge properly. This was really a bad user experience. 6. One of the system design was more focused on the Database internal. I have not worked on the database internal that much so this expectation is also bad. Ideally, they should have identified early on that my profile is not completely aligned and probably I am a better fit for other team or role. Also, the recruiter didn't provide any heads up about the design interview. Advice to the management and recruiting team: 1. your telephonic round is really long (2 rounds). People are vesting their time and energy on this so please show some respect and provide them heads up about each step and don't sneak in interviews without giving heads up. This causes unnecessary confusion and bad experience. 2. Train your interviews, ask them to stick to their laptop when they are taking interviews. In case, they need to take care of something urgent they can provide heads up to the candidate. 3. Design the interview so you can test the actual ability of the candidate and avoid situations/questions that are not relevant to his work experience. 4. Any good engineer can pick a new language quickly. Also, in a telephonic(algorithm) interview, you would not be able to judge java skill it is very less time and your focus should be on the algorithm not on the language expertise. if you really want to judge their java skills then have one specific interview for that (this is very old fashion and engineers would not like it).