Every resume has a skills section. Most of them are filler. The goal is narrow: list the tools and languages you can be tested on, grouped in a way a recruiter can scan, tailored to the industry you are applying to.
What goes in changes by field. Here is what we tell candidates targeting tech, finance, and consulting.
Tech and engineering
For technical roles the skills section is real estate. Group by category so a recruiter can scan in a second, and list concrete tools, not adjectives.
- Languages. Python, Java, JavaScript, TypeScript, C++, SQL, R.
- Frameworks and libraries. React, Node.js, Django, TensorFlow, PyTorch, Spring Boot.
- Tools. Git, Docker, Kubernetes, AWS, GCP, Azure, Jenkins.
- Databases. PostgreSQL, MongoDB, Redis, MySQL, DynamoDB.
A clean one-line version: Languages: Python, Java, JavaScript, SQL. Frameworks: React, Django, Flask. Tools: Git, Docker, AWS (EC2, S3, Lambda). Databases: PostgreSQL, MongoDB.
Finance and banking
Finance skills sections reward specificity. "Excel" is useless. "Excel (Pivot Tables, INDEX/MATCH, VBA macros)" tells the reader you have actually used it.
- Technical. Excel (advanced), VBA, Bloomberg Terminal, FactSet, Capital IQ, SQL.
- Modeling. DCF, LBO, M&A modeling, financial statement analysis.
- Programming. Python, R, MATLAB for quant-leaning roles.
- Certifications. CFA level, Series 7 or 63, Bloomberg Market Concepts.
Consulting
Consulting resumes tend to be thin on skills sections by design. The experience bullets are where you prove analytical chops. Keep this section short.
- Analysis tools. Excel (advanced), PowerPoint, Tableau, Alteryx, SQL.
- Languages. Any additional spoken languages with honest proficiency labels.
What to cut
The easiest upgrade to most skills sections is deleting half of it. If it does not give a recruiter new information, it is taking space from something that would.
- Microsoft Office as a bullet. It is assumed.
- Soft-skill claims like "communication skills," "team player," or "hard worker." No one believes them and you cannot be tested on them.
- Social media platforms, unless the role is in marketing or content.
- Outdated technology that signals you stopped learning a decade ago.
The rule that saves you
Only list what you can back up in an interview. If you write Python, expect to be asked a Python question. If you write "advanced Excel," expect to build something on a shared screen. Interviewers read the skills section like a menu of questions they are allowed to ask.
The short version
Group by category. List concrete tools. Mirror the vocabulary of the job description. Cut anything you cannot be tested on. A tight skills section will not win you the role on its own, but a sloppy one will lose you interviews you would have otherwise gotten.
Helpful resources
- Bureau of Labor Statistics - Occupational Outlook Handbook
- LinkedIn Learning - Professional development courses
- Handshake - Early-career job platform
Related topics