Your resume is the first thing a recruiter sees — and for campus placement, it shapes every question in the technical and HR round. A strong resume does not just list what you did; it tells a story that makes a recruiter want to interview you. Here is how to build one.

The Non-Negotiable Rule: One Page

For campus placement, your resume must be one page. No exceptions. Recruiters processing hundreds of resumes per day make split-second decisions. A second page signals poor prioritisation, not more experience.

Ideal Resume Structure for Freshers

  1. Contact Information
  2. Professional Summary (optional but powerful)
  3. Education
  4. Technical Skills
  5. Projects (most important for freshers)
  6. Internship / Work Experience (if any)
  7. Certifications and Awards

Contact Information

  • Full name (large, top of page)
  • Professional email: firstname.lastname@gmail.com
  • Phone number
  • LinkedIn URL (customised: linkedin.com/in/yourname)
  • GitHub URL (if your code is public and presentable)
  • Location: City, State only — no full address

Professional Summary

3 lines answering: who you are, what you can do, what you want.

Example: "Final year Computer Science student at XYZ University with strong DSA fundamentals and experience building full-stack applications. Completed a 3-month internship at ABC Startup where I improved backend API response time by 35%. Seeking a software engineering role where I can build scalable products that serve real users."

Education Section

  • Degree, Branch, University, Year of passing, CGPA/Percentage
  • Include only if CGPA is above 6.0 or percentage above 60%
  • Add relevant coursework if space allows and it is directly relevant

Technical Skills (Be Honest)

Group by category:

  • Programming Languages: Python, Java, C++
  • Frameworks: React, Node.js, Spring Boot
  • Databases: MySQL, MongoDB
  • Tools: Git, Docker, AWS basics
  • Concepts: Data Structures, OOP, REST APIs

Never list a skill you cannot defend in a 5-minute technical conversation.

Projects (Make or Break Section)

This is the most important section for freshers without work experience. For each project:

Structure Each Project As:

  • Project Name + tech stack used
  • What it does (1 sentence)
  • Your specific contribution (not the team's — yours)
  • Quantified outcome: "Reduced loading time by 40%" not "Improved performance"
  • GitHub link or live demo link

Quality Over Quantity

Three strong, well-described projects beat eight vague bullet-point entries. Recruiters ask about every project you list — only include ones you can discuss for 5–10 minutes.

ATS Optimisation for Placement

Applicant Tracking Systems (ATS) filter resumes before a human ever sees them. To pass ATS:

  • Use standard section headings (Education, Experience, Skills — not Creative alternatives)
  • Include keywords from the job description naturally
  • No tables, columns, or graphics (they confuse ATS parsers)
  • Submit as PDF unless the job posting specifies Word
  • Use a clean, readable font: Calibri, Arial, or Georgia at 10–11pt

Common Fresher Resume Mistakes

  • Listing "MS Office" and "Teamwork" as skills in 2026
  • Generic objective: "Seeking an opportunity to utilise my skills in a reputed organisation"
  • Copying project descriptions from the internet verbatim
  • Using a photo (not required in India for most tech companies — takes space unnecessarily)
  • Inconsistent dates, fonts, or formatting
  • No quantification: "Built a web app" instead of "Built a web app serving 500+ daily users"

Final Checklist Before Submitting

  • Is it one page?
  • Is everything grammatically correct?
  • Are all links working?
  • Is the CGPA above the company's cutoff?
  • Did you tailor the summary for this specific role?
  • Can you talk about every single item for at least 2 minutes?

FAQ: Resume for Placement

Q: Should I use a resume template from Canva or Zety?

A: Avoid templates with heavy graphics, columns, or tables — they often fail ATS. Use a clean, minimal template or build your own in Google Docs/MS Word.

Q: How do I write projects if I only built tutorial projects?

A: Extend a tutorial project: add a feature, integrate an API, deploy it, and measure something. Then that becomes a real project worth documenting.

Q: Should my resume include my class 10 and 12 results?

A: Only if they are above 80% and relevant to the application. If your CGPA is strong, class 10/12 details take up valuable space better used for projects.