Skip to content

BlogCraft

Writing an IT job ad that developers actually answer

An IT job ad that attracts states the pay, stack, remote days and contract in under 300 words. The EU pay transparency directive makes the range unavoidable.

9 min read

To write a job ad that attracts IT candidates, answer in under three hundred words the five questions a developer asks before clicking: how much, on which stack day to day, how many days remote, under what contract, and in how many stages. Everything else, the company culture, the list of perks, the history of the firm, comes afterwards or not at all. An ad that leaves out one of those five answers does not merely lose applications, it attracts the people who did not need the answer, which is rarely who you were looking for.

This is not a question of style. A job ad is not a text people read in order to be persuaded, it is a text they read to decide quickly whether to walk away, and its quality is measured by how well the people who stay fit the role rather than by how many of them there are.

What should a job ad that attracts IT candidates contain?

The five answers, written in terms that can be checked, and in the order the candidate looks for them.

Pay first, as an annual gross range for an employee and a day rate range for a freelancer. Then the stack, but the one used every day rather than the inventory: three or four technologies the person will spend their days on, with the version when it matters, rather than the twelve somebody once spotted in the client’s information system. Remote work as a number of days per week, and where the other days are spent. The contract, with no ambiguity about what it covers. Finally the process: how many interviews, with whom, and how quickly you commit to replying.

These five pieces of information share one property, which is why they come before everything else. They are the ones a candidate uses to rule themselves out, in ten seconds and without costing anyone a minute. An enthusiastic description of the team spirit lets nobody decide against applying, and that is precisely why it does not help.

Why put the salary range in the ad?

Because it is the information candidates want most, and the information employers give least.

The gap has been measured. According to Indeed Hiring Lab, 43% of job postings in France show a salary, and the trend has stalled for two years in most large European countries. On the candidate side, 66% of French workers surveyed in January 2025 say they are more likely to apply when an ad includes a range, and 74% think it should be there by default. These are stated preferences rather than counted applications, but a majority that size does not need to be exact to show the direction. LinkedIn reached the same result by another route: asked what they found most useful in a job ad, candidates put compensation first, alongside the qualifications required and what the working day consists of.

The range still has to be a range. The median annual range published in France is 19% wide, and Indeed’s example is €35,000 to €41,650. A developer ad at “€40,000 to €70,000 depending on profile” informs nobody: it tells the candidate that pay will be negotiated without any reference point, which is exactly what they were trying to avoid by reading the ad.

What does the EU pay transparency directive change?

It turns the range into a candidate’s right, and the French bill makes it a condition for publishing the ad at all.

Directive (EU) 2023/970 gives candidates the right to receive from the employer the starting pay or its range, based on objective and gender-neutral criteria, for example in a published vacancy notice, before the job interview or in some other way. It bans asking candidates for their pay history, and it requires gender-neutral vacancy notices and job titles. The question “what are you earning now?”, asked at the start of so many first calls, therefore becomes one that is no longer asked, and the offer has to be built from the job rather than from the candidate.

The first French bill, unveiled in March 2026, goes further than the European text on a point that directly concerns whoever writes the ad: it bans publishing or circulating a job offer that does not include the pay range and a reference to the applicable collective agreement provisions. Where no offer is published, the information has to be given in writing before or during the interview. In France, transposition goes through a bill presented in 2026, and most of the regime will come into force by decree, at the latest one year after the law is promulgated.

The exact timetable matters less than it seems for anyone writing an ad. The rule is written, its meaning is not in dispute, and a company that starts publishing its ranges today learns to defend them before it is forced to. Cobalt has set out what the directive requires of IT services firms, from the pay grid to the job descriptions, and that work comes before the ad: nobody can publish a range they have never calculated.

How long should a developer job ad be?

Under three hundred words for the published text, which matches what LinkedIn observed across 4.5 million job posts.

On posts published in 2016 and 2017 in the United States and the United Kingdom, ads of 1 to 300 words had an apply rate per view 8.4% above average. Those of 301 to 600 words came in 3.4% below average, and those over 600 words only 1% above. The data is almost ten years old and does not cover France, so it should be read as a direction rather than a scale. The reason LinkedIn gave has not aged, quite the opposite: more than half of the ads on the platform were already being viewed on a phone.

The practical consequence is a separation. The published ad carries the five answers and two or three sentences about the work itself; the full job description, with the project context, the team and the secondary tools, goes afterwards to the candidates who have passed that first filter. A nine-hundred-word ad does not show that you have a lot to say, it shows that you did not choose.

What drives applications down?

Anything that forces the candidate to guess, and anything that suggests nobody read the ad over.

