A Job Description Is a Theory About a Person Who Does Not Exist Yet

A job description is written as if its subject already exists.

The skills are known. The responsibilities are settled. The years of experience have been counted. Somewhere, apparently, there is a person who has done exactly this work, with exactly these tools, inside exactly this kind of organization, and is now waiting for the right posting to appear.

A remarkable person.

Possibly an imaginary one.

Every hiring process begins with this contradiction. A company needs a real human being, but it starts by describing an abstraction. The document looks concrete because it contains verbs, qualifications, and bullet points. Underneath, it is a theory about what the work requires and who might be able to perform it.

Like most theories, it reveals as much about its author as its subject.

Specification

Programmers write specifications because ambiguity is expensive. A system needs to accept certain inputs, produce expected outputs, and behave predictably when something goes wrong.

A job description often borrows this logic.

The employee will coordinate projects, communicate across teams, solve problems, manage competing priorities, and remain calm when the ordinary plan collapses. These phrases sound precise until someone tries to use them. Then the edges blur.

What kind of problems?

Which teams?

How many priorities can compete before “management” becomes improvisation?

A technical specification can fail because a requirement was missing. A hiring specification can fail because it describes the visible tasks while ignoring the conditions surrounding them. The spreadsheet matters. So does the manager who changes direction halfway through the week. The software matters. So does the customer who refuses to use it correctly.

Work never arrives alone. It brings a weather system with it.

A useful job description does not attempt to predict every storm. It identifies the conditions that are essential, the skills that can be learned, and the responsibilities that actually belong to the role.

That distinction matters.

Without it, preferences harden into requirements. Familiarity becomes expertise. The description grows more detailed while becoming less accurate.

Precision is valuable only when it describes something real.

Composite

The ideal candidate is often several former employees combined into one fictional successor.

One person understood the customers. Another knew the software. A third could calm a difficult meeting before it became a longer meeting about the first meeting. When those people leave, their strengths merge in memory.

The job description becomes a composite sketch.

This creates a quiet kind of inflation. The next hire is expected to preserve everything the organization valued in the past while also solving the problems it has accumulated since then. The position expands, but the title, authority, and compensation may remain exactly where they were.

Requirements are easy to add because each one sounds reasonable in isolation.

Together, they may describe nobody.

The answer is not to lower every standard. It is to separate what the person must know on the first day from what can be learned during the first six months. A candidate does not need to arrive as the completed system.

People are not downloaded.

They learn, adapt, misunderstand, recover, and become useful in ways the original document could not name. The candidate who matches every line may have stopped growing. The person who misses a few lines may understand how to learn the rest.

Potential is not a missing qualification.

Sometimes it is the qualification that matters most.

Compression

A résumé compresses a life into one or two pages.

Years become date ranges. Difficult projects become verbs. Months of uncertainty turn into a bullet point that says “managed implementation.” The document is useful precisely because it leaves almost everything out.

That is also why it can mislead.

Compression favors work that is easy to name. Revenue increased. A migration finished. A certification was earned. Yet many forms of value resist clean measurement: noticing an error before it spreads, teaching a new employee without being asked, knowing when a customer’s complaint is really a process failure, or keeping a team functional during an unpleasant quarter.

These contributions disappear because no spreadsheet requested them.

Hiring teams know résumés are incomplete, but they sometimes treat the missing information as neutral. It is not. The format rewards people who know how to translate their experience into familiar signals.

That ability can be valuable. It is not identical to doing the job.

A résumé is a map drawn by the traveler. It shows where the traveler wants you to look.

The wise reader studies the marked roads without assuming the blank spaces are empty.

Keywords

Software can compare a résumé with a job description faster than any person can.

Fast is not the same as wise.

Keyword matching works well when the language of the job is stable and candidates describe equivalent experience using identical terms. Human careers rarely cooperate. One company calls the role “operations coordinator.” Another calls nearly the same work “project specialist.” A third invents a title that makes sense only inside its own building.

The machine sees different strings.

The human work may be nearly identical.

This does not make screening technology useless. It makes the technology dependent on the assumptions built into it. If a system searches only for yesterday’s vocabulary, it may filter out someone capable of solving tomorrow’s problems.

The problem becomes sharper when familiar words are treated as proof. A candidate can repeat the language of the posting without understanding the work. Another can understand the work deeply but describe it in terms the system was never taught to recognize.

Automation can reduce repetition. It cannot decide which differences matter.

Every filter is a theory with an off switch. Someone should remember where the switch is.

Interviews

An interview is supposed to reveal the person behind the résumé.

Instead, it often reveals how that person performs during interviews.

These abilities overlap, but not completely.

Some candidates think carefully when given time and context but stumble when asked to narrate their reasoning under fluorescent lights. Others can produce polished stories for every behavioral question, complete with conflict, action, and resolution.

