The German job interview for engineers: the Fachgespräch, the trial day, and what to expect

You tuned the Lebenslauf, sent the Anschreiben, and the reply came back: they want to talk. This is the stage most guides skip — they stop at "submit" — and it's where international engineers most often misread the room. A German Vorstellungsgespräch (job interview) is not a US-style culture-fit gauntlet or a leetcode marathon. It runs on different assumptions, and they're learnable.

This is the engineer's version: what the rounds look like, what the technical conversation actually probes, and the etiquette that quietly counts. (Getting to the interview is its own game — for the search strategy around it, see Apply to 10 jobs a week, not 100.)

The shape of the process

Most German engineering hires run through three or four stages. Traditional Mittelstand firms and larger corporates tend to move at a deliberate pace; funded Berlin/Frankfurt scale-ups and the German offices of big tech often run a faster, more structured, more anglicised loop — so calibrate to the employer, not to a single "German" stereotype.

1. First screen (HR / recruiter) — historically a call about motivation, availability, rough salary range, and visa/relocation status. In 2026, expect this first gate to sometimes be automated instead: a one-way recorded ("async") video, or a short online coding test (Codility, HackerRank, CoderPad). Treat an async or AI-scored round as a real interview — structured answers, good lighting, and don't wait for a rapport that isn't coming.
2. The Fachgespräch (technical round) — the core. A conversation with engineers or the team lead about your actual work, sometimes with a take-home task or a live architecture discussion. Classic leetcode-style whiteboard puzzles are much rarer than in the US — at Mittelstand and mid-size firms. But the German offices of big tech (Amazon, Google) and well-funded Berlin/Frankfurt scale-ups do run full algorithm loops and timed online coding assessments. If those are your targets, prepare exactly as you would in the US.
3. Team / onsite round — meeting the people you'd work with (video-first if you're relocating from abroad). Some employers, especially smaller Mittelstand firms and agencies you can reach in person, invite a Probearbeit (trial day) around here — more on that below.
4. Final round / offer — often with a senior manager, then the Angebot (offer) and contract.

Two or three rounds is common. Between rounds, a slow cadence is normal at Mittelstand firms and corporates; a fast, tightly-scheduled loop is normal at scale-ups — neither is a bad sign. If a structured process does go quiet, a polite follow-up is fine.

What's different from a US/UK tech interview

• Depth over theater. Outside the big-tech/scale-up algorithm loops, German technical interviews lean toward "walk me through something real you built and the trade-offs you made" rather than timed puzzles. Be ready to go deep on one or two projects — the decisions, what broke, what you'd do differently.
• 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, non-defensive answer.
• The trial day (Probearbeit). Being asked to work alongside the team for a day is a genuine two-way audition — but know your rights. If you do real work, you must be paid for it: that's the law (§ 612 BGB), at least minimum wage. An unpaid multi-day "trial" doing production work is a red flag, not a norm to weigh. A brief unpaid observational visit (a Schnuppertag — you watch, you don't ship) is a different, legitimate thing. Note too that trial days mostly apply if you're already in Germany; interviewing remotely from abroad, you'll rarely do one.
• Less selling, more substance. The confident-narrative, metrics-everywhere US style can read as overclaiming here. State what you did and let the substance carry it — the same restraint the Lebenslauf rewards.

Inside the Fachgespräch

The technical round is where engineer-specific depth wins, so prepare for how it actually runs:

• They probe reasoning, not recall. Expect "why did you choose that database / framework / architecture?" far more than trivia. Have your reasons ready, including the trade-offs you rejected.
• One project, deeply. Pick a project you can defend end to end — requirements, design, the hard bug, the thing you'd change. Shallow breadth across ten projects loses to real depth on one.
• Take-home or live design. If there's a task, it's usually a small realistic problem or a system-design conversation. Clean, readable, well-reasoned beats clever.
• Never bluff a gap. German engineering culture prizes precision, and a caught bluff lands far worse than an honest "I haven't done that — here's how I'd approach it." Say what you don't know and reason from first principles.

Which language will the interview be in?

Don't assume English — this is the question that catches people out. Ask, before each round, which language it will be in. As a rule of thumb: German-heavy Mittelstand and hardware firms often run at least part of the Fachgespräch in German; English-first Berlin/Frankfurt startups usually interview in English but may still probe your German level, especially for customer- or team-facing roles. Whatever your CV claims, be ready to actually hold a conversation at that level — a "B2" on paper that collapses in the room is worse than an honest B1. If a role genuinely needs German you don't yet have, it's far better to surface that during the process than after you've signed.

The etiquette that quietly counts

