How Do You Write Your First Job Description When You’ve Never Hired Before?

Start With the Work, Not a Wish List

The instinct is to open with a job title and a bullet list of skills. Resist it. Before you write a single line of the post, write the mandate: on one page, list the five to seven things this person will actually be accountable for in their first year. Not tasks, outcomes. “Own our customer onboarding so new accounts reach first value in under a week” tells you far more than “strong organisational skills.”

This step does two things at once. It forces you to admit what the role really is, which is often narrower or broader than the tidy title you had in mind. And it tells you the seniority to hire for: if the outcomes need someone to build a function from scratch, that is not a junior job, however tight your budget is. Founders routinely write a mid-level job description, pay a mid-level salary, and then expect a leader. The mandate is where you catch that mismatch before it costs you a hire. If you are still working out whether this role should exist at all yet, our guide to when to stop hiring on instinct and start structuring it is the better place to begin.

What Actually Belongs in a First Job Description

Once the mandate exists, the post almost writes itself, because you are describing something real rather than inventing something impressive. A first job description does not need to be long. It needs to answer, honestly, the questions a good candidate is actually asking.

Notice what is not on the list: a decade of buzzwords, a culture manifesto, or a demand for ten years of experience with a tool that has existed for three. A first hire is reading for signal that the job is real and the founder knows what they want. Every honest, specific line builds that signal. Every generic one erodes it.

You Have About Fourteen Seconds

Here is the part that changes how you write. According to LinkedIn Talent Solutions, most candidates spend only 14 seconds deciding whether to keep reading your job post or move on. Fourteen seconds. That is enough time to scan a title, the first paragraph, and maybe the top of a list. Everything you buried below, the salary, the real scope, the one detail that would make the right person lean in, might as well not be there.

So write for the scan. Lead with what the role owns and why it matters, in plain language. Put the salary range where a person can find it in one glance, not at the bottom behind a wall of requirements. Use short paragraphs and a tight list rather than a dense block. You are not dumbing anything down; you are respecting that a strong candidate is reading five other posts today and will give yours a fraction of a minute before deciding.

The Mistakes That Cost First-Time Founders

Almost every weak first job description fails in one of a few predictable ways. None of them are about writing talent. They are about clarity, and they are easy to fix once you can name them.

• The kitchen-sink role. You need help everywhere, so you list everything. But a job that is sales, plus support, plus operations, plus a bit of marketing reads as a company that has not decided what it needs. Scope to the one thing that matters most now.
• The borrowed template. Copying a big company’s job description imports their assumptions: their layers, their process, their scale. It describes a job that does not exist in a team of eight, and it attracts people expecting one that does.
• The hidden salary. Leaving out the range does not create negotiating room. It filters out the candidates who value their time and keeps the ones who will discover the mismatch three interviews in, after you have both spent hours.
• The wall of requirements. Fifteen “must-haves” feels thorough. In practice it deters the capable, slightly-humble people you want and barely slows the ones who apply to everything anyway.

If you want the wider version of this, we pulled apart the most expensive hiring mistakes founders make without an HR background in more depth. The job description is simply the first place most of them show up.

Describe What Success Looks Like

The strongest thing you can add to a first job description is the one thing most founders leave out: what a good first 90 days looks like. A short line such as “by month three, you will have taken our onboarding off my plate entirely and cut the time to first value in half” does more work than a paragraph of adjectives. It tells a candidate the job is real, that you have thought about it, and exactly what they are being hired to change.

It also protects you. Writing down what success means forces you to be honest about whether the role is achievable and whether you can judge it fairly later. A candidate who reads that line and gets excited is telling you something useful. A candidate who reads it and goes quiet is saving you a mis-hire. Either way, you learn more from one concrete outcome than from ten rounds of “are you a good culture fit.”

From a Blank Page to a Live Post

None of this needs to take a week. The hard part is the thinking, the mandate, the honest scope, the one outcome that defines success. Once you have that, turning it into a clean, scannable post is mechanical. The mistake is doing it in the wrong order: reaching for a polished template first and trying to reverse-engineer the role to fit it.

This is one place a tool earns its keep for a founder with no HR support. Kynto turns a few honest lines about the role into a structured, scannable job description in one step, so you start from a real draft instead of a blank page, and keep editing until it sounds like you. It is the same idea that runs through the rest of the hiring process: less time on the admin, more on the judgement only you can make. For the bigger picture of what a first hire really takes, our timeline for a founder’s first recruitment walks through the weeks around this step.

Key Takeaways

• Write the mandate before the post: five to seven outcomes this person will own in year one. It defines the role and reveals the seniority you actually need to hire.
• Candidates give a job post about 14 seconds. Lead with what the role owns, publish the salary range, and keep it scannable, or the best part goes unread.
• Specificity is the whole game. A vague description attracts a vague pile of applicants; describing the real work and a clear first 90 days does the filtering for you.

FAQ

How long should my first job description be?

Shorter than you think. A clear company paragraph, a one-sentence role, five to seven responsibilities, a short must-have list, and a salary range is plenty. If it runs past a screen or two, you are probably padding it with requirements you do not really need, which costs you good applicants rather than protecting you.

Should I really put the salary in the post?

Yes. Publishing the range attracts people the role can actually afford and quietly removes the ones it cannot, before either of you spends hours in interviews. It also reads as confidence and fairness, which matters more to a first hire joining a small team than a polished pitch does.

What if I am not sure exactly what the role is yet?

Then the job description is doing its most valuable work, by exposing that. Do not paper over it with a broad, everything role. Write the mandate first and force yourself to name the one outcome that matters most in the next six months. If you genuinely cannot, that is a signal to wait or to reshape the role, not to post it vague and hope the right person figures it out.