The skills section

Hard skills are specific, teachable abilities you can test or show, such as accounting, Python, welding or Arabic typing. Soft skills are ways of working with people and tasks, such as communication, teamwork, problem solving and time management.

Examples:

• Hard skills: SAP FICO, AutoCAD, phlebotomy, Google Ads, forklift operation, payroll processing.
• Soft skills: negotiation, customer handling, leadership, adaptability, attention to detail.

On a resume, hard skills fit neatly into a skills list because the reader can check them quickly. Soft skills are better shown through your bullet points, where you give evidence, for example a line about resolving escalated complaints shows customer handling better than the words "customer handling" alone. Most employers want both, but they believe hard skills from a list and soft skills from examples.

Most jobs need both kinds, so name your hard skills clearly and prove your soft skills with examples.

Usually between 8 and 15 skills in the skills section, chosen for the job you are applying to. Fewer, well-chosen skills are more convincing than a long list.

Guidelines:

• Entry-level resumes often have 6 to 10.
• Experienced or technical resumes may have more, grouped under short headings.
• Every skill should be something you could discuss or demonstrate in an interview.

A list of 30 skills makes it hard for the reader to see what you are actually strong in, and some items will look padded. If you have many tools and technologies, group them (for example "Languages", "Frameworks", "Cloud") rather than writing one long line. Cut anything outdated, basic for your level, or unrelated to the job.

Quality beats quantity: a short, relevant list is easier to trust and easier to discuss.

Usually after your summary, or after work experience, depending on what you want the reader to see first.

Common choices:

• Near the top, under the summary: good for technical roles, career changers and anyone whose skills are the main selling point.
• After experience: good when your work history is strong and the skills mainly confirm it.
• After education: common for students and fresh graduates with little work history.

There is no fixed rule. Ask which section best proves you fit the job, and put that first. Whatever order you choose, keep the heading simple, such as "Skills" or "Key Skills", so both people and software recognise it. In a builder where sections can be reordered, try both positions and look at the preview.

You can include a few, but show them mainly through your experience bullets. A list of soft skills on its own convinces very few readers, because everyone writes "team player" and "good communicator".

A practical approach:

• Keep the skills section mostly for hard, checkable skills.
• Add two or three soft skills only if the job advert stresses them, such as "stakeholder management" or "conflict resolution".
• Prove each one somewhere in your experience.

Example of proof: "Mediated scheduling disputes between two shift teams, agreeing a fair rota both accepted." That bullet shows conflict resolution far better than listing the words. Choose specific soft skills ("client negotiation") over vague ones ("people skills").

Start from the job advert, then list only the skills you genuinely have that match it, plus a few core skills for your profession.

Steps:

• Highlight every skill, tool and qualification mentioned in the job advert.
• Mark the ones you can honestly claim and could demonstrate.
• Add essential skills for your role that the advert may not mention.
• Remove anything outdated, very basic or unrelated.
• Order the list so the most important for this job come first.

Example for an accounts payable role: "Accounts payable, three-way matching, vendor reconciliation, SAP S/4HANA, VAT invoicing, Excel (VLOOKUP, pivot tables)."

Keep a master list of all your skills in a separate document so you can choose quickly for each application.

Check the final list against your experience bullets so that each key skill is backed up.

Yes, if you have more than about 10 skills or they cover different areas. Grouping makes the list easier to scan and shows the shape of your expertise.

Common groupings:

• Technical: Languages, Frameworks, Databases, Cloud, Tools.
• Finance: Accounting, Systems, Reporting, Compliance.
• Marketing: Channels, Analytics, Content, Tools.
• General: Core skills, Software, Certifications.

Example:
"Data: SQL, Python (pandas), Power BI, Excel
Methods: A/B testing, regression, forecasting
Tools: Git, Jira, Snowflake"

Keep group headings short and plain. If you only have six to eight skills, one simple list is usually clearer than several tiny groups.

It is usually better not to. Graphic ratings are hard to interpret, can undersell you and may not be read correctly by applicant tracking systems.

Problems with visual ratings:

• Three stars out of five could mean "competent" to you and "weak" to the reader.
• Bars and circles are often images or shapes, so software may skip them entirely.
• Rating yourself highly in everything looks unrealistic; rating yourself modestly invites doubt.

Better options:

• List skills without levels.
• Use simple words where a level matters: "Advanced", "Intermediate", "Basic".
• Prove the level with experience: "Built monthly forecasting models in Excel using Power Query."

If you like a visual design, keep a text version of the level next to any graphic.

Plain text levels are clearer for human readers and safer for recruitment software.

Use short, consistent words such as Expert, Advanced, Intermediate and Basic, or show the level through experience and certifications.

Options:

• Words: "Excel (Advanced), Power BI (Intermediate)".
• Years of use, if accurate and meaningful: "AutoCAD (6 years)".
• Certifications: "AWS Certified Solutions Architect – Associate".
• Context: "Python for data cleaning and automation scripts".

Choose one method and use it consistently. Avoid levels that sound unsure, such as "a bit of" or "familiar with", for skills that matter to the job. If you are a beginner in something, it is often better to leave it out or mention it under "currently learning" than to label it "Basic" next to your main skills.

