A hiring manager opens last year’s job description, changes the title, adds two responsibilities, and sends it to a recruiter. The document is familiar. The work it describes may no longer exist in that form.

Perhaps the previous employee absorbed tasks that belonged elsewhere. Perhaps the business added a new system without removing an old process. Perhaps the team now needs someone to improve the operation, while the description still asks for someone to maintain it. A polished posting can conceal these unresolved choices.

Before deciding who to hire, decide what the person is being hired to accomplish. That conversation belongs ahead of the list of qualifications. It gives the manager, recruiter, interview panel, and eventual employee a common explanation of why the role exists.

This does not require a lengthy consulting exercise. It requires enough discipline to distinguish the business need from the wish list. The result should be a brief that a candidate can understand and a hiring team can actually use.

Start with the problem that creates the vacancy

The first question is not which title should appear in the posting. It is what work is currently missing, delayed, inconsistent, or dependent on the wrong person. A vacancy is one reason to recruit. It is not, by itself, a definition of the role.

Consider a hypothetical operations team that wants a coordinator. The manager describes an overloaded inbox, missed handoffs, and customers asking repeatedly for updates. A replacement posting might request scheduling experience, strong communication, and familiarity with several applications. Those requirements reveal little about the problem the coordinator needs to solve.

A clearer purpose would be to establish dependable ownership of incoming requests, communicate next steps, and make unresolved items visible before they become overdue. The tools matter because they support that work. They are not the work’s purpose.

Ask what would remain difficult if the vacancy were filled tomorrow. If the answer includes unclear ownership, unavailable approvals, or conflicting priorities, the hiring brief should acknowledge those conditions. Otherwise, the business may recruit a person to solve a problem it has not given them authority to address.

Replace activity lists with a few meaningful outcomes

An activity says what someone does. An outcome explains what the activity is meant to achieve. Both belong in a role, but a description made entirely of activities leaves success open to interpretation.

For the coordinator, processing requests is an activity. Maintaining an accurate view of each request’s owner and next step is an outcome. Sending updates is an activity. Ensuring customers know whether an item is progressing, blocked, or waiting on them is an outcome.

Choose a small number of outcomes that reflect the role’s real contribution. Describe what evidence would show progress. Avoid adding a number simply because a measurable statement appears more sophisticated. A target without a baseline, resources, or a reasonable explanation can create false precision.

For a new function, an early outcome might be establishing the baseline itself. A manager can reasonably expect an analyst to document the current process before recommending a target. Treat that discovery as valuable work rather than evidence that the analyst has not yet begun producing results.

Distinguish essential capability from familiar background

A person who has used your exact system may still need to learn your business rules. A person who has not used it may understand the underlying work unusually well. Hiring requires judgment about which gaps can be supported and which would prevent effective performance.

The U.S. Office of Personnel Management describes job analysis as examining job tasks, required competencies, and the relationship between them. That foundation is useful beyond the federal hiring setting: a requirement should have a clear connection to the work it supports. [1]

For each proposed qualification, ask what task depends on it. Then ask whether the candidate must possess it when starting or could develop it through a defined learning period. The answer should reflect actual capacity to train, not a vague assurance that the team will help.

Separate genuine requirements from preferences. A preference is allowed to matter, but it should not silently become an automatic rejection rule. If specific industry experience is essential, explain which decisions require it. If adjacent experience would be acceptable, describe what evidence would establish that transfer.

Make the learning plan part of the hiring decision

Calling a skill learnable creates a responsibility for the employer. Someone must provide access, instruction, feedback, and time. A hiring team cannot treat a gap as acceptable during selection and then treat the same gap as a surprise after the person starts.

Imagine two applicants for a reporting role. One knows the team’s reporting application but needs development in interpreting business requests. The other understands reporting logic and stakeholder needs but has not used the application. There is no universal answer about which person is stronger.

The decision depends partly on what the team can teach. If a capable application specialist can provide a structured orientation, the second candidate may have a workable path. If the role must immediately configure a complex environment without support, application experience may carry different weight.

Record that reasoning. It makes the tradeoff visible and gives the eventual manager a starting point for onboarding. It also prevents an interview panel from using different private assumptions about how quickly a person should become independent.

Define authority as carefully as responsibility

A posting may ask someone to own a process without explaining what ownership permits. Can the person change a workflow, establish a deadline, request information from another department, or escalate a missed commitment? Who can overrule the decision?

Responsibility without clear authority is difficult to assess in an interview. A candidate may describe sound judgment while imagining a level of control the role will not have. The hiring team may then interpret reasonable questions about approvals as reluctance to take ownership.

Describe the decisions the employee can make independently, those requiring consultation, and those reserved for a manager. Include recurring dependencies. If another team controls system access or final approval, that relationship belongs in the brief.

This is especially important when a role crosses functions. A project manager may coordinate delivery while technical leaders own design decisions. An account manager may resolve routine service issues while a commercial leader approves pricing changes. Clear boundaries make collaboration easier to discuss before an offer is accepted.

