The overall campus selection process had 2 phases. Phase 1: Offline written exam, consisting of MCQs on aptitude, coding (JS and Python), DSA and OOP. Difficulty level: 3/5 (Normal) Phase 2: Interviews: - 2.1: Technical interview 1 A senior engineer went through my resume and asked questions regarding my projects and listed skills. Basic questions or definitions of concepts as well as tools. Difficulty level: 2/5 (Easy) No coding or screen sharing, no DSA, no concepts out of my resume. 2.2: Technical interview 2 Resume and skillset-based questions. Interacted with the director. Got a high-level briefing of the role and its associated expectations. Difficulty level: 2/5 (Easy) No coding or screen sharing, no DSA, no questions out of my resume. 2.3: HR interview Introduction -> Hobbies -> Expectations -> About the company -> About the role -> About future plans -> Move to Bangalore Difficulty level: well, here its subjective. If (you have good communication skills): then it will be fairly easy Else: HR is supportive and will assist you as much as possible. Overall tips: 1) Don't bluff: Interviewers have good experience, and they will see through your facade. 2) Be polite and professional: you may not be a good engineer but at least try to be a good person, sometimes it makes a big difference. 3) Be humble: Don't copy projects from YouTube or Udemy and please never behave as if you know it all, because you don't, nobody does. 4) Be honest: Nobody expects a picture-perfect answer, do your best and if you don't know something then say "Sir, I'd have to go through the documentation". 5) I repeat: Don't copy projects from Udemy, Coursera, Edx or YouTube and behave as if you know all the related concepts. They will ask questions related to your projects, and it's pretty easy to spot a liar.