How to Write the Skills Section of a Resume
A skills list is a promise. Write only what you can show in an interview.
What the skills section is for
The skills section lets a reader see in a few seconds whether you have the tools and abilities the role needs. It also feeds screening software and keyword searches, which look for specific terms. It works only if it is specific, grouped and true.
Group, do not dump
One long comma-separated list is hard to scan. Group skills under short labels so the reader can find the relevant group straight away. The ApplyReady builder gives you four rows, each printed as "Label: skills", and you can rename every label.
| Role type | Example groups |
|---|---|
| Software or data | Languages: Python, SQL, JavaScript. Frameworks: React, Django. Tools: Git, Docker, Excel |
| Finance or accounts | Accounting: GST, TDS, bank reconciliation. Software: Tally, Excel, SAP. Analysis: variance analysis, budgeting |
| Marketing | Channels: SEO, email, social media. Tools: Google Analytics, Canva, Mailchimp. Analysis: A/B testing, reporting |
| Operations or support | Operations: scheduling, vendor coordination. Tools: Excel, CRM. Communication: Hindi, English, written reports |
| Core engineering | Design: AutoCAD, SolidWorks. Analysis: MATLAB, ANSYS. Practice: quality checks, documentation |
Order matters
- Put the skills named in the job advert first, both in the group order and inside each group. See tailoring your resume.
- Within a group, put your strongest skill first rather than alphabetical order.
- Keep the total to roughly 10 to 20 items. A list of 40 reads as padding.
Hard skills, soft skills and how to show them
Hard skills (tools, languages, methods) belong in the skills section because they are specific and searchable. Soft skills such as "team player" or "good communicator" are weak when only listed, because anyone can write them. Show them in the bullets instead: "Led a team of 15 volunteers" demonstrates leadership far better than the word does.
Languages you speak (Hindi, English, a regional language) are worth listing, with a level such as fluent, professional or conversational. The builder has an optional Languages section for this.
Levels, bars and percentages
Avoid skill bars, star ratings and percentages such as "Python 80%". They mean nothing to a reader (80 percent of what?), they cannot be copied by screening software, and they invite awkward questions. If a level helps, use words: "Advanced: SQL; Working knowledge: Tableau". Beginner-level skills can be left out unless the job lists them.
Common mistakes
- Listing things everyone has: "MS Office", "Internet", "Email". Keep "Excel" if you use it well, and say what for (pivot tables, VLOOKUP).
- Spelling a tool wrongly. It is Microsoft Excel, JavaScript, GitHub, PostgreSQL.
- Putting skills in a table or image. Plain text is read correctly by every system.
- Keeping outdated tools you have not touched in years.
To see how the skills section sits on a whole page, look at fresher resume examples by role.
Frequently asked questions
Should I list soft skills?
List a few only if the advert names them, and prove them in your bullets. A skills section full of adjectives helps no one.
Is it fine to list a skill I am still learning?
Only if you label it honestly, for example "Familiar with: Docker", and you are comfortable being asked about it. Otherwise, leave it out.
Should the skills section go at the top or the bottom?
For technical roles, near the top is fine. For others, after experience or education. In the ApplyReady builder you can reorder sections in the Design tab.
Do I need to list Microsoft Office?
Not unless the advert asks. If you use a specific feature, such as pivot tables or mail merge, name it instead.
How do I list languages?
In their own section or row, with a level: native, fluent, professional working, or conversational. Only list languages you can use at that level in a conversation.