BCA Fresher Resume Format with Sample (2026)

Most BCA freshers send the same resume to every company and wonder why nobody calls back. The problem is rarely your marks or your college. It is usually the format: a two-page bio-data with a photo, a declaration line, and a projects section that says nothing. Recruiters hiring for entry-level IT roles spend a few seconds on each resume. This guide gives you the exact one-page format that survives those seconds, plus a full sample you can copy.

The format that works

Before the sections, fix the basics. These rules look small but they decide whether your resume gets read at all:

• One page only. You have three years of study and maybe two real projects. That fits on one page. A second page tells the recruiter you cannot prioritise.
• Single column, no tables, no text boxes. Many companies parse resumes with software before a human sees them. Tables and graphics break that parsing.
• A plain font at 10–12 pt. Calibri, Arial or Georgia. Fancy fonts look good to you and broken to everyone else.
• PDF with selectable text, named properly. Firstname_Lastname_Role.pdf. Not resume_final_final2.pdf.
• No photo, no date of birth, no father's name, no declaration. Indian bio-data habits do not belong on an IT resume.

Section order for a BCA fresher

Order matters because recruiters read top to bottom and stop early. For a fresher with no work experience, this order works best:

• Header: name, phone, professional email, city, LinkedIn and GitHub links. That is all.
• Summary (2 lines): the role you want, your strongest skills, and one piece of proof. Change these two lines for every job you apply to.
• Technical skills: grouped into Languages, Frameworks, Databases and Tools. List only what you can answer questions about in an interview.
• Projects: two or three, each with the tech stack and two or three bullets about what you personally built. This is your most important section.
• Education: degree, college, university, years, and CGPA or percentage if it is above roughly 60 percent. Latest first. No 10th and 12th marksheet tables.
• Certifications and achievements (optional): hackathons, coding ranks, real courses. Skip participation certificates.

How to write project bullets

Weak bullets kill more BCA resumes than weak skills. The pattern that works is: action verb + what you built + the technology + something you can show. Compare these two lines for the same project:

• Weak: Worked on a library management project using Python.
• Strong: Built a Django library app with separate student and librarian logins, book search and loan tracking, deployed on Render with a PostgreSQL database.

The strong line names the framework, the features and the proof. If your project is a tutorial you followed, say what you changed or added yourself. Interviewers ask, and honest answers beat invented ones.

A complete BCA fresher resume sample

This sample is fictional. Copy the structure, not the details, and replace everything with your own real work.

Mistakes that get BCA resumes rejected

• Listing every technology you have heard of. Ten skills you cannot explain are worse than four you can. Interviewers pick one and dig.
• Copy-paste objectives. Seeking a challenging position in a reputed organisation says nothing. Write two lines about the actual role.
• Fake numbers. Increased efficiency by 80 percent on a college project invites questions you cannot answer. Use numbers only when you can show the working.
• Sending the same file everywhere. Match your summary and skills order to each job post. It takes ten minutes and doubles your shortlist chances.

Before you send it

Run through this checklist: one page, no photo, real email, working GitHub link, projects with concrete bullets, and a file name with your name in it. Then test your resume against an actual job description to see which skills the job asks for that your resume does not mention. You can do that free on ResumePakad: paste the job post, upload your resume, and get a skill-by-skill match report in seconds.