Interview Tips for Freshers: A Complete Handbook

Okay so this is something I've been wanting to write for a while because I keep seeing the same mistakes over and over again from freshers walking into interviews, and most of them are completely avoidable. I'm not talking about not knowing technical answers — that's a preparation issue and there's not much I can do about it in a blog post. I'm talking about the other stuff. The things that have nothing to do with your knowledge and everything to do with how you present yourself.

A bit of context: I've sat in on probably 200+ interviews over the past four years, across different companies, different roles, different levels. And the pattern that emerges with freshers specifically — people going for their first or second job — is remarkably consistent. They tend to make the same handful of errors, and those errors are usually what costs them the offer, not their technical skills.

Let me walk through what I've noticed, from before you even show up to the follow-up afterward.

The night before — and I cannot stress this enough — do your research on the company. Not a cursory glance at the "About Us" page. Actually understand what the company does, who their customers are, what products or services they offer, and ideally something recent they've done (a new product launch, an acquisition, a funding round, an award). When an interviewer asks "What do you know about our company?" — and they will — the difference between a prepared answer and a stammered "You're a leading technology company..." is enormous. It takes 30-45 minutes of browsing. That's it. And yet, I'd estimate that fewer than 30% of freshers I've interviewed could tell me what our company actually did beyond the industry we were in.

Also read the job description again the night before. Not just the title — the actual description. Match each requirement to something in your experience or skills. If they want "team collaboration," think of a specific example from a college project. If they want "problem-solving skills," prepare a story about a technical challenge you worked through. You're building a mental inventory of examples you can pull from during the conversation.

What to wear — this shouldn't be complicated but it trips people up because advice online ranges from "always wear a suit" to "just be yourself." Here's the practical rule: for corporate interviews (IT companies, banks, consulting firms, MNCs), wear formal attire. For men, that's a collared shirt, formal trousers, and decent shoes. A tie is optional at most Indian companies unless it's a banking or consulting firm. For women, formal Western or Indian attire — both are completely acceptable in India's corporate culture. For startup interviews, smart casual usually works fine — a clean polo or collared shirt, decent jeans or chinos, no flip-flops.

The point isn't the clothes themselves. The point is that you don't want the interviewer thinking about your appearance at all. You want them focused on what you're saying. Anything that distracts — clothes that are too casual, too flashy, wrinkled, or ill-fitting — takes attention away from your actual answers.

