The Resume Skills Section: What Recruiters Actually Read.

The junk drawer problem

I see hundreds of resumes a week in Greenhouse. Almost all of them have a skills section that looks like a tag cloud from 2010. Candidates list everything from 'Microsoft Word' to 'Leadership' to 'Agile Methodology' in a massive block of text. They think this helps them pass the ATS filters. It actually does the opposite. When you throw fifty random terms at a page, you dilute the impact of your actual expertise. A hiring manager scanning your profile wants to know if you can do the specific job they are hiring for. They do not care that you know how to use Slack. They do not care that you consider yourself a team player. They care about the hard, verifiable tools that are required to ship code or close deals. By cluttering your resume with irrelevant fluff, you make it harder for us to find the information we actually need. You are actively sabotaging your own application. Stop doing this.

Recruiters don't read your skills section to find out if you know how to use email. We read it to quickly verify if you have the baseline technical requirements for the role. If I need a React developer, I scan for React. If you bury React between 'Team Player' and 'Jira', I might miss it. You have about six seconds to prove you belong in the 'yes' pile. Don't waste them on filler. The best candidates treat their skills section like a curated exhibit. They only display the absolute best, most relevant pieces of their professional background. They understand that every word on the page needs to earn its keep. If a skill does not directly support the narrative that you are the perfect fit for this specific role, it has to go. This level of ruthless editing is rare. When I see a tightly focused skills section, I immediately assume the candidate is experienced and confident. Confidence is quiet.

Why soft skills don't belong here

Nobody has ever been hired because they wrote 'Hard Worker' on their resume. Soft skills are subjective. Anyone can claim to be a great communicator or a natural leader. When you list these in a dedicated skills section, you are just taking up valuable real estate. Hiring managers ignore them completely. Think about it from my perspective. I have never looked at a candidate's profile and thought, "Well, they don't know Python, but they did write 'Detail Oriented' in bold font, so let's bring them in." It sounds ridiculous because it is. Soft skills are behavioral traits. They cannot be proven in a bulleted list. They have to be demonstrated through your actions and your track record. Putting them in a list just tells me you do not understand how modern hiring works.

Instead of telling me you are a problem solver, show me. Your experience section is where soft skills belong. Describe a time you resolved a critical production outage or negotiated a difficult contract. That proves your problem-solving ability. A bullet point that says 'Problem Solving' proves nothing. If you want to highlight your leadership skills, write a bullet point about how you mentored three junior engineers who were later promoted. If you want to show you are adaptable, talk about how you pivoted a failing project to a new technology stack in three weeks. This is how you communicate soft skills effectively. You weave them into the narrative of your career. You let your achievements speak for your character. Show, don't tell.

This is especially true for senior roles. If you are applying for a Director position, I assume you know how to manage a team. Listing 'Management' as a skill looks amateurish. Focus on the hard, verifiable tools and technologies that make you effective. Senior candidates often fall into the trap of thinking they need to list every management philosophy they have ever encountered. They fill their skills section with terms like 'Servant Leadership' and 'Cross-functional Collaboration'. This is a mistake. At the senior level, your skills section should be incredibly brief. It should only contain the specific technical platforms or domain-specific methodologies that are relevant to the role. Your extensive experience should be doing the heavy lifting. If you have to explicitly state that you know how to collaborate, I am going to assume you actually struggle with it. Keep it technical.

The ATS keyword myth

There is a persistent rumor that systems like Workday and Lever automatically reject resumes that lack specific keywords. This is mostly false. ATS platforms parse your resume to make it searchable. They do not make hiring decisions. A human recruiter still looks at your profile. The idea of a robot gatekeeper tossing your resume into a digital shredder is a myth perpetuated by people selling resume optimization services. In reality, the ATS is just a database. It helps me organize and filter candidates. If I search for 'TypeScript', the system shows me resumes containing that word. It does not automatically reject the ones that do not. I still review the incoming queue manually. I still read the resumes. The keywords just help me prioritize my reading list.

Keyword stuffing your skills section will not trick the system. In fact, modern ATS parsers are smart enough to recognize context. If you list 'Python' fifty times in white text, the system flags it. If you list fifty unrelated skills just to cover your bases, the human recruiter will reject you for lacking focus. I have seen candidates copy and paste the entire job description into their skills section, hoping to hit every possible keyword. This is incredibly obvious. When I open the profile in Ashby, the formatting is usually broken, and the text looks like a chaotic mess. Even if it parses correctly, I can see exactly what you did. It shows a lack of integrity. It tells me you are trying to game the system instead of presenting a honest picture of your abilities. That is an instant rejection.

The best approach is radical honesty. Only list skills you would be comfortable answering technical questions about in an interview. If you used Docker once three years ago, leave it off. Nothing kills an interview faster than a candidate who cannot explain a technology they claimed as a core competency. I always tell my hiring managers to pick one obscure skill from the candidate's list and ask a deep technical question about it. If the candidate stumbles, it casts doubt on their entire resume. If they lied about knowing Kubernetes, what else are they lying about? Did they really lead that project? Did they really increase revenue by twenty percent? Trust is fragile in the interview process. Do not risk it by padding your skills section with technologies you barely understand. Be honest.

Formatting for human eyes

