Skip to content
Back Freelance Hourly Rates in Germany 2026, by Skill: What 2,906 Postings Advertised

Freelance Hourly Rates in Germany 2026, by Skill: What 2,906 Postings Advertised

Support jobs post 35 EUR an hour, DevOps 77, SAP 99. The gap to the 103 freelancers report says where to negotiate.

Blago Yanakiev
Blago Yanakiev

Nov 10, 2026

Pricing studie Freelancers
TL;DR

In the 12 months to September 2026, 2,906 freelance postings for Germany, Austria and Switzerland printed an hourly rate. The median posted ceiling was 76 EUR. Three tiers show up: support work at 30 to 45 EUR, development and DevOps at 75 to 80, and SAP, data, compliance and finance at 85 to 100. Senior postings sit 15 EUR above mid-level ones. Freelancers report 103 EUR on average, so treat a posted rate as the opening of the conversation and quote above it when your skill and seniority justify it.

Ask a hundred freelancers what a Kubernetes engineer earns and you get a hundred answers. Ask the job boards and you get one: the ceiling the client was willing to print. We collect freelance postings from boards across DACH, and in the last 12 months 2,906 of them stated an hourly rate. Here is what those numbers say, by skill, by seniority and by category, and what to do with them when you set your own rate.

The three tiers

The overall median posted ceiling is 76 EUR an hour (lower quartile 60, upper quartile 91, 90th percentile 112). Underneath that sit three clearly separated levels:

  • Support and workplace IT: 30 to 45 EUR. Service desk, Windows, Active Directory, network and onsite support. The medians run from 32 (onsite and network support) to 45 (Active Directory).
  • Development and DevOps: 75 to 80 EUR, with the upper quartile near 90. Java 75, Docker 75, React 75, Kubernetes 77, Python 80, AWS 80.
  • SAP, data, compliance and finance: 85 to 100 EUR, with upper quartiles above 100. SAP IS-U 100, SAP HANA 99, SAP S/4HANA 95, data migration 94, ABAP 91, compliance 90.

By service category the picture matches: software engineering 75 (n 2,086), architecture and engineering 81 (n 122), business and consulting 85 (n 570), finance and accounting 100 (n 58). Design and creative shows 73, but from 28 postings, so read it as a hint, not a number.

By seniority as the posting labels it: junior 30 (n 155), mid-level 70 (n 1,325), senior 85 (n 1,426). The move from mid to senior is worth 15 EUR at the median. The junior spread is wide (lower quartile 21, upper 50), so read 30 as a rough marker.

The skill list

92 skills appeared in at least 40 priced postings. Here are 27 that cover the three tiers. Postings carry several skills each, so the rows overlap and do not add up.

Skill

Postings

Lower quartile

Median

Upper quartile

SAP IS-U

40

84

100

112

SAP HANA

68

85

99

110

SAP S/4HANA

66

75

95

120

Data Migration

60

76

94

105

ABAP

61

77

91

104

Compliance

55

70

90

100

SAP FI

40

85

90

106

Quality Assurance

81

75

88

120

Risk Management

88

75

85

100

Data Analysis

51

76

85

90

Project Management

909

68

80

100

Python

201

68

80

90

SQL

176

70

80

86

AWS

108

70

80

90

Kubernetes

246

70

77

90

CI/CD

209

70

77

90

Java

186

70

75

85

Docker

158

66

75

85

React

70

70

75

81

TypeScript

82

65

75

85

ServiceNow

108

40

48

75

Active Directory

120

40

45

70

Technical Support

130

32

40

45

Microsoft Windows

138

30

38

50

IT Support

58

30

35

40

Onsite Support

73

30

32

35

Network Support

49

30

32

37

Look at the spread, not only the median. Python (68 to 90), SQL (70 to 86) and React (70 to 81) are tight: the market agrees on the number. Project Management (68 to 100), Quality Assurance (75 to 120) and ServiceNow (40 to 75) are wide, most likely because the same tag covers very different jobs. For a wide row, the role description tells you more than the tag does.

How we counted

Only about 5 % of postings print a rate at all; the other 95 % say "open budget" or print a fixed price. Of those that do, we take the maximum hourly rate, the ceiling the client or agency showed. So these are advertised ceilings, not agreed rates and not what anyone invoiced. The window is 1 October 2025 to 30 September 2026, postings for Germany, Austria and Switzerland, EUR as posted (Swiss budgets as posted, not converted). We kept ceilings between 20 and 250 EUR to cut out implausible values, merged skill spellings into one master skill, and counted only skills with at least 40 priced postings. We left out Microsoft PowerPoint and Excel (a few consulting postings that list Office tools inflate them), warehouse temp work and marketing (15 postings, too few). Our Q3 2026 market report lays out the rest of the method.

