Campus Placement Preparation: The Complete Guide for Freshers

A complete campus placement preparation guide for freshers: rounds, service vs product companies, semester timeline, resume, HR questions and mistakes.

By InternHack Team · 2026-09-29 · 9 min read · Placements

This guide is for third and fourth year engineering students in India who want a clear picture of how campus placements work and how to prepare without wasting a semester. You will get the usual round structure, a comparison of service and product hiring, a semester-wise timeline, and a list of mistakes that cost students offers.

How a typical campus placement process works

Every college and company differs, but most drives follow the same funnel. Companies first shortlist by eligibility (branch, CGPA or percentage cut-off, backlog rules). Then come rounds, each of which eliminates candidates.

1. Online assessment (OA). Usually the first and largest filter. It combines aptitude (quantitative, logical reasoning, verbal) with coding, or with technical MCQs. Product companies weigh coding heavily. Service companies often weigh aptitude and basic programming.

2. Technical interview. One to three interviews covering your projects, core subjects (DSA, DBMS, OS, OOP, networks), and sometimes live coding. For service companies, questions tend to be at the level of fundamentals and basic programs. For product companies, expect problem solving with follow-ups.

3. HR or managerial round. Checks communication, motivation, flexibility about location and role, and basic fit. It is not a formality: candidates do get rejected here for weak answers, inconsistency with the resume, or attitude problems.

Some companies add a group discussion, a communication assessment, or a case-based round. Check the process for each company in advance through your placement cell and seniors.

Service vs product companies: what changes for you

Neither track is "better". Service companies are a reliable route for most students and a good place to learn. Product companies are more selective and reward strong DSA. A practical strategy is to prepare for both: aptitude and communication keep the service door open, while DSA opens the product door, and the overlap in programming fundamentals is large.

What the big mass-recruiter tests look like, in general terms

Tests run by large IT services firms, such as TCS NQT, Infosys and Wipro style assessments, are usually described in general terms like this. Exact sections, durations, question counts and cut-offs change between years and hiring tracks, so always read the latest official notice from the company and your placement cell before you rely on any pattern.

In broad terms, these tests tend to include:

• Numerical and quantitative ability. Percentages, ratios, time and work, time-speed-distance, profit and loss, averages, permutations and probability at a basic level.
• Reasoning ability. Series, coding-decoding, blood relations, seating arrangements, puzzles, data interpretation.
• Verbal ability. Reading comprehension, grammar, sentence correction, vocabulary.
• Programming or coding section. Typically one or a few problems on arrays, strings, loops and simple logic, in a language of your choice. Some tracks add a harder coding problem for higher-paying roles.
• Technical MCQs or fundamentals. Basic questions on programming concepts, databases or networking.

Two lessons hold across these tests. First, speed matters: aptitude sections are timed tightly, so practise under a timer. Second, sectional or negative marking rules may apply, so learn the rules before guessing. For structured aptitude practice, use the aptitude section.

Semester-wise timeline for 3rd and 4th year

Start earlier than feels necessary. A steady start in the fifth semester is much easier than a panic in the seventh.

Semester 5 (start of 3rd year, second half)

• Pick one language and become comfortable writing programs in it. Java, Python and C++ are all fine.
• Begin DSA from basics: arrays, strings, recursion, sorting, hashing. The DSA foundations track is a sensible starting point.
• Start one aptitude topic a week, about 30 minutes a day.
• Build or extend one real project, and put it on GitHub.

Semester 6 (end of 3rd year)

• Continue DSA: linked lists, stacks, queues, trees, graphs, basic DP. Practise in the DSA section.
• Learn core subjects: DBMS and SQL, OS, OOP, computer networks. Use the interview guides and the SQL practice.
• Apply for summer internships. An internship gives you interview stories and sometimes a pre-placement offer. See open internships.
• Draft your first resume and get it reviewed.

Summer before 4th year

• Do an internship if you have one, or a serious project plus open-source work through the open source page.
• Do a full revision pass of DSA weak spots.
• Take your first timed mock online assessments.

Semester 7 (main placement season)

• Finalise the resume and check it with the ATS score checker.
• Do timed mock tests for aptitude and coding every week.
• Practise mock technical and HR interviews with friends or seniors.
• Register for every drive you are eligible for, and read each job description for skills that matter.
• Keep a tracker of company, date, round status and preparation notes.

Semester 8

• Continue off-campus applications through external jobs if you do not have an offer, or if you want a better one.
• Focus on interview feedback and fix repeat weak points.
• If you already have an offer, keep your fundamentals fresh and consider a stretch attempt at product companies where the rules of your college allow it.

The placement prep hub gathers many of these resources in one place, and the roadmaps can help you sequence topics by role.

Building a resume that gets shortlisted

