10 Resume Mistakes That Can Hurt Your Job Search

Making your resume unnecessarily long

Padding the resume because a longer one looks more impressive is the slip most freshers make. The file looks thin, so sections get added. Certificates, skills, a paragraph for every college activity, another for the internship. Before long there are three or four pages. Irrelevant information is what costs you, and extra pages are where it collects.

No rule says every resume has to be exactly one page. For a fresher, one page usually covers it because there is not enough relevant work to fill more. A few years in, one or two pages makes sense. Somebody twenty years into a career can go longer and nobody minds. Adding a page to look experienced does not work.

Read each line and ask whether it shows you can do this job. A college project does not need four sentences on the team's weekly meetings. What you built, the part you handled yourself, the tools you used, the result. Trim it and the page count falls on its own. Take the current draft and delete every line that does not name a tool you used or a result you produced.

Putting every skill you know on your resume

Python - Advanced

One online course, two hours long, is usually all that line means. The interview is where it gets expensive: the panel asks you to write a loop or explain a decorator, and you have nothing. You do not need to be an expert in everything you list. Be accurate about your level, and be ready to describe the project or coursework the skill came from.

Skills sections grow because nothing ever gets deleted from them. A mechanical engineering graduate applying for a design role lists CATIA, SolidWorks, GD&T and engineering drawing, and the recruiter reads all four. Add ten skills used once, and those four are harder to find.

Before typing, check which of your skills this particular job uses. A software opening wants Python, Java, SQL and Git. A VLSI opening wants Verilog, SystemVerilog and RTL. Same person, two resumes.

Five relevant skills you can demonstrate are enough for a fresher resume. Thirty that you have touched once give the panel thirty things to ask about.

Turning your resume into a project report

Pull up your project section and read it the way a recruiter will, in about twenty seconds. Background, objective, methodology, components, testing, results: a college report walks through every one of those. Pasted into a resume, it becomes four or five dense paragraphs sitting under one heading.

A recruiter needs three things from that space. What you built, with a clear name attached to it. What you personally did, which matters most in a five-person project where you did not handle every part. And what came out of the work. Numbers help: reduced weight by 10%, accuracy improved from 85% to 93%, processing time down 20%. Do not invent one. Where there is no genuine measurement, write the result in plain words.

BeforeDeveloped a complete aircraft wing design project. The objective was to study various aerodynamic parameters, understand airfoil characteristics, perform extensive design analysis, conduct simulations, analyze results and evaluate the overall performance of the wing.

BetterDesigned and analyzed a NACA 0010 aircraft wing using CATIA and ANSYS, focusing on geometry development and aerodynamic performance. Evaluated simulation results and documented design observations.

Letting AI write your entire resume

You paste your resume into a chatbot and ask it to rewrite the whole thing from scratch.

Used properly, AI works as an editor. It fixes grammar, shortens a sentence that ran too long, checks your resume against a job description, flags keywords you missed, and suggests clearer wording for a bullet you wrote in a hurry.

The trouble starts when you copy the output without checking a line of it. Claims you cannot defend end up on the page.

Expert in Python and advanced machine learning.

The interviewer asks a basic technical question about it and you cannot answer. The resume has now created a problem that did not exist before.

Feed the tool facts. Describe what you actually built on the project, which CATIA workbenches and tasks you handled, what you used Python for, and your own contribution if you worked in a team. Then let AI improve the wording. Do not let it turn limited exposure into expertise. Do not let it invent achievements, numbers, responsibilities or experience.

Choosing a pretty template over a readable one

There are thousands of resume templates online, and many of them come with multiple colours, icons, charts, skill bars, photos and complicated layouts. They look impressive on the first scroll. A recruiter opens the file with a few seconds to spare. Your education, experience, projects and skills have to be findable without hunting through decoration.

Open your resume, look at it for five seconds, then check what you can find: your name, your target role or professional identity, education or experience, relevant skills, projects or achievements, contact information. If you had to hunt for your own details, the design needs work.

• Too many colours
• A huge profile photo
• Skill bars
• Excessive icons and complicated graphics
• Three-column layouts that squeeze the content
• Decorative sections that don't provide useful information

