Playbook · 7 min read

How to write a hiring brief that gets you the right shortlist

The four questions that turn a vague role into a two-week shortlist — plus a copy-ready brief template and the details most teams forget to mention.

By the Strait team · Jun 2026 · 7 min read

Key takeaways

Great shortlists start with great briefs — lead with the outcome, not a tech list.
Answer four questions: what they own, what hours overlap, what 90-day success looks like, who they work with.
Specifics shrink the candidate pool to the right people and speed everything up.
A clear brief can be signed off same-day and turned into a shortlist in about two weeks.

A good shortlist starts with a good brief. The fastest hires we make come from clients who answer four questions clearly up front. The slowest come from send us a senior developer. Here is the difference, and a template you can copy.

1. What does this person own?

Not a list of technologies — an outcome. Owns our checkout flow and its conversion tells us far more than React, Node, 5 years. Skills follow from the outcome; lead with the outcome and the right candidates recognise themselves in it.

2. What hours must overlap?

Full overlap with CET? Four shared hours? Async with a daily sync? This single answer shapes the entire candidate pool, so it's worth being specific rather than defaulting to whenever. It also sets expectations honestly on both sides.

3. What does great look like in 90 days?

A concrete first-quarter goal helps us screen for people who have done that exact thing before — and gives your new hire a target from day one. Cut first-response time to under an hour is a brief; be good at support is not.

4. Who do they work with?

Solo, or inside a team? Reporting to a lead, or to you? Culture fit is real, and it is far easier to match when we know the room someone is walking into.

Lead with the outcome the person owns. The skills follow from it.

A copy-ready brief template

1Role outcome: the one thing this person is accountable for
2Must-haves: 3–5 non-negotiable skills or experiences
3Nice-to-haves: things that help but won't break the deal
4Hours & overlap: the working pattern you need
590-day goal: what success looks like by the end of the first quarter
6Team & reporting: who they work with and who they report to

Answer those and a Strait consultant can usually turn it into a written brief you sign off the same day — and a first shortlist inside two weeks.

Frequently asked questions

What should a hiring brief include?

A strong brief states the outcome the person owns, the required timezone overlap, a concrete 90-day success goal, and who they'll work with — plus must-have versus nice-to-have skills. Lead with the outcome; the skills follow from it.

How long should it take to get a shortlist?

With a clear brief, Strait typically returns a first shortlist of two or three vetted finalists in around two weeks. Vague briefs are the single biggest cause of delay.

What's the most common mistake in a job brief?

Listing technologies instead of outcomes. 'React, Node, 5 years' tells a recruiter far less than 'owns our checkout flow and its conversion rate.' Describe the job to be done first.

Hiring for a role like this?

Start a brief and a consultant takes it from there — first shortlist in about two weeks.

More from the notebook

Talent · 9 min read

Why Strait sources and vets remote talent in Egypt

A young, deep STEM talent pool one hour ahead of Amsterdam, strong English, and costs a fraction of a local hire — here's the full case for why Egypt sits at the centre of how Strait finds and tests every remote professional.

Jun 2026Read

Hiring · 8 min read

The real cost of a local hire vs. a managed remote hire

Salary is the smallest part of the gap. Here's a full breakdown of what a Benelux hire actually costs each month versus a fully-managed remote one — and how to compare them honestly.

Jun 2026Read

Remote · 6 min read

Working across the Cairo–Amsterdam hour

One hour of timezone difference changes everything about remote work. Here's how overlapping working hours make a distributed team feel local — and what to keep async anyway.

May 2026Read