Article

Most fresher interviews in India are lost in the first five minutes, not because you lack skills, but because you freeze on questions everyone knew were coming. The interviewer asks "Tell me about yourself", and you either recite your resume line by line or go blank. That is fixable, because the questions asked at Indian companies, whether it is a TCS or Infosys mass-recruitment drive, a Bangalore startup, or a product MNC, are remarkably predictable.

This guide walks through the questions you will actually face as a fresher, with full sample answers written out for someone whose experience is projects, internships, and coursework, not years on the job. Read the answers, then rewrite them in your own words. An answer that sounds memorised is worse than a rough one that sounds like you.

One thing before we start: interviewers hiring freshers are not expecting a finished professional. They are checking whether you can think, whether you will show up and learn, and whether you are pleasant to work with. Keep that in mind and half the pressure disappears.

The typical Indian interview rounds

Knowing the sequence lets you prepare for each stage instead of treating it as one blur.

• Aptitude or online test. Common at IT services companies and campus drives. Quantitative aptitude, logical reasoning, verbal ability, and often a basic coding section. This is an elimination round, so practise timed mock tests, because the pressure is speed, not difficulty.
• Technical round. You are asked about your projects, core subjects, and given problems to solve. For software roles expect data structures, a coding question, DBMS, OOP concepts, and questions dug straight out of your resume. For non-tech roles this becomes a domain or case round.
• HR round. The behavioural and personality questions, the "tell me about yourself", strengths and weaknesses, salary, relocation, notice period. Do not treat this as a formality. Freshers get rejected here for sounding arrogant, uninterested, or dishonest.
• Managerial round. Sometimes merged with the technical or HR round. The hiring manager checks fit, attitude, and whether you understand what the role involves day to day.

Startups compress all of this into two or three conversations and move fast. Large IT services firms run structured, high-volume drives. Product MNCs like a payments or e-commerce company run multiple technical rounds with a real coding bar. Prepare for the type of company, not a generic checklist.

The classic HR questions, answered

These five questions show up in nearly every fresher HR round. Learn the structure behind each, then rewrite the samples in your own words.

"Tell me about yourself"

This is the opener in almost every interview, and it sets the tone. Do not narrate your biography from Class 10. Use a simple structure: present, then background, then why you are here.

• Present: who you are right now, in one line.
• Background: two or three things that shaped your skills, mostly projects, internships, and relevant coursework.
• Why you are here: what you want next and why this role fits.

Here is a full sample answer for a final-year engineering student applying for a software developer role.

"I am a final-year Computer Science student at a college in Pune, graduating in 2026. Over the last two years I have focused on backend development. My main project was a food-delivery web app where I built the order and payment flow using Node.js and MySQL, and I handled the database design for around fifteen tables. During my internship at a small SaaS startup last summer, I worked on their reporting module and fixed a set of bugs that were breaking exports for larger accounts. That experience is where I learned to read someone else's code and work with a real team. I am applying here because your team works on backend systems at a scale I have only read about, and I want to build under people who have done it before."

That is roughly forty-five seconds. Notice it is specific, it names technologies, it mentions a real outcome, and it ends by connecting to the company. Rewrite it with your own details and rehearse aloud until it is smooth but not robotic. The structure fits non-technical roles.

"Why should we hire you?"

The interviewer is asking you to make their decision easy. Do not say "because I am hardworking and a quick learner", every candidate says that. Match your strengths to what the role needs, and back each claim with proof.

Sample answer for a fresher data analyst role.

"You are hiring someone who can take messy data and turn it into something a business person can act on. In my final-year project I pulled six months of sales data, cleaned it in Python, and built a dashboard that showed which product categories were dropping. I also did a two-month internship where I automated a weekly report that used to take the team half a day. So I already know the boring, careful part of the job, cleaning and validating data, not just the exciting charts. I am a fresher, so I will need guidance, but you will not have to teach me the basics of the work."

The honesty at the end is deliberate. Admitting you are a fresher while showing you have done real work makes you more credible, not less.

"What are your strengths and weaknesses?"

For strengths, pick two or three that are relevant and prove each with a short example. Saying "communication" means nothing on its own. Saying "I explained a technical bug to a non-technical client during my internship and they understood it" is a strength with evidence.

The weakness question trips up freshers the most. Do not give a fake weakness like "I am a perfectionist" or "I work too hard", interviewers have heard it a thousand times and it reads as dishonest. Give a real, minor weakness and then show what you are doing about it.

