The skills section of a resume is a short list of the tools, languages and methods you can do the job with. It is not a place to describe yourself. It is the part a recruiter’s search and a quick reader’s eye both go to first, so what you put there, how many you list and how you lay them out all matter more than its size suggests.
What the skills section is for
It is searched before it is admired. As the ATS keywords guide describes, a recruiter on Naukri or inside an applicant tracking system narrows candidates by typing a skill, then reads what is left. A skill you have but never wrote as plain text is, for that search, a skill you do not have.
So the section has two jobs. It makes you findable by the exact terms the job uses, and it lets a human see in five seconds that you match the stack. Everything below follows from those two jobs.
How many skills to list on a resume
For most resumes, 8 to 12 hard skills. A hard skill is something you could be tested on: a language, a tool, a certification, a method. Fewer than six and you may be missing terms you genuinely use. Past 12 or 15, you are probably listing half-skills, and a reader who sees a long tail starts to doubt the top of it.
| Profile | Hard skills | Why |
|---|---|---|
| Fresher | 6-12 | Only what a project, internship or course actually used |
| 2-5 years, technical | 8-12 | The core stack plus the tools you use daily |
| 5+ years, technical | 8-15 | A wider stack is believable, if grouped |
| Non-technical (sales, HR, accounts, support) | 6-10 | Fewer named tools exist, so the list is shorter |
Those are my rule of thumb, close to the ranges in the ATS keywords guide and the fresher resume format, and they are not a standard. Published guides disagree. On 12 October 2026 I read two. Indeed’s guide to resume skills (last updated 15 June 2026) says most job seekers list around 8 to 10. ResumeCoach’s skills section guide says 10 to 15, and it counts soft skills in that figure. They differ because they count different things. I would rather you count only what you could discuss for two minutes in an interview.
If your list runs past 15, the usual cause is one resume aimed at three different roles. Two focused versions beat one that tries to cover everything.
Where the skills section goes: top of the page or lower
Put it on page one. Beyond that, guides disagree, and the right place depends on what is strongest on your resume.
- With some experience (about 2 years or more): just under the summary, above your jobs. That is where the experienced resume format puts it, so a recruiter sees the stack before the history.
- Freshers: the fresher resume format places skills after education, projects and internships. That works when your projects show the same tools. If a role asks for a specific tool and your projects are thin, move the skills block up under the summary.
A skills block lower in the page still works. It is the section that is missing from a resume, or hidden in an image, that costs you.
Group them, do not rate them
Write skills as plain-text lines, grouped by type, with the group name first:
Languages: Java, Python, SQL
Frameworks: Spring Boot, Hibernate
Tools: Git, Docker, JenkinsGrouping lets a reader jump to the line they care about. Order the lines, and the items in each line, by what the job needs most.
Do not rate yourself. Skill bars, star ratings and percentages show a level, not a skill. Nobody can check “Python 80%”. At best the skill name still parses and the bar adds nothing a reader trusts. At worst the block is drawn as a picture and the words are not text at all, which is the case the ATS keywords guide warns about.
Layout also decides what a parser reads first. In our own two-column resume test, the left sidebar in two of the templates, Slate and Harbor, was extracted before the main column. That was pdf.js text extraction, which approximates and is not any vendor’s ATS. It does mean a skills sidebar can be read in an order you did not plan, so a plain line in the main column is the safer home.
If you build the resume in ApplyCove’s free resume builder, its List styles setting has a Grouped option that prints each skill as a bold group name followed by its items, such as “Frontend: React, TypeScript”. The Kernel and Vector templates use that layout by default. The builder also offers bars and dots, which I would not use, for the reason above.
Soft skills belong in your bullets
Communication, teamwork and leadership are real, and so is the problem with listing them. Most skills lists include them, and the ATS keywords guide notes that they are almost never filtered on. ResumeCoach (the guide cited above) takes a different view, that soft skills are often the deciding factor for recruiters. Its advice to put them throughout the resume agrees with mine on where they go.
So prove them in the bullets, where they come with evidence. “Led a team of [N] support agents” shows leadership. “Presented the quarterly plan to [N] senior stakeholders” shows communication. Resume bullet points examples shows how to attach a number, and action verbs for resume gives the verb to start each one. If the posting names a soft skill, one short line is enough.
Match the skills to the job description
The reliable method is a count, not a guess. Open five to ten current postings for the role you want, note every skill and tool they name, and keep the ones that appear in more than half. Drop any you could not discuss for two minutes. The tailoring guide walks the whole edit on one posting.
Use the posting’s spelling. “Power BI”, not “PowerBI”. “Machine Learning” or “ML”, whichever the postings use most. Write each skill once in the skills section and once inside a bullet that shows you used it, so the skill makes you findable and the bullet makes you credible.
Skills section examples by role
These are grouped patterns. Take the structure and replace every item with what you have actually used. Each block stays within 12 skills, in line with the counts above.
Software engineer (Java backend)
Languages: Java, Python, SQL
Frameworks: Spring Boot, Hibernate
Tools: Git, Maven, Jenkins, Docker
Cloud: AWS (EC2, S3)Data analyst
Analysis: SQL, Python (pandas), Excel (pivot tables)
Visualisation: Power BI, Tableau
Methods: A/B testing, regression, cohort analysisQA and test automation
Automation: Selenium, TestNG, Postman, RestAssured
Languages: Java, SQL
Tools: Jira, Git, JenkinsSales and business development
CRM: Salesforce, HubSpot
Prospecting: LinkedIn Sales Navigator, lead qualification, cold outreach
Process: pipeline management, proposal writing, contract negotiationHR and recruitment
Sourcing: Naukri, LinkedIn Recruiter, boolean search
Systems: Zoho Recruit, Keka, greytHR
Process: onboarding, payroll coordination, interview schedulingDigital marketing
Search: SEO, Google Ads, Google Search Console
Analytics: Google Analytics 4, Looker Studio
Social and email: Meta Ads Manager, MailchimpAccounts and finance
Software: Tally Prime, Zoho Books, MS Excel
Compliance: GST filing, TDS, bank reconciliation
Reporting: MIS reports, monthly closeCustomer support and operations
Tools: Zendesk, Freshdesk, MS Excel
Process: ticket escalation, SLA tracking, root-cause notes
Languages: English, Hindi, KannadaFresher (computer science)
Languages: Java, Python, SQL
Web: HTML, CSS, React
Tools: Git, VS Code, MySQLFor a fresher, every item should show up in a project or an internship line. “Studied DBMS” and “PostgreSQL” are different claims, and only the second belongs here. The full pool for each role is in the ATS keywords by role list.
What to drop
- Ratings of any kind: bars, stars, percentages, “expert” labels.
- Soft-skill words with no proof: “hardworking”, “team player”, “quick learner”.
- Anything you could not discuss for two minutes. Each skill is a question you have agreed to answer.
- Tools you touched once, and software so old the postings no longer name it.
- Spelling variants of the same skill as separate entries.
Keep it in sync with Naukri and LinkedIn
Skills get typed three times: on the resume, in the Key skills field on Naukri, and in the skills section on LinkedIn. During my own job hunt I was pasting the same expected CTC, notice period and current location into form after form. I once timed it at about 8 minutes per application, most of it re-typing what I had already typed elsewhere. Skills are the same trap with a different label, and the spelling drifts: “Power BI” in one place, “PowerBI” in another.
My opinion: rewriting the skills section for every application is not worth it. Keep one master list. For your 10 dream roles, reorder the top line by hand so the posting’s main requirement sits first, and tailor properly. For the rest, send the master. Then paste the same spelling into Naukri and LinkedIn. The Naukri field has its own rules about count and search, which key skills for Naukri profile covers. Its suggested count is higher (15 to 20 tags) because it is a search-tag field, while this is a document section a person reads.
One pass to do tonight
Open your resume. Count the hard skills. Cut it to the range in the table, put the group name at the start of each line, and delete any bar or rating. Then compare the top five skills with the posting you most want, and fix the spelling to match.