"Proficient" means you can use a skill confidently and independently in normal work, though not necessarily at expert level. It is fine to use if it is true.

Rough meanings readers often assume:

• Basic or familiar: you have used it but need help.
• Proficient or intermediate: you use it regularly without help.
• Advanced: you handle complex tasks and help others.
• Expert: you are a go-to person or could teach it.

Instead of writing "Proficient in Excel", consider being specific: "Excel: pivot tables, XLOOKUP, conditional formatting, basic macros". Specific features tell the reader exactly what you can do and are more believable than a level word on its own.

List it only if it matters for the job, and be specific about what you can do. For many office roles, basic Word and Outlook use is assumed and does not need listing.

When it is worth including:

• Admin, finance, data and reporting roles, where spreadsheet or document skills are central.
• When the advert asks for it explicitly.

How to make it useful:

• Name the applications that matter: "Excel, PowerPoint, Outlook".
• Add specific features for key tools: "Excel: pivot tables, XLOOKUP, charts".
• Use "Microsoft 365" if you also use Teams, SharePoint or OneDrive.

Writing just "MS Office" tells the reader almost nothing, because nearly every applicant can open Word.

Name the specific features you use and, ideally, what you used them for. "Excel" alone could mean anything from typing a list to building financial models.

Ways to describe your level:

• Basic: data entry, formatting, simple formulas such as SUM and AVERAGE.
• Intermediate: VLOOKUP or XLOOKUP, pivot tables, charts, conditional formatting.
• Advanced: Power Query, Power Pivot, complex nested formulas, macros or VBA, dashboards.

Example skills line: "Excel: XLOOKUP, pivot tables, Power Query, dashboard design."

Example bullet that proves it: "Built an Excel dashboard tracking 50 suppliers' delivery performance, used in weekly purchasing meetings."

Only list features you could use on the spot if an employer gave you a practical test.

Use the same wording as the job description where it truthfully describes your skill. This helps both the human reader and keyword searches in applicant tracking systems.

Examples of matching wording:

• Advert says "accounts receivable"; you wrote "collections". Add or switch to "accounts receivable" if that is what you did.
• Advert says "Microsoft Dynamics 365"; you wrote "Dynamics". Use the full name.
• Advert says "people management"; you wrote "team leadership". Either is fine, but consider using their phrase.

Do not copy skills you do not have, and do not paste the whole advert into your resume. A comparison tool, such as the job-description comparison in ResumeBuilder.ae, can show which frequent terms from the advert are missing from your resume, so you can check whether any of them truthfully apply.

Transferable skills are abilities you built in one job or setting that are useful in another, such as planning, customer service, budgeting, training others or data handling.

How to list them:

• Name the skill in the language of your target job, not your old one.
• Put the most relevant ones in your skills section.
• Prove each with a bullet from your past role.

Example for a hospitality worker moving into sales: skills section lists "Upselling, customer relationship building, handling objections"; experience bullet says "Increased average spend per table by recommending set menus to guests."

Transferable skills matter most for students, career changers and people returning to work, because they bridge the gap between what you have done and what the new job needs.

Name the skill the way the new field names it.

Yes, if you label them honestly, for example "Currently learning: Power BI (online course, due 2027)". Do not list them alongside your strong skills as if they were the same level.

Ways to show it:

• A short "Currently learning" line at the end of your skills section.
• A course in your education or training section with an expected completion date.
• A project that shows what you have built so far.

This works well when the skill is relevant to the job and you can talk about your progress. It shows initiative. What you should avoid is claiming a skill you have only just started, because a practical test or a technical interview question will expose the gap quickly.

Specific soft skills are worth listing when the job needs them; generic personality words are usually clichés.

More useful, specific soft skills:

• Stakeholder management
• Conflict resolution
• Negotiation
• Public speaking or presenting
• Coaching and mentoring
• Cross-cultural communication

Overused words that say little on their own:

• Hard-working
• Team player
• Good communicator
• Motivated
• Detail-oriented
• Fast learner

The overused ones are not forbidden, but almost every resume has them, so they do not help you stand out. If a quality matters, show it through an achievement instead: "Learned the new ERP system within two weeks and became the team's go-to person for it" proves "fast learner".

Yes, that is normal and helpful. The skills section is a quick summary; the experience section proves you used those skills at work.

How they work together:

• Skills section: "Salesforce, pipeline management, contract negotiation".
• Experience bullet: "Managed a pipeline of 60 opportunities in Salesforce, negotiating annual contracts with retail clients."

The reader sees the skill at a glance, then finds evidence in your history. Keyword searches in recruitment software also tend to pick up terms wherever they appear in the text.

What to avoid is listing important skills only in the skills section with no evidence anywhere else, or repeating the same skill word many times without adding anything new.

Lead with the skills your new field needs that you already have, written in the new field's language, and back them up with examples from your past work, studies or projects.

Steps:

• Collect common skills from several job adverts in your target field.
• Mark the ones you already have, from work or training.
• Add any new skills from recent courses or projects.
• Place the skills section near the top, under your summary.

