Their is total 3 rounds of discussion, including 2 technical and 1 hr. After clearing L1 and L2 round. HR asked for some documents and schedule the HR round. After 3 days when I tired to reach out they are not receiveing the call and after that HR told me that go for another offer without saying any reason. They should have to provide the proper feedback. If you want to waste your time then go for this interview process.

interview process went very smoothly which actually was my first interview it had many rounds first round would be aptitude continued with group discussion, technical round and HR which went well as people very generous . group discussion was easy to clear .

I had both experiences from the "bad" and good. I started the interview terribly in the first half and then recovered for the second half in all 3 interviews. So, I think I can say with confidence I know how the interviewers will react toward candidates whose trajectory seems to be in the direction of "no hire". As I'm still a beginner at interviewing, you can almost imagine how wobbly my interactions could've been. The "bad": Not once did I ever witness stressed nonverbal signals. They didn't speed up the interview to end it nor simplified the problem to prevent me from feeling inferior. Instead, they engaged in a delicate conversation to consider alternatives in a very inclusive manner. The engineers made the experience feel like a sense of, "if we won't hire you, let's try to push you in the right direction for another company". The good: I solved the problem decently and allowed my creativity to flow a bit more. I can only hope I had impressed them instead of just making the bar. Either way, the interviewers didn't bloat my ego nor did they make me feel inferior. They stuck with the questions, kept an open mind, and maintained neutrality in their composure for every problem. The only time I noticed the neutrality was ever off is when they provided hints and clues. That's when the engineers would express a "wondering" expression with a short playfulness. If you meet an engineer who has the title of Architect, prepare. The engineer is very solid at almost all levels of computer science. Also, he's totally a nerd with it and loves all aspects of CS, which I loved. I got asked from all ranges of CS topics and later found out he was just filtering for possible roles in which I might contribute best. So if you don't do well in some areas in the technical part, it's okay because you don't have to be great at everything but let's hope you're great at something else. If you get Julie as your technical recruiter then you'll be in a smooth operation. She is really good. Just let her fill you in on the details because she is very experienced.