The skills section is where applicant systems and recruiters look first for a match. Keep it short, grouped, and honest.
Rules that hold up
- List only skills you could discuss in an interview.
- Group them under plain labels so a person can scan.
- Use the exact wording from the job post where it is true.
- Put the strongest group first.
- Show each skill in a bullet somewhere too. A list alone proves nothing.
Example: software developer
- Languages: JavaScript, TypeScript, Python, SQL
- Frameworks: React, Next.js, Node.js, Express
- Tools: Git, Docker, GitHub Actions, Postman
- Practices: code review, unit testing, REST API design
Example: accountant
- Software: Tally, QuickBooks, Excel (pivot tables, VLOOKUP)
- Accounting: accounts payable, bank reconciliation, month-end close
- Compliance: GST filing, TDS, statutory audit support
Example: teacher
- Instruction: lesson planning, differentiated instruction, formative assessment
- Tools: Google Classroom, Canva, Kahoot
- Support: parent communication, classroom management
Skip the rating bars
"Python ●●●●○" gives a parser nothing to read and a human nothing to trust. Write "Python, 3 years" if the level matters.
See the keywords that recur for your role on the role keyword pages, or read how to find resume keywords in a job description.