Example for a retail manager moving into HR: "Recruitment and interviewing, onboarding, rota planning, performance conversations, staff training, HR policy (CIPD Level 3, in progress)."

Your experience bullets should then support these skills, so the reader sees a clear link between your past and your next role.

A skills-based (functional) resume is organised around skill headings, such as "Project Management" or "Customer Service", with examples under each, and a short job list at the end instead of detailed roles.

When people use it:

• Big career changes.
• Long gaps in employment.
• Many short or unrelated jobs.

Drawbacks:

• Many recruiters prefer to see what you did in each job and when.
• It can look like you are hiding something.
• Software that expects job titles and dates may read it less clearly.

A common compromise is a combination (hybrid) resume: a strong skills summary at the top, followed by a normal reverse-chronological work history. This keeps the benefits of a skills focus while still showing a clear timeline.

Choose the format that gives the clearest, most honest picture of your background.

Group them by type and list the most relevant ones for the job first. Technical readers scan for specific technologies, so precision matters.

Example structure:
"Languages: Python, TypeScript, Java
Frameworks: Django, React, Spring Boot
Databases: PostgreSQL, MongoDB, Redis
Cloud and DevOps: AWS (EC2, S3, Lambda), Docker, Kubernetes, GitHub Actions
Practices: REST APIs, unit testing, CI/CD"

Tips:

• Use official names and spelling (PostgreSQL, not Postgress).
• Leave out tools you used once years ago.
• Do not list obvious basics such as "Windows" or "internet".
• Show depth through your project and job bullets.

Only if they are relevant and you label them honestly, for example under "Familiar with". Otherwise leave them out.

Why it matters:

• Technical interviews and coding tests can include any language you list.
• A long list of languages you barely know can make your real strengths harder to see.

A simple way to separate them:
"Proficient: Python, SQL
Familiar: Go, Rust"

Use the "Familiar" line sparingly, and only for languages that are useful for the role. If a job asks for a language you used a little, mentioning it with a project helps more than a bare name: "Built a small CLI tool in Go as a personal project."

List a mix of customer-handling skills and the systems you use, matched to the advert.

Commonly relevant skills:

• Complaint resolution and de-escalation
• Phone, email and live-chat support
• CRM systems (for example Zendesk, Salesforce Service Cloud, Freshdesk)
• Order and refund processing
• Product knowledge and upselling
• Typing speed, if requested in the advert

Example skills section: "Complaint handling, live chat and email support, Zendesk, order processing, refunds and returns, Arabic and English customer support."

Prove the people skills in your experience with examples of difficult situations you handled well. If you speak the languages customers use, list them in your languages section too.

List selling skills, the sales tools you use and the markets or products you know.

Commonly relevant skills:

• Prospecting and lead generation
• Consultative selling
• Negotiation and closing
• Account management
• Pipeline management in a CRM (for example Salesforce or HubSpot)
• Product or sector knowledge, such as FMCG, real estate or medical devices

Example: "B2B prospecting, consultative selling, contract negotiation, key account management, Salesforce, FMCG distribution in the GCC."

Sales hiring managers care most about results, so make sure your experience section shows targets met or exceeded. The skills list supports that evidence; it does not replace it.

List channel skills, analytics, tools and content abilities that match the advert.

Commonly relevant skills:

• SEO and content marketing
• Paid search and paid social (Google Ads, Meta Ads, TikTok Ads)
• Email marketing and automation (for example Mailchimp, HubSpot, Klaviyo)
• Web analytics (Google Analytics 4, Looker Studio)
• Social media management
• Copywriting and basic design (Canva, Adobe Express)
• A/B testing

Example: "SEO, Google Ads, Meta Ads, GA4, email automation in HubSpot, content strategy, A/B testing."

Show results from your campaigns in your experience section. If you have certifications from ad platforms, list them in your certifications section with the date earned.

List organisation, office software and communication skills that match the advert.

Commonly relevant skills:

• Calendar and diary management
• Travel and meeting coordination
• Minute taking
• Document control and filing
• Microsoft 365 (Outlook, Word, Excel, Teams)
• Data entry with accuracy
• Petty cash and expense claims
• Bilingual correspondence, if relevant

Example: "Diary management, travel bookings, minute taking, document control, Microsoft 365, data entry, expense processing."

Add any specific systems you have used, such as SAP for purchase orders or a visa processing portal. These details help you stand out among applicants with similar general skills.

List technical disciplines, design and analysis software, codes or standards you work with, and site or project skills.

Example for a mechanical engineer:
"Design: SolidWorks, AutoCAD, GD&T
Analysis: ANSYS, FEA, thermal calculations
Standards: ASME, ISO 9001 processes
Project: commissioning, maintenance planning, vendor coordination"

Example for a civil engineer:
"Design: AutoCAD Civil 3D, ETABS, SAP2000
Site: quantity surveying, method statements, QA/QC inspections
Project: Primavera P6, subcontractor coordination"

Name codes and standards only if you have actually applied them. Professional registrations belong in a separate section with their numbers and dates as the regulator expects.