Three Rounds: Recruiter call > in-person technical and behavioural round > final round (technical + behavioural, again). Since this role was for juniors, 50% was deep diving on resume and your tech stack in your past internships and/or projects; the other 50% were on technicals and behaiorals, which were much simpler than expected. The technicals were LeetCode easy/medium, based on two-pointers and linked lists, and consecutive questions on simple data structures (lists, sets, maps) and their time complexity. Also, depending on what role you're applying to specifically, know that language's concepts. For example, if you're applying for a Java role, definitely know the tradeoffs of using Java vs C++/Python, Garbage collection, OOP, Collections interfaces, errors, file handling, etc . The behavioural were 2 STAR method questions (ex: tell me about a time you had a conflict with your team and how you resolved the issue). Definitely not the hardest interview I've done. Really focus on past experience + simple DSA + OOP, and you'll be fine.

little bit hard and long. I did it as a coop student, they interviewed like 30 students together at the same time all in break out rooms via zoom. Knowing that at the start make you already stressed as you are competing against a lot of students.