How to List Projects on a Resume (B.Tech, MCA, BCA)
Quick answer: List 2–4 projects in a separate "Projects" section, newest or most relevant first. For each project, write the title, tools used, your role and dates, then 2–3 bullet points that say what you built, how you built it and what the result was. Add a GitHub or demo link if you have one.
Why do projects matter so much on a fresher resume?
For B.Tech, MCA and BCA students, projects are often the only real proof of skill. Your CGPA shows you studied. Your projects show you can build something. Interviewers in campus placements and off-campus drives often spend a large part of the technical round asking about your projects.
That is also why you must understand every project you list. If you cannot explain the database design or why you chose a library, it can hurt more than it helps.
Where should the Projects section go?
- Freshers: after Education and Skills, before Internships. If your internship is stronger, put it first.
- Final-year students with no internship: Projects can be your biggest section.
- 1–3 years of experience: keep 1–2 strong projects after Experience, or drop them if your work bullets are enough.
See the full section order in our resume format for freshers in India.
What should each project entry include?
- Project title: a clear name that says what it is, such as "Hostel Mess Feedback App", not "Project 1".
- Tech stack or tools: Java, Spring Boot, MySQL, React, Python, Arduino, MATLAB, and so on.
- Type and role: final-year project, mini project, personal project or hackathon; solo or team of 4.
- Dates: month and year, for example "Jan 2026 – Apr 2026".
- 2–3 bullet points: what you built, your part, and the result.
- Link: GitHub repo, live demo or a short video, if it exists and works.
Project write-up templates you can copy
Use this simple formula for each bullet: Action verb + what you built + tools + result or scale. Need more verbs? Use our list of 150 action verbs for resumes.
All names, numbers and links below are examples. Replace them with your own true details.
Template 1: B.Tech CSE / IT final-year project
Smart Attendance System using Face Recognition | Python, OpenCV, Flask, MySQL | Final-year project, team of 4 | Aug 2025 – Mar 2026 | github.com/yourname/smart-attendance
- Built a web app that marks classroom attendance from a camera feed using OpenCV face recognition.
- Designed the MySQL database and REST APIs in Flask for student, class and attendance records (my main role).
- Tested with 60 students across 2 sections; reduced roll-call time from about 10 minutes to under 2 minutes per class.
Template 2: B.Tech ECE / EEE hardware project
IoT-based Water Tank Level Monitor | Arduino Uno, ESP8266, ultrasonic sensor, Blynk | Mini project, team of 3 | Jan 2025 – Apr 2025
- Designed a circuit that measures tank water level with an ultrasonic sensor and sends readings over Wi-Fi.
- Programmed the ESP8266 to send mobile alerts when the level drops below 20% and switch the pump automatically.
- Installed and tested the setup in my apartment building in Hyderabad for 3 weeks.
Template 3: B.Tech Mechanical / Civil project
Design and Analysis of a Lightweight Bicycle Frame | SolidWorks, ANSYS | Final-year project, team of 4 | Jul 2025 – Feb 2026
- Modelled a bicycle frame in SolidWorks and compared steel and aluminium designs.
- Ran static stress analysis in ANSYS under rider load and identified the weakest joint.
- Proposed a modified design that lowered frame weight in simulation while staying within safe stress limits.
Template 4: MCA project
Online Library Management System | Java, Spring Boot, React, PostgreSQL | MCA major project, solo | Jan 2026 – May 2026 | Live demo link
- Developed a full-stack app for book search, issue, return and fine calculation with role-based login for students and librarians.
- Wrote REST APIs in Spring Boot and built the front end in React with form validation.
- Deployed on a free cloud tier; used by my college library staff for a 2-week trial with 150+ book records.
Template 5: BCA project
Billing and Inventory App for a Kirana Store | PHP, MySQL, HTML, CSS, JavaScript | BCA final project, team of 2 | Nov 2025 – Mar 2026
- Built a billing app that prints GST invoices and updates stock automatically after each sale.
- Created a low-stock report so the shop owner knows what to reorder each week.
- Collected feedback from a local shop owner in Jaipur and added barcode search based on that feedback.
Template 6: Data analysis project (any branch)
Restaurant Ratings Data Analysis | Python (Pandas, Matplotlib), Power BI | Personal project | Jun 2025 | github.com/yourname/restaurant-analysis
- Cleaned a public Kaggle dataset of 9,000+ restaurant listings and removed duplicates and missing values.
- Analysed ratings, cost for two and cuisine type by city, and built a 2-page Power BI dashboard.
- Found that the highest-rated restaurants in the sample were not the most expensive, and shared the findings on LinkedIn.
Before and after: fixing a weak project entry
Before:
- Project: E-commerce website. Worked on front end and back end. Used many technologies.
After:
- ShopEasy – E-commerce Web App | MERN stack (MongoDB, Express, React, Node.js) | Team of 3 | Sep–Dec 2025
- Built product listing, cart and checkout pages in React with a Node.js and Express back end.
- Added JWT login and Razorpay test-mode payments; handled the cart and payment modules myself.
The second version tells the recruiter the exact skills, your own part and what the app does. It also gives the interviewer good questions to ask you.
Common mistakes when listing projects
- Listing 6–8 small projects. Pick the best 2–4. Quality beats quantity.
- Copying a tutorial project as your own. If you followed a course, say so, or add your own features first.
- No tools mentioned. Recruiters search for skill names like "React" or "SQL". Put them in the project line too, not only in Skills.
- Hiding team work. Say "team of 4" and explain your part. It is honest and shows teamwork.
- Broken GitHub links or empty repositories. Check every link before you apply.
- Long paragraphs. Keep 2–3 bullets, one or two lines each.
Software roles need extra care here. See our software engineer fresher resume guide for a full sample.
Add your projects faster with nm7.si
The nm7.si resume builder has a projects section with guidance on what to write. You can keep all your projects saved and use the show/hide switch to pick the 2–4 that fit each job. Templates are clean, single-column and ATS-friendly, and you can download as PDF or Word or share a link.
Frequently asked questions
How many projects should a fresher put on a resume?
Two to four is a good number. Choose the ones most related to the job and the ones you can explain in depth.
Can I add a mini project or a college assignment?
Yes, if it shows a skill the job needs. Label it clearly as a mini project and keep it short.
Should I add a project I did by following a YouTube tutorial?
Only if you changed or added something yourself and you understand how it works. Mention what you added in the bullets.
Do I need a GitHub link for every project?
It is not required, but it helps for software roles. Make sure the repository has a short README and working code.
What if my project was a team project?
Write the team size and clearly describe your own part, such as "Designed the database and login module".