• Sie by default. Address interviewers formally (Sie) unless they explicitly switch to first names / du — in many Berlin startups they will immediately; in a traditional Mittelstand firm they may not. Follow their lead, don't assume.
• Punctuality is real. Arrive 5–10 minutes early; for a video call, join on time. Lateness registers as a genuine mark against you in a way it might not elsewhere.
• Dress to the sector, not the stereotype. A Frankfurt finance-IT role skews formal; a Berlin startup, casual; much of the Mittelstand sits in between (smart-casual is a safe default). When unsure, slightly overdress.
• A firm greeting. A handshake and eye contact where offered; a simple, clear "Guten Tag" is fine even if the rest is in English.

Money, notice period, and references

• They will ask your salary expectation (Gehaltsvorstellung). Give a researched range in gross annual euros (brutto pro Jahr) — it's a normal, expected part of the conversation, often as early as the first screen. (Our Anschreiben guide covers how to pitch the number in writing.) One shift worth knowing: under the EU Pay Transparency Directive, employers are moving toward stating a salary or range up front, and asking candidates their current pay is set to become off-limits. Germany's implementation is running behind, but the direction is fixed and some employers already work this way — so you can ask for the band, and you never have to anchor yourself to a lower home-country salary.
• Notice period (Kündigungsfrist) shapes the timeline. If you're currently employed, German contracts often carry weeks-to-months of notice; be ready to state a realistic start date. Most contracts also open with a probation period (Probezeit) — up to six months, with a short two-week notice on both sides (§ 622 BGB).
• References work differently. Germany runs on the written Arbeitszeugnis (a coded employer reference) — which, as an international hire, you won't have in German form. That's fine and expected: say so, and offer a manager reference or LinkedIn recommendations instead.
• Relocation and visa are fine to raise. For roles hiring internationals, asking about relocation support and work-permit timelines is expected, not presumptuous. Keep the specifics of your own eligibility to primary sources — our how to apply in Germany guide covers the visa landscape at a high level.

They expect you to have questions

Ending with "no, I think you covered everything" reads as low interest. Have a few real ones ready — for engineers, the good ones surface how the team actually works:

• How is the team structured, and how are technical decisions made?
• 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 interview rewards depth, honesty, and preparation over performance: know one project cold, reason out loud, meet directness with directness, be punctual, confirm the language in advance, and treat salary and notice period as normal topics. Get that right and the Vorstellungsgespräch becomes a genuine two-way conversation about whether the fit is real.

Sources & further reading

The process and etiquette here are distilled from official German-government guidance and intercultural research; the legal points cite the statutes directly; and the "structured, depth-first interview rewards preparation" thesis rests on the personnel-selection literature. Where a claim is practitioner-reported rather than studied, it's flagged as such.

Official (German government / EU):

• Make it in Germany and deutschland.de — the Federal Government's guidance on the German job interview (punctuality, the two-minute elevator pitch, documents, and interview language).
• Statutes (Gesetze im Internet): pay for real trial work — § 612 BGB; probation and notice periods — § 622 BGB; your right to a written reference (Arbeitszeugnis) — § 109 GewO.
• EU Pay Transparency Directive (EU) 2023/970 — the salary-history ban and pay-range-disclosure rules (member-state transposition due June 2026).

Peer-reviewed research (why structured, depth-first interviews reward preparation):

• Levashina, Hartwell, Morgeson & Campion (2014), "The Structured Employment Interview: Narrative and Quantitative Review," Personnel Psychology — doi:10.1111/peps.12052.
• McDaniel, Whetzel, Schmidt & Maurer (1994), "The Validity of Employment Interviews: A Comprehensive Review and Meta-Analysis," Journal of Applied Psychology — doi:10.1037/0021-9010.79.4.599.
• Sackett, Zhang, Berry & Lievens (2022), "Revisiting Meta-Analytic Estimates of Validity in Personnel Selection," Journal of Applied Psychology — doi:10.1037/apl0000994. Structured interviews remain among the strongest predictors of job performance.
• Lukacik, Bourdage & Roulin (2022), "Into the Void: … Asynchronous Video Interviews," Human Resource Management Review — doi:10.1016/j.hrmr.2020.100789. On the rise of async / AI-assisted first-round screening.

Intercultural context (directness, formality, punctuality):

• Erin Meyer, The Culture Map (PublicAffairs, 2014) — places Germany among the most direct, low-context business cultures, consistent with Geert Hofstede's cultural-dimensions research (high uncertainty avoidance → structure, precision, punctuality).

Practitioner-reported (directional, not peer-reviewed):

• That big-tech German offices and well-funded scale-ups still run leetcode-style algorithm loops and timed online coding tests is drawn from candidate-reported interview experiences (Glassdoor, LeetCode discussions), not a formal study — treat the specifics as directional.

---

Prep starts with getting in front of the right roles. Match your CV against live German engineering roles — no account needed to try it. Getting to the interview is its own system — see Apply to 10 jobs a week, not 100 — and once conversations are in flight, track each one by the round it reached on your applications board.