A campus placement resume is a one-page, single-column document that leads with your degree, CGPA and branch, then proves your ability through projects, internships and positions of responsibility. Every fact on it must match your college records exactly, because the placement cell and the recruiter both verify it. Build one strong master resume before the season opens, then adjust the skills and project order for each company that comes on campus.
Campus placements are a different game
During placement season, recruiters screen hundreds of resumes from a single campus in a matter of hours. Your resume needs to be instantly scannable, factually tight, and aligned to the roles on offer. Three structural things separate this from off-campus applying.
First, the shortlist is often generated before anyone reads your resume. Most drives open with hard eligibility filters — a minimum CGPA, no active backlogs, sometimes a rule on year gaps or branch. Your resume cannot argue with those filters; it just has to state the numbers clearly enough to be verified.
Second, you are compared against an unusually narrow peer set — classmates with the same degree, the same syllabus and often the same final-year project theme. The generic parts of your resume carry almost no signal. The specific parts — what you built alone, what you shipped, what you led — carry all of it.
Third, placement cells collect resumes in bulk and forward a folder of PDFs to the company, which loads the batch into an applicant tracking system. The same parsing rules that govern off-campus applications apply here too.
Work with the placement cell format, not against it
Many Indian colleges mandate a standard template — fixed heading order, sometimes a college logo or an internal reference number. Follow it. A non-compliant file often gets returned or quietly dropped from the batch.
What you control inside that template is the content: the wording of every bullet, the order of items within a section, which projects appear, which skills come first. That is where the differentiation lives. If your college mandates nothing, start from a clean single-column layout — our ATS-tested resume templates are built so the parser reads top to bottom without scrambling your dates.
Two details students routinely get wrong: name the file exactly as the placement cell asks, usually NAME_ROLLNO.pdf, and export a text-based PDF, never a phone scan — a scan is a picture to a parser, so the document reads as blank.
The one-page structure for placement season
For freshers, one page is the standard. Cut anything that does not strengthen your candidacy and keep formatting clean so it parses cleanly in any ATS. Use this section order:
- Header: Name, a phone number that works on WhatsApp, a professional email address, LinkedIn URL, GitHub or portfolio link, and your city. Nothing else.
- Education: Degree, branch, college, graduation year and CGPA. Add Class 12 and Class 10 with board and percentage — Indian recruiters still screen on these, especially the mass IT hirers.
- Technical skills: Grouped into languages, frameworks, tools and databases. No rating bars, no stars, no proficiency percentages.
- Projects: Two or three, each with a tech stack line, a live or repository link, and two or three outcome bullets.
- Internships or training: Company, role, dates and what you actually delivered. A four-week industrial training counts if you describe real output.
- Positions of responsibility: Clubs, fests, sports, NSS, student chapters — with scale attached.
- Achievements and certifications: Hackathon results, competitive programming ratings, scholarships, and certifications that map to the roles on offer.
Notice what is missing: no photograph, no father's name, no date of birth, no marital status, no permanent address, no declaration paragraph. Those belong on a government form and consume space you need for evidence. For a fuller breakdown of each block, read our guide to the fresher resume format.
The career objective is optional and usually weak. If you keep it, make it two lines naming the role and the stack you have actually worked in. If it could sit unchanged on any classmate's resume, delete it and add a third project.
What different campus recruiters scan for
Companies visiting an Indian campus are not looking for the same things, so your section order should shift. A mass IT recruiter filters on consistency; a product company filters on what you built.
| Recruiter type | What they scan first | Put this near the top | What gets you filtered out |
|---|---|---|---|
| Service-based IT (mass hiring) | CGPA, backlogs, Class 10 and 12 marks, branch | Education block with clean, verifiable numbers | Missing board percentages, unexplained year gap, undeclared backlog |
| Product companies and tech startups | Projects, GitHub activity, coding profiles, internships | Projects and technical skills, ahead of education detail | Group academic projects with no individual contribution, dead links |
| Core engineering (mechanical, civil, electrical) | Domain software, industrial training, plant or site exposure | CAD, simulation and design tools, plus training | A generic software-heavy skills list with no domain depth |
| Analytics, consulting and finance | Quantitative coursework, case competitions, Excel and SQL | Achievements and case competition results | No numbers anywhere in the bullets |
You do not need five resumes. You need one master document and the discipline to reorder two sections and swap five skills before each drive. Running the shared job description through JD Screening tells you which keywords the posting leans on, so the reordering is evidence-based rather than a guess.
Project bullets that survive the technical interview
Projects are the highest-value section on a fresher resume, and where most students undersell themselves. A line reading "Developed a library management system using Java" tells an interviewer nothing about your contribution or your decisions.
Write each project as three parts: what it does, what you specifically built, and what changed as a result. For example: "Built the authentication and booking modules of a campus event platform in React and Node.js; deployed on a free tier host and used by the technical fest to register attendees across three days." That gives the panel three threads to pull on, all of which you can defend.
Never list a technology you cannot answer a basic follow-up question about — campus interviewers pick questions straight off your skills line. And check every link the week of the drive; a private repository or an expired deployment reads as carelessness.
Positions of responsibility, with the scale attached
Clubs, fests, sports and student chapters signal ownership, but only with a number attached. "Coordinator, technical fest" is a title. "Coordinator, technical fest — led eight volunteers and ran the registration desk across a two-day event" is evidence. Use figures you can verify: team size, events run, sponsorship raised in INR, participants registered. If you are unsure, use the honest smaller number.
The honesty rules: CGPA, backlogs and gaps
Your CGPA, dates and board percentages must match your official records exactly. The college verifies them before forwarding your resume, and the company verifies them again during background checks after the offer. A rounded-up CGPA is not a formatting choice; it is the kind of discrepancy that gets offers revoked.
State your CGPA the way your institution reports it, to the same decimal places as your grade card. If your college reports a percentage instead, use the percentage and let the recruiter apply their own conversion.
If you have an active backlog, a year gap or a branch change, do not hide it. A placement cell that discovers a concealed backlog will often debar you from the rest of the season — far costlier than one missed drive. Where there is a gap, add one clear line: exam preparation, medical leave, a certification completed.
Your placement season timeline
- Eight weeks out: Build the master resume and ship one project you can talk about for twenty minutes. Find the biggest gap between your skills and the roles your campus attracts, then close it with one focused course rather than five half-finished ones — our targeted courses exist for this, and the verified certificate goes straight onto the resume.
- Four weeks out: Run the document through the free ATS resume checker to confirm every section extracts cleanly. Update LinkedIn so the headline, education and projects match the resume.
- Two weeks out: Get one round of real feedback from a placed senior or a professional reviewer, then rewrite every bullet that describes a duty instead of an outcome.
- The week of each drive: Reorder projects so the most relevant sits first, lead the skills line with the stack they named, verify every link, and export a fresh PDF under the required file name.
Mistakes that quietly cost shortlists
- Spilling onto a second page. A one-and-a-bit-page resume signals you could not prioritise. Cut the weakest project, not the margins.
- Certificate stuffing. Fifteen course certificates with no projects behind them read as consumption, not capability. Keep the three that match the role.
- Design over structure. Sidebars, icons and skill meters look impressive on screen and parse badly in bulk.
- Inconsistent dates. Pick one format, usually MM/YYYY, and use it everywhere.
- Never updating it after Day 1. If two drives pass without a shortlist, change the resume before the third. Sending the same document twelve times is not persistence.
FAQ
Should a campus placement resume be one page or two?
One page. Your verifiable history as a fresher is a degree, a few projects and possibly an internship, all of which fits comfortably on a single page. A second page usually means coursework lists or a declaration paragraph that adds nothing.
Should I include my CGPA if it is low?
On campus, yes. The placement cell already holds your grade card and most drives publish a cutoff, so omitting it reads as concealment. Strengthen everything below it instead — projects, internships, certifications — so companies without a hard cutoff have a reason to shortlist you.
Can I use the same resume for every company that visits campus?
Use the same base document, but adjust it per drive. Reordering projects and leading the skills line with the technologies named in the job description takes ten minutes and changes how the resume reads to both parser and panel.
Do I need a cover letter for campus placements?
Usually not — most on-campus drives collect only a resume through the placement portal. Keep a short, tailored one ready anyway, since it is often required for off-campus applications, referrals and internship conversions.
What if I am not shortlisted in the early drives?
Treat it as a data point about the document, not about you. Check whether the resume parses correctly, whether your education numbers are clear, and whether your projects describe outcomes or only tools. Fix the weakest section before the next drive.
Start building
Placement season rewards preparation done weeks before the first company arrives. Build your master resume properly once, keep every number verifiable, and spend drive weeks tailoring rather than rewriting. Resumere's AI resume builder has a fresher mode that turns your projects, internships and positions of responsibility into quantified, one-page, ATS-safe bullet points.
Put this into practice. Check your resume with the ATS CV Checker, then follow our Graduate CV guide for role-specific bullets — and see Resumere pricing (pay-per-use, no subscription) when you're ready to build.
