Changing Jobs After 1 Year as a Developer in Germany

Twelve months into the job. The work has drifted from what was discussed in the interview. The tech stack that sounded exciting on paper turns out to be a legacy monolith with no migration plan. Or maybe the culture makes you feel like you are burning years instead of building skills. Sunday evenings get heavier.

Then the question: Can I leave after just one year, or will it wreck my CV?

Short answer: A single departure after one year is not a problem in the German tech market. Three departures in three years is. The difference comes down to your explanation and the overall pattern. This guide gives you the framework to make the right decision, understand the legal basics, and communicate the change in a way that does not cost you opportunities.

What German Recruiters Actually Think About Short Tenures🔗

One Change Is Not a Pattern🔗

The idea that you need to stay at least three years at every company persists. In practice, the German tech market has moved past it. Hiring managers know that companies restructure, roles shift, and not every position delivers what was promised.

What recruiters actually evaluate is not the duration of a single role. It is the overall picture. One departure after a year stands out. Two departures in two years raise questions. Three positions in three years, all under twelve months, gets read as a risk signal because the pattern suggests the candidate either makes poor decisions or struggles to settle in.

A single short tenure with a coherent explanation? For most tech recruiters, that is a non-issue.

What Actually Stands Out on Your CV🔗

Recruiters in Germany scan a CV in a few seconds. The question is not whether they notice the one-year stint. Of course they notice it. The question is what they do next.

If the rest of your CV shows stability, say two to four years at previous employers, a short tenure reads as a one-time exception. If your CV is a series of short stints, each one becomes evidence of a pattern.

Context matters. One year after three years at a previous employer tells a very different story than one year after another eight-month role.

Five Signs You Should Leave After One Year🔗

Not every urge to leave is justified. Sometimes frustration is temporary, and a conversation with your manager resolves the issue. But there are clear signals where staying is the worse option.

1. The role does not match what was agreed. The interview promised microservices. The reality is a ten-year-old monolith with no migration plans. The scope has fundamentally diverged from what was discussed. This is not a loyalty problem. This is a job that does not exist.

2. You have stopped learning. After twelve months, you are doing the same tasks you were doing after three months. No new challenges, no room to grow into other areas, no prospect of change. Stagnation in tech has real costs. Every year without growth makes your next move harder, not easier.

3. The culture is harming you. Toxic leadership, no psychological safety, meetings where ideas are systematically shut down. You do not need to spend three years in an environment that drains your energy and confidence. That is not entitlement. That is self-preservation.

4. You have a concrete better offer. Significantly higher compensation, a stronger role, or a tech stack you genuinely want to learn. Loyalty to an employer who has made no special commitments to you costs real money.

5. The company is unstable. Industry layoffs, hiring freezes, leadership changes every quarter. If the ship is sinking, leaving early is not weakness. It is risk management.

Three Reasons to Stay🔗

You are still actively learning. Even if the pace is slower than expected: as long as you are building new skills and working on challenging problems, the role is serving its purpose.

A major project is close to completion. A completed project on your CV is significantly more valuable than an unfinished one. If you are three months from launch, it usually makes sense to see it through.

The problems are solvable. Sometimes dissatisfaction comes from a communication gap with your manager or a task distribution that can be changed. An honest conversation might reveal that the situation is fixable. Have that conversation before you resign.

Probezeit, Notice Period, Arbeitszeugnis: The Legal Basics🔗

Probezeit (Probation Period)🔗

Almost all German employment contracts include a Probezeit of up to six months. During this period, either party can terminate with two weeks notice, no reasons required.

For early departures, the Probezeit creates a strategic timing question. If you know after six months that the role is wrong, it may be more practical to act during the Probezeit and take advantage of the short notice period. Waiting another six months extends your tenure to a year but does not change the underlying situation.

A five-month tenure on your CV requires more explanation than a full year. But it is not career-ending. And the two-week exit window during Probezeit can save you months of time.

Notice Period After Probation🔗

The statutory notice period for employees is four weeks to the 15th or last day of the month. Your contract may specify a longer period, commonly one to three months.

