What Skills to Put on a Resume (Without Lying)

The skills section of a resume is where candidates face the clearest version of a recurring temptation: the job requires a skill you have in a limited capacity, and adding it to the skills section would make your application stronger. Do you include it?

The answer depends entirely on the nature of that limitation — and on the consequences of claiming something you can't perform at the expected level. This guide walks through how to think about your skills section, what belongs there, what doesn't, and how to build a competitive skills section without exposing yourself to fabrication risk.

Why the skills section matters more than you think

The skills section serves two functions simultaneously. For ATS systems, it's a structured data field — most modern applicant tracking systems have dedicated skills extraction that weighs your listed skills against the job's required qualifications. A clearly labeled Skills section near the top of your resume helps the parser extract this data into the right fields, rather than leaving your skills buried as undifferentiated text in bullet points.

For human reviewers, the skills section is a fast-scan summary — a quick read that answers "does this person have the technical foundation this role requires?" A skills section that lists your 40 most adjacent competencies answers that question poorly. A focused list of your most relevant, demonstrable skills answers it well.

The categories of skills worth including

Technical / hard skills

Specific, verifiable competencies: programming languages, software platforms, tools, frameworks, methodologies, certifications. These are the easiest to include (they're objective) and the most scrutinized (they can be tested).

Include technical skills you can actually use at a professional level. "Familiar with Python" after a six-week bootcamp is a different claim than "Python" on a resume alongside a machine learning role where you used it daily. The label is the same; the implied competency is not.

Domain knowledge

Industry-specific knowledge that's not a discrete tool but represents real expertise: "HIPAA compliance," "financial modeling," "supply chain optimization," "enterprise SaaS sales cycles." These belong in the skills section when they're genuinely relevant and when your work history supports the claim.

Methodologies and practices

Agile, Scrum, Kanban, Design Thinking, Six Sigma, SQL query optimization — methodological competencies that are meaningful to a specific role. Include these when you've actually worked within these frameworks, not just read about them.

What not to include

Leave out:

• Soft skills ("communication," "leadership," "problem-solving") — these belong in your summary or bullets, demonstrated by examples, not asserted in a list
• Skills you used once or twice in a non-professional context
• Outdated tools that are no longer relevant to your target roles
• Skills that are so basic they go without saying (Microsoft Word for most knowledge worker roles)
• Skills you're actively learning but haven't yet applied professionally — unless you're transparent about that status

The gray area: how to handle partial competencies

Most candidates have some skills that don't fit neatly into "I have this" or "I don't have this." Here's how to handle the common cases:

Skills you have but haven't used recently

Include them if they're relevant, but be prepared to discuss currency. An interviewer who asks "walk me through your experience with X" deserves to know that your experience was primarily from three years ago. Being upfront about this isn't disqualifying — pretending to current fluency and then failing a technical question is.

Skills you have at a junior level when the role expects senior fluency

This is the highest-risk category. If you include a skill and the role requires you to perform at a level significantly above your actual competency, you'll fail at the technical screen, the interview, or the job itself. The question is whether the gap is closeable. If you're close enough that you can perform adequately with a short learning curve, that's judgment you have to make. If the gap is substantial, claiming the skill is a liability, not an asset.

Skills from adjacent experience (side projects, freelance work, education)

These are legitimately yours. A skill developed through a substantial personal project, freelance engagement, or academic work is real experience. Include it — and be ready to describe the context when asked.

Matching terminology to the job description

One of the highest-leverage optimizations in your skills section has nothing to do with what you include — it's about the words you use to describe what's already there.

ATS systems often match on exact terminology. "React" and "ReactJS" are usually parsed the same way by modern systems, but not always. More meaningfully: if the job says "customer success management" and your skills section says "account management," you may not match even though the underlying skills are the same. Where the terminology for your actual skill matches the job description's terminology, use their words.

This is not fabrication. It's using the right vocabulary for skills you genuinely have.

The integrity test

Before submitting any resume, apply this test to every item in your skills section:

"If an interviewer asked me to demonstrate this skill tomorrow — through a technical assessment, a case study, or a detailed conversation about my experience with it — could I do that honestly and competently?"

Skills that pass: include them. Skills that don't: either remove them or be prepared to disclose the limitation when asked. There is no scenario where failing a technical screen on a skill you listed as a competency works in your favor.

Tailoring your skills section for each application

Your skills section should not be identical across applications. For each role, review the required and preferred skills in the job description and adjust your section accordingly:

• Add any required skills you have that aren't in your current list
• Remove skills that are clearly irrelevant to this type of role
• Align terminology with the job posting where it matches your actual experience
• Order skills so the most relevant appear first (if your list is long enough to warrant ordering)

Tools like CareerFufu automate this alignment — extracting the required skills from the job description and comparing them against the skills in your master resume, then surfacing and aligning the relevant ones in your tailored output. The constraint is that nothing gets added that wasn't already in your master resume. Every skill in your tailored output is one you actually have.

The competitive advantage of an honest skills section

In a market where AI tools make it trivially easy to add any skill to a resume, the candidates with accurate, defensible skills sections have a real advantage at the interview and offer stage. They pass technical screens, speak fluently about their experience, and perform at the level their application implied.

That consistency — resume, interview, and on-the-job performance all telling the same story — is increasingly rare. And increasingly valued.