Fresher Interview Questions in India: 30 Answers That Work

Fresher interviews in India follow a predictable shape: an aptitude or online assessment, one or two technical rounds built around your final year project and core computer science subjects, then an HR round about relocation, shifts and expected CTC. If you can hold a clear five minute conversation about your own project, write basic code without an IDE, and explain why you want this specific company, you are already ahead of most of the batch. This guide lists the questions that actually come up at mass recruiters like TCS, Infosys, Wipro, Cognizant, Capgemini and Accenture, along with sample answers you can adapt. It also covers what product companies and startups add on top: data structures, time complexity, basic system design and much deeper project follow ups. Nothing here needs work experience. Everything can be answered from coursework, an internship, one project and a few weeks of honest preparation.

What a fresher interview is actually testing

Nobody expects a fresher to know the company codebase. The technical round is checking three things: whether you can explain something you built without hiding behind buzzwords, whether your fundamentals in one language plus DBMS and OOP are real or memorised, and whether you stay coherent when an answer is wrong. Interviewers at volume hiring drives may see forty candidates in a day, so clarity beats depth. The HR round is checking a different set of risks: will you relocate, will you accept night shifts or a service agreement, will you leave in six months, and does your expected CTC fit the band already fixed for the role.

This means preparation splits cleanly. Spend most of your time on your project, one programming language and the four core subjects, since that is where the technical panel will actually spend its questions. Spend the rest on rehearsing six or seven predictable spoken answers aloud until each one runs under ninety seconds. Reading them silently is not rehearsal, and it is the reason candidates who feel prepared still ramble on the day. Record yourself once if you can bear it, because the gap between what you think you said and what actually came out is usually large.

• One language you can defend properly, usually Java, Python, C++ or JavaScript.
• OOP concepts with your own examples, not textbook definitions.
• DBMS: joins, normalisation, keys, indexes, ACID.
• Operating systems and networking basics if the role is infrastructure adjacent.
• Your final year project, end to end, including what broke.
• Aptitude and logical reasoning for the online assessment stage.

The questions you will definitely be asked

These come up in nearly every fresher interview in India, in some form, and they are usually asked in the first ten minutes while the interviewer is still forming an impression. Write your own version of each one, then say it out loud until it stops sounding like a script. The sample answers below are deliberately short, because interviewers stop listening after about two minutes and a long answer buries whatever was good in it. Swap in your own college, your own stack and your own numbers rather than reusing the wording here, since panels hear the same recycled lines all day.

• Tell me about yourself. Sample: I am a final year Information Technology student at a college in Pune, with a CGPA of 8.2. I work mostly in Java and did a six week internship building REST APIs for an inventory tool. My final year project is a bus tracking app where I handled the backend and the live location updates. I am looking for a role where I can write production code from the first year itself.
• Why do you want to join our company? Sample: Two reasons. Your delivery model means freshers get put on live client projects early, and I would rather learn on real systems than in a sandbox. And the training programme in your first six months covers cloud, which is where I want my career to go.
• What are your strengths and weaknesses? Sample strength: I am stubborn about debugging, I do not move on until I understand the root cause. Weakness: I over engineer first drafts. On my project I built a caching layer before there was any traffic to cache, and my guide made me strip it out. Now I get something working first and optimise after.
• Where do you see yourself in five years? Sample: Still in engineering, not management. In five years I want to be the person on the team who owns a module end to end and can be handed an unfamiliar bug and fix it.
• Do you have any questions for us? Ask about the training period, the tech stack of the team you would join, or how freshers are allocated to projects. Never open with leave policy.

Core technical questions freshers get

At mass recruiters the technical round is broad and shallow. Expect rapid fire questions across subjects rather than one hard problem. At product companies it inverts: fewer questions, much more depth, usually one or two coding problems on a shared editor. Prepare for the breadth first, because the volume recruiters interview far more people and are therefore where most freshers get their first offer. The list below is not exhaustive, but if you can answer all of it comfortably you will clear the technical round at most service companies.

• Difference between an abstract class and an interface, with a case where you would pick each.
• What is method overloading versus overriding, and can a static method be overridden.
• Explain the four OOP pillars using your own project as the example.
• Difference between a primary key, a unique key and a foreign key.
• What is normalisation, and why would you deliberately denormalise.
• Difference between DELETE, TRUNCATE and DROP.
• Array versus linked list, and where each one hurts.
• Process versus thread, and what a deadlock needs to occur.
• Reverse a string, find duplicates in an array, check a palindrome, print a Fibonacci series. These still get asked and people still fumble them under pressure.

