Phase One of the Scientific Hiring Method: The Blueprint

A good job description does more than list duties. It helps the right person understand why the role matters, what success looks like, and whether the work fits them.

Most job descriptions are written backward. Someone finds an old document, adds a few responsibilities, expands the qualifications, and posts it as quickly as possible. The result may describe a position, but it rarely gives a strong candidate a clear reason to care.

The better approach is to define the work first. Once you know why the role exists, what the person must accomplish, and which capabilities truly matter, the job description becomes much easier to write. It also becomes more useful later because the same standard can guide screening, interviews, and the final decision.

Quick answerTo write a job description that attracts the right candidates, begin with the business reason for the role, describe three to five outcomes the person must produce, explain the essential responsibilities, separate required capabilities from preferences, and give candidates the practical information they need to decide whether the opportunity fits them.

Begin with the work, not the résumé

Before writing the job description, define the role. Ask why the position exists, what will remain broken or delayed if it stays empty, and what the person must accomplish during the first several months.

The U.S. Office of Personnel Management describes job analysis as the foundation for assessment and selection decisions. Job analysis examines the tasks performed in a job, the competencies needed to perform those tasks, and the relationship between the two. That principle applies just as well to a growing business as it does to a large institution.

If you begin with a candidate profile instead, the description often becomes a wish list. It may call for ten years of experience, several credentials, a long collection of skills, and a personality that sounds universally appealing. None of that tells a candidate what the company actually needs done.

Start with the work. Then decide what background and capability would allow someone to perform it.

Know whether you are writing a job description or a job posting

An internal job description and a public job posting serve related but different purposes. The internal description can document reporting relationships, responsibilities, essential functions, working conditions, and how the role fits into the organization. The public posting is an invitation. It should give qualified people enough information to understand the opportunity and decide whether to apply.

In everyday business language, both documents are often called a job description. That is fine as long as you know which purpose you are serving. This guide focuses on the public-facing version, while preserving enough substance to support the hiring process after candidates apply.

Use a clear and believable job title

The title should help the right person recognize the work. Use language candidates are likely to understand and search for. Avoid inflated titles that make a modest role sound senior, and avoid clever titles that hide what the job actually is.

The title should also match the level of authority and accountability. Calling someone a director when they have no team, budget, or decision authority may attract the wrong candidates and disappoint the right ones once they learn the truth.

Open with why the role matters

The opening should explain why the company is hiring and what the person will have the chance to improve, build, or own. This gives the role context and helps a strong candidate picture the difference they could make.

For example, “We are looking for an Operations Manager to oversee daily operations” says very little. A stronger opening might explain that the business is growing, the owner can no longer coordinate every handoff, and the new manager will create a more reliable operating rhythm without adding unnecessary bureaucracy.

The second version is more specific, but it also feels more human. It tells the candidate what is happening inside the business and why the role exists now.

Describe outcomes before listing duties

Duties tell candidates what they may do. Outcomes tell them what the company needs those activities to produce. Both belong in a useful job description, but outcomes should come first because they give the responsibilities meaning.

Instead of saying only that a Sales Manager will manage the pipeline, coach representatives, and prepare forecasts, explain what success should look like. The person may be expected to create a forecast the owner can trust, establish a consistent sales review, and improve the team’s ability to move important opportunities forward.

Three to five outcomes are usually enough. More than that often turns the description into a list of everything anyone might ever ask the person to do.

Use a simple structure

A clear job description does not need an elaborate format. It needs an order that makes sense to candidates and remains useful to the hiring team.

Section What to include
Job title A recognizable title that matches the work and level of responsibility.
Why the role exists The business need, problem, or opportunity that makes the position important.
What success looks like Three to five outcomes the person should produce, including reasonable early expectations.
Essential responsibilities The recurring work and decisions needed to produce those outcomes.
Required capabilities The knowledge, skills, judgment, experience, and behaviors needed on the first day.
Preferred qualifications Helpful background that may strengthen a candidate but is not essential to performing the work.
Practical details Location, schedule, travel, reporting relationship, compensation information, and other conditions candidates need to evaluate the role.
How to apply What candidates should send, what happens next, and any reasonable deadline or process information.

