The Skills Section: Stop Listing and Start Proving

Of all the sections on a resume, the skills section is the one that has been most thoroughly ruined by well-meaning advice. The instruction to "include a skills section" has been interpreted by millions of job seekers to mean "create a list of every competency you have ever claimed in polite conversation." The result is those bloated skills sections that list twenty-five tools, technologies, and soft skills in a dense paragraph or endless bullet points, many of which the candidate cannot actually demonstrate and several of which the reader knows full well are obvious table-stakes for any professional.

"Strong communication skills." "Proficient in Microsoft Office." "Team player." I want to be kind about this, but I have been at this long enough to be direct: these entries are doing negative work on your resume. They are not helping you. They are signaling to an experienced reader that you are filling space without adding substance. Cut them.

"A skills list is not evidence. It is a claim. And a claim without evidence is just an assertion — one of several hundred the hiring manager is reading today."

What the skills section is actually for

The skills section serves two legitimate purposes on a modern resume. First, it is an ATS optimization tool — a place to include relevant technical terms and keywords that might not appear naturally in your experience descriptions. Second, it is a quick reference for the human reader to verify that you have the specific technical or industry-specific competencies the role requires before they invest time reading the rest of the document.

Notice what it is not for: it is not for establishing that you have the obvious competencies everyone in your field has. It is not for listing soft skills that cannot be verified. It is not for padding the document with volume.

The skills section should be specific and technical. "Python, SQL, Tableau" is useful. "Data analysis" is not. "Salesforce CRM, Pardot, HubSpot" is useful. "CRM software" is not. "IFRS and GAAP accounting standards" is useful. "Accounting" is not. The test is: would someone in the field immediately recognize this as a specific, learnable, demonstrable capability? If yes, include it. If it is a soft skill or a generic category, it belongs in your experience descriptions where you can demonstrate it rather than merely claim it.

Proficiency levels: the trap

At some point, the advice circulated that you should include proficiency levels next to your skills. "Python: Advanced. SQL: Intermediate. Mandarin: Conversational." This seems like a good idea in theory. In practice it creates several problems.

First, proficiency labels are entirely self-assessed, and everyone assesses themselves differently. One person's "Advanced Python" is another person's "Intermediate." Interviewers know this. The label is not particularly meaningful to them.

Second, any skill you list will be probed in an interview if it is relevant to the role. If you list "Advanced SQL" and the interviewer asks you to walk through a complex query and you cannot, you have created a trust problem that is worse than if you had simply not claimed advanced proficiency in the first place.

My advice is to drop the proficiency labels unless the role specifically asks you to self-assess technical skills. Just list the skills, keep it accurate, and be prepared to demonstrate anything you list.

Proving skills in the experience section

The skills section is a list. The experience section is where you prove that the list is real. These two sections should work in concert. If you claim in the skills section that you are proficient in financial modeling, there should be bullets in your experience section describing specific instances where you built or used financial models to drive decisions. The claim is in one section; the evidence is in the other.

When I see a resume with an extensive skills list and experience descriptions that do not substantiate those skills, I treat the skills list with skepticism. When I see a skills list that is modest and specific, backed by experience descriptions that clearly demonstrate those skills in action, I believe it. The architecture of the resume communicates something about your credibility.

Soft skills deserve a better vehicle

I want to address soft skills specifically because they are genuinely important and genuinely hard to represent on a resume. "Leadership," "communication," and "problem-solving" are not worth listing in a skills section because they are not verifiable as stated. But they are absolutely worth demonstrating in your experience descriptions.

If you want to demonstrate leadership, describe a specific situation where you led something — a project, a team, a change initiative — and what happened as a result. If you want to demonstrate communication skill, point to instances where your communication created a measurable outcome: a deal you closed, a presentation that moved a decision, documentation you created that is still being used. Soft skills that are shown rather than told carry real weight. Soft skills that are simply listed carry none.

This is, in the end, the organizing principle for the entire resume: show, do not tell. Every list is just telling. Every specific, contextualized, outcome-linked achievement is showing. Build a resume that shows, and let the telling be minimal and precise.