Salary Negotiation After Probation in Germany

Six months ago you signed a contract. The number on it was a compromise. Maybe you lacked comparison data. Maybe you wanted the job badly enough to skip the negotiation. Maybe the recruiter asked for your salary expectations early, and you answered before you understood the role.

That was six months ago. Since then, you have learned the stack, integrated into the team, and delivered real results. You have a better picture of what the position is worth and what others in comparable roles earn. Something else has shifted too: your employer evaluated you during probation and decided to keep you. At the time you signed, that outcome was still uncertain.

Yet most developers never ask for a salary conversation after probation. They wait for the annual review or until they are frustrated enough to quit. Both approaches leave money on the table. This guide shows you why the end of probation is your strongest internal negotiation moment, how to prepare, and what to say.

Why the end of probation is your strongest internal lever🔗

What changed after six months🔗

During probation, either side can terminate the contract with two weeks notice. After probation, notice periods extend to one to three months, depending on the contract and tenure. By letting probation end without action, your employer made a decision: you stay.

That decision is not symbolic. Behind it are onboarding costs already spent. Projects you have been ramped into. Team dynamics that have adjusted to include you. If the company loses you now, the entire process restarts: job posting, screening, interviews, onboarding. Depending on the role, replacement costs run between 15,000 and 30,000 euros, often higher.

You know this math. Your employer knows it too. That changes the negotiating dynamic.

What employers calculate when they might lose you🔗

Imagine you earn 60,000 euros gross and ask for an increase to 66,000. That is 6,000 euros more per year. For your employer, that figure is manageable compared to the cost of replacing you: recruiter fees (typically 20 to 30 percent of the new hire’s annual salary), three to six months of reduced productivity during onboarding, and the real chance that the next candidate will cost more than what you are asking for now.

This does not mean every request goes through automatically. But it does mean that a professionally conducted salary conversation after probation carries virtually no risk for you. Your employer will not fire you for asking. They will either name a number, suggest a timeline, or explain why there is no room right now.

Preparation: Three steps before the conversation🔗

Step 1: Back up your market position with data🔗

Before you request a meeting, you need to know whether you are actually paid below market, and by how much. A gut feeling is not enough. You need numbers.

Benchmark your gross annual salary against at least two independent sources. The StepStone Salary Report provides broad data by region and role. levels.fyi is the best source for larger tech companies with level-based pay structures. Kununu covers the Mittelstand and smaller employers better than international platforms.

The overlap between these sources gives you your realistic market range. If your current salary is 10 percent or less below the median, your argument is weaker since you are technically paid at market rate. If you are 15 percent or more below the median, you have a clear, data-backed case.

One thing that often trips up international developers: all salary discussions in Germany happen in gross annual salary (Bruttojahresgehalt). If you are thinking “I need 500 euros more net per month,” convert that into the gross equivalent before you speak to anyone.

Step 2: Document your contribution over six months🔗

Market data shows what the role is worth. Your contribution shows why you personally deserve more than the current number. Together, these form your argument.

Review the past six months and write down three to four concrete points. Projects you were meaningfully involved in. Problems you solved, ideally with measurable outcomes. Areas where you became productive faster than expected. Knowledge or practices you brought to the team.

This does not need to be a formal document. Half a page of bullet points is enough. The purpose is to anchor the conversation on value, not on tenure or loyalty. “I have been here six months” is not an argument. “In six months I delivered X, Y, and Z” is.

Step 3: Set your target number and your floor🔗

Decide two numbers before the meeting: your goal and your walk-away threshold.

Your goal should be 10 to 15 percent above your current salary, provided market data supports it. If you earn 58,000 euros and the data shows 65,000 to 68,000 for your role and city, then 65,000 is your target. Not “a bit more,” not “somewhere around 63,000.” Concrete numbers lead to concrete responses.

Your floor is the number at which you start thinking seriously about a job change. You do not need to mention it in the conversation. But you need to know it so you do not accept something out of nervousness that will frustrate you three months later.

[1] CodingCareer's salary negotiation coaching includes market data analysis and mock negotiation for exactly this scenario.

Having the conversation🔗

Requesting the meeting🔗

The conversation does not happen in passing. You ask for a dedicated slot by email or Slack. The wording matters.

Write: “Hi [Name], I would like to have a brief conversation about my compensation now that probation is complete. Would you have 20 minutes sometime in the next two weeks?”

Two things to notice. First: “compensation,” not “raise.” Compensation sounds businesslike. A raise request sounds like a demand. The distinction is subtle, but it shapes the mindset your manager brings to the table. Second: you give a two-week window. That is not pressure, but it prevents the request from being deferred indefinitely.

The opening: value first, number second🔗

Start with your contribution, not with a number. Whoever establishes value first and names the number second negotiates from a stronger position than whoever leads with the ask.

Weak opening: “I would like to earn 65,000 euros.”

