Software Intern
Interview Date
2024-12-23
Result
Rejected
Difficulty
Overall: Challenging but thorough. OA: 3 LeetCode
Rounds
2 completed (Online Assessment, Technical Round - Coding)
Drive Type
On-Campus
Topics asked
Detailed experience
College: Not Specified
Interview Date: 2024-12-23
Interview Type: On-Campus
Result: Rejected
Difficulty: Overall: Challenging but thorough. OA: 3 LeetCode Medium, 1 LeetCode Hard. Technical Round: Standard LeetCode problems.
Rounds: 2 completed (Online Assessment, Technical Round - Coding)
Topics Asked: Data Structures and Algorithms (DSA), Operating Systems (OS), React (Class/Component architecture, hooks, features), Project Discussion, System Design (Google Docs), JavaScript (Event Loop), C++ Libraries.
The candidate applied for a Software Intern role through an on-campus hiring drive. The process was thorough, testing problem-solving abilities through coding and core subject questions.
Round 1: Online Assessment (OA) consisted of four questions: three LeetCode-medium and one LeetCode hard. The candidate managed to solve two fully and one partially. After this round, the candidate was waitlisted, but three weeks later, was informed of selection for the next rounds.
Round 2: Technical Round (Coding) lasted one hour. The interviewer, an experienced QA engineer, presented two standard Leetcode problems from Striver Sheet:
The candidate solved both DSA questions and explained their approaches. Following the coding, the interviewer asked about the candidate's favorite core subject (Operating Systems). Questions were then posed on OS concepts such as Concurrency and Conditions for Deadlock. The discussion also covered React, specifically the differences between Class/Component-based architecture, hooks, and features.
The candidate's project, an "Online Collaborative Sketching Platform," was discussed in depth. The interviewer delved into the code, asking for justifications behind choices like using promises instead of async-await and the decision to use MongoDB. Questions about scalability and future feature implementations were also asked. Further technical questions included OS library files in C++ and functions related to them, as well as the JavaScript event loop. The candidate struggled to effectively communicate their understanding of the event loop and to efficiently outline the functional requirements for Google Docs during a system design discussion.
The results were announced the next day, and the candidate did not progress to the final Hiring Managerial (HM) round, indicating rejection.
Tips from the candidate: Practice DSA extensively and communicate your thought process. Have thorough knowledge of your project code, tech stacks, design choices, and be prepared to discuss future improvements and scalability. Regularly revise core subjects like DBMS, OS, and OOPS. Possess basic knowledge of System Design, as it can provide an edge, especially for startups and dev-oriented companies.