How to Write a Job Post That Attracts Good Freelancers

Every buyer who has posted freelance work has had the same experience. The post goes live, forty proposals arrive within the hour, and thirty-five of them are the same paragraph with a different name at the top. You read six, lose the will, and end up hiring whoever happened to sound least generic.

That outcome is not bad luck, and it is rarely the freelancers’ fault. A job post is a filter, and a loose filter lets everything through. If your post could describe fifty different jobs, fifty different people will apply for it — and the ones best placed to do your job have no way of knowing that from what you wrote. This guide covers what to put in the post so that it filters properly. It pairs closely with our guide on writing a project brief, which goes deeper into the document you hand over once someone is hired.

Why most job posts attract the wrong people

A job post has one job: to make the right person feel it was written for them, and the wrong person move on. Most posts fail at both ends. They are too short to be recognisable and too generic to be self-selecting, so they read as an open invitation to anyone with a keyboard.

Three patterns cause almost all of it. The first is describing a role rather than a piece of work — “looking for a web designer” tells a designer nothing about whether they are a fit. The second is hiding the budget, which guarantees you will spend the first three messages of every conversation establishing whether you are even in the same universe. The third is asking for everything: a post that lists twelve skills reads as either an unrealistic brief or a badly defined one, and experienced freelancers treat both as a warning sign.

The fix is not length. Long posts are not better posts — a wall of text gets skimmed exactly like a short one. What matters is that a reader can answer four questions in the first thirty seconds: what is the job, is it in my skill set, is the budget realistic, and does this buyer seem organised. Everything below is about answering those four quickly.

Write a title that names the job, not the dream

The title is the only part of your post that most freelancers will ever see. On a listing page it competes with dozens of others, and it is doing the entire job of filtering before anyone clicks through.

Name the deliverable and the context in plain words. “Five-page WordPress site for a small accountancy practice” beats “Website needed” comprehensively, because it tells a WordPress specialist they are qualified and tells a mobile app developer to keep scrolling. “Rewrite eight product pages for a UK skincare brand” beats “Copywriter wanted” for exactly the same reason.

• Weak titleNeed a logo designer — could mean anything from a quick word mark to a full identity system.
• Strong titleLogo plus one-page brand sheet for a new coffee roastery — scope, sector and deliverable are all visible before the click.
• Weak titleLooking for SEO help — attracts everyone from link sellers to full-service consultants.
• Strong titleTechnical SEO audit for a 300-page WooCommerce store — a specialist recognises this instantly as their kind of work.

If you are browsing before you post, the category names themselves are a good source of accurate vocabulary. Opening the website development freelancers listing or the logo design services category shows you how practitioners describe their own work, which is usually more precise than the words a buyer reaches for first.

Lead with the outcome, not a task list

Open the body of the post with the result you want, in one or two sentences, before any list of tasks. “We want the booking form to stop losing enquiries on mobile” is a better opening than “fix form, test on iPhone, check spam filter” — and it produces better proposals, because a good freelancer will often tell you the cause is something you had not listed.

This matters more than it sounds. A task list invites quoting; an outcome invites thinking. When you lead with the outcome you find out very quickly who has actually diagnosed a problem like yours before, because they respond to the outcome rather than repeating your bullets back at you. That is one of the most reliable quality signals available at proposal stage, and it costs you nothing to create.

Follow the outcome with context: what exists today, who it is for, and what happens after delivery. Two lines is enough. “It is a WooCommerce store on a custom theme, roughly 300 products, and we handle our own content after launch” saves four rounds of questions from every serious applicant.

Define scope tightly enough to be quoted

Scope is where budgets die. If a freelancer cannot tell how big the job is, they will do one of three things: quote high to cover the unknown, quote low to win and renegotiate later, or not quote at all. All three are bad for you, and the third quietly removes your most experienced applicants.

You do not need a technical specification. You need countable things. How many pages, products, articles, minutes of video, revision rounds. Who supplies the copy and the images. What is explicitly not included. Six short lines of scope are worth more than four paragraphs of description.

• Count itPages, products, articles, screens, minutes, languages — anything that multiplies the work.
• Assign itSay who writes the copy, who supplies photography, and who owns hosting and domains.
• Bound itState how many revision rounds are included. Open-ended revisions are the most common cause of a job going sour.
• Exclude itName what is out of scope. “No content migration” or “no ongoing maintenance” prevents an argument later.

If you genuinely cannot define the scope yet, say so and change what you are buying. A short paid discovery piece — an audit, a sitemap, a scoping call written up as a document — is a perfectly normal freelance engagement, and it is far cheaper than a large project scoped by guesswork.

Put a real budget range in the post

Withholding the budget feels like negotiating leverage. In practice it costs you the applicants you most want. Established freelancers have more work than time; they filter on budget first and will skip a post that hides it rather than spend twenty minutes writing into a vacuum.

Give a range rather than a single number, and make the top of the range honest. A range tells applicants which class of solution to propose — a template build or a custom one, a quick pass or a thorough one — and it lets a good freelancer tell you, before anyone has wasted time, that your scope and your budget do not match. That is useful information, not a rejection.

If you have no idea what a job should cost, research before you post rather than fishing in the post itself. Our guides on what a website costs, freelance SEO pricing and logo design pricing set out typical market ranges. Costs vary by scope, complexity and experience, and on a marketplace every freelancer sets their own price — so treat published ranges as a sanity check, never as a tariff.

Be honest about the timeline

