How to Write a Toptal Brief That Gets You the Right Match the First Time
Toptal puts forward up to three candidates per role, so your brief decides who they are. What belongs in it, what to leave out, and how to use the trial.
Short answer: Toptal's model is matching, not browsing — its FAQ says you get up to three candidates per role, usually starting within 24 hours. That makes your brief the single highest-leverage thing you write in the whole process, because it is what the shortlist is built from. A brief that states one clear outcome, three or four real must-haves and how you will judge the work is worth more than a page of requirements.
Most of what search returns for this question is generic "how to write a job description" advice, or a review page published by a staffing firm that competes with Toptal. Neither tells you the thing that actually matters here: on an open marketplace you correct a bad brief by reading more proposals, and on Toptal you cannot. The shortlist is short by design.
I am a screened member of Toptal's network and there is a referral link further down, disclosed at the top. The advice below applies whether or not you use it.
Why the brief carries more weight here
On an open marketplace, a vague job post produces a flood of proposals and you filter it yourself. That is expensive in your time, but it is self-correcting — you see the range of people who responded and adjust. We worked through that trade in Toptal vs Upwork.
A matched service inverts it. Toptal reads the brief, searches its own network, and puts forward a handful of people. Per Toptal's FAQ that is up to three candidates per role, with the first candidates usually within 24 hours. Three well-chosen candidates is a fast, cheap way to hire. Three candidates chosen from a fuzzy description is a week lost, because you will spend it interviewing people who were never going to fit and you will not know why.
So the brief is not paperwork. It is the search query.
What actually belongs in the brief
| Section | What to write | Why it changes the match |
|---|---|---|
| The outcome | One sentence: what must exist in 30 days that does not exist now. | Sorts people by what they have shipped, not by keywords on a profile. |
| Must-haves | Three or four. Each one a thing the person will do in week one. | Every extra must-have removes real candidates; four is a search, twelve is a wish. |
| Nice-to-haves | Everything else, explicitly labelled. | Lets a strong candidate through who is missing one thing you can live without. |
| Stack and constraints | Language, framework, cloud, anything you cannot change. | Cheap to state, expensive to discover in week two. |
| Hours and duration | Hours per week and expected length, honestly. | Part-time and full-time availability are different pools of people. |
| Timezone overlap | The hours you need live, not the country. | "US-based" narrows the pool; "four hours overlap with US Eastern" often gets you the same thing and more candidates. |
| How you will judge it | The first deliverable and what "good" looks like. | Gives the trial a pass/fail line, and tells candidates whether they want the job. |
| Budget | A range you would actually approve. | Toptal does not publish rates, so the quote is built for your role — a range prevents three interviews that end at the number. |
That is one page. If yours runs to three, you are describing a person rather than a job.
A worked example
Here is a brief of the kind that produces a polite, unusable shortlist:
We need an experienced senior full-stack developer, rockstar level, strong in React, Node, Python, AWS, Kubernetes, GraphQL and machine learning, with excellent communication skills and startup experience. Must be a self-starter. Long-term potential.
Everything in it is true of the role and none of it is a filter. Seven technologies are listed as though equally load-bearing; there is no outcome, no timeframe, no budget and no way to fail. A matcher reading this can only guess which of the seven matters, and the guess is what arrives in your inbox.
The same role, written as a brief:
Outcome (30 days): our checkout flow moves off the legacy PHP service onto our existing Next.js app, with no drop in conversion.
Must-haves: production Next.js and TypeScript; has migrated a payment or checkout flow before; can read PHP well enough to port logic from it; works independently against a spec.
Nice to have: Stripe Billing, experience with feature-flagged rollouts.
Constraints: Vercel, Postgres, our design system. No rewrite of the design.
Hours: 30–40 per week for roughly 10 weeks, with at least four hours overlapping 9–5 US Eastern for standups.
First deliverable (end of week 2): the cart page served from the new app behind a feature flag, with tests, deployed to staging.
Budget: we have approved a range for a senior contractor at this level and will share it on the first call.
Same role, same seniority. The second version can be searched against. It also does something the first cannot: it tells a strong candidate whether the work is interesting, which matters when the person on the other side has a choice of clients.
Notice that the second brief is not longer. It is shorter than the first if you cut the adjectives.
The three mistakes that cost the most
Requirement inflation. Listing every technology in your stack as a must-have is the most common and most expensive error. Each genuine must-have is a constraint on a finite network; four hard constraints describe a specialist, eight describe nobody. Ask of each line: will they do this in the first two weeks? If not, it is a nice-to-have.
Hiding the budget. Toptal does not publish hourly rates — the number comes from a quote for your specific role — so withholding your range does not extract a better price, it just moves the conversation later. Say the range on the brief or the first call. If you are not sure what senior work should cost you, we broke down the confirmed fees and the break-even math in our Toptal pricing guide.
Describing a person instead of an outcome. "Rockstar", "self-starter" and "startup mentality" are not searchable, and everyone claims them. Outcomes are searchable, because people have either delivered that kind of thing or they have not.
What happens after you submit, and what it costs
Toptal publishes the shape of the process, so plan against these rather than against a blog's estimate:
- First candidates usually within 24 hours, and up to three candidates per role.
- A $79 subscription when you proceed with talent matching.
- A trial of up to two weeks, which you are not billed for if you are not satisfied.
- Invoices twice a month, on Net 10 terms.
The number that should change your behaviour is the trial. Two weeks not billed if it does not work out is only worth something if you set up the two weeks as a test. Most clients waste it: they use it as onboarding, discover nothing, and convert by default. Give it the first deliverable from your brief, with a date, and you have real evidence instead of an impression. If you are not technical yourself, the questions worth asking during that fortnight are in how to vet a developer when you cannot read code.
One more small thing that pays for itself: when you turn down a candidate, say which requirement they missed. "Strong, but has not done a payments migration" is a sharper input to the next search than "not quite the right fit."
When Toptal is the wrong choice
An honest brief-writing guide has to include the case where you should not submit one at all.
- The task is small and easy to check. A landing page, a scripted data export, a bug with obvious symptoms. Screening you do not need is the main thing you are paying for, and at that size it is not worth it.
- You cannot describe the outcome yet. If the work is genuinely exploratory and you do not know what done looks like, no brief will match well — and the trial cannot tell you anything, because there is nothing to pass or fail. Spend a week scoping with someone you already trust first.
- You need a whole team and a manager. A matched individual contractor is not an agency. If nobody on your side will own priorities and review work, that gap does not close by hiring a better engineer.
- Rate is your binding constraint. Toptal's floor is higher than an open marketplace's, and no brief changes that. If the budget is tight and the deadline can move, marketplace hiring is cheaper.
- You want to browse before committing. Toptal shows you matches, not a searchable directory. Some people simply want to look first, and that is a legitimate preference — is Toptal legit? covers what you can and cannot verify up front.
"Top 3%" is Toptal's own, self-reported claim about its network, not an audited figure. Treat it as positioning, and let the trial produce your evidence.
If you are going ahead
New clients who sign up and hire through a referral link receive $2,000, and the referrer receives $2,000 as well. The link below is mine, as the disclosure at the top of this post says.
The short version
- Toptal sends up to three candidates per role, usually starting within 24 hours — so the brief is the search, not paperwork.
- One outcome, three or four must-haves, everything else labelled nice-to-have. One page.
- State the hours, the timezone overlap you actually need, and a budget range.
- Write the first deliverable into the brief, then use the up-to-two-week trial to test it rather than to onboard.
- Reject candidates with a reason — it is the only way the next three are better than the first three.
- If you cannot describe the outcome, or the task is small and checkable, do not submit a brief yet.
