Your resume finally got through the ATS filters. You also cleared the online aptitude test. Now you have that email in front of you. It says, “Invitation for Technical Interview”.
For many new engineers in India, the technical round feels like the hardest step, whether it is at a large IT services company or a fast-moving startup in Bengaluru. In both, the interviewer is checking one thing: whether you actually understand what your resume says you know.
Questions can jump from OOP theory to a linked list problem to "walk me through your final-year project" within minutes. Without a plan, it is easy to freeze. A checklist keeps your preparation focused on what is usually asked of freshers.
1. Basics to Know First
Before you start coding on a board, expect questions on core computer science topics. Many interviewers in India focus on theory early. They want to see if your base is clear.
Go through these items:
- Object Oriented Programming (OOP): Be ready to talk about the four ideas: Abstraction, Encapsulation, Inheritance, and Polymorphism. Also share small real examples. Know how method overloading differs from overriding.
- DBMS: You should know what SQL and NoSQL mean. Practice basic query writing like SELECT, JOIN, and GROUP BY. Learn why normalization matters. Be clear on primary keys and foreign keys.
- Operating Systems: Review threads and processes. Understand multithreading. Know what deadlock is. Learn the idea of paging. Get the basics right.
- Computer Networks: Learn the OSI layers. Be able to explain TCP vs UDP. Know basic HTTP actions and what they do.
2. DSA Checklist
This part matters a lot in most software interview rounds. For a new role, you do not need to be a contest wizard. Still, you should know the common algorithms and patterns.
Mark these topics before you show up:
- Arrays and Strings: Work on basic tasks like duplicate detection, string reversal, and two-pointer style problems.
- Linked Lists: Be able to walk through nodes, reverse the list, and locate the middle node in a singly linked list.
- Stacks and Queues: Understand LIFO and FIFO, plus where they show up in real use.
- Trees and Graphs: Get comfortable with a BST and the usual walks: inorder, preorder, postorder.
- Hashing: Use hash maps and sets for counting, lookups and duplicate checks. Many brute-force answers improve with one.
- Recursion: Be able to trace a recursive function (factorial, Fibonacci, tree traversal) and explain the base case.
- Searching and Sorting: Know binary search, merge sort, and quick sort. Be clear on time and space costs using Big-O.
3. Resume Deep-Dive Checklist
Many interviewers start by looking at your resume. They pick one project and ask questions about it. If you struggle to explain what you built, they may think you copied it from somewhere online.
Prepare these points for your project:
- Can I describe the main problem my project solves in less than 60 seconds?
- Can I explain why I picked my tech stack, like why MongoDB over MySQL?
- Do I truly know the libraries, frameworks, and tools I wrote in the Skills section?
- Can I describe the hardest technical issue I hit and what I did to fix it?
Is your resume matching what you can actually do? Interviewers often pick questions straight from your skills list, so remove anything you can't explain. To check how well your resume matches a job description, use JobYaar's free ATS Resume Checker.
4. Live Coding (Whiteboard) Checklist
Coding on paper or a whiteboard feels nothing like working in an IDE such as VS Code. You do not get auto-complete. Typos and missing symbols stand out fast.
What to do during live coding
- Think as you go: Do not just stare for a long time. Talk through what you are doing. If your code has a bug, they may still judge your reasoning as clear.
- Try the simple plan first: Don't jump straight to the optimal approach. Explain a basic brute-force solution and its time complexity (for example,
O(n²)with two nested loops), then improve it step by step (for example, toO(n)using a hash map). - Look for edge cases: Before you claim it is finished, scan for tricky inputs like an empty array, negative values, or null data.
- Keep it tidy: Use sensible names like
userIndex. Keep the indentation lined up. Do this even when you are writing on a board.
5. Final Logistics Checklist
A small technical issue can throw off the whole interview. Take a minute to set things up.
Quick checks before you begin
- If it is remote: Is the connection steady? Does the webcam show you clearly? Is your space free of clutter?
- Materials: Do you have a pen and a notepad within reach so you can follow the steps?
- Questions to ask: Have at least two questions ready for the end. For instance, "What tech stack does your team use most for new microservices?"
Final Thoughts
A technical interview is not about memorizing facts. It is about how you solve problems. The interviewer is watching what you do when the answer does not come right away. If you use the checklist above, you can enter the room with a good base and handle the coding task they give you.
After the coding round, and after you finally get the offer letter, you will need to sort out your money. Taxes can catch people off guard. Use JobYaar’s free in-hand salary calculator to find your monthly take-home pay for FY 2026-27: In-Hand Salary Calculator.
FAQ
What programming language should I use in a technical interview?
If the job post does not force one language, pick the one you know best. In many DSA rounds for Indian freshers, Python and C++ are common choices.
What happens if my code is not perfect?
In a live interview, the reasoning and the plan usually matter most. Clear steps and correct logic often count for more than tiny syntax mistakes. Online coding tests are different: there, your code must compile and pass hidden test cases. If you forget a semicolon or mix up a bracket, but you explain the method well, the interviewer will usually focus on the idea.
Will they ask me to build a full app during the interview?
No, not for fresher roles. You are more likely to be asked to write one or a few functions or solve a specific algorithm. For example, they may ask for a function that checks whether a string is a palindrome.