What to put in a role brief before you open a remote seat for an experienced hire

The money is approved and the seat has been open for four months. The local market has no one at the level you need, or no one at that level who is looking. So you are going remote.

Before you post anything, write a role brief. A role brief is the one document that decides whether you hire the right experienced person or spend two quarters managing a mismatch. It covers scope, outcomes, decision rights, time zone, the pay range, and how the person will be managed at a distance.

Get it right and the search gets faster and more focused. Skip it and you will interview well-dressed generalists for six weeks and still not know who to pick.

This guide walks through what belongs in that role brief, in the order you should write it. It is written for founders, hiring managers, and operators at growing companies in the US, UK, Australia and beyond. They are hiring outside their local market because they have to, not because it is fashionable.

Start the role brief with the constraint, not the job title

Many briefs open with a title. That is the wrong first line. Open with the constraint.

What is actually stopping you? It is often one of three things:

• Availability. The few people near you who have done this work are not looking.
• Location. The people who have done this exact job at this exact scale live somewhere else.
• Timing. You need someone in the seat in weeks, not after a nine-month search.

Name the constraint in one sentence at the top of the brief. It keeps everyone honest later, when someone suggests lowering the bar or stretching the pay range. It also tells a recruiter what trade-offs are acceptable and which are not.

Example: We need a Head of Finance who has closed a Series B and run a 40-person company’s reporting stack. Nobody in our city has done this at our scale. We will hire remotely in a compatible time zone and pay at the 60th percentile of the remote market.

That single paragraph does more work than a page of responsibilities.

Define the outcome the role brief is buying

An experienced remote hire is not a set of tasks. It is an outcome you are buying. Write the outcome as a result, with a time frame.

Weak: Own the finance function.

Strong: Close the monthly books by day 8 and produce a board-ready pack by day 12. Complete the Series B data room within two quarters.

A good outcome statement has three parts:

1. The result. What is different in the business when this works?
2. The horizon. Ninety days, two quarters, a year.
3. The measure. How will you both know it happened?

If you cannot write the outcome, you are not ready to open the seat. You are ready to write a project plan first.

Separate the outcomes from the activities

Under the outcome, list the activities you expect. Keep them short and honest.

Experienced people read activity lists as a signal of how much you will micromanage. If the list runs to fifteen bullets, cut it to five and move the rest into a “first 90 days” section.

Write the first 90 days explicitly

Problems with a remote hire often show up in the first month. Write down what week one, week four, and week twelve look like.

Who do they meet? What do they ship? What decision do they own by day 30?

This section is also where you catch a bad brief. If you cannot describe week one, the role is not defined well enough to hire for.

Set decision rights inside the role brief

Many briefs skip this section, and leaving it out does real damage. An experienced hire who cannot decide anything cannot use their experience. An experienced hire who decides everything you did not intend to hand over is a problem.

Write down, in plain terms:

• What they decide alone. No approval needed.
• What they decide and tell you. They move, then inform.
• What they recommend and you decide. They bring options, you choose.
• What you decide. Out of scope for them.

Four lines. That is it.

But those four lines guard against two common remote failures. One is a hire who waits for permission on everything. The other is a hire who changes your pricing model in week three without telling you.

If you are hiring through a managed model, this section is also what your account owner uses to keep the engagement on track. It is the difference between a hire who waits to be told and one who runs their lane.

Be specific about time zone, overlap, and communication

Remote does not mean asynchronous by default. Say what you need.

• Core overlap hours. How many hours a day must they be reachable in your time zone? Two, four, or full?
• Meeting rhythm. Which standing meetings are mandatory, and which are optional.
• Response expectations. What is the expected response time during overlap hours?
• Tools. Where does work live? Slack, Linear, Notion, email, a shared doc?
• Escalation. Who do they go to when something is on fire, and how?

Be realistic. Say you write “must be available 9 to 5 US Eastern” for a role you are hiring in the Philippines. You have just shrunk your candidate pool and added a night shift to someone’s life.

If you actually need four hours of overlap, say four hours.

