Most fresher resumes in India say the same things in the same order and get skipped in under 30 seconds. After 27 years of reviewing resumes on the hiring side, here is the honest guide to writing one that actually gets read.
A fresher resume for IT companies is the first thing that decides whether you get a chance — or get skipped.
Not your CGPA. Not your college. Not your project.
Your resume.
Because nobody sees any of those things until they have first decided your resume is worth reading.
Here is the number I open every resume workshop with.
A recruiter at a large IT company — TCS, Infosys, Wipro, Accenture, HCL — reviews anywhere between 80 to 150 resumes on a busy campus drive day. That is not a number I am guessing. I have sat in those rooms. I know what that pile looks like and I know how fast it moves.
The average time spent on a resume before a decision to read further or move on? Under 30 seconds.
Thirty seconds. For something most students spend three hours writing.
I have reviewed thousands of fresher resumes over 27 years. The ones that get skipped are almost never skipped because the student was unqualified. They get skipped because the resume made the recruiter work too hard to find the relevant information. The recruiter’s job is not to search for your strengths. Your resume’s job is to put them directly in front of the recruiter’s eyes — in the first glance.
That is what this guide teaches you to do.
Before you write a single line, you need to understand what the reader is actually scanning for.
A recruiter reviewing a fresher resume for IT companies is looking for four things in rapid sequence.
First — Can this person join us? Eligibility. Graduation year, academic percentage, branch. These are filters. If the numbers are not clear and visible in the first glance, the resume gets set aside.
Second — Do they have relevant skills? Programming languages, tools, technologies. A recruiter at TCS is not reading your entire education section before they look for Java or Python. They scan for the skills section first.
Third — Have they done anything with those skills? Projects, internships, certifications. One real project that is explained well outweighs five buzzwords with no context.
Fourth — Do they communicate clearly? A resume full of spelling errors, formatting inconsistencies, or sentences that do not make sense tells the recruiter something important — and not something good.
Everything in your resume either supports these four questions or adds noise that makes them harder to answer. Remove the noise. Answer the four questions fast and clearly.
That is the entire strategy.
This goes at the top. Every time. Without exception.
What to include: Full name — large and clear. Mobile number — one number, make sure it is active. Professional email address — firstname.lastname@gmail.com. LinkedIn profile URL — shortened and active. GitHub link — only if you have meaningful code on it. City — just the city name, not your full home address.
What not to include: Date of birth. Father’s name. Religion. Marital status. Passport number. Photograph.
I still see resumes in 2026 with passport-size photos in the top right corner and father’s occupation listed under personal details. This is not the 1990s. Indian IT companies do not want this information on a resume and in some cases it creates compliance issues for them. Remove everything personal that is not your name, contact number, email, and LinkedIn.
Keep this to two sentences. Maximum.
Most fresher career objectives read like this: “To work in a dynamic organisation where I can utilise my skills and contribute to the growth of the company while also growing myself.”
That sentence says nothing. Every fresher says exactly that. It goes unread.
Write something specific instead.
Example that works: “Final-year Computer Science student at XYZ College, Bhubaneswar, with hands-on experience in Python and MySQL through a hospital management project. Looking to join a software development team where I can contribute from day one while building expertise in backend development.”
Specific. Brief. Shows what you have done and what you want to do next. That is the entire job of this section.
List in reverse chronological order — most recent first.
Format for each entry: Degree name — College name — University name — Year of passing — Percentage or CGPA
Example: B.Tech in Computer Science — ABC Engineering College — BPUT — 2025 — 72% (7.2 CGPA)
Do the same for Class 12 and Class 10.
Two things to get right here.
First — always show both percentage and CGPA if your college uses CGPA. Some companies calculate differently. Show both and let them use whichever they need.
Second — if your percentage is above 60 but your CGPA looks low because your college uses a 10-point scale, convert it and show the percentage prominently. A 6.5 CGPA on a 10-point scale reads differently to a recruiter than 65% — even though they are the same thing.
This is the section recruiters scan first after your name. Make it count.
Organise it in three sub-categories:
Programming Languages: Python, Java, C++ — list only what you can actually use, not what you studied briefly in second year.
Technologies and Tools: MySQL, Git, HTML, CSS, VS Code, Postman — again, only what you have actually used.
Soft Skills: Communication, problem-solving, team collaboration — list these sparingly. One line. Soft skills claimed without evidence mean nothing.
Here is the rule I give every student when they show me their skills section. If I put you in a room right now and asked you to demonstrate that skill in 10 minutes — could you? If yes, it goes on the resume. If you would need to Google the basics first — it does not. Recruiters ask about every skill on your resume in the technical interview. Skills you cannot back up turn into liabilities the moment the interviewer asks a follow-up question.
This is the most important section on a fresher resume. More important than education. More important than skills.
Here is why.
Education tells the recruiter what you were taught. Projects tell the recruiter what you actually did with it. There is a very large difference between those two things in the eyes of a hiring manager.
How to write a project entry:
Project name — Technology used — Month and Year
Two to three bullet points. Each bullet answers one question:
Example that works:
Hospital Management System — Python, MySQL, Tkinter — Jan 2025
Example that does not work:
“Developed a hospital management system using Python and MySQL as part of my final year project.”
One line. No outcome. No specific contribution. No indication of scale or impact. This version gets skipped.
The single most common resume mistake I see from freshers — and I mean this genuinely, after 27 years of reviewing resumes — is writing project descriptions that say what the project was but not what the student specifically did. If you worked in a team of three, tell me what your part was. “I built the login and authentication module” is a thousand times more useful than “we developed a web application.” Specificity is the difference between a project that impresses and a project that fills space.
List two to three projects. Your final year project first. Then any internship project. Then any personal or open-source project if relevant.
If you have done an internship — list it here above projects.
Format: Role — Company Name — Duration — Location (or Remote) Two to three bullet points on what you did and what you contributed.
Even a one-month internship from a small company is worth listing if you actually worked on something real. It shows initiative. It shows professional exposure. It makes you immediately different from the majority of freshers who have none.
If you converted your internship to a PPO or received strong feedback, mention it. For guidance on how internship experience translates into placement advantage, the Internship to PPO guide on cguru.co.in covers this in detail.
List certifications that are relevant to the role you are applying for.
Relevant: AWS Cloud Practitioner, Google Associate Cloud Engineer, Python for Data Science (Coursera), HackerRank certifications, NASSCOM FutureSkills badges.
Not worth listing: Random one-day workshop certificates with no assessment. Certificates of participation from college fests. Online course completion certificates from platforms with no credibility or assessment component.
One strong certification is worth more than six participation certificates. Quality over quantity. Always.
Keep this section brief. One to four bullet points maximum.
What belongs here: Hackathon wins or strong placements. Technical competition results. Leadership roles — placement cell coordinator, technical club head, student chapter lead. Academic awards or rank in class. NSS or NCC if you held a position of responsibility.
What does not belong here: “Participated in cultural festival.” “Member of photography club.” “Attended a national seminar.” Participation without outcome adds length without adding value.
I have reviewed resumes with seventeen bullet points in the achievements section — including “participated in college cricket tournament” and “attended a career fair.” When everything is highlighted, nothing is highlighted. A recruiter reading a long achievements section stops reading it after the third point. Four strong points are better than twelve weak ones every single time.
Content is what gets you the interview. Formatting is what gets your content read. Both matter.
Length: One page. Always. Freshers with zero to one year of experience have no justification for a two-page resume. If your resume is going to two pages, something needs to be cut — not formatted smaller.
Font: Calibri, Arial, or Georgia. Size 10 to 11 for body text. Size 14 to 16 for your name. No decorative fonts. No Comic Sans. No Times New Roman — it reads as old-fashioned to most recruiters under 40.
Margins: 0.75 inches on all sides minimum. Do not compress margins to fit more content. If you need to compress margins to fit everything — you have too much content.
Colour: Use one accent colour sparingly — for section headers only. Navy blue, dark teal, or charcoal work well. No bright colours. No gradients. No coloured backgrounds.
File format: Always save and send as PDF. Never Word. Word documents reformat differently on different computers. What looks perfect on your laptop may look broken on the recruiter’s screen. PDF preserves your formatting exactly.
File name: FirstName_LastName_Resume.pdf. Not “resume_final_v3_ACTUAL_FINAL.pdf.” Not “my resume.pdf.” Your name. The word resume. PDF extension. That is it.
Columns: Avoid two-column resume templates. Applicant Tracking Systems — the software many large IT companies use to scan resumes before a human sees them — often cannot read two-column formats correctly. Your skills section may literally disappear from the system’s view. Single column. Always.
This is the part most resume guides written for Indian students skip entirely.
Large IT companies — TCS, Infosys, Wipro, Accenture, HCL, Cognizant — use Applicant Tracking Systems to scan resumes before a human ever sees them. The ATS reads your resume and scores it based on keyword matches with the job description. Resumes below a certain score threshold are filtered out automatically.
You can write the perfect resume for a human reader and still never reach one — if the ATS cannot read your file.
What causes ATS failures:
Two-column templates — already mentioned. The ATS reads left column, then right column independently. Your content gets scrambled.
Tables and text boxes — ATS systems often skip content inside tables and text boxes entirely. Skills listed in a table may register as blank.
Headers and footers — contact information placed in the header of a Word document is invisible to many ATS systems. Put your contact details in the main body of the document.
Images and icons — decorative elements, icons next to section headings, profile photos — ATS systems cannot read any of these. They just see blank space where your content should be.
Uncommon section headings — ATS systems recognise standard headings: Education, Experience, Skills, Projects, Certifications. If you label your skills section “What I Bring to the Table” — the ATS may not recognise it and skip it.
The fix is simple. Clean, single-column format. Standard section headings. No tables, text boxes, or images. PDF format from a clean Word or Google Docs source. Your content in the main body — not in headers or footers.
I started warning students about ATS filtering around 2018 when large Indian IT companies began rolling out these systems for high-volume campus drives. Before that, every resume reached a human. Now many do not. The students who know this write differently. The students who do not know this write beautiful resumes that never get seen. Now you know.
Keywords are the specific words and phrases that match what the company is looking for.
For IT fresher roles, the most commonly scanned keywords in 2026 are:
Programming: Python, Java, C, C++, JavaScript, SQL Web: HTML, CSS, React, Node.js Database: MySQL, MongoDB, Oracle Tools: Git, GitHub, VS Code, Linux, Postman Concepts: Data Structures, OOPS, DBMS, Computer Networks, Operating Systems Soft Skills: Communication, Problem Solving, Team Collaboration, Analytical Thinking
Look at the job description or the company’s fresher hiring page. Note the specific words they use. Use those exact words in your skills section and project descriptions — naturally, not stuffed in awkwardly.
If TCS mentions “Java” and “DBMS” in their fresher job posting — make sure those exact words appear in your resume if you actually have those skills. Not “object-oriented language” for Java. The word Java itself.
Your base resume stays the same. But small adjustments for each company make a difference.
TCS: Emphasise programming fundamentals and DBMS. TCS NQT tests these specifically. If you have cleared TCS NQT, mention the score and track on your resume — it is a genuine signal. Read the full TCS NQT preparation guide on cguru.co.in.
Infosys: Emphasise problem-solving projects and any InfyTQ certification prominently. Infosys values platform-based learning evidence. Read the Infosys InfyTQ guide.
Wipro: Emphasise communication-adjacent experience — presentations, GD participation, spoken English training. Wipro NLTH weights communication heavily. Read the Wipro NLTH guide.
Cognizant: Emphasise verbal ability evidence and any data or analytics-adjacent project work. Read the Cognizant GenC guide.
Accenture: Emphasise client-facing or communication experience. Any presentation, workshop, or team leadership role. Read the Accenture hiring process guide.
HCL: Emphasise technical depth — specific tools and technologies you have genuinely used. Read the HCL Tech careers guide.
These five mistakes appear on more than half the resumes I review. Fix them before you send your resume anywhere.
Mistake 1 — Lying about skills. If Python is on your resume, expect a Python question in the technical interview. If you cannot answer it — the interviewer now knows your resume is not honest. One dishonest skill destroys the credibility of every honest one. List only what you can genuinely demonstrate.
Mistake 2 — Using the same objective for every company. “To work in a reputed organisation” is a sentence that tells the recruiter you did not care enough to write a specific line for their company. Two sentences. Specific to the role. Change it for each application.
Mistake 3 — Project descriptions with no outcomes. “Developed a web application using React and Node.js” describes what you built. It does not describe what it did, who used it, or what changed as a result. Add the outcome. Even a small one. “Reduced search time from 8 clicks to 2” is a real outcome. Use it.
Mistake 4 — No proofreading. A single spelling error on a resume signals carelessness. Two errors signal a pattern. The document you are sending is the first piece of professional writing a company sees from you. Read it out loud once. Then ask someone else to read it. Errors you cannot see after three hours of writing will be immediately visible to someone reading it fresh.
Mistake 5 — Sending a Word file instead of PDF. Already covered in formatting — but worth repeating here because it still happens constantly. Always PDF. No exceptions.
Seven days. One action each day. Start today.
Day 1: Open a blank Google Doc. Create the eight sections in order — Contact, Objective, Education, Skills, Projects, Internship, Certifications, Achievements. Just the section headings. Nothing else. This is your skeleton.
Day 2: Fill in Contact and Education completely. Double-check every percentage figure. Make sure graduation year is correct. Convert CGPA to percentage and show both.
Day 3: Write your Skills section. Go through each skill. Ask yourself — can I demonstrate this in 10 minutes? Keep it. If not — remove it. Be honest.
Day 4: Write your project descriptions. Use the three-bullet format — what you built, what technology and why, what the outcome was. Write this for every project before moving on.
Day 5: Write your Career Objective. Two sentences. Specific to IT fresher roles. Mention your branch, one skill, and what you want to contribute. Read it aloud. If it sounds generic — rewrite it.
Day 6: Format the entire document. Single column. Clean font. One page. Save as PDF. File name: YourName_Resume.pdf. Open the PDF and read it as if you are seeing it for the first time. Fix anything that looks wrong.
Day 7: Ask one person — a senior, a faculty member, or a classmate who has already been placed — to read your resume and tell you one thing they would change. Make that change.
Read these alongside this guide:
External resources:
One page. Every time. Without exception for a fresher with zero to one year of experience.
I understand why students push back on this. They have four years of coursework, multiple projects, several certifications, club activities, and they want it all visible. The instinct to show everything is understandable. But it works against you.
Here is the reality from the hiring side. A recruiter reviewing 100 resumes in a day does not read page two of a fresher resume. Page two does not exist in their mental model of a fresher candidate. Everything that matters needs to be on page one — because that is the only page that gets read.
The discipline of fitting everything into one page also forces you to make decisions about what is genuinely important. That decision-making process is valuable in itself. If you have to choose between listing your third college fest participation certificate and writing a stronger project description — you are forced to choose the project. Which is the right choice.
If your resume is going to two pages, here is what to cut. Remove the career objective if it is generic — those two lines now become project space. Remove weak achievements — participation without outcome. Remove skills you cannot demonstrate.
Tighten every project description to three bullet points maximum. That will get you to one page.
If it still does not fit — your font is too large, your margins are too wide, or you genuinely have too much content. Format first. Cut second. But always land on one page.
Put it on your resume. Always.
Leaving the CGPA blank does not make the recruiter assume it is high. It makes them assume it is low and that you are trying to hide it. That assumption — plus the impression that you are not being straightforward — is worse than the actual number.
Here is the practical reality. A 6.1 CGPA that meets the 60% threshold — which most large IT companies use — gets your resume through the initial filter. From that point, the assessment and interview performance is what decides everything. Your CGPA has done its job by clearing the threshold. It is no longer the primary factor.
What you can do at 6.1 or 6.2 is make sure everything else on your resume is genuinely strong. A real project with clear outcomes. One relevant certification. Clean formatting. A specific objective. These elements compensate in the human evaluation stage — not the filter stage, but the stage that actually decides your offer.
I have reviewed resumes with 6.1 CGPA that got selected over resumes with 8.5 CGPA — because the 6.1 student had a real project they could explain and the 8.5 student had three lines of generic text under each section. The CGPA opens or closes the door. What you have done with your time opens the interviewer’s interest. Both matter. Neither alone is the full story.
This comes up constantly. And there is a clean way to handle it.
Write the project entry normally — project name, technologies, two to three bullet points describing what the project did and what it achieved. Then in the bullet points, be specific about your individual contribution.
Instead of: “Developed an e-commerce platform using Django and PostgreSQL”
Write: “Built the user authentication and order management module of a four-person team project — an e-commerce platform using Django and PostgreSQL that handled 200 test transactions in deployment”
The phrase “four-person team project” is honest — it signals collaboration. “Built the user authentication and order management module” is also honest — it signals your specific contribution. You are not taking credit for the whole project. You are accurately describing what you did within it.
This approach actually works in your favour in interviews. When the interviewer asks about your project, you can speak confidently about your specific module — because you genuinely owned it. Students who wrote vague group project descriptions struggle to answer specific follow-up questions because they are not sure which parts they actually built.
Own your part specifically. Credit the team honestly. Both things can be true in the same bullet point.
This is the most honest and most common question I get from freshers. And the answer has two parts.
First — the short-term fix for the resume you need to submit now.
College coursework assignments can be framed as projects if they involved building something real — even if it was for a grade. A database management assignment where you built and queried a library management system is a project. A data structures assignment where you implemented a sorting algorithm and measured its performance is a project. Write it with the same three-bullet structure — what you built, what technology you used, what the outcome was. Be honest about the context — “academic project” is fine to include. Do not pretend it was professional work.
Add any online course you completed with an assessment — Python on Coursera, SQL on HackerRank, cloud fundamentals on AWS or Google. List the certification and the platform. It is evidence of learning initiative even without professional context.
Second — the medium-term fix you should start today.
Build one small personal project this month. It does not need to be complex. A weather app using a public API. A simple to-do list in Python with a database backend. A basic portfolio website. Something you built yourself, that works, and that you can put on GitHub.
The most competitive freshers I have seen in recent placement seasons are not the ones from the best colleges. They are the ones who built something small and real and can talk about it with genuine ownership.
A personal project you built alone — even a simple one — tells a recruiter more about your capability and initiative than three group assignments and a participation certificate. Start building something this week. It will be on your resume within a month.
I want to close this guide the way I close every resume review session.
Your resume is not a record of your past. It is an argument for your future.
Every line on it should answer one question — why should this company give me thirty minutes in an interview room?
Not every line needs to be impressive. But every line needs to earn its place.
If a line does not answer that question — cut it. If a section is weak — improve it or remove it. If your project descriptions are vague — make them specific. If your skills list includes things you cannot demonstrate — remove them today.
The resume that gets you into the room is not the longest one or the most decorated one. It is the most honest, most specific, most readable one.
Thirty seconds. That is your window.
Make every second count.
Written by Aslam Rahman — IT Career Consultant with 27 years of experience in IT hiring, fresher placement strategy, and career guidance for Indian students. Based in Bhubaneswar, Odisha. Founder of Career Guru — cguru.co.in.
Every IT interview in India starts with the same question. Most freshers answer it the…
HCL Tech is one of the most underrated fresher employers in Indian IT. After 27…
Most interns who do not convert internship to PPO in india, were not lazy or…
Getting placed is only the beginning. After 27 years of watching freshers join Indian IT…
The Accenture hiring process for freshers has more rounds than most students expect. After 27…
Most freshers either never negotiate or negotiate the wrong way. After 27 years of watching…