Project questions and how to survive them

Your final year project is the only thing on your resume that is genuinely yours, so interviewers dig into it. The failure mode is a candidate who describes a project in marketing language and then cannot say which database table stores the user session. Know your own stack cold, including the parts a teammate wrote, because you will be asked about them.

If your project was a guided tutorial build, say so and pivot immediately to what you changed, extended or debugged yourself. Honesty about scope, backed by specific technical detail, beats an inflated claim that collapses on the second follow up question, and interviewers who see hundreds of these projects recognise the standard ones anyway. One module you genuinely own is worth more here than a large system you can only describe from the outside.

• What problem does it solve, and who would actually use it.
• Which part did you personally write, and which part did your teammates write.
• Why this database, this framework, this hosting choice.
• What was the hardest bug and how did you find it.
• How many users could it handle, and what would break first.
• What would you build differently now.
• Is it on GitHub, and can you walk through a file right now.

The HR round and the CTC question

For freshers at large IT services companies the package is usually fixed by band, so the expected CTC question is a fit check, not a negotiation. The safe answer signals flexibility without sounding desperate. Try: I understand freshers join on a standard band, and I am comfortable with that. My priority right now is the training and the project I get put on. If there is any flexibility I would be glad to discuss it once the offer is drafted.

The rest of the HR round is risk screening. Relocation, rotational or night shifts, a service agreement after training, backlogs, gap years and family situation all get raised. Answer plainly. A hedged answer on relocation is read as a no, and a fabricated yes is worse, because you will be held to it in the offer letter and in the posting you actually receive. Decide your real limits before the round rather than during it, since the answer you improvise under pressure is the one that goes on your file.

• Are you willing to relocate anywhere in India. Say yes only if you mean it.
• Are you comfortable with rotational or night shifts.
• Do you have any active backlogs or a year gap, and what caused it.
• Are you appearing for other companies right now.
• Are you comfortable signing a service agreement for the training investment.
• What is your expected CTC, and would you accept our standard fresher package.

What actually gets freshers rejected

Very few freshers are rejected for not knowing an algorithm. They are rejected for things that are fixable in a week. The most common one is a resume claim they cannot back up, usually a technology listed to fill space. If it is on the resume it is fair game, so cut anything you touched once in a workshop. Trim the resume down to what you can defend and it becomes an asset instead of a trap.

The second is communication. Not accent or fluency, but structure: starting an answer before deciding what the point is, then trailing off. The fix is to state your conclusion in one sentence first and then explain it. The third is arguing when corrected. Say you are right, I had that mixed up, here is what I think the correct behaviour is, and move on.

• Listing skills on the resume you cannot answer two questions about.
• Reciting definitions word for word from a preparation site.
• No question at all when asked if you have questions.
• Claiming a group project as solo work.
• Saying you are flexible about location and then refusing the posting.
• Going silent for thirty seconds instead of thinking out loud.

Frequently asked questions

How long is a typical fresher interview in India?

The online assessment usually runs two to three hours and is done separately. The interview day itself is commonly one technical round of twenty to forty minutes followed by an HR round of ten to twenty minutes. Product companies and startups typically run longer, with two or three technical rounds spread across a day or across separate days.

Do I need DSA if I am targeting service based companies?

You need the basics: arrays, strings, linked lists, sorting, searching and simple recursion, plus the ability to state time complexity. Heavy dynamic programming and graph problems are rarely required at mass recruiters. If you are also applying to product companies or higher paying off campus roles, then yes, proper DSA practice is the single biggest differentiator.

What if I have a backlog or a year gap?

State it in one sentence, give the reason, and close with the resolution. For example: I had one backlog in second year in Digital Electronics, I cleared it in the next attempt, and there is nothing pending now. Do not volunteer extra detail or apologise repeatedly. Companies mostly care whether it is cleared and whether it will delay your joining.

Is it fine to say I do not know?

Yes, and it scores better than guessing confidently. Say you do not know, then offer the nearest thing you do know: I have not used that, but it sounds similar to X which I used in my project, and my guess would be it works this way. Interviewers are testing reasoning under uncertainty, which is most of the actual job.

How many companies should a fresher apply to?

On campus you are usually limited by your placement cell policy, often a one offer rule that removes you from the pool once you clear a company. Off campus there is no such limit, and applying widely is normal. Most freshers who land good roles report dozens of applications and several rejections before an offer, so treat volume as part of the process.

More guides for India