DevRev

Role: Developer Trainee (Full Stack Developer)

College: Not Specified

Interview Date: 2023-07-28

Interview Type: On-Campus

Result: Not Specified

Difficulty: Medium

Rounds: 1 (after project submission)

Topics Asked: Core Subjects (OS, CN, DBMS, OOPS), Technical Concepts (HTML, CSS, JS, Node.JS, Express.JS, MongoDB), Data Structures and Algorithms, Project Discussion.

Experience:

The recruitment process for the Developer Trainee role involved an on-campus placement drive across three colleges. Initially, interested students filled out a form, leading to approximately 600 shortlists. These shortlisted students were assigned different projects based on their preferred fields (Frontend, Backend, or Full Stack Developer). The candidate opted for Full Stack Developer and successfully completed a "Flight Ticket Booking System" project within 36 hours.

After a 10-15 day review period for all submitted projects, interviews were scheduled for groups of 5-7 students daily over three days, resulting in about 20 students being shortlisted for interviews. The interview notification was received 4-5 hours prior to the scheduled time. During this short preparation window, the candidate brushed up on Core Subjects (OS, CN, DBMS, OOPS), Technical Concepts (HTML, CSS, JS, Node.JS, Express.JS, MongoDB), reviewed their project, and some DSA concepts.

The interview began with an introduction. The interviewer then asked the candidate to demonstrate the hosted project along with its source code, followed by specific questions about the project and explanations of particular code segments. The interviewer then inquired about the candidate's preferred coding language (Java in this instance) and asked 2-3 OOPS-related questions:

• "Is Java pure Object Oriented?"
• "Difference between Abstract class and Interfaces"
• "Difference between Final, Finally, and Finalize"

Finally, a LeetCode medium-level DSA question was posed, with only 10 minutes allotted for a solution due to time constraints. The candidate explained their intuition, and the interviewer was satisfied with the approach, not requiring the full code implementation.