What European software job posts leave unsaid

Software job posts usually explain what candidates will build. They are less clear about how candidates are expected to work: "strong communicator," "team player," or "comfortable in a fast-paced environment." Those phrases influence who applies and what interviewers test, yet they rarely show what success looks like. This study asks a simple question: which human skills do European software employers actually name, and how specifically do they describe them?

That is the question we wanted to answer with data. We read 563 unique LinkedIn job posts for software engineers across ten European capitals (Brussels, Berlin, Paris, Rome, Madrid, Warsaw, Amsterdam, Vienna, Prague, and Stockholm), from 296 employers. As you read, keep your own job posts in mind: which soft skills do you name clearly, and which do you leave for candidates to guess?

We collected 1,000 posts (100 per city), but only 563 were different jobs. Eighty-six remote roles accounted for 437 duplicate listings across city searches. Market charts use the deduplicated set so a handful of repeated remote roles do not dominate the averages. City charts use all 100 posts per capital, because that is what a job seeker searching locally actually sees.

We also ran the same analysis on 4,920 pharma job posts from large employers, so you can compare the two side by side in section 6.

New to the PowerWheel? It is WiseWorld's map of 44 soft skills in six groups: teamwork, communication, thinking skills, work ethic, problem solving, and leadership. Each skill has a label on the wheel. The farther it sits from the centre, the more often job posts named it.

The callout below summarizes the sample: where the posts came from, how many we read, and how we counted skills.

Four headline numbers from the analysis:

When you read a claim in this article, use the four-step guide below.

Jump to any section:

The PowerWheel below shows which skills employers named most often. Start with the full market view, then switch to Berlin, Warsaw, Madrid, Paris, or Amsterdam. The farther a skill sits from the centre, the more often that city's posts named it.

The wheel shows 44 individual skills. The chart below rolls them into six categories and averages how often each group appears across all posts. Work Ethic leads at 30.6%, then Leadership at 22.2%. Communication sits lowest as a group at 2.3%, even though Collaboration ranks first on the wheel.

Category averages blend skills together. The table below lists the top 15 individual skills by share of posts. Collaboration ranks first at 81%, Task Mastery second at 70%, and Accountability third at 61%. A high share means often named in the text, not most important once someone starts the job.

At the far edge of the wheel sit skills employers rarely name. The table below lists every PowerWheel skill that appears in fewer than 2% of posts. Conflict Resolution, Negotiation, and Persuasion each show up in zero listings. Low mention often means assumed, not optional.

The table below pulls real lines from this sample. Each maps a vague phrase to the PowerWheel skills it points to, and a standard you could publish instead.

There is a gap between career advice and what employers actually write. Coaches tell candidates to lead with communication and teamwork. In this sample, posts lead with delivery instead: who you work with, what you ship, what you own. Communication is still there, but it is folded into those lines rather than named as the headline skill. A candidate who prepares from generic coaching may rehearse the wrong story.

The chart below compares two documents: the job post and a typical interview scorecard. We read 40 public templates from Greenhouse, Lever, and Ashby. We did not sit in on live interviews. Collaboration and Accountability show up often in posts. Conflict Resolution, Negotiation, and Persuasion barely appear in posts but still show up on many templates. Candidates prepare from the post, not the template.

Teamwork sits at a similar level in every city. Leadership is where the markets split. The heatmap below lines up all ten capitals across the top and three skills down the side: Collaboration, Leadership, and Ownership. Read across the Leadership row to rank cities; read down one column to see how a single capital mixes delivery and lead-the-work language. Berlin runs warm on leadership and ownership; Amsterdam stays cooler on leadership while collaboration holds steady.

The pattern tracks employer mix more than national style. Where large, office-based employers dominate, leadership language rises. Where remote startups dominate, posts still stress teamwork but name leadership less often. The table below lays all ten cities side by side.

The table counts list length. Figure 3 asks which skills move with headcount. Collaboration sits near six in ten posts for firms under 200 staff, then rises sharply in the mid-size band. Ownership and leadership follow the same curve: low in the smallest companies, much more common once headcount passes a few hundred. So size changes the mix, not just the number of lines. A three-skill post at a ten-person startup and an eight-skill post at a 600-person firm are often naming different kinds of work.

Where people work matters too. Remote posts spell out teamwork more often than on-site posts, which may reflect the need to make collaboration explicit when colleagues are not in the same room.

Now look at entry-level job posts. Do they ask candidates to lead? Job level is the clearest seniority signal. Lead and principal roles ask for leadership in more than four in five posts (84%). Entry-level roles lean on adaptability, the language of learning fast.

The table above is grouped by job title. Figure 5 groups the same posts by experience level on LinkedIn, so you can see how four skills shift across a career path. Ownership climbs from entry to director. Leadership is patchier: it dips in associate posts even though lead titles name it often. Collaboration stays high early, softens in the middle, then steadies at the top. Learning agility runs the other way, strongest in entry posts and rare by director level. If the junior leadership figure in the table surprised you, read the asterisk: many of those lines come from programme names, not role requirements.

Figure 5 is the cleaner read when you are benchmarking by seniority.

Contract type splits the market in a way that is easy to miss. Full-time and contract posts ask for teamwork at the same rate, but ownership appears in nearly two-thirds of full-time posts (64%) and only about one in six contract ones (16%). Contract posts ask instead for problem solving and the ability to work alone.

The table ranks the ten widest gaps. Task Mastery and External Relations sit at opposite ends: software spells out how work gets done; pharma spells out who the work is for. If you hire engineers into regulated or client-facing roles, do not assume the market template already names that part.

The skills named follow that split. In the urgent band, remote posts stress independence and problem solving. Hybrid and on-site posts stress ownership and work ethic. Figure 9 compares the two groups. If your role is remote and urgent, candidates will read a different brief than for a local permanent hire.

A clearer post only helps if the interview tests the same work. The gap we saw most often is not missing skills on the page. It is asking interviewers to score broad labels the post never defined.