The skills section is the fastest part of your resume to fix and the easiest to get wrong. Here is what belongs in it, how recruiters and applicant tracking systems actually read it, and what to write when you have no work experience yet.
The skills section is a short, scannable list of what you can actually do, usually sitting just below your work experience or beside it in a side column. It exists for two readers. A recruiter skims it in a few seconds to decide whether you are worth a longer look. An applicant tracking system reads it as structured data, matching the terms against the criteria set for that role and using them to rank you inside a candidate database. Neither reader is impressed by length. Both are looking for a specific overlap between what the job asks for and what you list. That is the whole job of this section — not to describe you completely, but to make the match obvious in the few seconds anyone gives it.
Hard skills are the specific, teachable, checkable things: SQL, Python, Tally, AutoCAD, GST filing, Power BI, Figma, spoken Japanese. They can be verified in an interview or a test, and they are what a keyword search actually finds. Soft skills are how you work with people and problems: communication, ownership, adaptability, conflict resolution, time management. Both matter, but they carry weight in different places. Hard skills belong in the skills list, named exactly as the industry names them. Soft skills are close to worthless as a bare list, because everyone claims them and none of them can be checked — a line reading excellent communication skills, team player, hard working tells a recruiter nothing. Soft skills land when they are demonstrated inside a bullet point instead: a line saying you trained four new joiners, or handled escalations for a 200 customer account, proves communication far better than the word communication ever will.
Between eight and fifteen is the range that works for most resumes, weighted toward hard skills. Fewer than six and the section looks thin, as though you struggled to fill it. More than twenty and it stops being a signal — a list of thirty tools reads as a list of thirty things you have heard of, and a recruiter has no way to tell which three you are genuinely good at. If you have more skills than fit, group them into two or three labelled clusters, which is easier to scan and still parses cleanly: technical skills on one line, tools and platforms on another, languages on a third. Cut anything you would not want to be questioned about. Everything in this section is fair game in an interview, and being asked to explain a tool you touched once in a college project is a bad way to lose a role.
Most large employers run applications through software that parses your resume into fields before a person opens it, extracting your contact information, work history, education and skills, then storing you in a searchable database. When a recruiter searches for a skill, they are searching that extracted text. This has practical consequences for how you write the section. Name skills the way the industry names them, and include both forms where two exist, because a search for one will not surface the other: write Chartered Accountant (CA) rather than only CA, Search Engine Optimisation (SEO) rather than only SEO. Keep the list as plain text — skills placed inside a table, a graphic, or a set of star ratings frequently come back empty when the file is parsed, which means a recruiter searching for your best skill never finds you. Our free ATS resume checker shows you the extracted text and flags which of a posting's terms are missing from yours.
Mirror the vocabulary, never the whole posting. If the job says Power BI and your resume says data visualisation, you have described the same ability in words the system will not match, and changing yours to name the tool is not gaming anything, it is being specific. What does not work is pasting the requirements list into your skills section wholesale. Recruiters see the raw parsed text, and a resume where the skills happen to be a word perfect copy of the advert is obvious and reads as dishonest rather than qualified. The older tricks are worse: hidden white text, keyword blocks in the footer, and repeated terms are all things modern parsers surface and humans then judge you for. The workable version is narrow. Add the terms you can genuinely defend, phrased the way the employer phrased them, and leave out the rest.
With no employment history, this section carries more weight, not less, because it is one of the few places you can show capability directly. Pull from coursework, projects, internships, certifications and part time work. A B.Tech student can honestly list Python, SQL, Git, data structures, and whichever cloud platform their final year project ran on. A B.Com graduate can list Tally, Excel, GST returns, accounts payable and reconciliation. A student who ran a college fest has budgeting, vendor coordination and event logistics, which are real skills whatever the setting. What matters is that each one is defensible: you should be able to describe where you used it and what happened. Transferable skills from unpaid or informal work count, and leaving them out is a common reason a fresher resume looks emptier than the person actually is.
A skills section on its own proves nothing, because it is a set of claims. The resumes that convert are the ones where the same skills reappear as evidence in the experience and project bullets, with a result attached. Listing SQL says you know SQL. A bullet saying you rewrote a weekly reporting query in SQL and cut a six hour manual process to forty minutes says you can use it. Repeat your three or four most important skills across the summary, the experience bullets and the list, because that repetition is both what a human remembers and what a keyword search scores. Skills mentioned only in the list, and never again anywhere on the page, are the ones recruiters quietly discount.
Rating your own skills out of five or with progress bars is the most common one. The scale means nothing without a standard behind it, and the graphics often do not survive parsing. Listing basic computer literacy such as MS Word, email or internet browsing signals inexperience rather than competence, unless the role genuinely asks for it. Mixing spoken languages and software into one undifferentiated list makes both harder to scan. Writing the same generic set on every application, when the posting in front of you names three specific tools, wastes the easiest tailoring win available. And listing something you cannot demonstrate is the only mistake here that can end an interview rather than just weaken a resume.
The ones the job actually asks for that you can genuinely defend. Read the posting, note the tools, systems and abilities it names, and list the ones you have, using the employer's own wording. Weight the list toward hard skills such as software, tools and technical methods, since those are what a recruiter searches for and what can be verified.
Eight to fifteen suits most resumes. Below six looks thin; above twenty stops being a signal, because a recruiter cannot tell which ones you are actually good at. If you have more than fit comfortably, group them into two or three labelled lines rather than one long run on list.
Hard skills are specific and checkable — SQL, Tally, AutoCAD, GST filing, a spoken language. Soft skills are how you work: communication, ownership, adaptability. Hard skills belong in the list. Soft skills work better proved inside an experience bullet, because a bare claim of good communication is something every applicant writes and none of them evidence.
Mirror the vocabulary, not the posting. If the advert says Power BI and you wrote data visualisation, change yours to name the tool — that is precision, not manipulation. What fails is pasting the requirements in wholesale, or hiding keywords in white text. Recruiters see the parsed text, and a skills list matching the advert word for word reads as dishonest.
For an experienced candidate, below the work experience, since your history is the stronger argument. For a fresher, above it or in a side column, because skills and education are what you are actually selling. Either way keep the heading plain — a section titled Skills is found by both a recruiter and a parser, whereas a creative label may not be.
Whatever you can defend from coursework, projects, internships, certifications and part time work. Name the tools and languages from your final year project, the software you used in an internship, the certifications you finished. Skills picked up organising a college event or helping with a family business are real and count. The only test is whether you can say where you used them and what happened.
No. A self assigned rating carries no shared standard, so a four means nothing to the person reading it, and the graphics used to draw those bars often do not survive parsing, which can wipe the section entirely. Name the skill plainly and let a bullet point in your experience show the level.
They matter enormously in the job and very little as a list. Employers care about communication, ownership and how you handle pressure, but they discount the words because everyone writes them. Convert each one into evidence instead: training new joiners, running a handover, resolving a customer escalation. That is the same claim in a form a recruiter can believe.