How to write a role profile that gets you the right person

Most hiring problems begin before a job is posted.

The owner feels overloaded, collects every task they dislike, and turns the list into one impossible role. The result is usually a search for a bookkeeper who also manages projects, edits video, answers customers, and somehow knows the company’s CRM on day one.

A better role profile starts with one business gap. It tells a candidate what they will own, what good work looks like, and where judgment matters.

Name the gap in one sentence

Before listing tasks, finish this sentence:

We need this person because…

If the answer contains three unrelated problems, you probably have more than one role.

For example: “We need this person because customer requests are sitting in the owner’s inbox and follow-ups are being missed.” That points toward an operations or customer support role. It does not point toward a general virtual assistant who is expected to do anything that comes up.

Write outcomes before responsibilities

Responsibilities describe activity. Outcomes describe the change you are paying for.

Compare these two lines:

• Manage the CRM.
• Every qualified lead has an owner, a next step, and a current status by Friday afternoon.

The first line can mean almost anything. The second tells the candidate where the work ends and gives the manager something concrete to inspect.

Choose three to five outcomes that would make the hire clearly worthwhile after 90 days. More than that usually means the role is too broad.

Describe the actual week

Candidates need to know what the job feels like, not only what the company hopes to achieve.

• Which meetings will they attend?
• Which systems will they use every day?
• What work repeats weekly or monthly?
• Which decisions can they make alone?
• What needs approval?
• Who gives feedback, and how often?

This section helps a good candidate decide whether they can thrive in your environment. It also exposes gaps in your own management plan before they become onboarding problems.

Separate required judgment from teachable tools

Hiring managers often screen too hard for software and too lightly for judgment.

A capable operations professional can learn a new task manager. A careful bookkeeper can learn your expense platform. It is harder to teach someone to notice that a number does not make sense, follow an unclear request to its source, or tell you early that a deadline is at risk.

Mark each requirement as one of three things:

• Required on day one: core knowledge or judgment the role cannot function without.
• Preferred: useful experience that shortens onboarding.
• Teachable: a tool or company-specific process a strong candidate can learn.

Ask for evidence in the interview

Once the role profile names real outcomes, your interview questions get better.

Instead of asking, “Are you organized?” ask the candidate to walk through how they handled a week with competing deadlines. Ask what they tracked, what they communicated, what slipped, and what they changed afterward.

For a finance role, give them a short list of transactions with missing context and ask how they would resolve them. For an operations role, show them an inbox with five requests and ask what they would handle first.

The point is not to catch someone out. You want to see how they think when the work is imperfect, because real work always is.

A role profile is also a management agreement

The profile should remain useful after the offer is signed. Bring it into the first-week conversation. Review the outcomes, decision boundaries, communication rhythm, and 90-day priorities together.

If the document only helps you attract candidates, it is a job ad. If it also helps the person understand and own the work, it is a role profile.