What counts as a core competency
A core competency is something you are clearly good at and that matters in your line of work. It is narrower than “skills”: out of everything you can do, these are the few things you would want a recruiter to remember about you.
Good core competencies tend to be:
- Specific: “B2B contract negotiation” rather than “communication”.
- Relevant to the jobs you are applying for.
- Provable: each one should show up somewhere in your work experience as a result or responsibility.
Most lists mix hard skills, like financial modelling or SQL, with a few well-chosen soft skills, like coaching or conflict resolution.
Examples by role
| Role | Possible core competencies |
|---|---|
| Project manager | Agile delivery, budget control, risk management, stakeholder management, vendor management |
| Software engineer | Backend APIs, Python, cloud infrastructure (AWS), code review, system design |
| Sales | Pipeline management, enterprise negotiation, CRM (Salesforce), forecasting, account expansion |
| Nurse | Patient assessment, medication administration, triage, wound care, patient education |
| Marketing | SEO, content strategy, paid social, marketing analytics, campaign planning |
| Customer support | Ticket triage, de-escalation, knowledge base writing, SLA management, Zendesk |
These are starting points, not a list to copy. Use the words that describe what you actually do.
How to choose and list them
- Read the job description. Note the skills it mentions more than once or lists as required.
- Match them against your experience. Keep only the ones you can back up with an example.
- Use the posting’s wording where it fits honestly. If they say “account management”, don’t only write “client care”. It helps both human readers and an applicant tracking system searching for that phrase.
- Put the strongest first. People read the first few items and skim the rest.
- Adjust for each application. Swap two or three items depending on the role.
A simple layout:
Core competencies Pipeline management · Enterprise negotiation · Salesforce · Forecasting · Team coaching · Account expansion
Skip ratings, skill bars and percentages. “Excel 80%” tells the reader nothing, and many hiring systems can’t read graphics. For more on choosing skills, see skills to put on a resume.
Core competencies vs the summary
Your summary is two or three sentences about who you are and what you have achieved. Core competencies are the keyword version of the same story. They work best together: the summary gives context, the list makes your strengths scannable. If space is tight on a one-page resume, a single line of competencies under the summary is often enough.
One check before you send it: for each item on the list, ask yourself where on the page a reader could see you using it. If the answer is “nowhere”, either add a bullet point to a job that shows it, or take it off the list. Interviewers often pick an item from this section and ask you for an example.
FAQ
What is the difference between core competencies and skills?
Core competencies are a selection from your skills, the few that define you professionally and matter most for the job. Your full skills section can be longer and include tools, languages and certifications.
How many core competencies should I list?
Six to twelve is a good range. Fewer can look thin, and more turns into a keyword list nobody reads. Pick the ones that match the job and that your experience section can back up.
Should soft skills be core competencies?
A few can be, if they are specific and you can prove them, such as "stakeholder management" or "coaching new hires". Vague ones like "hard-working" or "team player" add little and are better shown through results.
Where do core competencies go on a resume?
Usually just below your summary or headline, near the top, often in two or three short columns of keywords. On a simple single-column resume, a comma-separated line or a short bullet list works just as well.