Your skills section needs to be skimmable. A dense paragraph of comma-separated words is impossible to read quickly. Group your skills logically. If you are a software engineer, separate your languages, frameworks, and tools. If you are a marketer, separate your analytics platforms from your content management systems. This simple structural change makes a massive difference. When I am reviewing fifty resumes back-to-back, cognitive fatigue sets in. I do not want to hunt for the information I need. I want it handed to me on a silver platter. By categorizing your skills, you do the mental work for me. You show me exactly where to look for your frontend frameworks and where to look for your database experience. This makes my job easier, which makes me like you more. Make it easy.

Use clear, bold headings for each category. This creates visual hierarchy. When I am reviewing a stack of resumes in Ashby, my eyes naturally jump to the bold text. Make it easy for me to find what I am looking for. Do not use complex tables or multi-column layouts to achieve this. Keep it simple. A bold heading followed by a comma-separated list on a single line is perfect. For example, 'Languages: JavaScript, Python, Go.' This format is clean, professional, and universally readable. It parses perfectly in every ATS on the market. It also looks great on a printed page, which is important because many interviewers still prefer to hold a physical copy of your resume during the interview.

Keep the list tight. You do not need to list every version of a software you have ever used. 'Adobe Creative Suite' is better than listing Photoshop, Illustrator, InDesign, and Premiere separately. Less clutter means your most important skills stand out more. I frequently see candidates list 'Windows 10', 'Windows 11', and 'macOS' as skills. This is completely unnecessary. Unless you are applying for an IT support role, basic operating system proficiency is assumed. The same goes for standard office software. Listing 'Microsoft Excel' is fine if you are an accountant who uses complex macros. If you are a graphic designer, it is irrelevant. Edit your list ruthlessly. Every skill you include should add specific, measurable value to your application.

Where to put the skills section

Placement matters. If you are a recent graduate or a career changer, your skills section should be at the top of your resume, right below your summary. You need to establish your baseline qualifications immediately. Your experience might not speak for itself yet, so your skills have to do the heavy lifting. When you lack a long track record of professional success, your technical capabilities are your strongest selling point. Putting them at the top tells the recruiter, "I might not have ten years of experience, but I know exactly how to use the tools you need." It sets a positive tone for the rest of the resume. It frames your academic projects or bootcamp experience in the context of real-world technologies. Put it first.

If you have more than three years of relevant experience, move the skills section to the bottom. Your work history is now your strongest asset. I want to see what you have accomplished before I care about the specific tools you used to do it. Let your track record lead the conversation. A senior engineer's value comes from their architectural decisions and their ability to scale systems, not just their knowledge of a specific syntax. By putting your experience first, you highlight your impact. The skills section at the bottom then serves as a quick reference guide. It confirms that you have the necessary technical foundation to support the impressive achievements listed above. Experience wins.

Never put your skills in a narrow side column. Many older ATS parsers read left-to-right, top-to-bottom. A side column can scramble the text, mixing your skills into your job descriptions. Stick to a single-column layout for maximum compatibility. I cannot count the number of times I have opened a beautifully designed, two-column resume in Greenhouse, only to find the text completely garbled. The parser reads across the page, combining a bullet point about revenue growth with a random list of programming languages. It becomes unreadable. You might think the side column looks modern and stylish, but it is a massive technical risk. Always prioritize function over form. A boring, single-column resume that parses perfectly will always beat a beautiful resume that breaks the system.

The 'familiar with' trap

Many candidates try to inflate their skills section by adding a 'Familiar With' or 'Exposure To' category. Do not do this. It signals a lack of confidence. If you are not proficient enough to use a tool on the job tomorrow, it does not belong on your resume. This is a classic mistake made by junior candidates who are desperate to hit every keyword in the job description. They think that showing a tiny bit of knowledge is better than showing none at all. It is not. When I see 'Familiar With: AWS', I immediately assume you logged into the console once and got scared. It highlights your weaknesses instead of your strengths. It draws attention to the things you do not know well.

Hiring managers are looking for impact, not just exposure. We want to know what you can actually build or achieve. Listing a technology you watched a YouTube tutorial about only dilutes the impact of your real expertise. Your resume should be a highlight reel of your absolute best professional qualities. It should project confidence and competence. Including a list of things you are only vaguely aware of undermines that message. It makes you look hesitant. It makes me question the depth of your knowledge in the areas where you claim to be an expert. If you are truly an expert in React, why are you diluting that by mentioning you are 'familiar with' Angular? Focus on your strengths and own them completely. Be an expert.

If you are actively learning a new skill that is crucial for the role, mention it in your cover letter or summary. Say 'Currently completing an advanced certification in AWS.' That shows initiative. Putting 'AWS (Beginner)' in your skills section just looks weak. There is a huge difference between demonstrating a proactive desire to learn and admitting a current lack of proficiency. The former makes you look like a driven, ambitious professional. The latter makes you look unqualified. Always frame your developing skills as active pursuits rather than passive deficiencies. This subtle shift in perspective can completely change how a hiring manager perceives your potential.

Examples

Here is how the same set of skills looks when formatted poorly versus when formatted for a modern hiring pipeline. Notice how the strong version categorizes the tools and drops the subjective fluff.

Walk-away

Your skills section is a tool for quick verification, not a complete autobiography. Keep it sharp, honest, and easy to read. Here is what you need to remember.

Frequently asked questions

Related

• ATS resumes: what they actually check →
• 200+ resume action verbs →
• How to quantify achievements →
• How to tailor your resume to a job →
• Browse resume examples by role →

— Hannah Brooks. Frontend tech lead at three YC startups; on hiring loop for five years.