Campus Placement Resume Checklist (2026): 35 Points TPOs and Recruiters Check

Placement season compresses months of hiring into a few weeks, and the resume is the only part of it you control completely. The placement cell filters on data, the company's HR skims for seconds, and the interviewer reads it while you sit down. This checklist has 35 points across header, education, projects, internships, skills, positions of responsibility and formatting, plus a sample one-page resume, the differences between mass-recruiter and product-company versions, and an eight-week timeline.

How placement-season screening actually works

The sequence is close to universal, and each stage looks at the resume differently.

1. The TPO shortlist. The placement office receives the company's eligibility criteria: branches, minimum CGPA, Class X and XII percentages, backlog rules, sometimes a gap-year rule. This is a spreadsheet filter on the data you registered with the placement cell. Your resume is not read yet, but it will later be compared against this data.
2. The company's own screen. Shortlisted resumes go to the company as a merged PDF or through its portal. Mass recruiters push them into an applicant tracking system and re-check eligibility fields. Product companies and core-engineering firms have an engineer or HR person read the projects and skills and cut the list further.
3. Aptitude and coding tests. Online, usually the same day or the day before. The resume plays no role here, but the shortlist size after this round decides how carefully the next interviewer reads it.
4. Technical and HR interviews. The interviewer has your resume open. Every project bullet is a potential question and every listed skill can be tested. Anything you cannot defend for ten minutes is a liability.

So the resume has to survive an ATS parser, a two-second human skim, and a twenty-minute interrogation. The checklist is organised around those three tests. For the fundamentals of structure first, read the resume format for freshers.

The one-page placement resume layout most colleges expect

Almost every placement cell in India expects the same single-column, one-page layout, and many enforce it through a mandated template.

• Header. Name, phone, email, city, LinkedIn, GitHub or portfolio link. Two lines.
• Education. Degree with CGPA, then Class XII and X with board and percentage. Three lines.
• Projects. Two or three, each with title, stack and two or three bullets; the largest section.
• Internships / training. One or two entries with dated bullets.
• Technical skills. Grouped by type, one block.
• Positions of responsibility and achievements. Three to five lines.
• Certifications and courses. One or two lines; optional.

Most mandated layouts have no summary or objective, and it is fine to leave it out. If your college allows it, a two-line summary in the style of our career objective guide can help for product-company drives, where the reader is an engineer rather than a filter.

The 35-point checklist

Header (5 points)

• 1. Full name as printed on your marksheets, largest text on the page. The TPO matches resumes to registration data by name; a nickname creates a mismatch.
• 2. One phone number and one professional email. A firstname.lastname address, not the college email that expires at graduation or a handle from Class IX.
• 3. City and state only. A full postal address wastes a line and tells the recruiter nothing they need before an offer.
• 4. LinkedIn URL customised, GitHub only if it is alive. Three or more real repositories with READMEs help for software roles. An empty GitHub hurts more than no link.
• 5. No photo, date of birth or father's name unless the company's form asks. Those fields belong on a biodata, and they cost a third of the page.

Education (6 points)

• 6. Degree, branch, college, university and batch year in that order. "B.Tech Information Technology, Vindhya Institute of Technology (RGPV), Bhopal, 2023–2027". Recruiters filter by branch, so spell it out.
• 7. CGPA to one decimal, or percentage per your university's conversion, never both and never rounded up. A 7.96 written as 8.0 is caught when the TPO forwards marksheets, and the drive is over for you.
• 8. Class XII and Class X with board, year and percentage. Mass recruiters set cutoffs on these. Do not drop them to save space.
• 9. Backlogs stated truthfully. If none, do not write "no backlogs"; it invites the question. If active, the TPO data shows it, so state the count and clearance plan in one line.
• 10. Relevant coursework only to fill a gap. "Operating Systems, DBMS, Computer Networks" is worth a line for core CS drives if your projects do not already show those areas.
• 11. Gap year, lateral entry or branch change explained in one clause. "Lateral entry from Diploma (2023)" or "Gap year 2022–23 for JEE preparation". Do not leave it for the interviewer to find in the dates.

Projects (6 points)

• 12. Two or three projects, most impressive first, not most recent first. The first project gets the most interview time, so it should be the one you know best.
• 13. Each project has a title, a tech stack line, a one-line problem statement and two or three result bullets. A paragraph about what you learned is not a project entry.
• 14. At least one number per project. Users, records, test cases, response time, accuracy. "Built a hostel-mess feedback app" is a claim; "used by 800 students across 4 hostels" is evidence.
• 15. Your role in team projects is explicit. "Built the REST API layer and the MySQL schema" rather than "worked on backend". The truth comes out in the second question.
• 16. A live link or repository link for at least one project. Product companies open it. A repository with a README and screenshots is the minimum.
• 17. No unmodified tutorial clones. A "Netflix clone" from a YouTube series is recognised on sight. If you extended one substantially, describe the extension.