The first may be underestimated.

The second may simply have practiced.

Preparation is not dishonesty. It shows effort. Still, an interview remains an unusual simulation. Most jobs do not require someone to summarize their professional identity to a rotating panel of strangers while pretending not to notice the clock.

Even communication-heavy roles usually allow notes, follow-up questions, shared context, and the possibility of saying, “Let me think about that.”

A better interview does not pretend to eliminate subjectivity. It gives subjectivity something useful to examine.

Show the candidate a realistic problem. Explain the constraints. Let questions happen. Observe how the person gathers information, handles uncertainty, and changes direction when new facts appear.

The goal is not to catch someone being imperfect.

The goal is to see how imperfection moves.

Signals

Credentials, references, assessments, and work samples are signals.

Each tells part of the story. Each can be mistaken for the story itself.

A certification may show disciplined study. It may not show judgment.

Years of experience may indicate depth. They may also represent the same year repeated several times.

A strong reference can reveal consistency, though references are partly selected because they are expected to be strong. A work sample may expose practical thinking, provided the exercise resembles the actual job and does not ask candidates to perform unpaid consulting.

A precise process can still produce a shallow decision.

The answer is not to find one perfect signal. There is no clean sensor for human capability. The better approach is triangulation: use several relevant observations, understand the limitations of each, and look for patterns rather than confirmation.

Confidence should come from convergence, not volume.

A pile of weak evidence does not become strong evidence merely because it has its own folder.

Speed

An empty role creates pressure.

Work accumulates. Deadlines remain stubbornly employed. The people covering the gap begin to absorb tasks that were never supposed to become permanent. Soon, hiring quickly feels like the only responsible choice.

This is where speed becomes expensive.

A rushed process often skips the quiet questions. Why did the previous person leave? Which responsibilities are real, and which survived only because nobody removed them? Does the team need another employee, or does it need a broken workflow repaired?

The vacancy looks like the problem because it is visible.

The system around it may be the actual problem.

Moving deliberately does not mean allowing the role to remain open indefinitely. It means spending enough time on the definition that speed later becomes possible. A clear understanding of the work makes sourcing, interviewing, and evaluation faster because fewer people are being compared against a moving target.

Urgency without clarity is just haste wearing a calendar.

A fast hire can solve this week’s scheduling problem while creating next quarter’s management problem. The time saved at the beginning returns later as retraining, turnover, and another job posting.

Speed is useful.

Direction is what makes it progress.

Translation

Organizations tend to describe needs in the language of headcount.

“We need another person.”

The sentence may be true, but it is incomplete. The real need might be temporary capacity during a deadline, specialized knowledge for a limited project, coverage during an absence, or a long-term team member whose fit cannot be understood through interviews alone.

Headcount counts people.

Capacity counts what the system can carry.

This distinction matters because different problems deserve different forms of hiring. A staffing agency can operate within this translation layer, helping connect permanent, temporary, seasonal, or contract-to-hire needs with people whose experience may not mirror the original specification word for word.

The useful part is not simply finding more résumés.

It is clarifying what kind of relationship the work actually requires.

Translation changes the question from “Who matches this document?” to “What arrangement gives the work and the person a fair chance to succeed?”

That is a smaller question.

It is also a more honest one.

Trials

Contract-to-hire arrangements are sometimes framed as extended auditions.

That description misses half the system.

The organization is also being evaluated.

A candidate learns whether expectations remain stable after the interview, whether managers answer questions, whether the team shares information, and whether the culture described during recruitment survives contact with an ordinary Tuesday.

The company learns different things. It sees how the person approaches actual work, absorbs feedback, manages uncertainty, and interacts with the people who shape the role every day.

This is not risk elimination. Nothing involving humans offers that feature.

It is an exchange of evidence.

For the arrangement to remain fair, both sides need clarity about the timeline, compensation, evaluation criteria, and possibility of conversion. Ambiguity should not become a discount applied to someone’s labor.

A trial reveals more when the terms are not part of the test.

Temporary

Temporary work is often treated as permanent work with a shorter expiration date.

That is poor design.

A temporary employee usually enters with less context and less time to absorb it. The organization cannot hand over a dense folder, point toward the software, and expect useful work to appear automatically. The assignment needs a tighter boundary, a clear owner, and an answer to a basic question: what would “done well” look like here?

Good temporary roles are designed for entry.

The tools are available. Decisions have owners. Essential knowledge is written somewhere other than one veteran employee’s memory. The temporary worker is not expected to reverse-engineer the organization before contributing to it.

This is where temporary staffing can expose permanent weaknesses. If a capable newcomer cannot understand how work moves, the problem may not be the newcomer.