Your resume decides whether you reach the interview. Keep it to one page, and write in a plain single-column layout so applicant tracking systems parse it correctly.

Sections that work for freshers, in order: education, skills, projects, internships or experience, achievements, and links to GitHub and LinkedIn. Include your CGPA if it helps you clear cut-offs.

For projects, use short bullets with what you built, the stack, and one concrete result: "Built a REST API with Node.js and PostgreSQL supporting JWT auth and pagination". Do not invent numbers. If you list a technology, be ready to answer questions about it, because interviewers will pick the line you understand least.

More detail is in our guide to an ATS-friendly resume for freshers.

Preparing for the technical interview

Prepare in this order of priority:

1. Your own resume. Every project, skill and claim is fair game.
2. Programming fundamentals in your chosen language: data types, OOP, exception handling, memory basics.
3. DSA at an easy to medium level. Even service companies commonly ask arrays, strings, sorting and searching. Product companies go further. For complexity questions, see Big O notation with interview examples.
4. Core subjects. DBMS (normalisation, joins, transactions), OS (processes, threads, deadlocks), networks (TCP/IP, HTTP), and OOP.
5. Thinking aloud. If you are stuck, say what you have tried. Interviewers respond well to structured reasoning.

If you want a compact schedule for the DSA and fundamentals side, our 90-day preparation plan works equally well for placements.

Common HR questions and how to answer them

You do not need scripted answers, but you do need prepared thinking. Commonly asked questions include:

• Tell me about yourself. Give a 60 to 90 second summary: current education, one or two strengths backed by a project or internship, and why this role. Do not read out your resume line by line.
• Why this company? Mention something specific and true: its products, work culture you have researched, or the kind of work in the role. Generic praise sounds hollow.
• What are your strengths and weaknesses? Choose real strengths with an example. For a weakness, name something genuine that you are actively improving, and say how.
• Where do you see yourself in five years? Talk about growth in skills and responsibility, not a job title.
• Are you willing to relocate or work in shifts? Be honest. If you have a real constraint, say so calmly. A flat refusal without context can end the process.
• Tell me about a failure or a conflict. Use a short structure: situation, what you did, the result, and what you learned. The STAR method guide and the behavioral interview page walk through this.

Also prepare two or three questions to ask them, such as what onboarding looks like or what a new joiner works on in the first few months.

Mistakes that cost students offers

• Starting late. Beginning serious preparation two months before placements almost always leaves gaps in either aptitude or coding.
• Ignoring aptitude. Strong coders sometimes fail the first round because they never practised timed aptitude sections.
• Only doing theory. Watching videos without solving problems in a timed setting does not build test performance.
• Resume claims you cannot defend. Listing technologies you barely used invites questions you cannot answer.
• Treating service companies as backup only. Casual preparation for these tests can still fail you. Take them seriously.
• Poor communication. Rambling, long silences, or weak English fluency can decide close calls. Practise speaking answers aloud.
• Missing logistics. Overlooking registration deadlines, document requirements, or slot timings is a surprisingly common way to lose an opportunity.
• Giving up after a rejection. Most students face several rejections. Note what went wrong, adjust, and go to the next drive.

Day-of tips for online tests and interviews

For an online test, check your internet, laptop charge and browser setup the day before, keep ID handy, and read every instruction on proctoring rules. Attempt easy questions first in each section, watch the clock, and do not leave the coding section for the last five minutes.

For interviews, dress neatly, join early, keep your resume open, and stay calm when you don't know something. Saying "I'm not sure, but here is how I would reason about it" is better than a confident wrong answer.

FAQ

How early should I start campus placement preparation?

Start in the second half of your third year, about 12 to 15 months before placements. That gives time for DSA, aptitude, projects and at least one internship. If you are starting later, focus on aptitude, core programming and your resume first.

What is the difference between service and product company hiring?

Service companies hire in large batches and test aptitude, basic coding and communication. Product companies hire fewer candidates and test problem solving and DSA more deeply. Preparing aptitude plus DSA covers both types.

Do I need DSA for TCS, Infosys or Wipro style tests?

Usually you need programming basics and easy to medium problems on arrays, strings and simple logic, plus aptitude. Higher-paying tracks at some companies test harder coding. Check the latest official pattern, since it changes between hiring cycles.

What if I have a low CGPA or a backlog?

Many companies set eligibility cut-offs, so first check each company's criteria with your placement cell. Where you are ineligible, use off-campus hiring, internships and referrals. Strong projects, skills and clear communication can still open opportunities.

Can I apply off-campus if I miss campus placements?

Yes. Many companies hire freshers off-campus through career pages, referrals and job portals. Keep your resume updated, continue DSA and aptitude practice, and apply consistently to roles that match your skills.