Depending on the team, it may not be worth continuing if the process moves to an onsite interview. The flow is virtual interview followed by an onsite panel. Some panel members come across as rude and overly critical, particularly if you don’t answer certain trivia-style questions how they want. The scrutiny often feels disproportionate to the importance of the details being discussed. I don't think this was them giving me a hard time just to see how I can handle it, this may simply reflect their true personality. Other panelists are on their phones or laptops and made their decision before the interview even began. There is another description on Glassdoor which mirrors my experience.
Initial 30 minute phone screening. Second interview was an hour going over my previous work experience and technical questions that consisted of OOP fundamentals, pointers & references, mutex locks, TCP vs UDP, virtual funcitons
Interview questions [1]
Question 1
How would you troubleshoot HW & SW network communication?
Straight forward - 30 minutes phone screen with behavioral and technical questions on C++.
Followed by 5 hour in-person or virtual interview which included both technical and behavioral questions. Each hour was a different interview with different people.
A 30 minute microsoft teams meeting with questions regarding basic C++/C knowledge, resume review, and generic behavioral questions. Delved specifically into how I work in a team environment, personal strengths and weaknesses, and how to address difficult conversations.