Category: Selection Rounds.
The technical interview is the placement round where an engineer questions you on programming, computer science fundamentals, and your projects. It usually follows the online assessment and decides whether you reach the HR round.
For freshers, the core syllabus is stable: data structures and algorithms, object oriented programming, databases and SQL, operating systems, and computer networks. Panels also dig into your resume projects, and follow up questions are where most candidates fail. If you mention a technology, expect the interviewer to ask why you chose it and what broke while you built it.
Service companies keep the technical bar broad and moderate, testing whether you can learn on the job. Product companies go deeper on problem solving, often with live coding and questions about complexity and trade offs. Either way, saying I do not know and reasoning aloud from first principles scores better than bluffing, because panels probe every claim you make.
The safest way to prepare is to make your own resume the study guide. Write down every technology, project, and skill you listed, then ask yourself the follow up questions an interviewer would ask about each one. Why did you pick this database over another. What was the hardest bug you fixed and how. What would you change if you rebuilt the project today. Freshers who can only describe what their project does, but cannot explain why they made each choice, get exposed within two minutes. If you cannot defend a line on your resume, either learn it properly or remove it.
Communication carries as much weight as correctness in a technical round. When you get a coding problem, restate it in your own words, confirm the input and output with the interviewer, mention a brute force idea, and only then optimize. Narrate your thinking as you write code, because the panel wants to see how you approach an unfamiliar problem, not just whether you memorized the answer. If you hit a wall, say what you are stuck on and what you would try next. That honesty often earns partial credit and hints from the interviewer.
Handle unknown questions with structure instead of panic. It is completely normal to face a concept you have not studied. Rather than guessing wildly or going silent, reason from what you do know: relate the new idea to a familiar one, state your assumptions, and work toward an answer step by step. Interviewers frequently push into unfamiliar territory on purpose to watch how you cope under pressure. Composure and clear reasoning under uncertainty are exactly the traits they are hiring for.
Practice the way the interview actually happens, because reading solutions is not the same as producing them under a watchful eye. Solve problems out loud, ideally with a friend acting as interviewer, and write code without an editor that fixes your mistakes for you. Time yourself, since the pressure of a clock changes how you think. Do a few mock interviews before the real one, and ask for honest feedback on both your solutions and your communication. Freshers who only grind problems silently often freeze the first time they must explain their thinking to another person, which is a gap mock practice closes quickly.
For mass recruiters, arrays, strings, linked lists, stacks, queues, sorting, searching, and basic recursion cover most questions. Product companies additionally expect trees, graphs, and dynamic programming.
They complement each other. DSA clears the screening bar, while a project you can defend in depth is often what separates you from other candidates who solved the same problems.
Say so honestly, then reason aloud from related concepts you do know. Interviewers often ask hard questions to see how you handle uncertainty, so a calm, structured attempt scores far better than bluffing or staying silent.
Definitions prepare you to understand the process. Practice prepares you to clear it. Browse the full campus placement glossary, read verified company interview questions, or rehearse the actual rounds in a scored AI mock interview.