Your skills section is the most-scanned part of your resume after your name and current title. ATS systems use it for keyword matching. Recruiters use it as a 2-second compatibility check. If it's poorly organized, buried at the bottom, or filled with the wrong skills, both audiences move on.
This guide covers placement, formatting, grouping strategies, and complete examples for four different roles.
Where to Place Your Skills Section
The placement depends on your experience level and how important technical skills are to the role.
| Situation |
Best Placement |
Why |
| Technical role (SWE, DevOps, data) |
Below name, above experience |
Recruiters check your stack before reading bullets. ATS parses it first. |
| Non-technical role (PM, marketing, ops) |
Below experience |
Experience and results matter more. Skills support, not lead. |
| Career changer |
Below name, above experience |
Establishes relevant skills before the recruiter sees unrelated job titles. |
| New grad / intern |
Below education, above projects |
Education establishes context. Skills show what you can actually do. |
The rule of thumb: place skills where they'll be seen in the first 6 seconds of scanning. For technical roles, that means near the top. For roles where impact matters more than tools, experience comes first.
How Many Skills to List
Too few and you miss keyword matches. Too many and you look unfocused. Here's the guideline by experience level:
Recommended Skill Count
Junior / New Grad (0-2 years): 12-18 skills across 2-3 groups. Focus on tools you've actually used in projects or coursework.
Mid-Level (3-6 years): 18-25 skills across 3-4 groups. Include specialized tools that match the JD, drop basics like "Microsoft Office."
Senior+ (7+ years): 20-30 skills across 4-6 groups. Show breadth and depth. Include architecture-level skills (distributed systems, system design) alongside specific tools.
These are guidelines, not rules. A specialist might list 15 deeply relevant skills. A full-stack engineer might list 30. The test: can you have a 5-minute conversation about every skill listed? If not, remove it.
5 Skills Grouping Templates
Grouping your skills by function makes them easier for both ATS systems and humans to parse. Here are five templates for different role types.
Template 1: Frontend / Full Stack Engineer
Frontend: React, Next.js, TypeScript, Tailwind CSS, React Query, Zustand
Backend: Node.js, Express, PostgreSQL, Redis, GraphQL, REST APIs
Testing: Jest, React Testing Library, Playwright, Cypress
Infrastructure: Docker, AWS (ECS, S3, CloudFront), GitHub Actions, Vercel
Template 2: Backend / Systems Engineer
Languages: Go, Python, Java, SQL, Bash
Databases: PostgreSQL, Redis, DynamoDB, Elasticsearch
Infrastructure: AWS (EC2, ECS, Lambda, SQS), Docker, Kubernetes, Terraform
Observability: Datadog, Prometheus, Grafana, PagerDuty, ELK Stack
Architecture: Microservices, event-driven systems, REST, gRPC, Kafka
Template 3: Product Manager
Product: Roadmap planning, user research, A/B testing, PRD writing, prioritization frameworks (RICE, ICE)
Analytics: Amplitude, Mixpanel, SQL, Looker, Google Analytics
Design: Figma, user journey mapping, wireframing, design sprints
Tools: Jira, Linear, Notion, Confluence, Miro
Template 4: Data Analyst / Data Scientist
Languages: Python, SQL, R
ML/AI: scikit-learn, PyTorch, TensorFlow, Hugging Face, XGBoost
Data Engineering: Spark, Airflow, dbt, Snowflake, BigQuery
Visualization: Tableau, Looker, Matplotlib, Plotly
Statistics: A/B testing, regression, time series, causal inference, Bayesian methods
Template 5: Marketing / Growth
Channels: SEO, SEM, paid social (Meta, LinkedIn), email, content marketing
Analytics: Google Analytics (GA4), Mixpanel, HubSpot, Looker, SQL
Tools: HubSpot, Marketo, Salesforce, Semrush, Ahrefs, Figma
Skills: Copywriting, A/B testing, lead scoring, marketing automation, attribution modeling
For industry-specific keyword lists to pull from, see our resume keywords by industry guide.
Formatting Rules
How you format the skills section matters as much as what you include. Follow these rules for maximum ATS compatibility and readability.
Do This
Use plain text, comma-separated. ATS systems parse "React, TypeScript, Node.js" reliably. They struggle with tables, columns, and graphics.
Group by function, not proficiency. "Frontend: React, TypeScript" is useful. "Expert: React. Intermediate: TypeScript" is subjective and wastes space.
Bold the group labels. This creates visual anchors for recruiters scanning quickly.
List specific tools, not categories. "AWS (EC2, Lambda, S3)" matches more keywords than just "Cloud Computing."
Lead each group with the most relevant skill. If the JD emphasizes React, put React first in the frontend group.
Don't Do This
Don't use skill bars or star ratings. They waste space, are subjective, and ATS can't parse them. What does "4 out of 5 stars in Python" even mean?
Don't list soft skills here. "Communication," "teamwork," and "problem-solving" belong in your bullet points as demonstrated behaviors, not as skill labels.
Don't include obvious tools. Microsoft Word, Google Docs, email - these are assumed. They add noise without keyword value.
Don't use two-column layouts. Many ATS systems read left-to-right across both columns, creating garbled output. Stick to a single column.
Don't abbreviate without spelling out. Write "Amazon Web Services (AWS)" at least once. ATS might search for either form.
Complete Skills Section Examples
Here are four complete skills sections in context, showing how they look at the top of a resume.
Software Engineer (Mid-Level)
Alex Rivera
Software Engineer · 4 years · React, Node.js, AWS
Technical Skills
Frontend: React, Next.js, TypeScript, Tailwind CSS, React Query, Storybook
Backend: Node.js, Express, PostgreSQL, Redis, REST APIs, GraphQL
Testing: Jest, React Testing Library, Playwright, k6 (load testing)
Cloud & Tools: AWS (ECS, S3, CloudFront, Lambda), Docker, GitHub Actions, Datadog
Experience
[Experience bullets follow...]
4 groups, 20 skills. The headline previews the top 3 technologies so recruiters get the match signal before even reaching the skills section.
Product Manager
Jamie Okafor
Senior Product Manager · 6 years · B2B SaaS, Growth, Data-Driven
Experience
[Experience bullets first - PM resumes lead with impact...]
Skills & Tools
Product: Roadmap planning, PRDs, user research, A/B testing, RICE prioritization, go-to-market strategy
Analytics: Amplitude, SQL, Looker, Google Analytics (GA4), cohort analysis
Design & Collaboration: Figma, Miro, Notion, Jira, Linear, Confluence
Skills section comes after experience for PM roles. 3 groups, 18 skills. Notice the mix of methodologies (A/B testing, RICE) and tools (Amplitude, SQL) - PMs need both.
Data Scientist
Priya Mehta
Data Scientist · 5 years · ML, NLP, Python, PyTorch
Technical Skills
Languages: Python, SQL, R, Scala
ML/AI: PyTorch, TensorFlow, scikit-learn, Hugging Face Transformers, XGBoost, LightGBM
Data Engineering: Spark, Airflow, dbt, Snowflake, BigQuery, Kafka
Visualization: Tableau, Looker, Matplotlib, Plotly, Streamlit
Methods: NLP, computer vision, recommendation systems, A/B testing, causal inference
Experience
[Experience bullets follow...]
5 groups, 25 skills. Data science resumes need to show both the tools (PyTorch, Spark) and the methods (NLP, causal inference). The "Methods" group is what separates a data scientist from a data engineer in a recruiter's eyes.
Marketing Manager
Sam Torres
Growth Marketing Manager · 5 years · B2B SaaS, Demand Gen, PLG
Experience
[Experience bullets first...]
Skills & Tools
Channels: SEO, Google Ads, Meta Ads, LinkedIn Ads, email marketing, content marketing, webinars
Analytics: Google Analytics (GA4), HubSpot, Mixpanel, Looker, SQL, attribution modeling
Tools: HubSpot, Marketo, Salesforce, Semrush, Ahrefs, Figma, Webflow
3 groups, 20 skills. Marketing skills sections should separate channels (what you know) from analytics (how you measure) from tools (what you use). Skills section after experience - marketing is judged on results first.
Tailoring Your Skills Section
Your skills section should change for every application. It's the easiest section to tailor and has the highest keyword impact.
- Read the JD requirements. List every tool, technology, and platform mentioned.
- Match your skills. For every JD keyword you genuinely know, make sure it appears in your skills section.
- Reorder groups. Put the group that matches the role's primary focus first. If the JD leads with "Python and machine learning," your ML/AI group goes first.
- Drop irrelevant skills. If you're applying for a frontend role, remove your Ansible and Terraform skills. They add noise.
For a complete tailoring method, see our ATS resume checklist.
Common Skills Section Mistakes
Avoid These
1. Listing skills you can't discuss. If an interviewer asks about Kubernetes and you only watched a YouTube video, it hurts more than it helps. Only list skills you've used in a project or role.
2. One giant list with no groups. "Python, React, SQL, Figma, Jira, Terraform, Tableau, Leadership" - the recruiter can't tell what kind of engineer or PM you are. Group by function.
3. Including proficiency levels. "Beginner," "Intermediate," "Advanced" are subjective and waste space. If you need to mark something as "beginner," don't list it at all.
4. Burying the skills section. For technical roles, if skills are on page 2, most recruiters never find them. Above-the-fold placement for technical roles.
5. Using the same skills section for every job. A generic skills section misses JD-specific keywords. Take 2 minutes to reorder and swap skills per application.
Skills Section Checklist
Before You Submit
☐ Skills are grouped by function (not proficiency level)
☐ Each group has a bold label
☐ 12-30 skills total (appropriate for your experience level)
☐ The JD's top 5 required tools appear in your skills section
☐ Specific services listed, not just provider names (e.g., "AWS (EC2, Lambda)" not just "AWS")
☐ No skill bars, star ratings, or proficiency levels
☐ No soft skills listed (communication, teamwork, etc.)
☐ Every listed skill is backed by experience you can discuss
A well-structured skills section takes 5 minutes to write and 2 minutes to tailor per application. It's the highest-ROI section on your resume for ATS keyword matching - get it right and the rest of your resume gets read. The other high-impact section is your summary: see our resume summary examples for how to write one that reinforces your skills with context.
Related Resume Examples
Browse all 400+ resume examples →