In Germany, it takes 7.7 months on average to fill a vacant IT position. That is the result of a survey by the digital association Bitkom (in German) of 855 companies between May and July 2025. In Bitkom’s 2026 survey (in German), 31 percent said they receive practically no applications for their open IT positions.
The job advert alone is not to blame. But it is the part of the search you control. This article shows what belongs in a job advert for software developers in 2026: which questions to settle first, how to structure the advert, what applies to stating the salary, which wording is risky under German equal treatment law and which requirements screen out the best people.
Task first, advert second
Many job adverts are built from the previous one: adjust the title, swap the stack, publish. What gets skipped is the question of what the team actually needs right now.
On LinkedIn, Sören Elser, founder and managing director of ElevateX, describes a client who had advertised a technically demanding role for weeks: job boards, LinkedIn, their own network, no suitable applications. In his view, this was not down to a lack of quality in the market. ElevateX then looked at the requirement, in Sören’s words “not the job description, but the actual task”: “What does the team really need? Which technology, which experience, which character?” In his experience, a search almost always goes quickly “when someone really understands the requirement before they search.”
The same applies to your advert. The first question, according to Sören, is: “What do I need – for this task, now, in this situation? Which competence? Which experience? In what time frame?”
Before Sören searches for a client, he goes through these questions with them step by step. They work just as well as preparation for a job advert:
- The overall project: “In the first step, I ask about the overall project: what is it about, what are you building, what are you working on with your team right now?”
- The person and the skill: What kind of person are you looking for, and which skill do they need?
- Tech stack and role: Which stack do you work with, and what should the person do on the technical side? Sören has the client describe the role.
- Fit with the team: Only once he understands what the person should do technically does he ask “whether they work on their own or together with the team.”
- The way of working: Sören also listens for the human side: “Is it a person who tends to be proactive, or one who enjoys working through tasks and collaborating with a team?”
If you cannot answer each of these five questions in two sentences, the advert is not ready yet.
In practice: In Sören’s experience, the main thing a client needs to bring to the first conversation is this: they need to know what their problem is and who they are looking for. That includes how the team is set up today, where the real bottlenecks are, whether they lack capacity or know-how, and what the technical environment is. The details can be worked out together in the first conversation. But if a client does not really know what they need, it gets more complicated.
What belongs in a developer job advert
Developers read a job advert like a specification: what is the task, what are the tools, who is on the team, what are the terms? That gives you eight building blocks.
| Building block | What goes in | Typical mistake |
|---|---|---|
| Job title | A common title with level and focus, for example “Senior Backend Developer Java (m/w/d)” | Creative titles or internal job grades nobody searches for |
| Task | What the person will work on in the first six months, on which product, with which goal | “Varied tasks in software development” |
| Tech stack | Languages, frameworks, cloud, databases, deployment and the AI tools used day to day, weighted by importance | Twenty technologies without weighting, legacy systems left out |
| Team and way of working | Team size, roles, leadership, code reviews, release cycle, on-call duty | “Dynamic team” without any details |
| Requirements | Three to five must-haves, the rest as “nice to have” | A wish list nobody can meet |
| Salary range | Starting salary or range and what the placement within it depends on | “Competitive salary” |
| Location and terms | Remote, hybrid or on site, office days, travel, full or part time, fixed-term or permanent | “Flexible working” without a rule |
| Application | Steps, duration, contact person and what you need for the first step | Long form, no reply |
“Three to five must-haves” is a rule of thumb, not a study. It forces you to decide what is really necessary.
For the order, the AIDA model from marketing helps: Attention (the headline), Interest (subtitle and introduction), Desire (the main part with task, stack and offer) and Action (the way to apply).
Job title: the way developers search
Use the title developers type into a search box themselves: role, level, focus. Internal titles and wordplay cost you visibility. German adverts usually add (m/w/d), English-language adverts in Germany often (m/f/d). More on that in the section on equal treatment law.
Task and tech stack: specific, not exhaustive
Write what the person will work on in the first six months, and name the biggest open problem. For the stack, weighting helps: what is used every day, and what only at the edges? Mention legacy systems too. Anyone who only learns about them in the interview feels misled.
In 2026, this part also covers how you work with AI tools: which tools you use and what for.
Team, location and application
How big is the team, who leads it, how do reviews and releases work? These are questions four and five from Sören’s list, and they belong in the advert, not just in the interview. For the location, state the rule: how many days in the office, at which site, how much travel. For the application, list the steps, how long they take and who will reply.
An example
Before:
We are looking for a motivated software developer for varied tasks in a dynamic team. We expect several years of experience with modern technologies. We offer a competitive salary.
After (made up for illustration):
Senior Backend Developer Kotlin (m/f/d). Together with four colleagues, you will rebuild billing for our product: from a PHP monolith to Kotlin services on AWS. In the first six months, you will extract the invoicing module together. We deploy daily, every pull request gets a review, and we work with AI coding agents day to day. You have run a service in production and designed interfaces that other teams use. Salary: X to Y euros gross per year, depending on your experience with distributed systems. Remote within Germany, two days in the office once a month. Application: CV or profile link, one conversation with the team, one task on real code, a reply within a week.
Salary range: what the EU directive requires and what applies in Germany
Directive (EU) 2023/970, the Pay Transparency Directive, covers the time before hiring in Article 5:
- Information on pay: Job applicants have the right to receive information from the prospective employer about the starting pay for the position or its range, and where applicable about the relevant provisions of the collective agreement.
- Timing: The information must be provided in a way that allows informed and transparent pay negotiations, for example in a published vacancy notice, before the job interview or otherwise. The advert is one possible place, but not the only one.
- No questions about previous pay: Employers may not ask applicants about their pay history in current or previous employment.
- Gender-neutral: Vacancy notices and job titles must be gender-neutral.
Under Article 34, member states had to transpose the directive by 7 June 2026.
Status in Germany on 11 November 2026: There is no implementing act yet. In an answer to the German parliament, the federal government wrote that the responsible Federal Ministry for Education, Family Affairs, Senior Citizens, Women and Youth had made the preparations for a bill and was still clarifying individual questions. After that, the legislative procedure would be started (Bundestag printed paper 21/7026 of 8 July 2026, in German). The answer gives no timetable. On 8 September 2026, a motion by the Left parliamentary group called on the government to present a bill (printed paper 21/7916, in German). When we checked on 11 November 2026, we found no published draft bill from the ministry or the cabinet. When the law will come and what exactly it will require is therefore still open.
What applies until then? The current German Pay Transparency Act (Entgelttransparenzgesetz, in German) of 2017 contains no duty to state the salary in the advert or before the interview. On the directive itself, the federal government answered a question from a member of parliament on 14 July 2026: in principle, it has no direct effect between private parties, but existing national law must be interpreted in line with the directive in individual cases. Towards public employers, individual provisions could exceptionally have direct effect (printed paper 21/7180, question 95, in German).
There are good reasons to put the range in the advert now anyway. In Bitkom’s 2025 survey, 63 percent said applicants’ salary expectations did not match their qualifications. 56 percent said they did not fit their own pay structure. A range in the advert settles this before the first conversation. Add what the placement within the range depends on, such as experience with certain systems or responsibility in the team. And remove the question about current salary from your process: the directive prohibits it.
This section reflects the situation on 11 November 2026 and is not legal advice.
Equal treatment law: keeping the advert free of discrimination
If you advertise a position in Germany, Section 11 of the General Act on Equal Treatment (AGG) applies. In the official English translation it reads: “A vacancy may not be advertised in violation of section 7 (1).” Section 7 (1) prohibits discrimination against employees on any of the grounds in Section 1: race or ethnic origin, gender, religion or belief, disability, age or sexual orientation. Job applicants count as employees under the act (Section 6 (1)).
The consequences of the wrong wording:
- Burden of proof: If a rejected applicant proves facts that suggest discrimination, the employer has to prove that no violation occurred (Section 22). Wording in the advert can be such an indication.
- Damages and compensation: Both are governed by Section 15. If the person would not have been hired even without discrimination, compensation is capped at three months’ pay.
- Time limit: As a rule, the claim must be made in writing within two months of receiving the rejection. There is no right to the job itself.
The guide “Fair in den Job!” (in German) by Germany’s Federal Anti-Discrimination Agency (2019) shows which wording is risky. The examples in the table come from there, translated:
| Risky | Better | Ground |
|---|---|---|
| “German as a native language”, “native speaker” | “very good German” or “business fluent German”, if the task requires it | ethnic origin |
| “Young team is looking for you”, “young professionals”, “fresh out of training” | “several years of professional experience”, “senior” or “junior” as a function title | age |
| Age limits such as “up to 55 years” | no age reference | age |
| Male-only job title or the addition “(m/w)” | “(m/w/d)”, a gender star or a neutral term such as “specialist” | gender |
Factual requirements remain allowed. According to the guide, a justified amount of professional experience is not age discrimination, even if younger people are at a disadvantage as a result. You may require language skills if the job needs them. The guide recommends explaining why in the advert, for example because of frequent customer contact. Among other cases, the act permits different treatment if the characteristic is a genuine and determining occupational requirement (Section 8).
This section is not legal advice either. If in doubt, have an employment lawyer check the advert.
Requirements that screen out the best
The most common weakness of developer adverts is the wish list. Every additional must-have shrinks the group of people who feel addressed.
This becomes especially clear with AI. By Sören’s estimate, 75 to 80 percent of inquiries to ElevateX in 2026 involved AI skills at least in part. He knows from briefing conversations how not to phrase it:
“We need someone with 5 years of agentic coding experience.”
According to Sören, this requirement “is logically impossible to meet”. Agentic coding as teams use it in projects today had been a real topic for one year at most when he wrote about it on LinkedIn in 2026. Asking for five years means looking for someone who does not exist. For him, what lies behind it is “uncertainty disguised as quality assurance”: anyone who wants to play it safe with a new technology falls back on criteria built for classic seniority. As a result, the best get screened out.
For Sören, degrees, certificates and years of experience are the right criteria for classic seniority. For developers who consistently work with AI, he considers them the wrong ones. Whoever develops this way today did not learn it at university, but has built their own projects and gained production experience in the last 12 to 18 months. That looks different on a CV, but in his assessment it is often the stronger profile. His three test questions:
- “What has the person built in the last 18 months?”
- “What runs in production – not just as an experiment?”
- “Where have they learned something that did not exist like this before?”
For the advert, this means: describe what someone should have built or run instead of counting years.
| Instead of | Better |
|---|---|
| “5 years of experience in AI-assisted development” | “You have built software with AI coding agents that runs in production, and you can show how you approach it.” |
| “Degree in computer science” | “Degree in computer science or comparable practical experience” |
| Twelve technologies as must-haves | “You have run a service on Kubernetes in production. You will learn the rest with us.” |
Which phrases unintentionally narrow the filter for senior profiles, and which channels reach these people beyond job boards, is covered in Finding a Senior Agentic Engineer in 2026.
When the task cannot wait: permanent team and freelancers
A good advert shortens the search. It does not turn months into weeks. What the time until a role is filled costs you is covered in the article on time to fill.
Some tasks do not have that time. Asked when he advises clients to bring in a freelancer alongside the job advert, Sören says: “Whenever it is a task that needs results at short notice.” Short notice, for him, means someone should really be working on it within two to four weeks. This applies above all when it “causes serious problems if there is no one who can help ad hoc” for the project and the whole team around it.
If that is not the case, the job advert is the right route, and you give it the time it needs.
The freelancer does not replace the permanent role. The advert stays online, and the search goes on. For Sören, a permanent team and freelancers are “not an either-or”. He considers “Do we take a freelancer, or do we hire someone permanently?” to be “almost always the wrong first question”: the task comes first, then the type of contract, and there are situations in which a permanent employee is the right answer. Recently, he advised a client who had more freelancers than internal staff to also hire permanently and build a stable core of permanent employees.
ElevateX places IT freelancers with companies. You get the first matching profiles within 48 hours of finalizing your request with us. Costs only start on the first working day, and there is no minimum term. Important: a freelancer is not an employee. They are not bound by instructions and decide on place and working hours themselves, but as service providers they align with what the project needs. What to watch out for is covered in our guide to false self-employment.
Checklist before you publish
- Can you describe the task for the first six months in two sentences?
- Is there a job title developers actually search for, with (m/w/d) or (m/f/d)?
- Are stack, team and way of working described as they really are?
- Are there no more than five must-haves, and does each describe something you can check?
- Is the salary range in the advert, and does nobody in the process ask about current pay?
- Are location, office share and contract terms clear?
- Is the advert free of references to age, origin and gender?
- Has someone from the development team reviewed it?
Conclusion
A good developer job advert starts before the writing: with the task, the role, the stack and the question of how the person fits into the team. In the advert itself, what counts is specific information, a few requirements you can check, a salary range and wording that does not discriminate against anyone. If the task needs results within a few weeks, a freelancer can start alongside the permanent team while the search for the permanent hire continues.



![The 6 Phases Of The Candidate Journey [with Graphic]](/_astro/what-is-the-candidate-journey-featured-en.BElIk8IQ_2j5bqs.webp)