Separate requirements from preferences

A requirement should be something the person truly needs to perform the job. A preference may be helpful, but the company could still hire a strong candidate without it.

This distinction matters because long qualification lists can screen out capable people before the company has a chance to evaluate them. It also matters inside the hiring team. When preferences are written as requirements, interviewers may reject candidates for failing to match a familiar background even when they have strong evidence of doing the work.

OPM’s guidance on selection competencies makes a useful distinction: only competencies applicants are expected to possess on the first day are appropriate for selection. Capabilities that can reasonably be learned through training or experience after hire should not automatically become entry requirements. See OPM’s explanation of entry competencies and selection.

Ask whether each requirement is connected to an outcome, whether the company can teach it, and whether a different form of experience could provide the same capability.

Describe essential functions and working conditions carefully

The job description should accurately describe the work people must be able to perform, with or without reasonable accommodation. Avoid copying physical requirements from another role simply because they appear in an old template.

The Equal Employment Opportunity Commission explains that essential functions are the basic duties an employee must be able to perform, and it advises employers to examine each job carefully when determining which functions are essential. The EEOC also notes that a written description can be evidence of what the employer considered essential, although it is not the only evidence. See the EEOC’s guidance on employer responsibilities under the ADA.

Include schedule, travel, location, physical environment, and other practical conditions when they genuinely affect the work. Be precise rather than dramatic. “Fast-paced environment” tells a candidate much less than explaining the actual pace, volume, deadlines, or interruptions the person will handle.

Write for a qualified person, not for a search engine

Use the words people in the field commonly use, but do not repeat titles and skills unnaturally. A job description should sound like a credible person explaining a real opportunity.

Remove stock language that could apply to almost any company. Claims about being innovative, world-class, fast-growing, or like a family mean little unless the description shows what makes the business and role different.

Keep the tone honest. Strong candidates do not need every challenge hidden from them. A clear description of the work, resources, authority, and constraints helps people decide whether they are suited to the role before either side invests more time.

Show what success looks like in the first months

Early expectations help candidates understand the pace and seriousness of the role. They also keep the company from changing the standard after the person starts.

You might explain that an Operations Manager is expected to understand the current process within 30 days, install a weekly operating review within 60 days, and show that the team is using the new rhythm by day 90. Those expectations should be realistic, but they should not be vague.

The same outcomes should later appear in the job scorecard and in the person’s early performance reviews. That creates a direct connection between the promise made in the job description, the evidence collected during hiring, and the results expected after the hire.

A weak opening and a stronger one

Weak: “We are seeking a dynamic Operations Manager with excellent communication skills who can thrive in a fast-paced environment and oversee daily operations.”

Stronger: “Our business has grown to the point where the owner can no longer coordinate every priority and handoff personally. We are hiring an Operations Manager to make the work more predictable, give the team clearer ownership, and reduce the recurring problems that slow customers and employees down.”

The stronger version does not rely on adjectives. It explains the situation, the work, and the result the company needs.

Review the job description before publishing

  • The title is clear, recognizable, and consistent with the actual level of the role.
  • The opening explains why the position exists and why the work matters.
  • The description names three to five outcomes instead of relying only on duties.
  • Essential responsibilities are connected to those outcomes.
  • Required qualifications are truly needed on the first day.
  • Preferred qualifications are clearly separated from requirements.
  • Working conditions and practical details are accurate.
  • The language is specific, readable, and free of unnecessary jargon.
  • The description gives qualified candidates enough information to decide whether the role fits them.
  • The same standard can be used later in screening, interviews, and the final decision.

Legal and fairness note: Employment requirements and advertising rules can vary by location and circumstance. Selection criteria should be job-related and applied consistently. The EEOC provides employer guidance on recruiting and hiring employees. This page is educational and is not legal advice.

What comes next

Begin with Define Success Before You Hire when the role itself is still unclear. Once the job description is written, use the Job Scorecard to turn the same outcomes into a consistent evaluation standard.

The next phase is to build a repeatable way to attract better candidates and connect the description to a wider recruiting strategy, rather than depending on one job-board posting to solve the entire search.

See how role definition and candidate attraction connect inside the Scientific Hiring Method.