Menu

Earn Premium with Referrals

Invite your friends and earn Premium rewards through our referral program.

See how it works and start inviting friends.

Resume Guide - Part 1
CSE_PLACEMENT_GUIDE

Resume Guide - Part 1

Learn the fundamentals of creating a placement-ready resume, including structure, sections, formatting, and the information recruiters look for.

Resume Blueprint

Your resume is not a summary of everything you’ve done.

It’s a marketing document designed to convince a recruiter that you’re worth interviewing.

Most recruiters spend 6–10 seconds scanning a resume before deciding whether to continue reading. During those few seconds, they look for relevant skills, experience, projects, and achievements that match the job.

Your goal isn’t to include everything you’ve ever done. Your goal is to make the most important information easy to find.

General Resume Rules

Before writing any section, follow these rules:

  • Keep your resume to one page if you’re a student or fresher.
  • Export it as a PDF.
  • Use a clean, ATS-friendly layout.
  • Maintain consistent formatting throughout.
  • Use bullet points instead of long paragraphs.
  • Prioritize quality over quantity.
  • Update your resume regularly.
  • Tailor your resume for every application.

Recommended Resume Structure

A typical software engineering resume should follow this order:

  1. Header
  2. Education
  3. Experience (if any)
  4. Projects
  5. Technical Skills
  6. Leadership & Achievements
  7. Certifications (Optional)

If you don’t have internship experience, place your Projects section above Education.

Header

Your header should contain only the essential contact information.

Include:

  • Full Name
  • Professional Email
  • Phone Number
  • LinkedIn
  • GitHub
  • Portfolio Website (Optional)

Example

Alex Johnson

+1 234 567 8901

alex.johnson@email.com

linkedin.com/in/alexjohnson

github.com/alexjohnson

alexjohnson.dev

Why?

Recruiters should be able to contact you immediately without searching.

Common Mistakes

Photo

Full postal address

Date of birth

Father’s name

Multiple email addresses

Unprofessional email IDs

Example:

coderboy123@gmail.com

Use something professional instead.

alex.johnson@gmail.com

Education

Keep this section short and clean.

Include:

  • College Name
  • Degree
  • Branch
  • Graduation Year
  • CGPA (if it’s good)
  • Relevant Coursework (Optional)

Example

ABC Institute of Technology

B.Tech in Computer Science

2022 – 2026

CGPA: 8.6/10

Relevant Coursework

Only list subjects useful for software engineering interviews.

Examples:

  • Data Structures & Algorithms
  • Object-Oriented Programming
  • Database Management Systems
  • Operating Systems
  • Computer Networks

Avoid listing every subject from your syllabus.

Experience

Experience is one of the first sections recruiters read.

Each bullet should answer three questions:

  • What did you do?
  • How did you do it?
  • What impact did it create?

A simple formula:

Action + Technology + Result

Weak Example

Worked on backend APIs.

Better Example

Developed REST APIs using Spring Boot that reduced response time by 35%.

Another Example

Instead of

Worked on testing.

Write

Created automated UI tests using Cypress, reducing manual regression testing effort by 60%.

Recruiters love numbers because they make achievements believable.

Projects

For students and freshers, projects are often the most important section.

Choose 2–4 strong projects.

Every project should explain:

  • What problem does it solve?
  • Which technologies were used?
  • What technical challenges did you solve?
  • What measurable impact did it have?

Each project should include:

  • Project Name
  • Tech Stack
  • 2–3 strong bullet points
  • GitHub Repository
  • Live Demo (if available)

Weak examples:

  • Calculator
  • To-do List (without advanced features)
  • Weather App copied from YouTube
  • Simple CRUD app with no unique functionality

Show Engineering, Not Just Features

Instead of saying

Built an e-commerce website.

Explain what makes it technically interesting.

Example:

Implemented JWT authentication, payment gateway integration, Redis caching, Docker deployment, and CI/CD automation.

This demonstrates engineering skills instead of basic development.

Always Quantify Results

Instead of

Improved performance.

Write

Reduced page load time by 45% using lazy loading and image optimization.

Instead of

Optimized database queries.

Write

Reduced average query execution time from 1.8 seconds to 450 milliseconds through indexing and query optimization.

Technical Skills

Recruiters scan this section very quickly.

Organize similar skills together.

Example

Languages

Python, Java, C++, JavaScript

Frontend

React, Next.js, HTML, CSS

Backend

Node.js, Express, Spring Boot

Databases

MySQL, PostgreSQL, MongoDB

Cloud & DevOps

Docker, Kubernetes, AWS, GitHub Actions

Tools

Git, Linux, Postman

Don’t Lie

Never list a technology you cannot explain.

If you list Kubernetes, be prepared to answer Kubernetes questions.

Only include technologies you’re comfortable discussing.

Leadership & Achievements

Recruiters appreciate students who contribute beyond academics.

Include:

  • Open Source Contributions
  • Club Leadership
  • Hackathons
  • Technical Events
  • Competitions
  • Mentoring
  • Community Building

Weak Example

Member of Coding Club

Better Example

Organized coding workshops attended by more than 250 students and coordinated technical events across multiple departments.

Again, numbers create stronger impact.

Certifications

Only include certifications that demonstrate relevant skills.

Examples:

  • AWS Cloud Practitioner
  • Microsoft Azure Fundamentals
  • Google Cloud Digital Leader
  • Meta Front-End Developer
  • Google Data Analytics

Avoid adding certificates simply because you completed a short online course.

ATS Optimization

Many companies use an Applicant Tracking System (ATS) before a recruiter reviews your resume.

ATS extracts information using standard section names.

Use headings like:

  • Education
  • Experience
  • Projects
  • Skills
  • Certifications

Avoid creative titles such as:

My Journey

Technical Arsenal

Things I’ve Built

These may confuse ATS software.

Resume Formatting Rules

Keep your resume clean and professional.

Recommended:

  • One font family
  • Consistent spacing
  • Black text
  • Bullet points
  • One page
  • Adequate white space

Avoid:

  • Tables
  • Progress bars
  • Skill ratings
  • Multiple colors
  • Large icons
  • Decorative graphics

Simple resumes usually perform better than heavily designed ones.

Use Strong Action Verbs

Instead of “Worked on”, use:

  • Built
  • Designed
  • Developed
  • Engineered
  • Implemented
  • Optimized
  • Automated
  • Reduced
  • Improved
  • Scaled
  • Migrated
  • Integrated
  • Deployed

Strong verbs make your contributions clearer.

Quantify Everything

Whenever possible, include numbers.

Instead of

Improved API performance.

Write

Reduced API response time by 42%.

Instead of

Managed a team.

Write

Led a team of five developers during a semester-long software engineering project.

Instead of

Built automation.

Write

Automated repetitive workflows, reducing manual effort by approximately 70%.

Numbers make achievements more credible.

Tailor Every Resume

Never send the same resume everywhere.

Before applying:

  • Read the Job Description.
  • Identify important keywords.
  • Highlight relevant projects.
  • Reorder skills if necessary.
  • Remove unrelated technologies.
  • Match your resume to the role.

A Backend Developer resume should not look identical to a Data Science resume.

Common Resume Mistakes

  • More than one page
  • Poor formatting
  • Too many projects
  • Weak bullet points
  • No measurable achievements
  • Grammar mistakes
  • Broken GitHub links
  • Fake skills
  • Generic objectives
  • Using Canva templates with complex layouts
  • Adding photos
  • Listing every technology you’ve ever tried

My Private Notes

Notes are auto-saved locally to this device.