Internships (4 points)

• 18. Company, role, city and month–year range on the entry line. Missing months on an eight-week internship makes it look longer than it was.
• 19. Bullets describe what you delivered, not what the company does. Nobody needs a line about the company being a leading provider of anything.
• 20. Training programmes and virtual internships labelled as such. A four-week online course with a certificate is "Training", not "Internship". Misrepresenting it loses offers at document verification.
• 21. No internship, no empty heading. Use the space for a third project, an open-source contribution or a substantial technical responsibility.

Skills (4 points)

• 22. Grouped by type. Languages / Frameworks and tools / Databases / Core concepts. A flat list of fifteen words looks padded.
• 23. Only skills you can be questioned on for ten minutes. Listing Kubernetes after one tutorial is how a friendly interview turns hostile.
• 24. No "MS Office", "communication skills" or "teamwork" in a technical skills block. They dilute the real skills and mark the resume as generic.
• 25. Every listed skill appears in a project or internship. A skill with no evidence elsewhere on the page should be backed up or removed.

Positions of responsibility and extracurriculars (4 points)

• 26. Each PoR states scope. "Technical Head, Coding Club" means little; "Technical Head, Coding Club: ran 6 contests for 300+ participants" means something.
• 27. Hackathons, contest ranks and paper presentations with level and year. "Smart India Hackathon 2025, national finalist" is worth a line. "Participated in a hackathon" is not.
• 28. Hobbies in one line or not at all. Nobody shortlists on "reading and music". State-level sport or a performing-arts credential shows commitment and can stay.
• 29. Nothing from school unless it is national level. Class X quiz prizes and school captaincy are out by final year.

Formatting (6 points)

• 30. One page, A4, margins between 0.5 and 0.75 inch, body text 10.5 to 11 point. Anything smaller is unreadable when the TPO merges resumes at reduced scale.
• 31. Single column, no layout tables, icons, skill bars or colour blocks. Parsers read single-column text reliably and mangle the rest; our ATS resume guide explains what breaks.
• 32. Consistent date format and tense. "May 2026 – Jul 2026" everywhere; past tense for finished work, present for ongoing.
• 33. File named Firstname_Lastname_Branch_Year.pdf, exported as PDF, under 1 MB. Not a Word file, not a screenshot, not "resume_final_v3.pdf". Placement cells sort by file name.
• 34. Zero spelling errors, checked by two other people. Spell-check misses "form" for "from". A senior placed last year and a friend from another branch are the readers you want.
• 35. Identical facts on the TPO portal, the company form, Naukri and LinkedIn. Different CGPAs or internship dates across platforms read as dishonesty, whichever one is right.

Print it, tick it: the TPO-ready pass

Screens hide problems. Print the resume on plain A4 at 100 percent and tick each of the 35 points with a pen against the printed sheet. Why this beats a laptop:

• Margins, font size and page overflow are visible at the size the interviewer will hold it.
• You read slower on paper, which is how you catch "Bhopal" spelt two ways.
• The TPO's merged PDF is often printed at reduced scale for panel interviewers. If 10.5 point looks small on your print, it will be worse on theirs.
• Ticking forces a yes-or-no answer. "Mostly done" is a no.

Then hand the sheet and the checklist to a senior who sat through last year's drives and ask them to tick it independently; where you disagree, they are right. After the paper pass, check your resume's ATS score free to confirm the parser reads your name, education and skills the way a human does.

Sample one-page placement resume (B.Tech IT, 2027 batch, Bhopal)

A final-year student from a Tier-2 private college affiliated to RGPV, sitting for both mass-recruiter drives and a product-company drive. Two projects, one internship, a hackathon credential and a grouped skills block, with every point in the checklist applied.

For a software-role version with a summary line and deeper project bullets, see the software engineer resume guide. Lay it out in one of the minimal single-column designs in resume templates; if your college insists on a Word file, the Word resume format guide keeps it parser-safe.

Mass recruiter vs product company vs core engineering: what changes

Most students sit for all three kinds of drives, and one resume does not fit all three. Keep the facts identical and change the emphasis.

Keep one master file and export two variants: a broad one for mass-recruiter and core drives, and a project-heavy one for product companies. When a drive asks for a cover letter, as some product companies and consulting firms do, the cover letter guide has a placement-specific structure.

