📄 Resume Project Guide

Write project descriptions that make recruiters stop scrolling. Real examples, proven formulas.

✍️ Writing

📋 Examples

🌐 Portfolio

📐 Formatting

🎯 The Formula That Works

[Action Verb] + [What You Built] + [How] + [Result/Metric]

✓ GOOD

Built a real-time parking slot finder using React, Node.js, and Google Maps API, reducing average search time by 40% for 500+ test users.

✗ BAD

Made a parking website using React.

📊 Use Numbers Everywhere

Users: "served 500+ users" or "tested with 50 students"

Performance: "reduced load time by 60%" or "processed 10K records in 2 seconds"

Scale: "handled 1,000 concurrent users" or "stored 50GB of data"

Impact: "saved 10 hours/week of manual work" or "reduced errors by 90%"

💡No real users? Use test data: "Processed 1,000 test records with 99.5% accuracy" or "Achieved 95 Lighthouse performance score."

🔤 Action Verbs That Impress

Category	Verbs
Building	Built, Developed, Created, Designed, Implemented
Improving	Optimized, Reduced, Improved, Enhanced, Streamlined
Leading	Led, Managed, Coordinated, Mentored, Drove
Technical	Architected, Integrated, Automated, Deployed, Migrated

⚠️Never use: "Worked on," "Helped with," "Was responsible for." These are passive and vague. Always start with a strong action verb.

🏗️ STAR Method for Projects

Situation: What problem did you solve? (1 sentence)

Task: What was your goal? (1 sentence)

Action: What did you build and how? (1-2 bullet points)

Result: What was the outcome? Use numbers. (1 bullet point)

💡Interview bonus: If you can explain your project using STAR in an interview, you'll stand out from 90% of candidates.

💻 Web Application

✗ BEFORE

Online Store — Built an e-commerce website using React and Node.js.

✓ AFTER

HyperLocal Marketplace — Built a neighborhood grocery group-buying platform using React, Node.js, and Razorpay, enabling 200+ apartment residents to pool orders and access wholesale prices, reducing grocery costs by 15-25%.

🤖 AI/ML Project

✗ BEFORE

Crop Disease Detector — Used machine learning to detect plant diseases from photos.

✓ AFTER

CropGuard AI — Developed a mobile-first crop disease detection system using TensorFlow and MobileNet, achieving 94% accuracy across 15 disease categories. Deployed as a PWA serving 500+ farmers with treatment recommendations in 3 regional languages.

📱 Mobile App

✗ BEFORE

Medicine Reminder App — An app that reminds people to take their medicine.

✓ AFTER

MedBuddy — Built a React Native medicine reminder app with family tracking, enabling caregivers to monitor medication adherence remotely. Reduced missed doses by 60% in a 2-week pilot with 30 senior citizens.

🛠️ Developer Tool

✗ BEFORE

API Testing Tool — A tool to test REST APIs.

✓ AFTER

APITester — Created a browser-based REST API testing tool with request history, environment variables, and response visualization. Reduced API debugging time by 40% for a team of 5 developers during a 3-month internship.

📊 Data Project

✗ BEFORE

Data Analysis — Analyzed sales data using Python and created visualizations.

✓ AFTER

SalesPulse Dashboard — Built an interactive sales analytics dashboard using Python, Pandas, and Plotly, processing 50K+ transactions to identify top-performing products and seasonal trends. Insights led to a 20% inventory optimization recommendation.

🌐 Where to Host Your Portfolio

Platform	Best For	Cost
GitHub Pages	Developers, free hosting	Free
Vercel	React/Next.js projects	Free
Netlify	Static sites, forms	Free
Notion	Quick setup, non-developers	Free
Personal domain	Professional branding	₹500-1000/yr

💡Minimum viable portfolio: A GitHub profile with pinned repos + a one-page site with your projects, skills, and contact. That's enough to get hired.

📋 What Each Project Entry Needs

Title — Short, descriptive name (not "Project 1")

One-liner — What it does in one sentence

Tech stack — Languages, frameworks, APIs used

Live link — Working demo (even if basic)

GitHub link — Clean code with README

Screenshot/video — Visual proof it works

📝 GitHub README Template

✓ TEMPLATE

# Project Name
One-line description.

## Features
- Feature 1
- Feature 2

## Tech Stack
Frontend: React, Tailwind
Backend: Node.js, Express
Database: MongoDB

## Setup
Steps to run locally.

## Screenshots
Add 2-3 screenshots.

🏆 Portfolio Priorities

Quality > Quantity. 3 polished projects beat 10 unfinished ones.

Deploy everything. A live link is 10x more impressive than "run locally."

Write good READMEs. Recruiters check your GitHub. Clean README = professional impression.

Include problem-solving projects. Real-world problems > todo apps and calculators.

📐 Resume Project Section Format

✓ FORMAT

PROJECTS

HyperLocal Marketplace | React, Node.js, Razorpay | Live | GitHub
• Built a neighborhood grocery group-buying platform enabling 200+ residents to access wholesale prices
• Implemented real-time order tracking, UPI payments, and automated price calculation per member
• Reduced grocery costs by 15-25% in pilot testing with 3 apartment complexes

📏 How Many Projects?

Experience Level	Projects to Show	Focus
Fresher (0 exp)	3-4 projects	Diverse skills, real problems
1-2 years exp	2-3 projects	Best work, relevant to role
3+ years exp	1-2 projects	Only if impressive/side projects

💡Order matters. Put your strongest project first. Recruiters spend 6 seconds on a resume — make the first project count.

✅ Project Description Checklist

Starts with a strong action verb (Built, Developed, Created)

Includes tech stack (languages, frameworks, tools)

Has at least one number/metric

Describes the problem being solved

2-4 bullet points (not more)

Each bullet is one line (no wrapping)

Includes links (Live demo + GitHub)

⚠️Common mistakes: Listing every project you've ever started. Including "todo app" or "calculator." Writing paragraphs instead of bullets. No links to code/demo.

🎯 Tailor to the Job

Frontend role? Highlight UI/UX, responsive design, performance optimization

Backend role? Highlight APIs, database design, scalability, security

Data role? Highlight data processing, analysis, visualization, ML models

Full-stack? Show end-to-end projects with both frontend and backend

💡One resume per application. Swap project order and adjust descriptions based on what the job asks for. Generic resumes get generic results.

How to Write Project Descriptions That Get Interviews

Your project section is the most important part of a technical resume. Recruiters spend an average of 6 seconds scanning a resume — and they spend most of that time on your projects. A well-written project description can be the difference between getting an interview and getting ignored.

The Problem with Most Project Descriptions

Most students write project descriptions like feature lists: "Built a website using React." This tells the recruiter nothing about your skills, the impact, or why they should care. The fix is simple: use the formula (Action + What + How + Result) and include numbers.

Projects > Degrees

In tech hiring, what you've built matters more than where you studied. A strong portfolio of 3-4 real-world projects demonstrates practical skills that a degree alone can't. Focus on building projects that solve real problems — that's what makes recruiters stop scrolling.