SWE Summer Intern
Interview Date
Applied July 17, 2023; Phone Screening Sept 4, 2023; Subsequent interview dates not specified.
Result
Not Specified
Difficulty
Medium to Hard (for some follow-ups and specific d
Rounds
3 (Phone Screening, First Interview Round, Second Interview Round)
Drive Type
Off-Campus, Internship
Topics asked
Detailed experience
College: Not Specified
Interview Date: Applied July 17, 2023; Phone Screening Sept 4, 2023; Subsequent interview dates not specified.
Interview Type: Off-Campus, Internship
Result: Not Specified
Difficulty: Medium to Hard (for some follow-ups and specific data structures)
Rounds: 3 (Phone Screening, First Interview Round, Second Interview Round)
Topics Asked: Introduction, past experiences, coding profiles, preferred language, Tree (company hierarchy), Queue, Custom Sort (Comparator Class), Priority Queue, Time and Space Complexity
Amit Maity shared his Google India SWE Summer Intern'24 interview experience on Medium. He applied on July 17, 2023, and received a referral. His coding profile included LeetCode (2000+ ratings, 1000+ questions solved) and Codeforces (Specialist, 1425 ratings, 500+ questions solved), along with Android freelancing experience.
Phone Screening (10 Minutes): This round occurred on September 4, 2023, after the recruiter called twice. The recruiter introduced herself, and the candidate introduced himself. They discussed his experience, coding profiles, and preferred programming language.
First Interview Round: The questions were based on Tree concepts, presented as raw examples of company hierarchy. The candidate solved both problems and coded them within the time limit, also discussing time and space complexity.
Second Interview Round: This round included questions based on Queue, Custom Sort (using a Comparator Class), and Priority Queue. A follow-up to the first question was also asked. The candidate solved and coded both questions within the time limit. However, he admitted to not handling some edge cases for the last question, which the interviewer pointed out after the coding part. He explained his mistake, and the interviewer agreed.