Short assignments are diagnostic tools.

They reveal whether the organization has built a process or merely accumulated habits.

Seasons

Seasonal demand looks predictable when viewed from far enough away.

The calendar says the busy period happens every year. Then reality adds a late contract, an early rush, an equipment failure, three absences, and a customer request that apparently exists outside time.

Predictability has limits.

Seasonal staffing works best when the organization distinguishes repeatable demand from genuine uncertainty. Historical volume, scheduling patterns, training time, and productivity after onboarding can inform the plan.

None can turn a forecast into a promise.

The useful question is not whether the prediction will be exact. It will not. The question is how costly the error will become.

Too few people create delays and burnout. Too many create idle time and unnecessary expense. A resilient plan considers both possibilities and identifies the point at which staffing should expand or contract.

Forecasting does not remove uncertainty.

It gives uncertainty a shape.

Fit

“Culture fit” sounds warm and often behaves vaguely.

At its best, it means a person can work effectively within the organization’s norms. At its worst, it becomes a reason to prefer candidates who already sound, think, and behave like the people making the decision.

Familiarity feels safe.

It can also reproduce a team’s blind spots.

A better question is whether the candidate can contribute to the working environment without being forced to imitate it. Does the person communicate clearly enough for the role? Can the team handle disagreement without treating it as disloyalty? Are the organization’s stated values visible in daily decisions, or do they live mainly on the careers page?

Fit should describe an interaction, not an identity.

Shoes fit feet. People fit systems only when both can adjust.

A team that never needs to adjust may not be welcoming new people. It may simply be producing copies.

Gaps

A gap in employment looks like empty space.

It rarely is.

A person may have cared for family, recovered from illness, studied independently, moved, searched during a weak market, or taken time to reconsider a career that had stopped making sense. The résumé leaves a blank because human life does not always fit inside professional categories.

Hiring processes often treat uninterrupted employment as evidence of reliability. Sometimes it is. It can also reflect luck, health, timing, and access to opportunity.

A gap deserves a question, not an automatic conclusion.

The same principle applies to nonlinear experience. Someone who moved between industries may lack a tidy narrative but possess a valuable ability to learn unfamiliar systems. A candidate without the expected title may already have performed the work under another name.

Careers are not databases.

Missing rows are not necessarily missing data.

Onboarding

Hiring does not end when an offer is accepted.

That is when the original theory meets production.

The new employee arrives and begins testing every assumption embedded in the job description. Some responsibilities prove accurate. Others belong to someone else. Tools are missing. Priorities conflict. The manager discovers that an “obvious” process was obvious only to the people who had used it for five years.

Onboarding is often treated as orientation: passwords, policies, introductions, and forms.

Those pieces matter. They are not the whole system.

Real onboarding explains how decisions get made, where reliable information lives, who can resolve a blocked task, and which mistakes are normal during the first few months. It gives the new employee a way to compare the written role with the lived one.

A person cannot succeed inside a system they are still being asked to guess.

Clarity at this stage does more than improve comfort. It shortens the distance between arrival and useful contribution. It also reduces the risk that silence will be mistaken for understanding.

The first weeks should not test whether the employee can find hidden information.

They should reveal whether the organization knows how to share it.

Revision

The job description should change after the person arrives.

This may sound backward. The role was supposed to define the hire, not the other way around. Yet any organization that refuses to revise its theory after receiving new evidence is not practicing consistency.

It is ignoring the experiment.

A new employee may bring a skill nobody expected, notice an inefficient handoff everyone else accepts, or reveal that one “essential” responsibility consumes time without producing value. The position becomes more accurate because someone is finally living inside it.

This does not mean rewriting the role around every preference. Some work remains necessary even when nobody enjoys it.

It means recognizing that descriptions are models, and models should improve when reality disagrees with them.

The best hiring outcome is not a person who disappears neatly into a predefined box.

It is a person who performs the necessary work while helping the organization understand the box.

Unknowns

Hiring promises prediction.

That promise cannot be fully kept.

A description can clarify the work. A résumé can compress experience. An interview can reveal patterns. A temporary or contract-to-hire arrangement can create evidence under real conditions. References, assessments, and work samples can add perspective.

None can calculate a human future.

People change when responsibility becomes real. Teams change when someone new joins them. Managers discover strengths they did not request and weaknesses they forgot to mention. The work itself keeps moving, quietly making parts of the original document obsolete.

This uncertainty is not a flaw to remove.

It is the condition of hiring anyone who is still capable of becoming more than their application.

The job description begins as a theory about a person who does not exist yet. Its purpose is not to predict that person perfectly. It is to make the first conversation accurate enough, open enough, and honest enough that a real person can eventually appear.

The description begins the search.

The person rewrites the role.

DISK TIMES