Why freelancers report 103 and postings say 76

The Freelancer-Kompass 2026 from freelancermap, a survey of 5,412 freelancers between November 2025 and February 2026, puts the self-reported average hourly rate at 103 EUR (104 the year before, the first year without a rise). Our median ceiling is 76. Two caveats before reading anything into the 27 EUR difference: the Kompass is a mean of what people say, ours a median of what clients print, and the two groups are not the same people.

Still, 103 is above our upper quartile (91) and below our 90th percentile (112). The average freelancer reports a rate that between one posting in ten and one in four advertises. Our reading, and it is a reading rather than a finding, is that postings show the low-information end of the market. A printed number is a public anchor, and a client with an open budget keeps room above it. Experienced freelancers negotiate above what is printed. We cannot see agreed rates, so we cannot prove this. We can say that the posted number is where a conversation starts, not where it ends. (More on the income side in our piece on the 103 euro paradox.)

Place yourself in three steps

  1. Find your skill row, and the tier. Take the row for your main skill. If your work spans two (SAP plus data migration), take the higher one and check that you really do both.
  2. Add seniority. In the data a senior posting runs about 15 EUR above a mid-level one (85 against 70). If you are senior by the clients' own yardstick, start from the upper quartile of your row rather than the median.
  3. Check location and country. In the Q3 2026 sample (1,208 postings), hybrid roles posted a median of 85, remote 77, and on-site 40, the latter skewed by support and temp work. By country: Germany 77, Austria 82, Switzerland 100 (58 postings, as posted).

A worked example: a senior Kubernetes freelancer reads a median of 77 and an upper quartile of 90. As a senior in a hybrid role, 90 is a sensible base. That is our rule of thumb, not a measured rate.

When to quote above the posted ceiling

  • When no rate is printed. Ninety-five of a hundred postings say nothing. There is no ceiling to exceed. Ask for the budget, and anchor on the upper quartile of your row.
  • When you sit in the top quarter of your skill. If you can name the evidence (a migration you led, a certification the client requires), the row's upper quartile is your starting point, not your limit.
  • When the tag is wide. For rows like Project Management or Quality Assurance, the ceiling depends on the job. Read the role, not the tag.
  • When the client is in Switzerland. Posted ceilings run higher there (median 100, as posted, from 58 postings).

When not to: on a narrow row (Python, SQL), quoting 20 EUR over a printed ceiling usually ends the conversation. There, differentiate on scope, speed or availability and not on the hourly number.

To turn an hourly rate into a day rate and a yearly income, do not multiply by eight and 220: 187 billable days is the realistic base. And when it is time to ask for more, the 25 percent guide walks through how.

What to do on Monday

  1. Find your skill in the table and write down its lower quartile, median and upper quartile next to your current rate.
  2. Place your rate: below the median, between median and upper quartile, or above. If you are senior and below the median, that is the first thing to fix.
  3. Open three live postings in your skill. Note which print a rate and what the role asks for beyond the tag.
  4. Draft a quote sentence for open-budget postings: "My rate for this scope is X EUR, based on the upper end of the market for senior Y."
  5. Set a date to raise your rate with your next client, using the 25 percent guide.

Companies searching for freelancers find them by skill. A free 9am profile lists yours, and the job search over more than 100 boards shows you the postings in your own skill as they appear.

Rates are posted ceilings from scraped board data, not negotiated or invoiced rates. They are general information, not advice on pricing a specific contract.

Blago Yanakiev

Co-founder & CPO

Blago is a product leader and SaaS founder. He runs product at 9am and directs events and growth for the Freelance Unlocked conference.

9am profileLinkedIn

Latest Articles

Time Tracking for Freelancers in 2026: What Counts as Proof, What Clients Sign Off, and the Tools Compared

Time Tracking for Freelancers in 2026: What Counts as Proof, What Clients Sign Off, and the Tools Compared

'Development, 6 hours' will not survive a disputed invoice. What German courts expect from an hourly record, and nine tools priced.

A Client Just Left. The 30-Day Plan to Replace the Revenue (With Gabriella Yan, Ep. 81)

A Client Just Left. The 30-Day Plan to Replace the Revenue (With Gabriella Yan, Ep. 81)

Gabriella Yan lost clients and always found new ones. Her order of moves, turned into a four-week plan, with the caveat she gives herself.

Freelancer, Agency or Hire? What Each Really Costs a German Company in 2026

Freelancer, Agency or Hire? What Each Really Costs a German Company in 2026

A €90,000 employee delivers about 207 working days at roughly €520 each. Put that next to an €800 freelancer day and the picture changes.