How to Prepare for a Job Interview: 2026 Campus Placement Guide

Campus placement interviews follow a consistent three-round structure, and each round needs a different type of preparation.

These three rounds are not equally weighted, and each calls for a different approach. An aptitude-heavy IT drive eliminates most candidates before anyone sees your face. A product-company coding contest is the real filter, and the technical interviews that follow are where the offer is decided. Knowing the format before you prep is half the work.

For a month-by-month timeline of everything before that final interview day, see FACE Prep’s six-month campus placement plan. This article focuses on the week and day of a specific interview.

Understand the interview format first

Campus placement formats differ by company type. Here’s the rough pattern:

Company type	Round 1	Round 2	Round 3
Mass-hire IT services	Online aptitude and coding	Technical interview	HR interview
Mid-tier IT (3–5k employees)	Aptitude test	Combined tech and HR	Final offer
Product companies and funded startups	Online coding contest	Two to three technical rounds	Culture-fit and offer

The difference in prep strategy is real. At a mass-hire IT drive, passing the online test is the dominant hurdle. The technical and HR rounds that follow are lighter and more conversational. At a product company, the online coding round is a qualifier but the technical interviews are where most candidates are screened out.

Check AmbitionBox before you begin preparing. Most companies that recruit on campus have candidate-reported interview experiences that tell you exactly how many rounds ran, what the technical round covered, and how long the process took.

Research that actually changes your answers

Company research doesn’t mean reading the company’s Wikipedia page.

Two things actually move the needle:

Match your resume to the JD. Pull the job description for the exact role. List every skill mentioned. For each skill on the JD that you have, prepare a 60-second explanation of how you’ve applied it. For any listed skill you don’t have, prepare an honest “I haven’t worked with X directly, but here’s how I’d approach learning it” response. Interviewers often test the JD verbatim.

Find the specific hiring process, not just the company brand. AmbitionBox, Glassdoor, and many companies’ own careers FAQ pages document the number of rounds, the structure of the coding test, and common technical topics. Knowing there are two technical rounds means you prepare for two, not one.

One additional note: find one current piece of company news, such as a recent product launch, a new client vertical, or a sector expansion. Not three years of corporate history. Just one specific data point you can use in a “why this company?” answer. It signals current awareness rather than rehearsed answers.

What to prepare the night before

Split the evening before into material prep and logistics prep.

Material prep

• Review your resume once, end to end. Be ready to explain every project, skill, and gap.
• Prepare a 2-minute version of your strongest project: what it does, the technical choices you made, and what you’d do differently now.
• Run through five to seven common HR questions using FACE Prep’s HR interview preparation guide.
• Don’t try to learn new topics. One evening doesn’t move competency on anything substantive.

Logistics prep

• Print 6 copies of your resume. Campus drives run larger than expected, and shared printers fail at inconvenient times.
• Gather originals and photocopies: 10th, 12th, and current degree mark sheets; a government photo ID.
• Pack a notepad and pen for working through problems on paper during the technical round.
• Confirm the venue address and the slot time. Aim to arrive 30 to 45 minutes early.

Cut off preparation at 11 PM. Fatigue makes clear articulation harder; one more hour of cramming doesn’t offset that.

Three habits that separate shortlisted candidates

Pause before answering. Three to five seconds of silence before a technical answer isn’t awkward; it signals deliberate thinking. Blurting a half-formed answer and then backtracking mid-sentence reads worse than the pause.

State your approach before you write. For coding or technical problem questions, spend 60 seconds explaining your approach before writing a single line. Name the data structure you’d use, the time complexity you’re targeting, the edge case you’d handle first. Interviewers evaluate reasoning, not just output. A well-explained approach with a minor implementation bug scores better than code written without any explanation.

Be honest about gaps. “I haven’t used Docker in a real project yet, but I understand containerisation and here’s how I’d approach picking it up” is a stronger answer than a bluffed response that collapses under one follow-up. Campus recruiters know they’re hiring freshers. Intellectual honesty is a trait they’re specifically looking for.

Questions to ask at the close

When the panel asks “do you have any questions for us?” have two or three ready. The types that work:

• Role clarity: “What does a typical first assignment look like for someone joining this team?”
• Team context: “How big is the immediate team, and what does the current tech stack look like?”
• Next steps: “What are the next steps in the process, and what’s the expected timeline?”

Salary, work-from-home policy, and leave entitlements belong to the post-offer conversation, not the interview. Asking about CTC during the interview shifts the read from “candidate who researched the role” to “candidate who’s only here for the number.”

If the interviewer asks about AI or projects

This question is appearing across campus drives more often than it did two years ago. In FY26, AI-skilled graduates made up 60% of TCS’s fresher hires, per TCS CHRO Sudeep Kunnumal at the AI Impact Summit in March 2026. The question “have you worked on any AI or ML projects?” is now showing up in technical rounds even for roles that don’t list AI skills explicitly.

If you have a project: run it through the 2-minute format from the preparation section above, covering what it does, the technical choices you made, and what you’d improve. If you don’t: say so honestly, and add “I’m currently working on X” only if that’s true.

The 2-minute project explanation is the hardest answer to deliver if you haven’t actually built something. TinkerLLM’s guided tracks let you ship a working LLM-powered app for ₹299, which gives you a concrete answer to that question instead of a vague “I’m broadly interested in AI.”

After the interview

Most candidates stop preparing the moment the interview ends. A brief follow-up note distinguishes the ones who actually wanted the role.

Within 24 hours, send a short email to the recruiter or HR contact who coordinated the drive. Three to four sentences: thank them for the time, mention one specific topic from the conversation (the project question, a technical problem you discussed), and confirm your interest in the role. Don’t ask about the outcome in the same message.

If you haven’t heard back in 10 business days, one polite follow-up is appropriate. Beyond that, treat the silence as a signal and move on to the next application. Campus drives process hundreds of candidates, and timelines slip often for reasons that have nothing to do with your performance.

For the complete preparation cycle that leads up to this point, FACE Prep’s comprehensive interview preparation guide covers the technical and aptitude rounds in more depth.