Software Development Engineer (SDE)
Interview Date
October 2024
Result
Rejected
Difficulty
Hard
Rounds
4 rounds
Drive Type
On-Campus/Full-Time
Topics asked
Detailed experience
College: Not Specified
Interview Date: October 2024
Interview Type: On-Campus/Full-Time
Result: Rejected
Difficulty: Hard
Rounds: 4 rounds
Topics Asked: Data Structures, Algorithms, Computer Science Fundamentals, Object-Oriented Programming (OOPS), HTTP Status Codes, System Design, Python, C++, Java Differences, SQL, Project Architecture
The candidate interviewed for the SDE role during campus recruitment and, despite navigating several technical and managerial rounds, ultimately received a rejection after the final round.
Round 1: Online Coding Test (2 hours)
This comprehensive round had three sections: 8 Data Structures and Algorithms (DSA) problems, 15 Computer Science Fundamentals questions, and 15 Puzzles & Aptitude questions. Out of 131 participants, 30 were shortlisted for the next round.
Round 2: Technical Interview (80 min)
This round delved into both DSA and core CS concepts. DSA problems included "Decode String" (LeetCode 395), "Three Sum" (LeetCode 15), and "Longest Substring Without Repeating Characters" (LeetCode 3). Discussions covered OOPS pillars, various HTTP status codes, and system design topics like load balancing, horizontal vs. vertical scaling, and SOLID principles. The interviewer also asked about key differences between Python, C++, and Java. After this round, 18 students advanced.
Round 3: Technical Interview (40-50 min)
This shorter technical interview primarily focused on coding. The candidate was asked to code a solution in VS Code and discussed the approach, edge cases, and time/space complexity.
Round 4: HR + Managerial Round (approx 70-80 min)
The final round assessed soft skills and project-specific technical depth. It started with a self-introduction. A medium-to-hard level SQL query was given. There was an in-depth discussion about projects, including drawing an architectural diagram of one project on paper and explaining its components, connections, behavior, and interaction.
Overall Experience: The process was rigorous, and despite not being selected, the candidate found it a valuable learning experience for sharpening technical and problem-solving skills.