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.
Where to Place Your Skills Section
| Situation | Best Placement | Why |
|---|---|---|
| Technical role (SWE, DevOps, data) | Below name, above experience | Recruiters check your stack before reading bullets |
| Non-technical role (PM, marketing, ops) | Below experience | Experience and results matter more |
| Career changer | Below name, above experience | Establishes relevant skills before unrelated job titles |
| New grad / intern | Below education, above projects | Education sets context, skills show what you can do |
The rule: place skills where they'll be seen in the first 6 seconds of scanning.
How Many Skills to List
| Experience Level | Count | Notes |
|---|---|---|
| Junior / New Grad (0-2 years) | 12-18 skills, 2-3 groups | Tools you've actually used in projects or coursework |
| Mid-Level (3-6 years) | 18-25 skills, 3-4 groups | Specialized tools matching the JD; drop basics like "Microsoft Office" |
| Senior+ (7+ years) | 20-30 skills, 4-6 groups | Show breadth and depth; include architecture-level skills |
The test: can you have a 5-minute conversation about every skill listed? If not, remove it.
5 Skills Grouping Templates
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, RICE prioritization
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
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
Formatting Rules
Do this:
- Use plain text, comma-separated. ATS parses "React, TypeScript, Node.js" reliably; it struggles with tables and columns.
- Group by function, not proficiency. "Frontend: React, TypeScript" is useful. "Expert: React. Intermediate: TypeScript" wastes space.
- Bold the group labels. Visual anchors for recruiters scanning quickly.
- List specific tools, not categories. "AWS (EC2, Lambda, S3)" matches more keywords than "Cloud Computing."
- Lead each group with the most relevant skill for the role you're targeting.
Don't do this:
- Skill bars or star ratings. Subjective, space-wasting, ATS can't parse them.
- Soft skills. "Communication" and "teamwork" belong in bullet points as demonstrated behaviors, not as labels.
- Obvious tools. Microsoft Word, Google Docs - assumed, add noise without keyword value.
- Two-column layouts. Many ATS systems read left-to-right across both columns and produce garbled output.
- Abbreviations without spelling out. Write "Amazon Web Services (AWS)" at least once.
Complete Skills Section Examples
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
Cloud: AWS (ECS, S3, CloudFront, Lambda), Docker, GitHub Actions, Datadog
4 groups, 20 skills. The headline previews the top 3 technologies so recruiters get the match signal before reading the skills section.
Product Manager
Jamie Okafor | Senior Product Manager · 6 years · B2B SaaS, Growth
[Experience first for PM roles]
Skills & Tools
Product: Roadmap planning, PRDs, user research, A/B testing, RICE prioritization, go-to-market
Analytics: Amplitude, SQL, Looker, Google Analytics (GA4), cohort analysis
Design: Figma, Miro, Notion, Jira, Linear, Confluence
3 groups, 18 skills. 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, 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
5 groups, 25 skills. 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
[Experience first for marketing roles]
Skills & Tools
Channels: SEO, Google Ads, Meta Ads, LinkedIn Ads, email, content, webinars
Analytics: Google Analytics (GA4), HubSpot, Mixpanel, Looker, SQL, attribution modeling
Tools: HubSpot, Marketo, Salesforce, Semrush, Ahrefs, Figma, Webflow
3 groups, 20 skills. Channels (what you know), analytics (how you measure), tools (what you use).
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
- Reorder groups - put the group matching the role's primary focus first
- Drop irrelevant skills - applying for a frontend role? Remove Ansible and Terraform.
Common Mistakes
- 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
- One giant ungrouped list - the recruiter can't tell what kind of engineer or PM you are
- Proficiency levels - "Beginner/Intermediate/Advanced" is subjective; if you need to mark something beginner, don't list it
- Burying skills on page 2 - for technical roles, above-the-fold placement is essential
- Same skills section everywhere - 2 minutes of reordering per application is worth it
Skills Section Checklist
- ☐ Skills grouped by function, not proficiency level
- ☐ Each group has a bold label
- ☐ 12-30 skills total (appropriate for experience level)
- ☐ Top 5 required tools from the JD appear in your skills section
- ☐ Specific services listed (e.g., "AWS (EC2, Lambda)" not just "AWS")
- ☐ No skill bars, star ratings, or proficiency levels
- ☐ No soft skills listed
- ☐ 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.
Want to see how your skills section is scoring against a specific job description? WriteCV's ATS checker shows your keyword match rate with specific gaps called out.
Top comments (0)