10 reasons placement resumes get rejected

1. A CGPA that does not match the marksheet. Ends the candidacy at document verification.
2. Unexplained or hidden backlogs. The TPO data shows them; omitting them looks like concealment.
3. Two pages. The second page is cut off in the merged file or not read.
4. Project bullets that describe the technology, not the result. "Used React and Node.js to build a web application" says nothing about the application.
5. A skills list the candidate cannot defend. Discovered in the first five minutes of the technical round.
6. A generic objective. "To work in a challenging environment that offers growth" wastes the most valuable line on the page.
7. An unprofessional email address. Recruiters notice, and some mention it in feedback to placement cells.
8. Different data on the TPO form and the resume. Internship dates, percentages, even the spelling of the college name.
9. Wrong file format. A Word document that reflows on the recruiter's machine, or a JPEG that no parser can read.
10. A third of the page on personal details. Photo, date of birth, father's name, permanent address: none of it helps, and it pushes projects below the fold.

Timeline: what to fix 8 weeks, 4 weeks and 1 week before drives

8 weeks before

• Pick the project that will lead your resume and finish it: deploy it, write the README, collect one usage number.
• Write the first full draft using the layout above; our how to write a resume guide has the bullet formula.
• Get feedback from two seniors placed last year, one at a mass recruiter and one at a product company.
• Fix your LinkedIn and GitHub so the links on the resume lead somewhere worth visiting.

4 weeks before

• Split into the two variants, broad and project-heavy, with every fact identical.
• Run both through the free ATS checker and fix anything the parser misreads.
• Submit to the placement portal in the mandated format and confirm the data matches your registration record.
• Write two likely interview questions for every bullet and rehearse the answers aloud.
• Set your Naukri headline to match the resume, using the patterns in resume headline for Naukri, so off-campus applications tell the same story.

1 week before

• Freeze the content. Last-minute additions are the ones you cannot defend.
• Export the final PDFs with the correct file name and check them on a phone and a different laptop.
• Print five copies of each variant on plain white A4 for panel interviews.
• Prepare a two-minute spoken walkthrough of the resume, ending on the lead project.
• Read the job description shared for each drive and note which of your bullets map to it.

Frequently asked questions

Should I put my CGPA on the resume if it is below 7?

Yes. The TPO already has it, company forms ask for it, and leaving it off makes recruiters assume it is worse than it is. Write it to one decimal and put your strongest project directly below education so the eye moves on to something you control. If a drive's cutoff is above your CGPA, no resume will get you shortlisted; spend your effort on drives where you are eligible.

Can a placement resume be two pages?

Not for campus drives. TPOs merge hundreds of resumes into one file, mass recruiters skim for seconds, and many college templates are hard-coded to one page. If you have more than a page of material, cut the weakest project, school-level achievements and the hobbies line until it fits.

Do TPOs actually read the resume, or just the CGPA?

The first shortlist is usually a spreadsheet filter on CGPA, backlogs and branch. After that, the placement cell and the company's HR do read the resume, especially for product-company and core-engineering roles where the shortlist is small. Inconsistencies between your TPO data and your resume get noticed at this stage.

Should I use the college's mandatory resume template?

If the placement cell mandates a template for its portal, use it there without argument. Keep a second, cleaner one-page version for company forms, off-campus applications and Naukri, with every fact identical across both.

What if I have no internship?

Replace the internship section with a lead project that has a live link, an open-source contribution, or a substantial responsibility such as running a technical fest's website. Do not leave an empty heading and do not present an online course as an internship. Mass recruiters weigh aptitude scores and communication more than internships; product companies care about what you built.

Should I write expected CTC or preferred location on a placement resume?

No. The CTC is fixed by the company for the drive and the location is assigned after the offer. Both lines waste space and suggest you have not read the job description shared by the placement cell.

Is a career objective needed on a placement resume?

It is optional. If you include one, keep it to a single line naming the role and field, such as software development or core electronics. A two-line summary stating your branch, year, two skills and your best project does the same job with more information. Never use a generic objective about growth and challenging environments.

Related guides & tools

• Free ATS score checker — confirm the parser reads your resume correctly
• Resume format for freshers — the one-page structure in detail
• Software engineer resume — for product-company drives
• ATS resume — what breaks parsers and how to avoid it
• Career objective for resume — if your template requires one
• Resume headline for Naukri — for off-campus applications
• Cover letter — for drives that ask for one
• Resume templates — single-column designs that print cleanly