Sample weakness answer.

"Earlier I used to take on too much and try to do everything in a group project myself, which meant I burned out and my teammates felt left out. During my last project I forced myself to delegate and I started using a shared task board so everyone owned a part. It is still something I watch, but I have got much better at trusting the team."

That answer shows self-awareness and improvement, which is what the question tests. Never name a weakness that is core to the job, do not tell a coding interviewer you are weak at logic.

"Where do you see yourself in 5 years?"

Interviewers ask this to check ambition and whether you are likely to stay. They are not holding you to a literal plan. Show that you want to grow within the kind of work the company does, and avoid two traps: sounding like you will leave for higher studies or a different field, and sounding so vague that you clearly have not thought about it.

Sample answer.

"In five years I want to have grown from writing code that others review to being someone whose judgement the team trusts, maybe leading a feature or mentoring the next batch of freshers. I am not fixed on a title. What matters to me is going deep in backend engineering rather than jumping around. If I am solving harder problems in five years than I am today, I will consider that good progress."

If you genuinely plan higher studies soon, do not lie, but do not volunteer it in a way that ends the interview. Focus on what you will contribute in the near term.

"Why do you want to work here / this role?"

This question exposes candidates who applied everywhere without thinking. Spend fifteen minutes before the interview reading their website, their product, recent news, and what the role involves. Then connect one real thing about them to your own interest.

Weak answer: "Your company is a great place to grow and has a good reputation." This fits any company and shows nothing.

Sample strong answer.

"Two reasons. First, the role is backend-heavy and that is exactly the direction I have pushed myself in through my projects, so I would be building on skills I already enjoy rather than starting over. Second, I read that your team recently moved to a microservices setup. In college I only worked on monolithic apps, so learning how a real system is broken into services, from people who have actually done it, is something I genuinely want. I would rather learn that here than read about it."

Specificity is the whole game. One concrete detail about the company beats three paragraphs of praise.

The STAR method for behavioural questions

Behavioural questions start with "Tell me about a time when" or "Give me an example of". Freshers ramble here because they have no framework. Use STAR: Situation, Task, Action, Result. It keeps your answer tight and makes sure you land on an outcome.

• Situation: set the scene briefly.
• Task: what needed to be done.
• Action: what you specifically did, use "I", not "we".
• Result: what happened, ideally with a number or a clear outcome.

Sample answer to "Tell me about a time you handled a conflict in a team."

"During our final-year project, two of us wanted to use one framework and two wanted another, and we lost almost a week arguing (Situation). We had a submission deadline and no code was getting written (Task). I suggested we stop debating and each pair build a tiny prototype of the login feature in their preferred framework over two days, then decide based on which was actually faster to work with (Action). The prototype made it obvious, one option had far less setup, so the team agreed without any bad feeling and we shipped on time (Result)."

For a fresher, project and internship stories are perfectly acceptable STAR material. You do not need corporate experience. Prepare three or four flexible stories in advance, one about conflict, one about a mistake you fixed, one about a tight deadline, one about learning fast. Most behavioural questions can be answered by reshaping these.

Salary expectations for a fresher

This makes freshers nervous, but the approach is simple. For a campus placement or a mass IT services drive, the package is usually fixed, so just accept the standard offer. For an off-campus role at a startup or mid-size company, research what freshers in that role and city earn, then give a range rather than a single number.

Sample answer when asked "What are your salary expectations?"

"Since I am starting out, my priority is the role and the learning, and I trust that a company like yours pays fresher salaries fairly for the market. Based on what I have seen for similar roles in this city, something in the range of X to Y lakhs per annum would work for me, but I am open to discussing it based on the overall offer and growth."

Never quote a random high number, and never say "whatever you think is fine", which signals you have not thought about your worth. If you have a competing offer, it is fine to mention it politely, but do not invent one, it backfires if they ask for details.

"Do you have any questions for us?"

Saying "no, I think you covered everything" is a soft rejection of your own candidacy. Always have two or three questions ready. Good questions show you are thinking about the actual job, not just getting hired.

Ask things like these.

• "What does a typical first six months look like for a fresher in this role?"
• "How is performance measured for someone at my level in the first year?"
• "What is the biggest challenge the team is working on right now?"
• "Is there a mentor or buddy system for new joiners?"

Avoid asking only about leave, salary hikes, or work-from-home in the first interview, it leaves a poor impression when it is the only thing you are curious about. Ask one thing about the work and, if the moment is right, one thing about growth or how success is measured.

