How to Write a Role Brief That Gets You the Right Shortlist

A role brief that gets you the right shortlist does three things. It explains what the person will actually do, it says what good looks like after a few months, and it is honest about the practical constraints: experience level, language, working hours and start date. Everything else is detail.

The brief is not a job advert. It is a working document for whoever is finding candidates, whether that is your own team or a provider. The clearer it is, the less time you spend interviewing people who were never quite right.

1. Start with a Plain Role Title

Use the most common, recognisable name for the role, not an internal label. “Customer Support” or “Bookkeeping & Accounting” will be understood everywhere. “Customer Happiness Ninja” will not. If your role blends two functions, pick the main one and explain the rest in the description. The Services page lists the 38 standard role names Remoteli uses, which is a useful reference even if you hire elsewhere.

2. Describe What They Will Be Doing

This is the heart of the brief. Write three to six sentences about the work itself: what the person will own, what they will support, which tools they will use and who they will work with. Specific beats comprehensive.

Compare two versions. “Support the marketing team with various tasks” tells a recruiter almost nothing. “Schedule and publish our weekly social posts, build two email campaigns a month in our email platform, and pull a monthly performance report for the marketing lead” tells them exactly who to look for.

Then add what success looks like. If you can describe a good first 90 days, the people reading your brief can find someone capable of delivering it.

3. Say What You Are Looking For

List the skills and qualities that genuinely matter, and split them into two groups. Must-haves are the things you would turn someone down for lacking. Nice-to-haves are welcome but trainable. Long lists of must-haves shrink your shortlist without improving it.

• Specific tools or systems the person must already know
• Relevant experience, such as supporting B2B customers or working with a particular platform
• Communication needs, such as writing for customers or presenting to senior stakeholders
• Working style, such as comfort with ambiguity or preference for clear processes

Leave out anything that does not affect the work. Avoid wish lists copied from other job descriptions, and be wary of asking for years of experience with a specific tool when a capable person could learn it in a fortnight. If a requirement would not change your decision between two otherwise equal candidates, it probably belongs in the nice-to-have column.

4. Choose the Experience Level

Experience level shapes both who you meet and what you pay, so decide it deliberately. A useful frame is Junior (1–2 years), Mid (3–5 years) and Senior (5+ years), which is how Remoteli structures every role. The level you choose also changes the price, as how much it costs to hire remote talent in Africa explains.

Ask how much direction the person will get. Well-documented, process-led work with a supportive manager can suit a Junior professional. Work that needs independent judgement, or someone to set up a process from scratch, points towards Senior. Mid often fits the space in between.

5. Set the Working Language and Hours

State the language the person will work in every day, and whether that is with your team, your customers or both. If you need French or Arabic as well as English, say so up front, because it can change where you look.

Then be precise about hours. Do they need to overlap fully with a UK and Europe day, cover North American mornings, or work flexibly with a few fixed meetings? “Some overlap” is too vague to plan around. Our guide to time zones and working hours for remote teams can help you decide how much overlap the role really needs.

6. Add a Preferred Start Date

A start date helps everyone plan. It also forces a useful question: is your team ready to onboard someone on that date, with access, tasks and a named point of contact in place?

If the honest answer is no, pick a later date and use the time to prepare. A professional who starts a week later with everything ready will usually be productive sooner than one who starts on time and spends their first days waiting for logins.

A Role Brief Template You Can Reuse

A good brief pays off twice: once when you hire, and again when you onboard, because it already describes what the first months should look like. For where the brief fits in the wider process, see our practical guide to hiring remote talent internationally, and when your new professional is chosen, use our 30-day onboarding plan.