Push everything into three narrow columns and the font size is the first thing to shrink.

Sending the same resume to every job

Three positions. One file uploaded to each. The Mechanical Design Engineer posting gets a page that opens with Python, Java and SQL. The VLSI opening gets the same page. Neither recruiter reaches the line about CATIA or Verilog, because the top half is spent on work the role does not involve.

You are the same person in all three applications. The jobs are not, and the parts of your background that deserve the most attention change with them. Software roles pull Python, APIs, SQL and Git forward. Mechanical design pulls CATIA, SolidWorks, GD&T, engineering drawing and CAD projects. VLSI pulls Verilog, SystemVerilog, RTL and FPGA.

Nobody needs 100 resumes. Build one base file and change the job title, the skills line, the project descriptions and, occasionally, the order of the sections. A project bullet sitting third on a mechanical resume can move to the top of a software one if that project is the one with an API in it. The table on this page lists what each role type responds to, so check it before you start editing.

Save each version under the role name, so resume_mech_design.pdf goes to the design posting and resume_final.pdf stays on your desktop.

Chasing an online ATS score

What ATS score is good enough to get shortlisted? That is the search. You find a tool, upload your resume, and a number appears. Maybe 97% ATS Score.

No single system scores resumes for every company. Employers run different applicant tracking systems, and their screening methods differ. A high score from a third-party scanner says nothing about whether a recruiter will contact you.

Don't spend hours dragging an imaginary 83% up to 97%.

Open the job description and read it closely.

• Responsibilities listed in the posting
• Skills the company has asked for
• Qualifications named in the ad

Now write your resume so the relevant work you have done sits where a screener can see it. Used SQL in a project? One clear line. Completed a design project in CATIA? Name the project and the tool. Inside a long paragraph, the same experience gets missed.

Adding unnecessary personal information

The most common slip is pasting date of birth, father's name, mother's name, marital status, full residential address, a large passport photograph, religion and other unrelated details into a resume.

A resume is not an identity document. For most modern professional applications, the focus should be on information that helps the employer evaluate your professional fit. That means name, phone number, professional email, LinkedIn, portfolio or GitHub where relevant, education, experience, skills, projects and relevant achievements.

Photographs are not a universal yes-or-no rule. Whether a photo belongs on a resume can depend on the country, industry, employer and type of position. Don't blindly copy a resume format from someone on the internet just because it looks professional. Look at the expectations for the role and location where you are applying.

Treating certificates like experience

Certifications: Python, SQL, Excel, Data Analytics, Machine Learning, Cloud, Communication, Leadership

That line sits near the top of the resume and covers four or five rows. Below it, the Projects section says "Academic project on machine learning" and stops. The recruiter has a page of course names and no idea what you built with any of them. A certificate records attendance and a passing score. The job posting is asking about something else.

Some certificates do carry weight. A cloud provider's associate certification, a vendor exam with a proctored test, a recognised data analytics programme. Those belong on the page. A two-hour course on a learning app does not take the same space as a semester project, and it should not. Your project entry has room for the tool you used, the problem you hit, the fix, and the result.

Which ones to list

• Directly relevant to the role you are applying for
• Recognised by the industry, not only by the course seller
• Recent, where recency matters
• Backed by a project you can describe out loud

Lying on your resume

Open your resume and read the dates next to each job. If one of them was stretched by two months to close a gap, change it back before you send the file anywhere.

An invented employer is the version people picture first. The other edits are smaller and do not feel like lying.

• Dates moved to hide a gap
• A job title you never held
• Marks or percentages raised
• A skill listed as advanced
• Results the project never produced
• Responsibility for work someone else did

The interview is where it surfaces. An interviewer can ask about anything printed on the page. Claim experience with a technology and the technical round tests that claim. Say you led a project and the questions turn to decisions you took. Put a number in a bullet and someone may ask how you measured it.

If you are covering a career gap, do not invent an employer to fill it. Explain the gap when it comes up, and use the rest of the resume to show what you did in those months. If a project did not produce an impressive figure, write what it did produce. If a skill is at a basic level, word it that way.

A claim about work you never performed is the hardest one to defend. You have to describe it in detail, on the spot, to an interviewer who does that work every day.