Strong opening: “The past six months have shown that I make a concrete contribution in [area]. [Example.] I have researched my market value and found that my current salary does not fully reflect it. I would like to discuss an adjustment to [number].”

The structure is: contribution, evidence, market basis, number. In that order. Everything you prepared in the previous steps feeds into this moment. The number comes last because by then it is already supported by two arguments.

The three typical reactions and how to handle them🔗

After your opening, one of three things happens.

“Let me discuss this internally.” The most common reaction at mid-size and larger companies. This is not a rejection. It means your manager cannot decide alone and needs budget approval. Clarify the next step immediately: when will you have an answer? Send a brief follow-up email afterward summarizing what was discussed.

“We can increase to X.” If X meets your target, accept. If X falls short, ask calmly: “That is a step in the right direction. I had [number] in mind. Is there room to close the gap?” A factual follow-up question is not confrontation. It is professional negotiation.

“That is not possible right now.” Ask for the reason. Budget? Timing? Company policy? The answer determines your next move. For budget, pivot to benefits (more on that below). For timing, agree on a specific follow-up date. For policy, you now have important information about how this company manages compensation.

The five most common mistakes🔗

Waiting too long🔗

The further you get from the end of probation, the weaker your lever becomes. After three months, your salary is the new normal. Your employer has gotten used to paying you that amount. The urgency to adjust fades with every week.

The probation review meeting, if one is scheduled, is the most natural entry point. If there is no review, request a meeting within the first two weeks after probation ends.

Arguing from personal need🔗

“Rent went up” or “my partner is between jobs” are not negotiation arguments. Your employer pays for the value you deliver, not for your cost of living. Every argument you bring should rest on market data or your concrete contribution.

Framing the number softly🔗

“A bit more would be nice” hands control of the number to the other side. The response to a vague ask is always vaguer than the response to a concrete one. Name a number. The conversation immediately becomes more specific, and you are taken more seriously.

Settling for the status quo🔗

“I am just glad I have this job” is a thought that stops many developers from negotiating after probation. Understandable, but it confuses gratitude with passivity. You can be happy with your role and still observe that your salary does not match market rate. The two are not mutually exclusive.

Treating the conversation as a single shot🔗

If you receive a no today and agree on a clear timeline for the next conversation, that is not failure. You have signaled that compensation matters to you. You have a follow-up date. That is the beginning of a process, not the end of one.

If the answer is no🔗

Negotiate benefits when salary is blocked🔗

When the salary budget is exhausted, there is often room on other line items. Additional vacation days are the easiest win because they cost the company relatively little on paper. Moving from 28 to 30 days is achievable at many companies and noticeably improves your quality of life. Anything below 30 vacation days in a tech role is already a signal that the company is not competitive on compensation.

Other levers: a remote work arrangement (written into the contract, not just a “team agreement”), a training budget (one conference or course per year), flexible working hours. These are not consolation prizes. Two extra vacation days and a 2,000-euro training budget have real economic value.

Get the timeline in writing🔗

If your manager says “we can revisit this next quarter,” write it down. Send a brief message three weeks before the agreed date: “I wanted to follow up on our conversation from [date]. Does [date] work for a quick update?” That sounds professional, not pushy.

Start a parallel job search🔗

If the conversation reveals that the company is structurally unwilling to pay at market rate, that is valuable information. You do not need to quit immediately. But running a job search while still employed gives you the strongest possible negotiation position for a move. You make no decision under pressure.

The conversation plays out differently depending on where you work. At startups and scale-ups, the founder or head of engineering often decides directly, which can be fast, but the budget may genuinely be tight. Equity adjustments or faster review cycles are realistic alternatives here. At mid-size tech companies, internal salary bands often exist that your manager cannot override alone. Expect the answer to come after internal alignment. At large corporations and DAX companies, the processes are most rigid. Increases outside the annual review cycle are possible, but you need to advocate actively and document the process.

How CodingCareer helps with the post-probation salary conversation🔗

Negotiating salary with your own manager is psychologically harder than negotiating at a new employer. You see this person every day. You do not want to damage the relationship. You have no idea how they will react.

CodingCareer’s salary strategy coaching addresses exactly this situation. You prepare the conversation with someone who understands the German tech market, can anticipate typical manager reactions, and gives you honest feedback. It starts with an analysis of your market position: where do you stand compared to other developers with your experience in your city? How large is the gap between your current salary and what you can realistically ask for? From there, you move into a simulated negotiation where you practice the opening, respond to counterarguments, and learn to sit with silence instead of lowering your own ask.

The coaching is part of the The Salary Jump and High-Pay Tech Strategy packages. The pay-on-success model ensures CodingCareer’s incentives align with yours: you pay a reduced amount upfront and the rest only after you reach your goal.

Book your free 15-minute diagnostic call and find out whether your current situation calls for an internal negotiation, a job change, or both.