How Long Does It Really Take to Hire a Developer in Germany?

Ask a hiring manager in Germany how long to hire a developer, and most will quote the search itself: four to eight weeks from job ad to signed offer. Ask them again three months after the candidate accepts, and the honest answer changes. The search was six weeks. The wait for that person to actually start was closer to five months on top of it.

That second number is the one companies plan around too rarely, and it is the one that determines whether a project ships on time or drifts into next year. This post breaks down where the time actually goes: sourcing, screening, interviews, the offer, and the legal notice period most German employment contracts require before someone can leave their current job.

Sourcing and screening: two to four weeks

For a mid-level or senior PHP, Symfony, or React developer, expect two to four weeks to build a shortlist worth interviewing. A recruiter or internal talent team posts the role, sources candidates who are not actively looking, and filters resumes. In a market where Bitkom has reported well over 100,000 unfilled IT positions in Germany, strong candidates are usually mid-conversation with two or three other companies by the time they respond to yours.

Screening calls add another few days per candidate, and companies that skip this step often pay for it later: they invite someone straight to a technical interview, discover in the first ten minutes that the role does not match what the candidate is looking for, and have to restart sourcing from a smaller pool.

Interviews and decision: two to five weeks

This is the stage companies most often let drag. A typical process runs a first-round conversation, a technical assessment (a take-home exercise, a pairing session, or a system design discussion), and a final round with the hiring manager or team. Each round needs scheduling time, and every extra week between rounds is a week a competing offer can land first.

Companies that move well here share one habit: they schedule the next round before the current one ends. Companies that move slowly usually have the opposite problem, where feedback sits in someone's inbox for a week because the hiring manager is traveling or the interview panel has not agreed on a decision process. For senior candidates specifically, a slow decision often functions as a rejection. They accept somewhere else and let your offer expire on its own.

If the process is dragging and you want a second opinion on where the friction is, our post on red flags and green flags when hiring senior developers in Germany covers the interview signals worth checking before you extend an offer.

The notice period: one to three months, and it starts after signature

Here is the part that catches non-German companies off guard. Once a candidate accepts your offer, they still have to resign from their current job, and German employment contracts routinely carry a notice period of one, two, or three months, sometimes tied to the end of a calendar month or quarter rather than a fixed number of weeks. A contract with a three-month notice period ending on the last day of a quarter can turn a resignation submitted in early April into a start date in July.

Senior developers and anyone with more than a few years at their current employer are the most likely to be locked into the longer notice periods, which is exactly the group companies are usually trying hardest to hire. The practical effect: your six-week search plus your candidate's three-month notice period is a four-and-a-half-month gap between deciding to hire and having someone at their desk, and that is the fast case where nothing else goes wrong.

Why the real timeline often stretches toward a year

Add the pieces together and the picture looks different from the one in most hiring plans. Sourcing and screening take three to four weeks. Interviews and the offer take another three to five weeks. Notice periods add one to three months, often landing on a quarter boundary that adds extra weeks beyond the stated period. Onboarding to real productivity, where a new developer is shipping work independently rather than still ramping up, typically takes another four to eight weeks depending on the codebase.

Stack the slower end of each stage and you are looking at nine to twelve months from the day you decide you need someone to the day they are contributing at full capacity. Companies that budget six weeks for "hiring a developer" and then wonder why the timeline blew past a year are usually not doing anything wrong. They are just measuring the visible part of the process and missing the notice period, which is the largest single component and the one you have the least control over.

What you can actually shorten

Some of this timeline compresses with better process. Faster feedback loops between interview rounds, a technical assessment that respects the candidate's time, and a hiring manager who is available to make a decision within a week all cut real time off the search phase. None of that touches the notice period, though, because that clock belongs to the candidate's current employer, not to you.

What does help with the notice period is starting the search earlier than instinct suggests. If a role will likely go to a senior candidate with a long notice period, starting the search three months before you actually need the person is not overly cautious. It is closer to the realistic minimum.

Berlin and Munich move differently

The timeline above is a national average, and the two biggest tech hubs pull it in different directions. Berlin has a larger pool of developers and more freelancers who can start with shorter notice, which can shave a few weeks off the search phase for mid-level roles. Munich has a higher concentration of large employers with structured career ladders, and candidates there are more likely to be on the longer three-month notice periods that come with more senior, more established positions. Neither city changes the legal notice period once someone has signed a contract, but Berlin's larger candidate pool means you are less likely to be stuck relying on one strong applicant with a long notice period as your only option.

Remote-friendly roles complicate the comparison further. A company willing to hire outside Berlin or Munich opens up a bigger pool immediately, but it does not shorten anyone's existing notice period, so the sourcing phase gets faster while the wait after signature stays the same.

What can run in parallel while you wait

The months between signature and first day do not have to be dead time. Onboarding documentation, environment access, and codebase orientation materials can all be prepared before the new hire's first day, so the ramp-up clock starts earlier in practice than it does on paper. Some companies also use the gap to bring in short-term technical support, whether that is contract development work to keep a roadmap moving or a code review to catch issues before the new hire inherits them, so the project is not simply on hold for months.

If your team is staring down a multi-month gap between a signed offer and a start date, and the project cannot wait, custom software development support can keep things moving without committing to a second full-time hire. We have covered both ends of this problem for companies in Germany, from the interview process itself to bridging the gap while a new hire serves their notice.

If you want to talk through your specific timeline, current headcount plans, or where a hiring process might be losing time, reach out to hello@wolf-tech.io or find more detail on wolf-tech.io. A short conversation is often enough to spot which stage is costing you the most weeks.