How to Write an Effective Resume for Freshers in India

I'm going to tell you something embarrassing. My first resume was three pages long. Three pages, with zero work experience. I had a decorative border, a passport photo in the corner, my father's name, my blood group (why?), and an objective statement that started with "To obtain a challenging position in a reputed organisation." I sent it to maybe 20 companies during campus placement season. Got zero calls. Not one.

A friend who'd already landed a job at Infosys looked at it and said, "Bhai, this looks like a biodata for a marriage site." He wasn't wrong.

I've since helped a bunch of juniors and cousins with their resumes, and I keep seeing the same mistakes I made. So this isn't a theory article. It's a workshop. Grab a pen or open a doc. You're going to actually build the thing as you read. Some sections I'll go deep on because I've seen them trip people up repeatedly. Others I'll keep short because they're straightforward and you don't need me rambling about them.

The Three Things (Start Here)

Before you touch any template, do this. Write down three things you're good at that aren't on your degree certificate.

Not your CGPA. Not your subject list. Three actual abilities. Maybe you're good at explaining technical stuff to non-technical people. Maybe you built something on your own — a website, an app, a spreadsheet that automates something tedious. Maybe you organised an event for 500 people and pulled it off without a disaster.

When I was a fresher, my three things were pathetic. I wrote "good at teamwork" — which means absolutely nothing — "quick learner" — which every fresher claims — and "proficient in MS Office" — which, come on. It took me three rewrites to get to anything specific. One of them eventually became "built a working inventory tracker in Python for my uncle's hardware shop that he still uses." That's a real thing. That's what belongs here.

Be specific. "Good communication skills" is meaningless. "Explained a database normalisation concept to a group of 40 non-CS students during a workshop and got positive feedback" — that's something a recruiter can picture. Write your three. One sentence each. I'll wait.

Contact Details — Quick But Important

This section is simple so I won't belabour it. Name at the top in a slightly larger font. Phone number, email, LinkedIn URL, city — one or two lines.

The email thing: if yours is something like [email protected], go make a [email protected] right now. I once received an application from someone with the email "hotchick_divya@" something. She was qualified. I still couldn't take the resume seriously. It's not fair, but that's reality.

Don't include your photo unless the posting asks for one. Don't include father's name, date of birth, blood group, marital status, or religion. That's biodata for a different purpose. Also — and I keep seeing this — don't include your full postal address. "Pune" is enough. Nobody's mailing you a letter.

LinkedIn: only include the URL if your profile is actually filled out. An empty LinkedIn with just your name and college is worse than no link at all. If yours is sparse, leave it off and fix it later.

Kill the Objective Statement

If you've written "To obtain a challenging position in a reputed organisation where I can utilise my skills and contribute to the organisation's growth" — cross it out. Literally draw a line through it. I can't tell you how many hundreds of resumes I've seen with this exact sentence. I think there's a template floating around Indian colleges that has it pre-filled and people just leave it in.

Replace it with two to three sentences that answer: What can you do, and what's the evidence?

