Why small mistakes matter so much
At a busy campus drive a recruiter might review several hundred CVs for one role, often on the evening before the interviews. Most CVs get a quick scan: name, course, CGPA, the top project, a few skills. If something is confusing or missing, the recruiter moves on. Nobody calls to ask what you meant.
The good news is that most of the problems below take an afternoon to fix. Work through them in order.
1. Half the first page is personal details
Date of birth, father’s name, mother’s occupation, religion, marital status, passport number, full permanent address, and a list of languages “known.” This format is common because it was copied from an old template, and it pushes your actual work to the bottom of the page.
Fix: keep your name, a professional email, a phone number, your city, and links to LinkedIn and GitHub or a portfolio. Your university already holds the rest.
2. A career objective that says nothing
“To work in a challenging environment where I can utilise my skills for the growth of the organisation.” Every recruiter has read this sentence thousands of times.
Fix: replace it with a one-line headline that says what you are and what you are aiming for, for example: “Final-year B.Tech ECE student focused on embedded systems, with two firmware projects on STM32.” If you cannot write it, that is useful information about what to work on.
3. Academic numbers that do not match your records
This is the mistake that hurts most, because it looks like dishonesty even when it is a typo. A CGPA of 8.2 on the CV and 7.9 on the university record. A 12th percentage rounded up. “No backlogs” when one was cleared only last month.
Fix: copy your numbers from your marksheets, state the scale (“CGPA 7.9 / 10”), and mention a cleared backlog honestly if asked. On platforms where the university verifies academic records, such as EzUnihire, recruiters see the verified value anyway, so a mismatch helps no one.
4. Projects written as titles, not results
“Library Management System using Java.” “Face Recognition Attendance System.” Recruiters see the same final-year project titles every season. The title tells them nothing about what you did.
Fix: for each project write two or three lines that answer what problem it solved, what you personally built, and what happened. For example:
- Built the REST API and MySQL schema for a hostel complaint tracker used by around 400 students in our block
- Cut average response time from three days to one by adding automatic routing to the warden on duty
A small real project with a number beats a large project with none.
5. A skills list you cannot defend
C, C++, Java, Python, JavaScript, React, Node, Machine Learning, Deep Learning, Blockchain, Cloud, MS Office. The technical interviewer will pick one at random and ask you to write code in it. If you listed it, it is fair game.
Fix: list the skills you can use in an interview today, and group them: languages, frameworks, tools. Put your strongest first. Drop MS Office unless the role specifically asks for Excel modelling. Three skills you can defend are worth more than twelve you cannot.
6. One CV for every drive
Sending the same CV to a service company, a product startup, a core electrical company, and an analytics firm means it is not quite right for any of them.
Fix: keep a master CV with everything, and make a short version per role family. For an analytics role, lead with your SQL and statistics projects. For a core role, lead with your internship and lab work. Read the job description and make sure the skills it names appear in your CV where they genuinely apply.
7. Formatting that breaks on the recruiter’s screen
Two-column designs with icons, tables, text inside images, headers and footers holding your contact details, three pages for a fresher, and a file called resume final new (2).pdf. Many of these break when an applicant tracking system reads the file, and your contact details or skills simply disappear.
Fix: a single column, standard section headings (Education, Projects, Experience, Skills), one page unless you have substantial work experience, exported as a PDF named Firstname-Lastname-CV.pdf.
Before every application, ask one question: could a recruiter who knows nothing about me understand what I can do in thirty seconds?
Check your CV before you send it
EzUnihire’s CV Analyzer scores a CV on five checks: file quality, skills, headline, academic completeness, and contact completeness, using what is actually in your profile. It is a quick way to catch several of the mistakes above before a recruiter does. Pair it with the AI interview prep, which builds practice questions from the real company and role you are applying to, so your CV and your answers tell the same story.
Your placement cell is also a good second reader. Most placement officers have seen thousands of CVs and will tell you in five minutes what a recruiter will think in five seconds.
