Info Edge Software Engineer Interview Questions
& Process

So, there are 2 rounds coming up: DSA and Managerial. For these, we need to get better at problem-solving and core technical stuff. For DSA, we'll practice patterns like arrays, sliding window, hashing, linked lists, stacks, queues, trees, graphs, recursion, and dynamic programming, making sure we get both the easy way and the optimized way. Besides just solving coding problems, we should review time and space complexity and figure out why and when a certain method works best. For SQL, we'll work on writing tough queries, joins, subqueries, window functions, aggregation, indexing, and making queries faster, and understand database normalization. Being able to talk about why we designed the schema a certain way and how data is fetched fast will be useful in the managerial chat too. For computer basics, we'll focus on OS stuff (processes, threads, scheduling, deadlocks, memory), DBMS basics (transactions, ACID, isolation), OOP, networking, and basic system design. If you can explain these with real examples, it'll make things clearer. In the managerial round, be ready to back up your problem-solving methods, how you communicate, work with others, decisions on past projects, and how fast you pick things up. Having good DSA skills, solid SQL knowledge, and well-reviewed computer fundamentals will set you up for success in both rounds.

The interview process starts with an online coding round on HackerRank/Mettl, where you'll tackle 2-3 DSA problems of medium to hard difficulty. These problems typically involve Arrays, Trees, HashMaps, Recursion, Greedy, or DP, and you'll have about 90 minutes. Make sure you're comfortable with LeetCode mediums and a couple of hards. Next is Technical Round 1, focusing on DSA and Core Java/Spring Boot. This involves live coding for DSA problems like LRU Cache or Sliding Window, and questions on Core Java concepts (OOP, multithreading, collections, exceptions). You'll also cover Spring Boot basics (REST APIs, DI, annotations, JPA) and SQL (Joins, indexing, normalization, query optimization). Technical Round 2 is about Low-Level Design and a deep dive into your projects. You'll design a system (e.g., Library Mgmt) and discuss classes, interfaces, design patterns, and data modeling. Expect grilling on your project decisions, tradeoffs, and tech choices, along with some Spring Boot and architecture questions. The Managerial Round (MIN Round) is behavioral and scenario-based, covering conflict resolution, ownership, and performance under pressure. They'll also ask about project ownership, cross-functional work, and team collaboration, possibly throwing in tech questions to gauge your stress handling. Finally, the HR Round assesses culture fit, notice period, and salary expectations. Be honest and confident, as they seek individuals who align with their culture and values.

It was an on-campus placement drive. The first step was an online test with aptitude questions and one DSA question (easy to medium difficulty), which needed to be completed in Python. Then, I was invited to their office for further rounds. Around 7-8 of us were called in. The first round commenced about 4-5 hours after reporting time. This round focused heavily on OOPS concepts and JavaScript. I was also asked a pattern question, basic theoretical questions about arrays, linked lists, queues, and stacks, and SQL. Nothing from my resume was discussed. The interviewer was very helpful, guiding me through questions and offering constructive criticism on areas for improvement. Although I wasn't selected after this round, the subsequent process included an HR round, followed by a Senior Tech round, after which candidates were selected.