Build your own skills glossary from real job postings

You have real skills. What you may be missing is the vocabulary that describes them in the terms your target field uses. That vocabulary is sitting in plain view, in the job postings for the roles you want. This guide is the do-it-yourself method for pulling it out and putting it to work.

This method helps you avoid guessing what employers want or trusting a generic list of "transferable skills." You're reading the language of current job postings and matching it to work you did.

Why start with job postings instead of a resume template

Most resume advice hands you a template and asks you to fill it with impressive words. That approach produces lines that sound good and fall apart the moment an interviewer asks a follow-up.

Start somewhere better: with the words your field already uses. When a recruiter searches their applicant pool or LinkedIn for someone with a skill, they type the words they know — the ones from the posting they wrote. If your profile describes the same ability in academic language, the search skips you, not because a machine rejected you, but because you filed a real skill under a word nobody searched for. Postings are a guide to the search terms a recruiter may use. Build your glossary from the map.

Recommended: Get together with someone else who’s searching for jobs at a similar level as you and build the glossary together. A job search buddy is an excellent source of support for a difficult process.

Step 1: Pull vocabulary from real postings in your field

Open LinkedIn, Indeed, or Idealist and find six to eight postings for roles you'd plausibly want. Pick a range — a couple of entry-level, a couple a step up, across a few fields you're curious about. Copy the job titles and the full "Responsibilities" and "Qualifications" sections into one document. (Postings come down fast, sometimes within a day, so save the text, not the link.)

Now read for skills terms — any word or phrase describing something the candidate should be able to do. Write down every one that appears, especially the ones you'd never use about yourself. "Stakeholder management," "cross-functional," "deliverables," "program coordination," "synthesize," "facilitation." Some will be familiar. The unfamiliar ones are the point — that gap between their word and yours is exactly what you're closing.

Note which terms show up across several postings. A word that appears in five listings for your target field is a word worth having on your profile.

Step 2: Break down what you did, not what it was about

Now leave the postings for a moment and pick one real piece of your own work — a thesis chapter, a seminar paper, a campus job, a club you ran, a section you TA'd. Don't describe what it was about. Describe what you did to produce it, step by step, in plain language.

A research paper doesn’t go on your resume as "a paper about the French Revolution." The skills you used to complete it go on your resume: chose and narrowed a topic, searched databases, read forty sources, worked out where they disagreed, developed an argument that accounted for the disagreement, drafted, revised based on feedback, tracked citations, and delivered a long document on a deadline. That list of verbs is your raw material. The topic is not.

This is the step people skip, and skipping it is why so many resumes remain vague. The skill lives in the process, so the process is what you have to identify first.

Step 3: Match your work to the words

Put the two lists side by side. For each thing you did, find the closest term from the glossary you built in step 1.

What you didTerm from your glossary
Searched databases and chose credible sourcesResearch; source evaluation
Worked out where sources disagreed and whySynthesis; research analysis
Built and defended an original argumentAnalytical thinking; evidence-based reasoning
Revised the document across several draftsEditing; attention to detail
Delivered a long project by a deadline, soloProject ownership; time management
Led a weekly discussion of assigned readingsFacilitation; stakeholder communication

Notice what happened. One paper became six searchable skills, each in a term you found in real postings rather than one you invented. That's the whole trick, and it's honest, because every line traces to something you did.

Expect a feeling of resistance here. Turning months of intellectual work into blander professional terms can feel reductive and flattening. You’re not alone in feeling that way. The alternative — leaving the skill invisible because its academic name doesn't travel — is worse for your employment prospects. You're finding the capability underneath the academic framing and giving it a name your reader already uses.

Keep the facts exact while you change the words

There's a line between translation and invention, and staying on the right side of it is what keeps you safe in the interview.

Translate the language, never the facts. Don't round three students up to "a team." Don't turn one event into "events." Never invent a number. If a line would be stronger with a figure you don't have — "grew attendance by [X]%" — leave it as a bracketed placeholder you fill in later with a real number, or cut the figure. A bracket is honest and reminds you to get the real number. A made-up percentage is a trap that springs the moment someone asks about it. The test for any line: if an interviewer asked you to tell the story behind it, could you? If not, it doesn't belong on your resume yet.

Add the strongest terms to your LinkedIn Skills section

The Skills section is one of the main ways LinkedIn matches your profile to a recruiter's search. Someone searching "qualitative research" or "program coordination" sees profiles carrying those exact terms. A student who did qualitative research but listed it as "independent study" won't appear.

Add fifteen to twenty skills, drawn from your glossary and tied to something real in your experience or education. As you type, LinkedIn suggests matching terms from its own taxonomy — use the suggestions, because they're the vocabulary the search indexes. "Analytical thinking" and "research analysis" appear; "critical analysis" often doesn't. Meet the platform where it is.

Do it yourself, or let Unbracket shortcut it

Everything above works. It also takes a couple of focused afternoons, a tolerance for reading job ads, and enough distance from your own work to see the skills you've stopped noticing — which is the difficult part, because the work is yours and the skills feel ordinary to you.

This is exactly what Unbracket does for you. It asks about your real experiences through a set of reflection questions, names the skills living inside your answers in language recruiters recognize, sorts them by how much evidence you gave, and leaves a bracketed placeholder wherever a line needs a number only you can supply. The method is the same one on this page. If you'd rather do it yourself with this guide, you have everything you need. If you'd rather have it done thoroughly and fast, that's the shortcut you're paying for — you can see a sample profile first.

For more on the raw material hiding in your coursework, see the skills you build writing a seminar paper or thesis. Once your skills have names, the next move is telling people — how to ask for an informational interview covers that. And if you teach, this method comes from a career readiness curriculum for educators.

What's one thing you did in school that you've never thought to name as a skill? Start your glossary there.

All guides