Resume structure · Published September 21, 2026
Put skills near the top when they answer an early screening question; move them lower when recent experience already proves the same capabilities better.
Short answer
Put the skills section near the top when a recruiter needs to verify tools, technical methods, languages, laboratory techniques, or credentials before your job titles make sense. Put it lower when your recent experience already proves the same capabilities more convincingly.
For many experienced same-field candidates, work experience should lead and skills can follow. For technical candidates, new graduates, and career changers, a concise skills block may deserve a higher position. There is no universal best location. The better question is: what does the reader need to confirm first?
A skills list is an index, not proof. Important skills should also be supported by experience, projects, education, certifications, or a portfolio.
Apply the FIRST-QUESTION rule
Ask one question before moving the section:
What is the first material question the target reader cannot answer from my headline, summary, education, and recent role?
Then place the section that resolves that uncertainty earliest.
- Technical or specialist role: If the first screen is “Do they use our stack, method, or equipment?”, a short technical-skills block near the top can help.
- New graduate: Education, projects, and skills may all carry more decision value than limited work history. Put the most relevant evidence first, with skills close enough to support it.
- Career changer: A bridge summary followed by targeted skills can make transferable fit visible before unrelated job titles create the wrong first impression.
- Licensed or credential-gated role: Put the required credential where it can be verified quickly. A broader skills section can sit nearby if it adds information.
- Experienced same-field candidate: If recent roles already show the right level, tools, and outcomes, let experience lead. Use the skills section later as a compact reference.
This is consistent with the broader principle in current career-service guidance: organize the resume around relevance rather than a fixed universal section order. Penn Career Services, for example, highlights a computer-engineering resume that places Technical Skills immediately after Education because those qualifications matter early, while CareerOneStop describes combination resumes that may include a skills section near the top while still preserving detailed work history.
Treat the skills section as an index, not evidence
A strong skills section helps the reader answer “What can this person work with?” quickly. It should not have to answer “How well have they used it?” by itself.
MIT Career Advising and Professional Development recommends using the skills section for technical, procedural, language, or laboratory skills, while showing interpersonal abilities through experience. MIT also recommends reinforcing technical skills inside experience descriptions because context makes the claim more credible.
That creates a useful two-part structure:
Index: SQL · Python · Power BI · Databricks
Proof: Built recurring Power BI reporting from Databricks SQL datasets and investigated data-quality issues before release.
The first line makes the toolkit easy to scan. The second shows what the candidate actually did.
What should go in the skills section?
Prioritize abilities that are relevant to the target job, specific enough to evaluate, and true enough that you could discuss them in an interview.
Good candidates include:
- software and platforms;
- programming or query languages;
- technical methods and frameworks;
- laboratory or production techniques;
- job-relevant languages;
- licenses or certifications when they fit the section logically.
Broad soft-skill labels such as “communication,” “team player,” or “leadership” are usually weak as standalone entries. Show the behavior instead. “Presented weekly release updates to business stakeholders” carries more information than simply listing “communication.”
There is also no evidence-based magic number of skills that works for every resume. A shorter, targeted list is usually more useful than a warehouse of everything you have touched. Group related items when that improves scanning, for example Data, Platforms, Methods, or Languages.
Keep the section ATS-safe without designing for a mythical ATS score
Use a conventional heading such as Skills or Technical Skills and keep the content as plain text.
CareerOneStop currently recommends a simple single-column resume, standard section headings, and avoiding tables, text boxes, logos, columns, images, and graphics because they can interfere with parsing. Greenhouse Recruiting likewise lists columned layouts, complex tables, headers, footers, graphics, photos, and text boxes among formatting patterns that can cause unsuccessful resume parsing.
That does not mean every ATS fails on every two-column resume. Different systems parse files differently. It does mean that decorative skill grids, star ratings, progress bars, and text boxes add risk without adding much evidence.
If you need density, use short grouped lines or plain separators rather than a graphical proficiency meter. “Python 85%” has no shared professional meaning anyway.
Worked example: the same person can justify a different order
Nora is moving from laboratory operations into quality systems. Her recent title does not clearly signal document control, CAPA support, audit preparation, or regulated data handling. She uses a short bridge summary, then a targeted skills block with those supported capabilities, followed by experience bullets that prove them.
Sam is a senior data engineer whose last two roles already show Snowflake, dbt, Python, orchestration, and platform ownership. A large skills block at the top would delay stronger evidence. He leads with a compact summary and work experience, then places a categorized technologies line after the experience section for quick reference.
Neither order is universally superior. Nora has a translation problem. Sam has a duplication problem. Their section order should solve different reader questions.
Run the claim-to-proof audit
For each prominent skill, identify at least one place that supports it.
- SQL: Analyst role, second bullet. Proof: built recurring cohort analysis.
- Vendor management: Operations role, first bullet. Proof: negotiated and monitored 12 suppliers.
- French: Languages section. Proof: CEFR B2 and used in client support.
Delete skills that are irrelevant, too shallow to defend, or impossible to support. If a required tool appears only in a short course or personal project, label that context honestly rather than implying production experience.
This audit also improves interview preparation because every important skill has a story behind it.
Common placement mistakes
Moving skills to the top only for keywords. Higher placement does not turn an unsupported term into experience.
Copying the job description into the section. Use the employer's terminology when it accurately describes your background. Do not manufacture a match.
Letting skills push stronger evidence down the page. If your recent work already proves the target capabilities, a large skills block can make the resume weaker rather than stronger.
Using rating bars or stars. They consume space, depend on an undefined self-rating scale, and add graphical complexity.
Listing soft skills without context. Put the evidence in achievements, projects, or responsibilities where the reader can judge it.
A quick placement test
Before finalizing the resume, answer three questions:
- What must the employer verify first for this role?
- Which section contains my strongest credible proof of that requirement?
- Does the current order make that proof easy to find without hiding chronology?
If skills answer question one but experience answers question two more strongly, keep the skills section concise and let experience do the persuasion.
Questions readers usually ask
Should skills go above work experience?
Sometimes. Put skills above experience when technical qualifications, transferable capabilities, languages, or credentials need to be confirmed before your job history makes sense. Put experience first when recent roles already provide stronger evidence of fit.
Where should skills go for a new graduate?
There is no single rule. Relevant education, projects, and technical skills may all deserve early placement. Penn Career Services shows technical student resumes where the skills section appears directly after education, which can work well when those qualifications are central to the target role.
Should soft skills be listed in the skills section?
Usually not as broad labels. MIT recommends keeping the section focused on technical, procedural, language, or laboratory skills and showing interpersonal skills through experience. Evidence such as leading a project, training colleagues, or presenting to clients is more informative than writing “leadership” or “communication.”
How many skills should I list?
Use enough to represent the target role without turning the section into an inventory dump. Relevance, grouping, and proof matter more than hitting a fixed number.
Can I copy skills from the job description?
Use the employer's wording when it truthfully matches your experience. Do not add a skill merely because it appears in the posting. Tailoring should change emphasis, not facts.
Can a two-column skills section hurt ATS parsing?
It can create parsing problems in some systems. CareerOneStop recommends a simple single-column layout, and Greenhouse lists columned resumes among formatting patterns that can cause unsuccessful parsing. Plain text in a clear reading order is the safer default.
Sources and methodology
- CareerOneStop Resume Guide: Formatting — U.S. Department of Labor-sponsored guidance on resume structure, standard headings, single-column formatting, and ATS-readable layout.
- MIT Career Advising & Professional Development: Resume guidance — Guidance on targeting resumes, showing skills in context, and using standard resume structure.
- MIT CAPD: Enhance your resume — Guidance on using a skills section for technical, procedural, language, and laboratory skills while showing interpersonal skills through experience.
- Penn Career Services: Undergraduate resume samples — Examples showing how section order can change when technical qualifications deserve early emphasis.
- Greenhouse Support: Unsuccessful resume parse — First-party documentation on formatting patterns that can interfere with resume parsing.
Section order varies by occupation, career stage, country, and employer. The recommendations here separate documented formatting guidance from HireDraftAI's editorial judgment about information order. No section position or keyword pattern can guarantee an interview. Editorial review: September 25, 2026.
Take the next useful step
Circle the five skills most important to the target job and locate proof for each. Then place the skills section where it answers the reader's first unresolved question without delaying stronger evidence.
Use the Resume Skills Generator to build a focused list, or map the job description to your existing evidence before rewriting. If you want to create a tailored application from the same verified career evidence, start with HireDraftAI.
Choose the examples separately from the placement
If you need to decide what belongs in the section, use the general resume-skills examples. For more specific evidence, see computer skills and proficiency, retail skills, or customer-service skills. Then return to the placement decision: put the section where it makes your strongest relevant evidence easiest to find, without repeating the same list throughout the resume.