The signals are familiar to anyone who reads technical job ads. A list of twelve technologies, half of which contradict each other, says the client’s inventory was copied in. “Attractive package” or “pay depending on profile” say the figure is below market, rightly or wrongly. “Remote possible” says the rule has not been set, or that it has and nobody wants to write it down. An inflated title, an “expert” for a role needing three years of experience, attracts the wrong profiles and puts off the right ones, who read the gap between the title and the content.

This paragraph is trade observation rather than measurement, and we present it as such. To our knowledge, ads in which each of these defects is fixed in isolation have never been compared publicly. But every one of these signals has the same effect on the reader: it turns a decision they could have taken alone into a question they would have to ask, and most developers who already have a job do not ask the question, they move on to the next ad.

Mission or permanent contract: how should an IT services firm write it?

By saying explicitly what happens when the mission ends, because it is the question every candidate at an IT services firm asks and the standard ad never addresses.

An IT services firm often hires on a permanent contract for a specific mission, and the ad then mixes two promises: the employer’s, which lasts, and the client’s, which has an end date. The candidate needs both. The client’s sector and size, even without its name, the mission location and days on site, the expected duration, and what the firm does with its consultants between two missions. That last point is usually left out, even though an experienced candidate knows that time on the bench has a cost and an average length, and would rather have an honest answer than none.

For a freelancer the rule is simpler and broken more often: a day rate range, the duration, the on-site rhythm, and the start date. A mission ad with no rate attracts first the profiles willing to accept any rate, which is not the first quality criterion anyone was looking for.

Should the ad be written before or after the client intake?

After, always, because it is only the public version of what the intake established.

The range, the criteria that genuinely rule a candidate out, the interview schedule and the number of days on site are all answers that the intake meeting must have obtained before any search begins. An ad written before the intake invents those answers, or leaves them out, and either way it produces applications for a job the client will not recognise. The ad is also the first test of the intake: if you cannot write down the range or the remote rhythm, the question was never asked.

This is a place where an agent provides a service you can check. Balt drafts the ad from the recorded need, adding nothing the intake does not contain, and flags what is missing to complete it. Publishing it, however, goes out of the company under its name and commits it to a level of pay: a person reads it and releases it, like everything an AI writes for the outside world.

Is more applications really the goal?

No, and that is the concession owed to those who hesitate to write everything down.

Volume is no longer the problem. Applications have surged on the large platforms, a growing share is written by tools that copy the ad’s wording word for word, and we have put figures elsewhere on that flood and what the first screen actually takes from it. A vague ad in that context does not produce fewer applications, it produces more bad ones, which somebody will have to read before finding the good ones.

A precise ad therefore does the opposite of what people expect of it. It sometimes reduces the number of applications, and it raises the share of those that last until the offer, because pay, contract and rhythm were accepted before the first conversation rather than discovered at the last one. What remains is to answer the people who applied, within a time they consider reasonable, or else the silence undoes the work the ad did.

Frequently asked questions

  • Should an IT job ad show the salary before the law requires it?

    Yes, because the question will be asked anyway and the EU directive makes it unavoidable. Publishing an honest range today avoids interviewing candidates who will walk away at the offer stage, and prepares the company for a rule the French bill has already written down.

  • How long should a developer job ad be?

    Under 300 words for the published ad, which fits on a phone screen in two or three scrolls. LinkedIn’s data on 4.5 million posts shows that short ads get more applications per view than long ones, and the full job description can be sent afterwards to the candidates who are shortlisted.

  • How should remote work be stated in a job ad?

    As a number of days per week, and with who decides. “Remote possible” tells a developer nothing, whereas “two days a week on site at the client, in Nanterre” lets them decide alone whether to apply, which is exactly what an ad is for.

  • Should an IT services firm name the end client in the ad?

    Not necessarily by name, which is often confidential, but always by sector, size, mission location and expected duration. A candidate who does not know where they will be working in three months is not applying for a permanent job, they are applying for uncertainty, and they know it.

Sources

  1. Indeed Hiring Lab, Lisa Feist, Salary transparency in Europe remains a distant prospect (May 2026, in French)hiringlab.indeed.com
  2. LinkedIn Talent Blog, 4 New Job Post Stats That Will Help You Attract Candidates (August 2018)linkedin.com
  3. CMS Francis Lefebvre, Transposing the directive: pay transparency from hiring onwards (June 2025, in French)cms.law
  4. EY Avocats, Pay transparency: what the first French bill provides (March 2026, in French)avocats.ey.com
  5. Cobalt, EU Pay Transparency Directive: what every IT staffing firm must do (2026)cobalt-ia.com

Balt does this work

Read next

Give Balt its first job.

Thirty seconds to add it to Teams and get to work.

Try for free