Two dates belong in the post: when you want to start, and when the work needs to be finished. If there is a hard external deadline — a trade show, a product launch, a funding round — say what it is. A real reason is far more persuasive than “ASAP”, which most freelancers read as either panic or no deadline at all.

Be equally honest about your own side of the schedule. If feedback will take you a week because it goes to a committee, write that down. Freelancers plan capacity around your turnaround as much as their own, and a buyer who admits to a slow approval cycle up front is far more attractive than one who reveals it in week two.

Avoid inventing urgency to win a discount. Rush pricing is a real thing, and if you compress a timeline that did not need compressing you will pay for it in money or in quality. If you and your freelancer are in different parts of the world, agree working hours and response expectations in writing — and check the current local time on both sides when you do, because some regions shift their clocks twice a year and others never do, so the gap between you is not a fixed number.

Ask for the right evidence, not a portfolio dump

“Send me your portfolio” produces a link to everything a person has ever made, which tells you very little. Ask instead for the two or three pieces closest to your job, and ask what the freelancer’s specific contribution to each one was. On collaborative work — a site built by an agency, a campaign run by a team — that question separates the person who led it from the person who was nearby.

Ask for one relevant result rather than a list of client logos. “Tell me about a project like this one and what happened after it launched” is a single question that reveals scope experience, honesty and communication in one answer. Our guide to reviewing a freelancer’s portfolio covers what to look for once the samples arrive.

Do not ask for unpaid custom work. Spec work as a screening device filters for people with free time rather than people with a track record, and the strongest freelancers decline it on principle. If you want to see how someone handles your problem specifically, pay for a small piece of it — that is exactly what Micro Zinns are for, and they are fixed at $5, $10, $15 or $20.

Add one screening question that cannot be copy-pasted

The single highest-return line in any job post is a short, specific question placed at the end, with a request to answer it in the first line of the reply. Mass applicants ignore it because their template does not contain an answer. Everyone who answers it has, by definition, read your post.

Keep it relevant to the work rather than a trick. Good examples: “Which content management system would you recommend for this, and why?” “What is the first thing you would check about our current form?” “Roughly how long would the migration take, and what could go wrong?” Each takes a competent person sixty seconds and is unanswerable from a template.

One question is enough. A screening form with six questions reads as an unpaid assignment and costs you good applicants at the same rate as spec work. The point is not to test knowledge — it is to prove attention.

Phrases that quietly repel good freelancers

Some standard job post language reads very differently from the other side of the screen. None of these phrases is dishonest, but each one costs you applicants you would have wanted.

• “Simple job, should be quick”Reads as a buyer who has pre-judged the effort and will resist the real estimate.
• “Rockstar / ninja / guru”Signals that the brief is about enthusiasm rather than scope. Specialists skip these.
• “Long-term work for the right person”Used so often as an argument for a low first rate that it now reads as one. If it is true, say what the follow-on work actually is.
• “Send me your best price”Invites a race to the bottom and filters directly for inexperience.
• “Must be available on demand”Independent professionals have other clients. Ask for a response window instead.

Replace each one with the specific thing you actually mean. “Simple job” becomes the scope list. “Long-term work” becomes “we expect roughly one of these a month if the first goes well”. “Available on demand” becomes “we need a reply within one working day”. Specificity is what makes a post credible.

A job post template you can copy

This structure works for almost any freelance job. It takes about fifteen minutes to fill in properly, and it will save you hours of proposal triage afterwards.

• TitleDeliverable, scale and context. One line, no adjectives.
• OutcomeOne or two sentences on the result you want and why it matters now.
• BackgroundWhat exists today, who it serves, and what platform or tools are involved.
• ScopeCountable items, who supplies what, revision rounds, explicit exclusions.
• BudgetAn honest range in USD, with a note on whether you want a fixed price or an hourly rate.
• TimelineStart date, finish date, the reason for the deadline, and your own feedback turnaround.
• EvidenceTwo or three relevant samples, plus the freelancer’s specific role in each.
• Screening questionOne specific question, answered in the first line of the reply.

Write it once and keep it. Most buyers post similar work repeatedly, and a saved template that already contains your background paragraph and your standard exclusions turns a fifteen-minute job into a three-minute one.

Posting your job on Zinn Hub

Posting a project on Zinn Hub is free, and buyers pay no platform fee — the price you see is the price you pay, with nothing added at checkout. All prices are in USD; you can view an approximate equivalent in your own currency across 59 display currencies, but USD is always what you are charged.

There are three routes, and the right one depends on how well defined your job already is. If the scope is clear and standard, buy a fixed-price service outright — browse the specialist marketplaces or a category such as writing and translation. If the scope needs proposals, post the job free and let Zinners quote against it: copywriting projects and website development projects are two of the busiest boards. If you would rather approach people directly, browse verified Zinners and narrow by a single skill such as copywriting or SEO, then invite the ones you like into your brief.

Zinners are verified with government-issued photo ID and evidence of their skills and past work, and reviews on Zinn Hub require a confirmed purchase. Payment protection depends on how your chosen Zinner is set up: choose a Platform Protected Zinner and your payment is held by Zinn Hub until the order completes — the whole order, as a single amount. If anything is refunded, it is credited to your Zinn Wallet in full, in USD.

One last trick worth knowing. If two applicants look equally good on paper, you do not have to decide on paper. A $10 Micro Zinn — a headline rewrite, a single graphic, a short audit — buys you a real sample of how each of them works before you commit to the main job. Browse by category, such as articles and blog posts, and treat it as the cheapest interview you will ever run.