Write the Role, Not the Resume

Before you think about qualifications, answer one question with precision: what should success in this role look like at 90 days?

That is different from listing responsibilities. It asks what the hire will have actually produced, changed, or set in motion that tells you the decision is working.

In regulated industries this difference becomes obvious. Credentials may determine eligibility, but they do not tell you who can navigate complexity cleanly, remove bottlenecks, or make sound decisions in your environment.

Outcomes force the role definition back into reality. They move you away from generic proxies and toward the work the person needs to complete once they join.

Once the outcome is clear, work backwards into the capabilities required to reach it. This is different from listing static skills or career milestones.

Capabilities describe what someone can do, independently and repeatedly, inside your context. They also point toward the signals you need to test for during screening and interviews.

If the outcome is to build a scalable onboarding process across several markets, the capability is not simply project management experience. It is the ability to design systems under ambiguity, communicate across functions, and make decisions with incomplete information.

This shift also widens the candidate pool in useful ways. LinkedIn research has shown that removing rigid degree filters dramatically expands the available pool when the actual work can be performed without them.

A job description does two things at once: it filters people out and attracts the right people in. Most founders optimize only for the first half.

That produces a document full of must-haves and nice-to-haves that reads like a compliance checklist instead of an invitation to solve an important problem.

Strong candidates with options want to understand the environment, the scope of ownership, and why the work matters. They need to see the problem they would be stepping into, not just the gatekeeping criteria they must satisfy.

Leading with context helps the right people self-select in for the right reasons.

Pressure-test every description against three questions. Does it describe an outcome or just a profile? Are the requirements genuinely necessary, or simply inherited from the last version of the posting?

Ask the harder follow-up on each requirement. If you cannot explain why it is essential to the outcome, it is probably acting as a filter for familiarity rather than performance.

The Burning Glass Institute has shown how blunt degree requirements remove a large share of otherwise capable workers from the pool. That matters if your goal is better signal, not narrower convention.

The final question is whether the right candidate has a reason to apply. If the answer is no, the description still is not written for the person you actually want.