Concrete example: if you have a three-month notice period and want to start a new role in October, you need to resign by the end of June at the latest. The job search in Germany typically takes three to six months. Start looking before you resign, not after. That way you avoid a gap on your CV.

Arbeitszeugnis After a Short Tenure🔗

You have a legal right to a qualifiziertes Arbeitszeugnis (qualified reference letter) in Germany, even after one year. Request it in writing as soon as your resignation is confirmed.

A reference letter for a short tenure will naturally be shorter. Still, pay attention to the coded language: “Stets zu unserer vollsten Zufriedenheit” (to our fullest satisfaction at all times) is the top grade. “Zu unserer Zufriedenheit” (to our satisfaction) is a warning sign. If you receive a reference you consider unfair, you have the right to request corrections.

Our Arbeitszeugnis decoding guide explains the codes in detail.

How to Explain the Change in Applications🔗

In Your CV🔗

Do not try to hide a short tenure. Using years only (“2025 - 2026”) without months looks like an attempt to obscure the timeline and invites questions. Write month and year for both start and end: “Jun 2025 - Jul 2026”. Clear and unambiguous.

If the reason was clearly company-driven, restructuring, department closure, you can add a brief note: “Jun 2025 - Nov 2025 (position eliminated due to restructuring)”. This answers the question before it is asked.

What matters far more than tenure length on your CV: show what you accomplished in that one year. A concrete result (“Migrated payment API to new gateway, reduced error rate by 40%”) weighs heavier than any question about why you only stayed twelve months.

Our guide to CV standards in the German tech market covers how to optimize for the 6-second recruiter scan.

In the Interview🔗

The question about the early departure will come. Count on it. Prepare a clear answer that does three things: states the reason factually, points forward, and does not invite follow-up probing.

The basic rule: state the reason in one to two sentences. Do not give a novel. Do not criticize the former employer. Pivot immediately to what you are looking for next.

For preparation on the full HR round, not just the departure question, see our HR interview guide.

Salary When Changing Jobs: The Real Lever🔗

A job change is the strongest salary lever you have as a developer in Germany. Internal raises typically land at 3 to 5 percent per year. When switching employers, 10 to 20 percent is common.

But “I’m underpaid” is not an argument in a job interview. Employers do not care what you currently earn. They care what someone with your experience and profile is worth on the market. Argue from market value, not from your current number.

That requires two things: current salary data for your target position and a clear negotiation strategy. Our salary negotiation guide covers both in detail.

What a Single Early Departure Means Long-Term🔗

One job change after one year leaves a mark on your CV. But what that mark means depends on what comes next.

If you leave after one year and stay three or four years at the next company, the short tenure reads as a one-time course correction. That is coherent and understandable. If you leave after one year and also leave the next role after eight months, a pattern emerges that becomes hard to explain.

The Two-Year Rule for the Next Job🔗

Plan realistically: if you leave after one year, the next role should last at least two, ideally three years. Not out of obligation, but because your CV tells a cumulative story. One short tenure between two longer ones is a story. Two short tenures in sequence is a problem.

This also means investing in choosing the next role carefully. Clarify in the interview exactly what to expect. Ask about the team, the tech stack, the roadmap. If you left because the role did not deliver what was promised, make sure the next set of promises is more concrete.

How CodingCareer Helps With a Job Change🔗

Leaving after a short tenure puts three challenges on your plate at once: presenting the CV so the short stay does not become an obstacle, handling the departure question confidently in interviews, and negotiating salary correctly with the new employer.

CodingCareer specializes in guiding developers through exactly this process. CV optimization restructures your resume according to German standards, with measurable results instead of task descriptions, optimized for the 6-second recruiter scan. Mock interviews with an HR focus let you rehearse the departure question under realistic conditions and get concrete feedback on how your formulation lands. Salary negotiation sessions work with current German market data so you do not start below your value at the next employer.

The pay-on-success pricing model means you pay a reduced amount upfront and the rest only after you land the job. CodingCareer succeeds only when you do.

Book your free 15-minute diagnostic call and get an honest assessment of where you stand and what the next step is.