The software engineer interview in Germany: the Fachgespräch, system design, and take-homes

You found the roles (part one) and shaped the CV (part two). Now they want to talk. This is the stage most guides skip — they stop at "submit" — and it's where international developers most often misread the room. There's a catch, though: the German software interview varies more by employer type than by country. A traditional Mittelstand firm runs a very different process from an English-first Berlin scale-up or a US-headquartered big-tech office — and the biggest mistake is assuming one "German style" you can prepare once. It runs on different assumptions, and they're learnable.

The shape of a software hiring process

Expect three or four stages at a traditional firm, and five or six at an English-first scale-up or US-HQ'd employer, at a more deliberate pace than the US tech norm:

1. Recruiter / HR screen — usually a call. Motivation, availability, rough salary range, visa/relocation status if you're abroad. Not deeply technical.
2. An online coding screen — common at scale-ups, fintechs and big-tech offices (Codility, HackerRank, CoderPad), often two medium algorithm problems. Rare at Mittelstand and traditional firms. If you're aiming at the English-first roles part one points to, assume it's there until you learn otherwise.
3. The technical round(s) — at traditional employers this is the Fachgespräch: a depth conversation with engineers or the team lead about your actual work. At scale-ups it's usually split into a live-coding / pair-programming round and a system-design round. A take-home task can appear at either.
4. Team / values round — meeting the people you'd work with; US-influenced employers (Amazon in particular) run a structured behavioural/values interview here. Occasionally a paid trial (Probearbeit), mostly at smaller firms — it's rare in software.
5. Final round / offer — a senior manager, or at a startup the founder / CTO, then the Angebot (offer) and contract.

One thing that unsettles candidates applying from abroad: the pace between stages is genuinely slow. A week or two of silence is normal, not a rejection, and a polite follow-up after ~10 working days is fine.

How much leetcode? It depends on the employer

The single most important thing to get right — and where a lot of "interviewing in Germany" advice is wrong: there is no single answer to whether you'll face timed algorithm puzzles. It splits cleanly by employer type:

• Traditional German product/enterprise firms and the Mittelstand lean away from leetcode and toward "walk me through something real you built and the trade-offs you made." Depth over puzzles.
• English-first Berlin/Munich scale-ups, fintechs, and US-headquartered big tech — exactly the well-paid, visa-sponsoring roles part one points you toward — do run algorithm screens, often as the first technical gate (N26, HelloFresh, Datadog, and Amazon's and Google's German offices all do). Skipping data-structures-and-algorithms prep because "Germany doesn't do leetcode" is how strong candidates get filtered out at these companies.

So the real instruction is: the format is company-specific, not country-specific — look the employer up on Glassdoor or Blind before you prep. That said, across most of the market the following carry more weight than raw puzzle speed, so prepare them regardless:

• The one-project deep dive. Pick a project you can defend end to end — requirements, design, the hard bug, the thing you'd change. Real depth on one system beats shallow breadth across ten.
• System / architecture design. A conversation about how you'd structure a service: data model, scaling, failure modes, trade-offs you rejected and why. Clarity and reasoning beat buzzwords.
• A take-home task, sometimes — usually a small, realistic problem, not a puzzle. Clean, readable, well-tested beats clever. Treat it like code you'd actually ship.
• Reasoning over recall. "Why that database / framework / queue?" far more than trivia. Have your reasons — including the options you rejected.

Domain honesty matters. German engineering culture values precision: if you don't know something, say so and reason from first principles. Bluffing lands far worse than an honest gap, and the technical round is designed to find the seams.

Directness is a feature

Interviewers may push back on a technical claim or point out a gap plainly. This is engagement, not hostility — meet it with a straight answer, including "I haven't done X, but here's the closest thing I've built." The confident-narrative, metrics-everywhere US style can read as overclaiming; state what you did and let the substance carry it.

The etiquette that quietly counts

• Sie by default. Address interviewers formally (Sie) unless they switch to first names / du — many Berlin startups will immediately; a traditional employer may not. Follow their lead.
• Punctuality is real. Arrive 5–10 minutes early; join a video call on time. Lateness registers as a genuine mark.
• Dress to the sector. Berlin startup: casual. Frankfurt finance-IT: smarter. Smart-casual is a safe default; when unsure, slightly overdress.

Money, notice period, and relocation

A rough 2026 sanity check before you name a number (it varies widely by city, stack and company — Munich and Stuttgart pay at the top, Berlin close behind): junior engineers land around €45–55k, mid-level €60–80k, and senior €85–110k+, with AI/ML and specialist roles higher. Pull a real benchmark for your city and stack — Levels.fyi, the StepStone Gehaltsreport, Glassdoor — before the call.

• They will ask your salary expectation (Gehaltsvorstellung) — often at the HR screen. Give a researched figure in gross annual euros (brutto pro Jahr), as a tight range or a single number: German HR tends to anchor to the lower end of whatever you name, and quote your base (flag any 13th-month payment or bonus separately). (One shift to watch: as Germany transposes the EU Pay Transparency Directive in 2026, more employers will publish a pay range up front and stop asking your salary history.)
• If you need a visa, your number is also a visa gate. The 2026 EU Blue Card thresholds are €50,700 gross per year in general and €45,934.20 for shortage occupations (which cover most IT and engineering roles) and recent graduates. Name a Gehaltsvorstellung below the figure that applies to your role and you can talk yourself out of the Blue Card. (Whether a specific role qualifies is for you and the employer to confirm — treat this as the floor to clear, not a promise.) Self-taught or bootcamp developers without a degree can still qualify via the IT-specialist route — roughly three years of relevant IT experience in the last seven — at that reduced threshold. Already in Germany on a Blue Card and switching jobs? A change of employer in your first 12 months usually still needs the immigration office's sign-off — check the specifics for your case — and the new salary must still clear the threshold.
• Notice period (Kündigungsfrist) shapes your start date; German contracts often carry weeks-to-months of notice, plus a probation period (Probezeit) of commonly up to six months (with a short two-week notice during it). If you already hold a German contract, that notice is what sets your start date. On a first move from abroad, it's instead your current (home-country) employer's notice plus visa processing — not something you already owe a German employer.
• Relocation, visa, or neither — raise it early. For roles hiring from abroad, asking about relocation support and work-permit timelines is expected; needing sponsorship is a real filter, though — Berlin scale-ups, big tech, and shortage-occupation roles sponsor routinely, while many Mittelstand employers won't take on the paperwork, so aim where sponsorship is normal. If you're already in Germany with the right to work, lead with it — no sponsorship, no relocation timeline, available for onsite rounds, and a quick start once your notice is served is a genuine edge over an abroad candidate for the same role. No offer yet and still abroad? The Chancenkarte (Opportunity Card) and the job-seeker visa are legitimate routes to arrive and search on the ground. Keep your own eligibility specifics to primary sources; our how to apply in Germany guide covers the visa landscape at a high level.

Have questions ready

Ending with "no, you covered everything" reads as low interest. Good engineer questions surface how the team really works:

• How are technical decisions made, and how is the team structured?
• What does on-call / incident response look like?
• How do you balance new features against tech debt?
• What's the remote / hybrid policy in practice, not just on paper?

The bottom line

The German software interview rewards depth, honesty, and preparation: know one system cold, reason out loud, meet directness with directness, be punctual, and treat salary and notice period as normal topics — and, for the English-first and big-tech roles, put in the algorithm prep too. Get that right and the interview becomes a genuine two-way conversation about fit.

The best interview prep is getting in front of the right roles in the first place. Match your CV against live German software roles — no account needed to try it — or revisit the developer's German CV from part two.