Where to Put Skills on Your Resume (and Which Ones)
Most resumes we review at PotatoResume have a skills section that was clearly an afterthought — a block of 15-20 words dumped at the bottom, mixing "Python" with "Team Player" with "MS Excel" with "Leadership." That's not a skills section, that's a word cloud. Where you place it and what you put in it should depend entirely on your situation, not a template you copied.
Where the skills section goes — it depends on who you are
There's no universal answer here. The right placement changes based on how much experience you have and what story your resume needs to tell.
If you're a fresher or final-year student
Put skills right after your education section, near the top. You don't have work experience to lead with, so your degree and your demonstrable skills (programming languages, tools, certifications) are your strongest opening pitch. A recruiter scanning for "SQL" or "React" should find it in the first third of the page, not after three internships worth 6 months combined.
If you have 5+ years of experience
Push skills down, below your work experience. At this stage, your experience bullets carry the weight — a hiring manager wants to see that you led a team of 8 or cut deployment time from 3 hours to 20 minutes before they care about your tools list. A skills section up top on a senior resume reads like you're hiding behind a keyword list instead of showing impact.
If you're switching careers or industries
Skills go higher, often right under your summary. If you're moving from, say, operations into product management, your last job title won't signal relevance — your skills (stakeholder management, Jira, wireframing, basic SQL) have to do that work instead, before the recruiter gets confused by your actual job history.
If you're in a technical role (engineering, data, design)
A dedicated, categorized skills section near the top is expected and often scanned first. Recruiters and ATS tools alike parse these roles by stack — Java vs Python vs Go isn't a nuance, it's a filter.
Hard skills vs soft skills — they don't belong in the same list
Hard skills are specific, teachable, and verifiable — SQL, Tally, Figma, GST filing, Google Ads, a particular machine or certification. These are what ATS software and recruiters actually search for by keyword. List them plainly, in a dedicated section.
Soft skills — "communication," "leadership," "problem-solving," "team player" — are close to meaningless as a standalone list. Nobody has ever been shortlisted because their resume said "strong communication skills." These need to be shown, not claimed, inside your experience bullets:
- Instead of listing "leadership": "Led a 4-member design team to deliver a client rebrand 2 weeks ahead of schedule."
- Instead of listing "communication": "Presented weekly performance reports to the regional sales head, driving a shift in territory strategy."
- Instead of listing "problem-solving": "Identified a billing error causing 8% revenue leakage and fixed the reconciliation process."
If you must include soft skills at all, keep it to 2-3 and only if the job description explicitly asks for them (common in sales, customer support, and BPO roles in India, where "interpersonal skills" genuinely gets keyword-matched).
How to actually choose which skills to list
Don't write your skills section from memory or from a generic "top skills for [role]" list online. Reverse-engineer it from real job postings for the role you want.
- Pull up 3-5 live job postings for your target role and level on LinkedIn, Naukri, or Instahyre.
- List every hard skill, tool, and certification that appears across them, and note which ones repeat.
- Keep only the skills you can genuinely back up — in an interview, in a project, or in a past role. Never list a skill you can't speak to for 2 minutes if asked.
- Order your skills section by what's most frequently mentioned across those postings, not by what you're personally most comfortable with.
- Drop anything outdated or irrelevant — "MS Office" on a 2024 resume for a marketing role signals nothing; "HubSpot, Google Analytics 4, Canva" does.
This takes 20 minutes and produces a far more targeted list than any generic "50 skills to put on your resume" article, because it's built from what employers hiring for your exact role are actually asking for right now.
Format it so it's actually scannable
Group skills into 2-3 labeled categories instead of one long line. For a data analyst, that might be:
- Languages & Tools: Python, SQL, Power BI, Excel (Advanced)
- Techniques: A/B testing, regression analysis, data cleaning
- Platforms: Google Analytics, Tableau, AWS (basic)
This does two things a flat list doesn't: it helps a recruiter scan in 5 seconds, and it shows you understand the difference between your core tools and your supporting ones — which, ironically, is itself a soft skill worth demonstrating rather than listing.