The first hurdle was an online test with four distinct sections. The key here was time management and having a strong foundation.
- Aptitude: This section was generally easy to medium difficulty. Basic quantitative ability, logical reasoning, and verbal skills were tested. A consistent practice from any standard aptitude portal should be enough to get you through.
- Computer Fundamentals: This is where your core CS knowledge is tested. They asked a lot of questions on OOPs concepts (think Inheritance, Polymorphism, Encapsulation, etc.). Make sure your basics here are rock solid.
- SQL: This was a dedicated section for writing queries. The problems weren't too complex, but they checked your understanding of basic commands like
SELECT, WHERE, JOIN, and GROUP BY.
- Coding Questions: They gave us two coding problems, and I found them to be very easy. If you are comfortable with basic array and string manipulations, you can easily solve them within the time.
💡 My Tip for OA: Practice speed and accuracy. For the coding part, don't ignore the simple problems; they are easy marks if you don't make silly syntax errors.
This round felt like a deep dive into everything I had learned. It was a mix of SQL, DSA, and my projects.
Part 1: The SQL
The interviewer directly shared three problem statements and asked me to write the SQL queries for them. They were scenario-based, like finding top performers from a sales table or calculating average metrics from a dataset. It tested my ability to translate a business problem into a working SQL query using JOINs, aggregate functions, and WHERE clauses.
Part 2: The Project Deep-Dive
Then, they shifted to my resume. They asked me to explain one of my web development projects. I chose my most confident one and walked them through the architecture, the tech stack I used (like React, Node.js, Express, MongoDB), and the problem it was solving. They asked follow-up questions about the database schema, why I chose a particular framework, and the challenges I faced.
Part 3: The DSA Challenge
Finally, they presented two medium-level Data Structure questions focused on Linked Lists. One involved detection and removal of a cycle, and the other was about a complex reversal. I had to explain my approach first and then code it out. Practicing standard problems from platforms like LeetCode really paid off here.
💡 My Tip for TI-1: When you explain your project, be prepared for "Why?" questions. Why MongoDB? Why React? Also, keep revising your core DSA topics, especially Linked Lists, Trees, and Graphs.
This was the most challenging and comprehensive round. The interviewer really tested the depth of my knowledge.
Part 1: Advanced SQL Queries
They upped the ante with five SQL queries that were more complicated. We're talking about multi-table joins, nested subqueries, and extensive use of HAVING and CASE statements. One question even required a Common Table Expression (CTE). If you have practiced well, you'll find them manageable, but they definitely separate those who are comfortable with SQL from those who aren't.
Part 2: The Web Development Inquisition
This was intense! They asked detailed questions on every single technology I had mentioned on my resume. For my MERN stack project, they drilled down into:
- The event loop in JavaScript.
- Closures and Promises.
- The difference between
PUT and PATCH.
- Authentication middleware in Express.js.
And then came the trick question! They asked me to write a middleware function on the spot to log incoming requests. It was a moment that tested my practical understanding, not just theoretical knowledge.
💡 My Tip for TI-2: Don't just list technologies on your resume. Be prepared to write code for them. Practice writing small middleware, helper functions, and understand the "how" and "why" behind every tool you use.
Looking back, here’s my consolidated advice for all of you preparing:
- Your Resume is Your Bible: Whatever you write, you should know every detail of it. Be ready to explain, defend, and code anything mentioned there.
- OOPS is Non-Negotiable: It's a favorite topic across all companies. Revise your OOPs concepts thoroughly.
- Practice Machine Coding (For Web Dev Folks): Don't just build full projects. Practice building small, functional components or features in a limited time. This is crucial.
- JavaScript Basics are a MUST: I cannot stress this enough. If you are a web developer, you must know JavaScript inside out. My go-to resource? "Namaste JavaScript" by Akshay Saini. Watch it, understand it, and you'll be confident in any JS-related grilling.
- SQL is a Key Player: For many product-based companies, SQL is as important as DSA. Practice a variety of problems, from easy to hard, on platforms like LeetCode or HackerRank.
The journey can be demanding, but with focused preparation and a calm mind, you can absolutely ace it. All the very best! You've got this!
Ananya out!
.png)
