How to Write a Freelance Job Post (With Template)

“Looking for a talented developer for an exciting project.” Every freelance marketplace has thousands of posts that open like this. Experienced freelancers skip them, not because they’re lazy, but because they know the real scope will only emerge on the third call.

The complaint shows up in data too. Freelancermap’s Freelancer-Kompass 2026 surveyed about 5,400 freelancers in German-speaking Europe, and 55 percent named unclear requirements and briefs as their biggest communication problem with clients. Slow feedback came second at 47 percent. Clients without the authority to decide came third at 42 percent.

Most of that can be fixed before anyone applies.

What a busy freelancer checks first

Someone with options reads four things before anything else. Is this my field? Is the money right? Do I have to be on site? How long does it run? Those four belong at the top, ideally in one line.

The same survey shows why. 70 percent turn projects down because the rate is too low, and 49 percent because there’s no remote option. If you hide both, you’ll mostly hear from people who don’t mind. They’re rarely the ones you want.

A structure that works

Seven parts, in this order, make a solid job post.

1. Key facts in one lineRole, duration, workload, remote setup, rate range.
2. OutcomeWhat will be finished and accepted, in two sentences.
3. Starting pointWhat already exists: code, designs, tools, data, team.
4. RequirementsMust-haves and nice-to-haves kept apart, five must-haves at most.
5. CollaborationContact person, decision-maker, meeting rhythm.
6. Selection processFirst call, paid test task if needed, decision by a date.
7. How to applyTwo samples and an answer to one specific question.

The last part is your strongest filter. A question like “How would you migrate a live Vue 2 app to Vue 3 without a freeze?” separates people who have done it from people sending a template, and it costs a qualified applicant five minutes. Pick a question with no single right answer. You learn more from how they reason than from whether they agree with you.

Template you can copy

This one is written for a development project, with a US-style rate. For design or marketing, swap the stack for brand guidelines and channels.

Backend developer (Node.js) for a billing module · 4 months · about 3 days a week · fully remote · $90–115/hour

Outcome: A module that generates monthly invoices from our usage data, sends them as PDFs and hands them over to our accounting system. It’s done when a full monthly run for 2,000 customers completes without errors.

Starting point: An existing Node.js API on PostgreSQL, deployed through GitHub Actions. One frontend developer on the team, no backend capacity.

Must-haves: PostgreSQL and payment or billing logic in production. Automated tests as a habit. Fluent English. Nice to have: Experience with e-invoicing standards.

Collaboration: Our CTO is your contact and makes the decisions. One weekly call, everything else async. You choose your hours.

Selection: A 30-minute call, then a paid four-hour test task. Decision by 15 November.

To apply: Two projects where you built similar logic, and three sentences on how you’d prevent duplicate invoices if a run fails halfway.

That’s about 200 words. Nothing more is needed for a first contact.

The title decides whether anyone clicks

On most platforms a freelancer first sees the title and maybe two lines. For its 2026 report, freelancermap analysed the 100 most-clicked and most-applied-to projects on its board. They averaged eleven applications, 94 percent were advertised as fully remote, and words like “ASAP” turned up regularly in their titles.

So urgency doesn’t scare people off. Urgency without a date, a budget or an outcome does. “Node.js backend for billing module, 4 months, remote” beats “Developer wanted” on every count.

Phrases that cost you good applicants

Some phrases quietly reduce your applicant pool. Others can cause legal trouble later.

The fourth and fifth rows are not about style. The IRS groups the evidence for worker status into behavioural control, financial control and the type of relationship. Set hours and holiday rules are behavioural control in plain sight. British clients of medium or large size decide a contractor’s IR35 status themselves, and in Germany the test is integration and instructions under § 7 SGB IV. If you hire there, our guide to false self-employment in Germany explains it.

The last row matters more than people think. Anti-discrimination rules often reach beyond employees. Germany’s equal treatment act explicitly covers access to self-employed work, and in the US, 42 U.S.C. § 1981 bars race discrimination in making contracts of any kind.

Hourly rate or fixed price?

Use an hourly range when the scope is open, such as ongoing development or support. Use a fixed budget for outcomes you can define completely, a landing page or a logo.

Keep the range honest. “$40 to $150 an hour” isn’t a range, it’s a shrug. If you don’t know the market, look at our overview of freelancer hourly rates before you write the number down.

After you post: the brief

The post gets applications. The brief gets the project moving. It holds everything too long for the post: access, existing documentation, design files, detailed acceptance criteria, a phone number for your contact person.

Send it after the first call, once both sides want to continue. For anything confidential, get a non-disclosure agreement signed first and carry it into the freelance contract.

If writing the post shows you’re really describing four roles, backend and frontend and design and hosting, take that as a signal. Maybe a team with its own project lead suits you better, and it’s worth seeing how a studio like OnlineBuilders works before writing four separate posts.

Your next step

Take the template, replace every line with your project and delete anything you can’t fill in concretely. What’s left is your post. Our comparison of freelance platform fees helps you decide where to publish it, and it pays to plan a paid test project into the selection from day one.

Step by step

1. Define the outcome Describe in two sentences what will be finished, accepted and usable at the end.
2. Set the constraints Name the tech stack or brand rules, existing systems and hard deadlines.
3. State budget and duration Give an hourly range or fixed budget, a start date and the estimated effort in days.
4. Describe how you work together Cover the remote setup, the contact person, who decides and how often you meet.
5. Shape the applications Ask for two relevant samples and an answer to one project-specific question instead of a CV.

Questions people ask

How long should a freelance job post be?

Around 200 to 400 words is enough for the post itself. Detailed specs, data models and brand guidelines belong in a separate brief that you send after the first call. If the post runs to two pages, most readers stop before they reach the budget.

Should I put the budget in the job post?

Yes, as a range. In freelancermap's Freelancer-Kompass 2026, 70 percent of freelancers named a rate that was too low as a reason to turn projects down. A range saves both sides a call that ends at the price.

Should I ask for a CV?

Rarely. For freelance work, two relevant samples and a short answer to a project-specific question tell you far more than a CV. Ask for references later, once someone is on your shortlist.

What should a freelance job post not include?

Fixed working hours, holiday rules, reporting lines and a place in your org chart. Those describe an employee. If a tax authority ever reviews the relationship, a post like that is evidence against you.