Writing Your First Resume in India: What No One Tells You

When I was finishing my engineering degree, I spent three days perfecting my resume. I had a Canva template with a gradient sidebar, a pie chart showing my "proficiency" in different languages (Python: 80%, Java: 60%, C++: 40%), and an objective statement that said something like "seeking a challenging role in a growth-oriented organisation."

Every single thing I just described was wrong.

Here's what I wish someone had told me before I sent that resume out to 40 companies and heard back from exactly two of them.

The pie chart / skill bar thing — please stop

They look cool. They mean nothing. How do you decide you're "80% proficient" in Python? No one knows. Recruiters don't know. You don't know. More importantly, ATS software can't parse them at all — it just skips over them. You're wasting prime resume space on something that actively hurts you. Delete it. Write a plain list of skills instead.

Your projects are your experience

You don't have work experience. That's fine — the recruiter knows you're a fresher. What they're looking for is evidence that you can actually build things. Your projects section is where that evidence lives.

But most fresher projects sections are terrible. "Built a CRUD application using React and Node.js." That's not a project description — that's a technology list. Tell me what it does, who it's for, what problem it solves, and what you had to figure out to build it.

Compare:
❌ "Todo application using React"
✅ "Task manager app for college teams — React frontend, Supabase backend, real-time updates via WebSockets. Handles concurrent edits without conflicts. 200+ classmates used it during exam season."

The second one shows initiative, shows that people actually used the thing, and shows you thought about a real problem. That's what gets you a callback.

The objective statement is dead

Nobody reads objective statements. "Seeking a challenging role in a dynamic environment" tells a recruiter exactly nothing about you. Replace it with a 2-3 line summary that actually says something: your degree, your strongest technical skills, and what kind of role you're targeting. Keep it specific. "B.Tech CSE graduate with strong Python and SQL skills, looking for backend or data engineering roles at product companies" is infinitely better than generic aspirational language.

Your CGPA — include it or not?

If it's above 7.5, include it. If it's 7.0-7.5, use your judgment — some companies filter below 7.0 so being above helps. If it's below 7.0, leave it out unless a company specifically asks. Your projects and skills matter more anyway.

One page, always

You have zero years of experience. You do not need two pages. If your resume is running over one page, cut something. The certifications section can go on your LinkedIn. The "hobbies" section should already be gone (cricket and music don't help you get a software job). Keep it tight.

Before you send it anywhere

Run it through Uplio. It'll catch the keyword gaps, the missing sections, the ATS formatting issues — the things that are silently getting your resume filtered out before anyone sees it.