Structure: [Degree and institution]. [One specific skill or project]. [What kind of role you're after].

Like this: "B.Tech Computer Science graduate from VIT Vellore. Built a full-stack e-commerce app handling 500 concurrent users as a final-year project. Looking for a software engineering role focused on backend development."

Or: "B.Com from Symbiosis Pune with a Google Data Analytics certificate. Analysed customer churn data for a retail dataset using SQL and Tableau as a capstone project. Seeking an entry-level data analyst role."

Write yours. Read it back. Does it tell a stranger what you studied, what you can actually do, and what you're looking for? If it sounds like it could've been written by any graduate from your college, try again with something more specific.

Education

Straightforward. List qualifications in reverse chronological order. Degree name, institution and city, year, CGPA or percentage.

The Class 10/12 question: if either score is above 85%, include it. If both are below 80% and your graduation score is decent, leave them out. I go back and forth on this honestly — I've met recruiters who care about 10th marks and recruiters who think including them is juvenile. My general rule is: include what helps, remove what doesn't. If in doubt, leave them in for now. You can always remove them later.

If your institution is well-known — IIT, NIT, BITS, Delhi University — the name does some work for you. If it's less known, that's fine, but your projects and skills sections need to carry more weight. I went to a college nobody outside my city has heard of. The projects section is what got me interviews.

Projects — This Is Where You Win or Lose

I'm going to spend the most time here because this is the section that matters most for freshers and the one I see botched most often.

In the absence of work experience, your projects are your proof that you can actually do things. I've seen freshers with 6.5 CGPAs get calls from good companies because their project descriptions were specific and impressive. I've seen 9+ CGPA students get ignored because their project section said "Mini project on library management system using Java" and nothing else.

First, list every project you've ever done. Academic, hackathon, personal, freelance, open-source. Don't filter. Just dump them all on the page.

Now, for each one, answer four questions:

What did I build or do? (one sentence)
What tools/technologies did I use?
What was the result? (a number, a metric, a deployment — anything measurable)
How long did it take?

Here's what a good project entry looks like:

"Smart Attendance System using Face Recognition (Jan–Apr 2025): Built an automated attendance system using Python, OpenCV, and a CNN. Achieved 96% face recognition accuracy across 200 registered students. Reduced manual attendance time from 10 minutes to under 30 seconds per class. Deployed on Raspberry Pi."

Compare that to: "Smart Attendance System — Used Python and face recognition." The first tells a recruiter everything. The second tells them nothing.

A friend of mine had a project that was genuinely impressive — he'd built a crop disease detection app during a hackathon that farmers in his village actually used. But his resume just said "Developed an agriculture app using ML." I wanted to shake him. We rewrote it together, added the user count (about 40 farmers), the accuracy (87%), and the fact that it worked offline on low-end phones. He got three interview calls in the next two weeks. Same project. Different description.

Pick your three to four strongest ones — the ones where you can fill in all four answers with specific details. Those go on the resume. The rest stay in a separate "master list" document you keep for future tailoring.

Internships

If you had one, write it up using the same four questions. Company name, role, duration, what you contributed.

If you didn't — and plenty of people from smaller cities or less connected colleges don't, and that's not a character flaw — skip this. Strong personal projects can be just as good. An app on the Play Store or a web tool you built for yourself shows initiative that nobody assigned to you.

The Skills Honesty Check

This is the exercise that saves you from embarrassment in interviews. Trust me on this.

Write down every technical skill you think you have. Then go through and honestly mark each one: P for Proficient (you could handle interview questions on this without panicking) or F for Familiar (used it in a course, would need to brush up).

Now cross out anything where your honest assessment is "I watched a YouTube tutorial" or "I attended a 2-hour workshop." I made this exact mistake — listed SQL on my resume because I'd done one college assignment with it. The interviewer asked me to write a join query. I sat there. Blank. For what felt like a full minute. It was maybe the most uncomfortable silence of my life. He moved on to the next question and I could tell I was already done.

Don't list 15 languages you can't use. List 5 you actually can. On the resume, you can label them "Proficient" and "Familiar" or just list the proficient ones. Either way is honest.

Group them by category: Programming Languages, Web Technologies, Databases, Tools. Makes it scannable for recruiters doing a quick pass.

Certifications, Extracurriculars, and Other Sections

I'm combining these because individually they don't need much explanation.

Certifications: Only include ones from recognised providers — Google, AWS, Microsoft, NPTEL, Coursera specialisations from actual universities — that are relevant to the jobs you're targeting. Three strong ones beat twelve random Udemy certificates. If you have nothing here, that's useful information about where to invest your time before the next application round.

Extracurriculars: Include them only if they demonstrate a relevant skill. Event coordinator managing Rs. 8 lakh budget and 35 volunteers? Yes. "Hobbies: reading, listening to music." No. And when you include them, be specific — not "member of debate team" but "represented college at national-level debate at IIT Bombay, semi-finals against 150 teams."

The declaration: "I hereby declare that the information is true to the best of my knowledge" — remove this. It's an outdated relic from paper application days. Nobody needs it. Also remove references unless specifically asked. "References available upon request" is filler.

ATS — The Robot That Reads Your Resume First

Most freshers don't know this exists, and it cost me at least a few opportunities before I figured it out. Before a human ever sees your resume, software scans it. TCS, Infosys, Wipro, HCL, Cognizant — they all use Applicant Tracking Systems to filter applications. If your resume isn't ATS-friendly, it gets rejected by a machine and no human ever knows you applied.

I'm not sure exactly how much each company's ATS differs — I don't think anyone outside those HR teams really knows the specifics. But here's what's generally accepted:

Simple single-column layout. Tables, text boxes, and graphics confuse parsers.
Standard section headings: "Education," "Skills," "Projects." Not "My Toolbox" or "The Journey So Far."
Readable font — Arial, Calibri, Times New Roman. 10-12 point.
Save as PDF (usually safer) or .docx.

The keyword thing is real. If a job says "Java, Spring Boot, and MySQL" and your resume says "Java, Spring Framework, and SQL," you might miss the match on "Spring Boot" and "MySQL" specifically. Use the exact phrasing from the job description wherever your skills genuinely align. I don't mean stuff keywords artificially — I mean if you know Spring Boot, write "Spring Boot," not "Spring Framework."

Fitting It on One Page

You've got all the raw material now. Assemble it in a clean template — no colours, no decorative borders, no icons. One-inch margins, single-spaced.

If it's over one page, here's the cutting priority: contact info and summary stay always. Education stays. Top 3-4 projects stay. Skills stay. Certifications get trimmed to 3-5. Extracurriculars are the first to go.

One page. That's the rule for freshers, no exceptions. Recruiters at mass hiring drives spend maybe ten seconds on an initial scan. If I can't find your key selling points in ten seconds on a single page, your resume needs editing, not a second page.

The Polish Pass — Verbs, Numbers, and Proofreading

Three things to do before you call it done.

First, fix your verbs. Find every instance of "was responsible for" or "worked on" and replace it with an action verb. "Was responsible for managing social media" becomes "Managed social media across three platforms, growing followers by 40%." "Worked on a machine learning project" becomes "Developed a machine learning model predicting customer churn with 89% accuracy." Start every bullet point with what you did, not what your job description said.

Second, add numbers everywhere you can. "Tutored students" becomes "Tutored 15 students over two semesters, 12 of whom improved by at least one grade." Numbers make claims concrete. If you don't have exact figures, approximate — "approximately 200 users" is infinitely better than no number at all.

Third, proofread. Read the whole thing out loud — you'll catch awkward phrasing your eyes skip over. Run it through Grammarly or whatever spell checker you have. Then — and I know this feels like overkill but I swear it matters — send it to one person you trust and ask: "Is anything confusing? Does anything seem off?" Every time I've skipped this step, I've regretted it. I once sent out 15 applications with "collage" instead of "college" in my education section. A friend caught it on day three. Fifteen applications. I still cringe.

Save as PDF. Name it "FirstName_LastName_Resume.pdf." Not "resume_final_v3_FINAL(2).pdf" — yes, I've seen that.

One Last Thing

Tailor your resume for every job you apply to. I know, I know — when you're sending out 30-40 applications, customising each one feels insane. And honestly, I'm not sure how much the tailoring matters for mass-hiring at service companies where they're filling 500 seats. For those, a good general resume might be fine. But for product companies, startups, and specific roles? Tailoring makes a real difference. Swap in the most relevant project, reorder your skills to match the job description, tweak the summary. Ten to fifteen minutes per application. The tailored resume gets callbacks. The generic one sits in the pile.

I'm not going to end this with some inspirational line about how your resume is your first impression and your ticket to the future. It's a document. An important document that you'll probably revise a dozen times over the next few years. The version you make today won't be perfect — mine certainly wasn't. But it'll be functional, honest, and specific, which puts you ahead of most freshers still sending out that three-page biodata with the decorative border. Start there.

How to Write an Effective Resume for Freshers in India