Most people hear "job requisition" and think of a form someone in HR fills in to get budget approval for a new role. That's not entirely wrong. But it undersells what a good requisition actually does.

A well written job requisition is the foundation every other part of the hiring process stands on. It defines what the role is, why you're hiring for it, what success looks like, and what you're willing to trade off. Get this right and everything downstream, the job description, the interview guide, the scorecard, the debrief, becomes easier. Get it wrong and you end up hiring the wrong person with a great process.

Here's what a job requisition is, what it should include, and how to write one that's actually useful.

What is a job requisition?

A job requisition is the internal document that formally opens a new role. It's the thing that exists before the job description, before the posting, before the first interview. It captures everything an internal team needs to agree on before starting a search.

Think of it as the hiring brief. The job description is the public-facing version you share with candidates. The requisition is the internal alignment document the hiring team works from.

In bigger companies, requisitions are tied to budget approval and require sign-off from finance or leadership. In smaller teams, they're often informal or skipped entirely. That's a mistake. Even a 20-person startup benefits from taking 45 minutes to write one before opening a role.

Why job requisitions matter more than they sound like they do

Three reasons.

It forces alignment before the search starts. The most common hiring failure isn't interviewing badly. It's starting a search with hiring managers, HR, and the founder all having slightly different ideas of what the role is. A requisition is where those differences surface and get resolved. If you can't agree on the requisition, you can't run the search.

It's the foundation for everything else. The competencies in the requisition become the competencies in your [interview guide]. The must-haves become the screening criteria. The success definition becomes what you evaluate against. Skip this document and every subsequent step becomes guesswork.

It prevents scope creep. When a requisition is written down, it's much harder for the role to quietly morph mid-search. Without one, it's easy to end up three weeks in realizing the hiring manager has been interviewing for a different job than HR has been sourcing for.

What should a job requisition include?

Role title and reporting line. What the role is called, who it reports to, and where it sits in the team. Be specific. "Marketing Manager reporting to the Head of Growth" is more useful than "someone for marketing."

Why the role exists. Is this a backfill, a new position, a specialization split from an existing role? The reason the role exists shapes the kind of candidate you want. Backfilling a departing senior hire is a different search from creating a new function from scratch.

What success looks like in the first 90 days. Two or three concrete outcomes you'd expect a great hire to deliver by the end of their first quarter. This is the single most useful section. Every subsequent decision, from screening to offer, should connect back to what you wrote here.

Core competencies required. Three to five competencies that are genuinely non-negotiable. Be specific. "Strong communicator" is vague. "Ability to give clear written updates to non-technical stakeholders" is useful. These become the backbone of your interview guide.

Must-haves vs nice-to-haves. Every role has requirements that are genuinely essential and ones that would be nice. Separate them explicitly. Candidates who tick 80% of your nice-to-haves can be exceptional hires. Candidates who miss a must-have can't.

Compensation range. What you're willing to pay for this role, including base, any variable component, and equity if relevant. Agreeing on this upfront prevents awkward mid-process conversations and lets you screen effectively from the start.

Time to fill target. A realistic timeline for when this role should be filled. Knowing the target helps you decide how much process is appropriate. A five-week target leaves no room for four rounds of interviews.

Hiring team. Who's involved in this search, who's interviewing, who's making the final call. Clear ownership prevents the "whose decision is this" problem later.

How to write a job requisition that's actually useful

Most bad requisitions share two problems: they're too vague, or they're a copy paste of a previous requisition without anyone rethinking it. Both lead to the same bad outcome, a search that loses momentum because the team was never really aligned.

Here's what to do instead.

Write it collaboratively with the hiring manager. HR shouldn't write the requisition alone. Sit with the hiring manager for 30 to 45 minutes and work through it together. The conversation is the value. The document is a record of what you agreed to.

Be specific about competencies. For every competency you list, ask "what would a weak example look like, and what would a strong one?" If you can't articulate that, the competency is too vague.

Cap the must-haves. If your requisition has eight must-haves, you're going to reject great candidates over trivial gaps. Limit yourself to three or four genuine must-haves. Everything else goes in nice-to-haves.

Connect it to the team's broader plan. Why are you hiring this role now versus six months from now? What does this hire unlock? If you can't answer, you're not ready to open the search.

Revisit after every hire. Look back at the requisition six months later. Did the person you hired match the competencies you wrote down? Did they deliver the 90-day outcomes? Update your requisition template based on what you learn.

Requisition vs job description: what's the difference?

The terms get used interchangeably, but they're different documents with different audiences.

The requisition is internal. It's honest, specific, and includes things candidates shouldn't see, like your compensation band, your timeline, and your priority list of must-haves versus nice-to-haves.

The job description is external. It's the candidate-facing version. It sells the role, the company, and the opportunity. It translates the requisition into language a candidate wants to read.

You write the requisition first. The job description is built from it. Trying to write the job description without first writing the requisition is how you end up with generic job ads that don't attract the right candidates.

The short version

A job requisition is the internal document that defines what you're hiring for and why. It forces alignment before the search starts, gives you the foundation for every subsequent hiring decision, and prevents scope creep mid-process.

It doesn't need to be long. Two pages is enough for most roles. But it does need to exist. Skip it and you're running a hiring process on vibes.

For a broader view of where the requisition fits, see [Hiring Process Stages: What Each Step Should Actually Include].