Arriving — get there 15 minutes early. Not 30 (that's awkward for the receptionist and makes you look overly anxious), not 5 (that's cutting it too close and you'll be flustered), and definitely not late. If it's a video interview, log in 5 minutes early, test your camera and mic, and make sure your background is clean. The number of video interviews I've been on where the candidate spends the first three minutes troubleshooting their audio is... depressingly high. Test your tech beforehand.

Now, the interview itself.

The opening question is almost always some version of "Tell me about yourself." This is not an invitation to recite your resume from Class 10 onward. I've watched freshers spend four minutes on this, starting with their school, going through their college, listing every subject they studied, and ending 90 seconds after the interviewer's eyes glazed over.

Here's a better approach: 60-90 seconds max. Start with your education (one sentence), mention your key skills or area of interest (one sentence), highlight one or two things you've done — a project, an internship, a certification — that are relevant to the role (two-three sentences), and close with why you're interested in this opportunity (one sentence). Practice this until it sounds natural, not rehearsed. Record yourself on your phone. Listen back. Cringe. Improve. Repeat.

When answering technical questions, it's okay to think for a few seconds before responding. Silence feels uncomfortable but it's infinitely better than blurting out a wrong answer. If you need a moment, say "Let me think about this for a second" — interviewers respect that. If you genuinely don't know the answer, say so. "I'm not sure about that, but based on what I know about [related concept], I'd guess [your best reasoning]." Honesty doesn't get you rejected. Making up nonsense and getting caught does.

Ask questions. When the interviewer says "Do you have any questions for us?" — and this comes at the end of almost every interview — do NOT say "No, I think you covered everything." This is an opportunity, not a formality. Good questions to ask:

• "What does a typical day look like for someone in this role?"
• "What's the team structure I'd be working with?"
• "What are the biggest challenges the team is currently working on?"
• "How do you evaluate performance for someone in this position?"
• "What's the learning and growth path for someone joining at this level?"

These questions accomplish two things: they show you're genuinely thinking about the role (not just any job), and they give you information to help you decide if you actually want to work there. An interview is a two-way evaluation, and freshers often forget that they're also evaluating the company.

Body language stuff that people overthink but genuinely matters:

Make reasonable eye contact. Not unblinking stare-into-their-soul eye contact — just look at the person when they're talking to you and when you're talking to them. In panel interviews, primarily address the person who asked the question but occasionally include the others with brief eye contact.

Handshakes — in India, this varies by context. In corporate settings, a firm (not crushing) handshake is standard when you greet the interviewer. In some contexts, a namaste is equally appropriate. Read the room. If the interviewer extends their hand, shake it. If they don't, a slight nod and a smile work fine.

Don't fidget. No clicking pens, no bouncing legs, no checking your phone (put it on silent and keep it in your pocket or bag). Nervous energy is normal — channel it into sitting slightly forward in your chair, which conveys engagement. Leaning back signals disinterest even when you don't mean it.

Smile when appropriate. You don't need to grin through a discussion about database normalization, but a genuine smile during introductions, when sharing something you're passionate about, and when the conversation turns casual creates warmth. People hire people they'd enjoy working with, and warmth is part of that equation.

The stuff that happens after the interview, which barely anyone does but really should:

Send a thank-you email within 24 hours. Keep it brief — three to four sentences max. Thank them for their time, mention one specific thing from the conversation that you found interesting or valuable, and reiterate your interest in the role. Most freshers in India don't do this, which means it stands out when someone does. I've seen hiring decisions between two close candidates tipped by a well-written follow-up email. It signals professionalism and genuine interest.

If you haven't heard back after a week, a polite follow-up is fine. One email. Not three. Not a LinkedIn message AND an email AND a call. One. "Hi [name], I wanted to follow up on our conversation last [day]. I remain very interested in the [role] and would be happy to provide any additional information. Looking forward to hearing from you." That's it. If they don't respond to that, the ball is in their court. Move on to other applications.

While you're waiting to hear back from one company, keep applying to others. The biggest mistake freshers make in their job search is putting all their emotional eggs in one basket. You had a great interview and you're sure you'll get the offer? Apply to five more places today anyway. Even if you do get that offer, having alternatives gives you negotiating use and peace of mind.

Rejection happens. It happens to good candidates, qualified candidates, well-prepared candidates. Sometimes you did everything right and they went with someone else because of budget changes, internal hiring, or simply that another candidate had one specific skill they needed more. Don't take a single rejection as a verdict on your worth. Learn what you can from each interview — what went well, what you'd do differently — and carry those lessons into the next one.

The Difficult Scenarios Nobody Prepares You For

Here's something that comes up all the time and most interview advice completely ignores: what do you do when you're asked a technical question and you have absolutely no idea what the answer is? Not "I sort of know but need to think" — I mean genuinely blank. It happens. And the wrong move is to freeze, stammer, or try to bluff your way through something you clearly don't understand. Interviewers can spot bluffing in about three seconds, and it damages your credibility for the rest of the conversation. The better approach: "I haven't worked with [that specific technology/concept] yet, but here's how I'd approach learning about it" or "I'm not familiar with that particular algorithm, but the problem it seems to solve is similar to [thing you do know], so my instinct would be to approach it this way." Showing your thinking process when you don't know the answer is sometimes more impressive than reciting a memorized answer. It tells the interviewer how you'll handle the countless situations at work where you encounter something new — which is basically every week when you're starting out.

Salary discussions trip up freshers more than almost anything else. At some point during the process — usually in the HR round — someone will ask "What are your salary expectations?" and if you haven't thought about this beforehand, you'll either lowball yourself or throw out a number that makes the HR person raise an eyebrow. Do your research. Check Glassdoor, AmbitionBox, and LinkedIn salary insights for the role and company. Know the range. When asked, give a range rather than a single number: "Based on my research, I understand this role typically pays between X and Y LPA, and I'd be comfortable somewhere in that range depending on the overall package." This shows you've done homework without locking yourself into a specific figure. And if they push for one number, go slightly above the midpoint of your researched range — you can always negotiate down, but it's much harder to negotiate up from a low anchor.

Group interviews and group discussions are a different animal entirely, and some large companies — especially during campus placement drives — use them as a screening round. The biggest mistake in group settings? Either talking too much or not talking at all. Both get you eliminated. The people who advance are the ones who make 2-3 substantive points, listen to others, and occasionally build on what someone else said rather than just waiting for their turn to speak. If you notice the group going off-topic, gently redirecting the conversation scores you points with the evaluators. "That's an interesting point, but I think we were trying to address [the original question]" — that's a leadership signal, and evaluators are specifically watching for it. What they're not watching for is the loudest person in the room. Being loud and being insightful are different things, and evaluators know the difference even if it doesn't always seem like it in the moment.

Virtual Interviews — The Stuff That's Different From In-Person

A huge percentage of first-round and even second-round interviews happen over video now, and the dynamics are different enough from in-person that it's worth addressing separately.

Your setup matters more than you think. The camera should be at eye level — not looking up your nose from a laptop on your lap, and not looking down at you from a high shelf. Stack some books under your laptop if needed. Your face should be well-lit from the front, not backlit by a window behind you (that turns you into a silhouette). Background should be clean — a plain wall is fine, a neat bookshelf works, your unmade bed does not. These sound like small details but they form the interviewer's first impression in the two seconds before you start speaking.

Audio is honestly more important than video in virtual interviews. A slightly pixelated video is fine. Choppy, echoing, or crackling audio makes the entire conversation painful and puts you at a disadvantage because the interviewer is spending mental energy trying to understand you rather than evaluating your answers. Use headphones with a built-in mic if you can — they're almost always better than your laptop's built-in microphone, which picks up every keyboard click and ambient noise. Test this before the interview, not during it.

The eye contact thing is counterintuitive on video: to make "eye contact" with the interviewer, you need to look at your camera lens, not at their face on screen. This feels unnatural because you can't see their reactions when you're looking at the camera. A decent compromise is to position the video call window as close to your camera as possible (usually at the top of your screen) so you're roughly looking in the right direction even when watching their face. And when you're making a point you want to land — look directly into the camera for that sentence. It makes a noticeable difference in how engaged you come across.

One more virtual interview thing: the awkward pause. Video calls have a slight delay, and both people end up talking over each other, then both stop, then both start again. It happens to everyone and it's annoying every time. The simple fix is to pause for a beat after the interviewer finishes speaking before you start your answer. It feels slow to you but it reads as natural to them, and it eliminates the overlap problem entirely.

If something goes wrong during a virtual interview — your internet drops, your software crashes, your roommate walks in — don't panic. Interviewers deal with this all day and they're used to it. Rejoin the call, briefly apologize, and move on. What matters is how you recover, not that it happened. I've never seen a candidate rejected because of a technical glitch. I have seen candidates rejected because they fell apart emotionally after a minor disruption and couldn't recover their composure for the rest of the conversation.

The interview process is a skill, and like any skill it improves with practice. Your fifth interview will feel dramatically more comfortable than your first. Your tenth will feel almost routine. Nobody walks into their first professional interview and nails it perfectly. Give yourself permission to be nervous, to make mistakes, and to learn from them. That's the entire point of being a fresher — you're not expected to be polished. You're expected to be genuine, prepared, and willing to grow.

Wherever you end up landing — and you will land somewhere — look back at the interview process as the first professional skill you taught yourself. It'll serve you for the rest of your career, in ways you probably can't see yet.