Skip to content

Glossary

Hiring glossary

Short definitions of the terms a small team actually uses when hiring. Written for operators, with the EU details US glossaries leave out.

A

3 terms

C

2 terms

H

1 term

J

1 term

P

1 term

R

1 term

T

1 term

How to use this hiring glossary

Hiring glossary

This hiring glossary is a shelf of short definitions for the words a small team actually says in a hiring meeting. Glossary entries are written for the person running the process, not for a textbook. Each term says what the word means in practice, where teams get it wrong, and how it shows up on one record instead of in three tools.

Start from the word you just used and could not agree on. If two people mean different things by pipeline, open that entry before you rename stages. If a candidate asks what you store, open the entry that covers the record, not a general essay about software. The glossary is alphabetical so you can jump. It is not a course you finish.

Use an entry when you write a job post, a scorecard, or a note to a colleague. The definition is the sentence you can paste into a discussion so you are arguing about the same object. The example is a small company, because that is who gets hurt first when a term is only a slogan. If the entry does not change the sentence you were about to send, you do not need it today.

Terms link to each other on purpose. Applicant tracking is not the same page as an applicant tracking system. The work and the product are different, and mixing them is how a team buys software for a problem it has not named. Read the neighbour when the first definition keeps using a word you also do not share.

A hiring glossary is a list of words your team already uses, with one meaning each. It is not a textbook. Open it when two people are about to spend a meeting defining a word that should have been a field on the record. If the entry does not change the field, the word was not the problem.

Use the entries in the order the work happens. A requisition before a post. A pipeline before a funnel chart. A talent pool before a sourcing target. Teams that start from the chart end up with a number and no list of people behind it. The glossary is there to point at the list.

When you hire someone new, do not ask them to read the whole glossary. Ask them which word they heard in their first week and did not trust. Read that entry together and point at the place in the product where the word is a field. A glossary that never meets the screen is a second language the team will not speak.

Come back to an entry when the meaning has drifted. 'Pipeline' in March might have meant four stages. In June it might mean a report someone exported. Pick one. Change the entry or change the report. A hiring glossary that keeps both meanings will be cited by both sides of the same argument, and it will settle nothing.