What European software job posts leave unsaid

Picture a candidate on a Tuesday evening, rereading your job post for the third time. They know what they would build. What they cannot picture is how they are supposed to work with the team: "strong communicator," "team player," "comfortable in a fast-paced environment." Those lines shape who applies and what they rehearse before the interview. They rarely show what a good week actually looks like.

We wanted to see what European employers write when nobody is yet sitting in the interview room. So 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 one of your own posts open beside this page: which human skills do you name clearly, and which do you leave for candidates to guess?

The collection story has a twist. We pulled 1,000 posts, one hundred per city. Only 563 were different jobs. Eighty-six remote roles had been listed again and again across city searches, producing 437 duplicate listings. One opening could look like ten local jobs depending on where someone searched. Market charts count each job once so a handful of repeated remote roles do not skew the averages. City charts keep all one hundred posts per capital, because that is what a job seeker actually sees when they search locally.

We also ran the same lens on 4,920 pharma job posts from large employers, so you can compare software and pharma on the same wheel later in this article.

The PowerWheel is WiseWorld's map of 44 soft skills in six groups: teamwork, communication, thinking skills, work ethic, problem solving, and leadership. The farther a skill sits from the centre, the more often posts named it.

Start with the snapshot of what we collected:

Four numbers that frame the rest of the story:

Every percentage here describes public post language, not interview performance or whether candidates actually have the skill:

Topics in this article:

The PowerWheel is the market's silhouette. Start with the full European view, then switch to Berlin, Warsaw, Madrid, Paris, or Amsterdam and watch the shape shift. The farther a skill sits from the centre, the more often that city's posts named it.

Zoom out from individual skills and the story groups into six categories. 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. Employers talk about delivery and ownership far more often than they label communication as its own headline skill.

Drill back into the top fifteen skills by name and the same delivery story repeats. Collaboration ranks first at 81%, Task Mastery second at 70%, and Accountability third at 61%. Remember: a high share means often named in the post, not automatically most important on the job.

At the far edge of the wheel sit the skills employers almost never write down. Conflict Resolution, Negotiation, and Persuasion each show up in zero listings. Low mention often means assumed, not optional. If your team lives on those moments, the post may be leaving the hard part unstated.

Six real lines from this sample map a vague phrase to the PowerWheel skills inside it and a standard you could publish so a candidate can picture the job.

Career coaches still tell people to lead with communication and teamwork. In this sample, posts lead with delivery: who you work with, what you ship, what you own. Communication is folded into those lines rather than named as the headline skill. A candidate who prepares from generic coaching may rehearse the wrong story entirely.

We compared the public post to what interviewers often score behind the scenes. 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 scorecard templates. Candidates prepare from the post. Interviewers grade from the template. Nobody agreed which script was the real one.

Teamwork sits at a similar level in every city. Leadership is where the markets part ways. The heatmap lines up all ten capitals and three skills side by 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 language with 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 character. Where large, office-based employers dominate, leadership language rises. Where remote startups dominate, posts still stress teamwork but name leadership less often. All ten cities side by side so you can match a candidate's home market to the voice they learned to write in.

Length is only the first chapter. 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: quiet in the smallest companies, much louder once headcount passes a few hundred. A three-skill post at a ten-person startup and an eight-skill post at a 600-person firm are often describing different kinds of work on the page, not a longer template list.

Where people work rewrites the brief too. Remote posts spell out teamwork more often than on-site posts, as if employers know they must describe collaboration when nobody shares a hallway.

Now picture a graduate reading an entry-level post. Do you ask them to lead? 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. Grouped by job title on LinkedIn, posts shift with the name on the door:

Figure 5 tells the same story through years of experience on LinkedIn. 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 title 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 until you sit across from two finalists with the same title and different employment types. 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. Same word on the org chart, different story on the page.

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 of the job.

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, even when the title matches.

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.