Experienced people read this section carefully. It tells them whether the job is livable.

Put the money and the terms in the role brief

Do not hide the pay range. An experienced candidate will ask in the first call, and if you dodge, they assume the number is low. Write the range, the structure, and the terms.

• Base range. A real range, not “competitive.”
• Variable. Bonus, commission, or none. If none, say none.
• Employment model. Are you hiring onto your own payroll, or engaging through a staffing partner?
• Equipment and setup. Who pays for the laptop, the chair, the internet?
• Leave and holidays. Which country’s public holidays apply?
• Contract length or notice. What is the commitment on both sides?

The employment model matters more than most briefs admit. If you hire onto your own payroll in another country, you are dealing with local employment law, benefits, and tax. If you engage through a partner, the partner engages and pays the person instead.

Both are valid. They are just different, and the brief should say which one you have chosen and why.

If you are not sure yet, that is a signal to decide before you post, not during the offer stage.

Write the must-haves and the nice-to-haves separately

Briefs for experienced hires fail when everything is a must-have. You end up with a unicorn spec and no shortlist.

Split the requirements into three buckets:

• Must-have. Without this, the person cannot do the job on day one. Keep this to three or four items.
• Strong signal. Evidence they will be good, but you would flex for the right person.
• Nice-to-have. Genuinely optional. Cut this list if it grows.

For each must-have, write how you will test it. If you cannot describe a test, it is not a must-have. It is a preference.

Example must-have: Has run a monthly close process at a company with more than $10M in revenue. Test: Walk me through your last close. What broke, and what did you change?

That is a real requirement. “Strategic thinker” is not.

Name the person the role reports to, and who owns the hire

An experienced remote hire needs one clear manager. Not a committee. Not “the founders.”

One person who owns the relationship, sets priorities, and gives feedback.

Write down:

• Who they report to. Name the person.
• Who else they work with. Key peers and stakeholders.
• Who owns the hiring process. One name, one inbox.
• Who signs off on the offer. Usually the same person, but say it.

If the role reports to a founder who is also closing a funding round and traveling for six weeks, say so. Then say who covers in the meantime.

Experienced remote hires who cannot get time with their manager often leave. That is a good hire lost to a problem the brief could have prevented.

Decide how you will manage the engagement, not just the hire

Hiring is the start, not the finish. The brief should say how the working relationship will be run after day one.

A few things worth writing down:

• Check-in cadence. Weekly one-to-one, biweekly, monthly?
• Review points. Day 7, day 30, day 60, day 90. What is reviewed at each?
• Feedback loop. How does the person raise a problem before it becomes a resignation?
• Replacement terms. What happens if it does not work out?

If you are working with a staffing partner, this is where their process shows up. Ours starts with a qualified shortlist in five business days and a live identity interview on every profile.

With Embed, we recruit the professional, engage them as a contractor, and pay them. You also get a named account owner, check-ins at day 7, 30, 60, and 90, then a monthly report. Those belong in the brief because they shape what you are buying.

If you would rather hire onto your own payroll, the brief should say that too. With Search, we find and verify the person, and you hire and manage them. One replacement search within 90 days is included, and the review points after the start are yours to run.

Match the brief to the way you want to work

Not every remote seat needs the same structure. The brief should reflect which of these you are actually buying:

• One experienced person, embedded. You want a single experienced hire who works inside your team, on your tools, with your priorities. This is the classic remote seat.
• A small team with a lead. You need three or more people and one accountable lead. The brief needs a team-level outcome, not just an individual one. Pods is built for that shape.
• A function you hand over. You want us to own a queue, a pipeline, or a whole function and its outcome. You stay out of the day-to-day. Run is the model for that, and every Run starts as a Pod so both sides have a real baseline.

Write the brief for the shape you have chosen. A brief for one embedded hire does not work for a pod, and a pod brief does not work for one hire.

Common mistakes in a remote role brief

A short list of things that cost time and money:

• Writing the brief after the shortlist. If you write it after you see candidates, you will reverse-engineer it around the person you like. That is how bad hires happen.
• Hiding the pay range. Experienced candidates drop out. You waste two weeks.
• Listing fifteen responsibilities. It signals micromanagement and scares off the people you want.
• Skipping decision rights. You get a hire who either waits for permission or oversteps.
• Ignoring time zone reality. You write a spec no one in the target market can live with.
• No named manager. The hire has no one to go to.
• No review points. Problems surface at month six instead of week two.
• Writing the terms for a lesser hire. You are hiring an experienced professional. Write the terms you would offer one.

Each of these is fixable in an afternoon of writing. None of them is fixable after the offer is signed.

A one-page template you can use

If you want a starting point, this is the structure that works:

1. The constraint. One sentence. Why this seat is remote.
2. The outcome. Result, horizon, measure.
3. First 90 days. Week one, week four, week twelve.
4. Decision rights. Four lines: decide alone, decide and tell, recommend, you decide.
5. Time zone and communication. Overlap hours, meeting rhythm, tools, escalation.
6. Money and terms. Base, variable, model, equipment, leave, notice.
7. Must-haves. Three or four, each with a test.
8. Strong signals and nice-to-haves. Kept short.
9. Reporting line and hiring owner. Named people.
10. Engagement plan. Check-ins, review points, replacement terms.

One page. If it runs to three, you are writing a job description, not a brief.

The brief is for you and your hiring partner. The job description is for candidates, and it comes after.

What a good role brief changes about the search

When the brief is tight, three things happen.

First, the shortlist is faster. A recruiter with a clear brief can screen against real criteria instead of guessing. That is how you get a qualified shortlist in five business days.

Second, the interviews are better. You are testing must-haves with real questions, not trading impressions. A live identity interview on every profile means you are not wasting time on candidates who are not who they say they are.

Third, the offer is easier. You already wrote the range, the model, and the terms. There is nothing to negotiate from scratch at the worst possible moment.

None of this is clever. It is just written down. That is the whole point of a role brief.

If you want a second pair of eyes on the brief before you open the seat, that is a normal thing to ask for. It takes less time than fixing a bad hire.

You can read more on how we approach this in our Insights. If you are a professional looking at remote roles, see For professionals.

Write the brief, then open the seat

The order matters. A role brief written before you post saves you weeks of interviews and months of managing a mismatch.

It forces you to name the constraint, define the outcome, and set decision rights. It makes you be honest about time zone and money, and decide how the engagement will actually run.

A clear brief gives the search something to aim at. A vague one leaves everyone guessing.

If a seat needs an experienced person you cannot find locally, and you want a qualified shortlist in five business days, book a call. Bring the constraint. We will help you write the role brief before you open the seat.

Frequently asked questions

How long should a role brief be?

One page. If it runs longer, you are writing a job description, not a brief.

The brief is an internal document that covers the constraint, the outcome, decision rights, time zone, money, must-haves, reporting line, and engagement plan. The job description for candidates comes after, and it can be longer.

Should I include the salary range in the role brief?

Yes. Experienced candidates ask in the first call, and hiding the range wastes everyone’s time.

Write the base range, any variable pay, the employment model, equipment terms, leave, and notice. If you do not know the range yet, decide before you post, not during the offer stage.

What are decision rights, and why do they matter in a role brief?

Decision rights are four lines. They say what the hire decides alone, what they decide and tell you, what they recommend and you decide, and what you decide. They guard against two common remote failures: a hire who waits for permission, and one who changes something important without telling you.

How much time zone overlap does an experienced remote hire need?

As much as the role actually requires, and no more. Many of these roles work with two to four hours of daily overlap.

Writing “must be available 9 to 5 US Eastern” for a role hired in a distant time zone cuts your candidate pool. It also adds a night shift to someone’s life. State the real requirement.

What happens if an experienced remote hire does not work out?

That should be written into the role brief before you open the seat. Agree on review points at day 7, 30, 60, and 90, a clear feedback loop, and replacement terms.

If you work with us, the replacement terms depend on the service. With Embed, Pods and Run, we replace a professional who does not work out. With Search, one replacement search within 90 days is included.