How to handle a question you cannot answer

You will hit questions you do not know, especially in technical rounds. How you react matters more than the gap itself. Do not bluff, experienced interviewers spot it instantly and it costs you their trust.

Try this instead. Think out loud, say what you do know, and attempt to reason toward the answer. If you are genuinely stuck, be honest and show curiosity.

Sample response to a technical concept you have not studied.

"I have not worked with that directly, so I would be guessing if I said I knew it well. From the name and what I do know about related concepts, my guess is that it works something like this, and then explain your reasoning. If I am wrong I would like to know the right answer, because I will read up on it tonight either way."

That answer turns a gap into evidence of honesty and hunger to learn, which is what a fresher is really judged on. Never argue that the question is unfair, and never go silent for long, narrate your thinking so the interviewer can follow you.

Virtual and online interview etiquette

A large share of fresher interviews now happen on video, over platforms your college or the company sets up. The technical basics are non-negotiable and freshers lose offers to them all the time.

• Connection: use the most stable internet you have and keep a mobile hotspot ready as backup. Join five minutes early. If your connection drops, rejoin calmly and apologise briefly, do not panic.
• Camera: keep it on unless told otherwise, position it at eye level so you are not looking down at the interviewer, and look at the camera when you speak, not at your own face on the screen.
• Lighting and background: sit facing a window or light source, not with a bright window behind you that turns you into a silhouette. A plain wall behind you is best. A tidy, quiet room signals you take this seriously.
• Audio: use earphones with a mic if you can, they cut background noise. Find a quiet room and tell your family you have an interview so nobody walks in.
• Setup check: test the camera, mic, and the meeting link at least fifteen minutes before. Keep your resume open in another tab and a notepad and pen handy.

Dress the same as you would in person, at least on top. Interviewers notice when a candidate treats a video call as casual.

Body language and first impressions

The first thirty seconds shape how the interviewer reads everything you say afterwards, in person and on video.

• Greet with a genuine smile and, in person, a firm but not crushing handshake if one is offered.
• Sit up straight, do not slouch or lean back like you are relaxing at home.
• Make steady eye contact, not a stare, and glance at all interviewers if there is a panel.
• Keep your hands calm. Some gesturing is natural, but do not fidget, click a pen, or touch your face constantly.
• Speak at a measured pace. Nervous freshers rush. Pausing for a second before answering makes you sound thoughtful, not slow.

Enthusiasm is underrated. Interviewers hiring freshers often pick the candidate who seems genuinely excited over a slightly more skilled one who looks bored.

The most common mistakes freshers make

• Not researching the company. Walking in without knowing what they do is the fastest way to fail the "why us" question.
• Memorising answers word for word. It sounds robotic and collapses the moment the interviewer changes the wording. Learn the structure, not a script.
• Lying on the resume. If you put a skill on paper, expect to be tested on it. Freshers get caught claiming projects they barely touched.
• Badmouthing college, professors, or a past internship. It signals you will do the same to this company later.
• Being unable to explain your own project. This is the number one technical failure. You must know why you made each choice, what was hard, and what you would do differently.
• One-word answers or endless rambling. Aim for answers that are complete but not exhausting, usually thirty to sixty seconds.
• Neglecting the follow-up. A short, polite thank-you note after the interview is rare among freshers and quietly sets you apart.

Your next steps

Use this as a checklist in the days before any fresher interview.

1. Write and rehearse your "tell me about yourself" out loud until it is smooth, around forty-five seconds.
2. Prepare four STAR stories from your projects and internships, covering conflict, a mistake, a deadline, and fast learning.
3. Be able to explain every line on your resume, especially each project, why you built it, what was hard, and what you would improve.
4. Research the company for fifteen minutes and prepare two or three specific questions to ask them.
5. Draft honest answers for strengths, weaknesses, five-year plan, and salary, then say them aloud so they sound natural.
6. For online interviews, test your internet, camera, mic, lighting, and the meeting link the day before and again fifteen minutes prior.
7. Revise your core subjects and practise a few coding or aptitude problems if the role demands them.
8. Sleep well, arrive or log in early, and remember they already liked your resume enough to call you.

You do not need to be perfect. You need to be prepared, honest, and clearly interested in the work. Do the preparation above and you will walk in as one of the calmer, sharper freshers in the queue, which is exactly where offers come from.