Placement shortlisting starts with a filter, not a reading. Companies set a cut-off on branch, year and CGPA, and someone runs down a stack of resumes checking those three things. Everything else only matters once you clear that pass.
So the format has one job before it has any other: make the eligibility facts impossible to miss, then give the interviewer something to ask about.
What goes where
-
01
Header
Name, branch and year of passing, phone, email, GitHub or LinkedIn.
-
02
Academic record
Degree with CGPA, Class 12 and Class 10 with percentages. Include the scale on every result.
-
03
Technical skills
Grouped by languages, frameworks and tools. Only what you can be tested on in a technical round.
-
04
Projects
Two to four with your specific contribution and one measurable outcome each.
-
05
Internships
What you shipped, not what the team shipped.
-
06
Certifications and coursework
NPTEL, cloud fundamentals, relevant electives.
-
07
Achievements and responsibilities
Contest ranks, hackathons, positions held in clubs and fests.
Write for the technical interview
Interviewers pick questions off your resume. Anything you list is fair game, so remove technologies you touched once in a tutorial, and keep the ones you can defend for ten minutes.
For each project, be able to say why you chose the approach, what broke, and how you fixed it. If you cannot answer that, the project is not ready to be on the page.
Numbers a student actually has
You do not need revenue figures. Use the numbers already sitting in your work: records processed, users in a trial, dataset size, accuracy, page load time, hours of manual work removed, team size, contest rank out of a field.
One resume, small edits per company
Keep a single base resume and change the skills order and project order to match each job description. Mirror the vocabulary of the posting, since both the portal and the reader match on the words used there.
What gets a resume rejected at the filter
- CGPA buried in a paragraph instead of aligned in the education block.
- A skills list so long it is obviously untrue.
- Group project described with no indication of what you did.
- Two pages when the placement cell asked for one.
- A file named resume_final_v3.pdf instead of your name.
Questions people ask
Should I mention backlogs?
Only if the company or the placement form asks. If asked, state the current position accurately, including cleared backlogs, because it will be verified before an offer.
How many projects should a placement resume have?
Two to four. Depth on three beats a list of eight, and every one of them invites questions.
Does a career objective help in placements?
Rarely. A short profile line naming your strongest area is more useful, and many placement cells ask you to drop the objective entirely.
Should I include school achievements?
Only if you have nothing comparable from college. Sports at state level or above is worth keeping.