Tell the truth about the working environment

Some roles involve frequent interruptions. Others require protected concentration. Some organizations have documented procedures. Others expect the new employee to help build them. None of these conditions should be disguised behind phrases such as fast paced or entrepreneurial.

Translate the environment into observable expectations. Explain the typical balance between planned and urgent work, how priorities change, and where the employee can seek a decision. If travel or specific working hours are essential, say so accurately and early.

For remote work, describe how the team coordinates. A location label does not explain meeting expectations, time zone coverage, or how decisions are documented. Candidates need enough information to understand the working arrangement, not just whether they can avoid a commute.

Honesty also means separating the current situation from the aspiration. A team may want a calm, repeatable operation while currently managing a backlog. Describe the starting point and the support for improving it. Candidates can evaluate a challenge more intelligently when it is presented plainly.

Agree on evidence before meeting candidates

Once the role is defined, choose how applicants will demonstrate the capabilities that matter. Do not wait until the interview debrief to decide that communication, judgment, or ownership was the decisive quality.

OPM’s structured interview guidance describes using job-related questions about past behavior or hypothetical situations, with consistent questions and evaluation standards. [2] A business can apply that principle without turning every conversation into a rigid script.

For example, ask candidates to explain how they would handle a request with incomplete information and a deadline. Assess whether they identify missing information, distinguish urgency from importance, communicate the uncertainty, and propose a reasonable next step.

If an exercise is used, keep it proportionate and explain its purpose. A short fictional scenario can reveal reasoning without asking candidates to perform productive work for the business. Decide the assessment criteria in advance and give comparable candidates a comparable opportunity to respond.

Test alignment inside the hiring team

Before launching the search, ask the recruiter and each interviewer to explain the role’s three most important outcomes. Listen for differences. Those differences are useful information while there is still time to resolve them.

One leader may want immediate delivery. Another may expect a process redesign. A third may assume the employee will train the team. Each expectation might be reasonable separately. Together, they may create a role that exceeds its title, authority, or available time.

Discuss tradeoffs explicitly. Which outcome comes first? What can wait? What will stop being done? If the business cannot answer these questions, an applicant cannot resolve them merely by being talented or enthusiastic.

The recruiter should leave this discussion knowing which evidence matters, which gaps are acceptable, and which questions require a manager’s answer. That is a more useful search tool than a long list of adjectives describing the ideal candidate.

Build a brief that survives the interview process

A workable hiring brief can fit on a few pages. It should state the role’s purpose, early outcomes, recurring responsibilities, essential capabilities, trainable skills, decision boundaries, working conditions, and assessment approach. The exact format matters less than the agreement behind it.

For the hypothetical coordinator, the brief might prioritize dependable request tracking, clear customer updates, and timely escalation. It could identify spreadsheet accuracy and written communication as immediate requirements, while allowing time to learn the internal platform.

The same brief should explain that the manager approves changes to service commitments, another team controls access, and the first month includes reviewing current request categories. These details let an interviewer distinguish relevant evidence from a candidate’s general confidence.

When something changes during the search, update the brief and tell the people using it. Quietly changing the standard between candidates makes the final comparison harder to explain. A change in the business need is legitimate. An undocumented moving target is a process problem.

Use the brief to identify what the role does not own

An effective definition includes boundaries. Without them, every adjacent problem can become part of the vacancy simply because the new person appears capable. Ask which responsibilities remain with the manager, another function, or an external partner.

For the coordinator, resolving a billing dispute may belong to finance even when the coordinator tracks the request. Maintaining visibility does not mean deciding the financial outcome. Naming that boundary helps the recruiter assess coordination skills without implying that the applicant also needs specialist financial authority.

Discuss what happens when work falls between functions. The answer should identify an escalation path, rather than assuming the new employee will negotiate every boundary alone. A clear role can still be flexible. It simply gives the team a starting point for recognizing when an additional responsibility requires a conversation about priorities, support, or scope.

Carry the agreement into the first months

The brief should continue to matter after the offer. Use it to plan introductions, training, access, and early conversations about progress. A person hired to establish a process needs opportunities to observe it and meet the people who depend on it.

If an expected resource is unavailable, discuss the effect on the work. Do not leave the original target untouched while removing the conditions that made it reasonable. Revisit priorities as the employee learns what the role actually requires.

Make space for the new employee to improve the definition. They may identify a dependency the hiring team missed or discover that a recurring task serves no clear purpose. Listening to that evidence does not weaken managerial accountability. It makes the original brief a working document rather than a promise nobody revisits.

The job description is the public invitation. The hiring brief is the agreement that gives the invitation substance. Before asking candidates to prove they can do the job, the business should be able to explain what the job is, how success will be assessed, and what support comes with it.

Sources

1. U.S. Office of Personnel Management: Job Analysis

2. U.S. Office of Personnel Management: Structured Interviews