How to Pass the HR Interview at German Tech Companies

You spent two weeks grinding LeetCode. You reviewed system design fundamentals. You polished your CV three times. Then the HR screening call comes, and 25 minutes later you get a rejection email that says nothing useful. What happened?

The HR interview is where most candidates lose their shot, and it is the round they prepare for least. Developers tend to treat it as a formality, something to survive before the “real” interviews start. In Germany, this assumption is especially dangerous. The HR round is not a warm-up. It is a structured evaluation with specific pass/fail criteria, and the person conducting it has the authority to end your candidacy before a single engineer sees your code.

This guide covers what HR at German tech companies is actually screening for, the questions you will face in almost every first-round call, how to handle salary expectations without giving up leverage, and the cultural norms that catch both international and local candidates off guard.

What the HR Interview Actually Is🔗

The Gatekeeper Function🔗

At most German tech companies, the hiring process starts with a 30- to 45-minute call with someone from HR or People Operations. This person is not a developer. They are not evaluating your technical skills. They are evaluating whether you should be allowed to take up the engineering team’s time.

The HR screener is checking a specific set of boxes: Does this person communicate clearly? Do their salary expectations fall within the budget? Are they genuinely interested in this company, or are they spraying applications? Will they fit into the existing team without creating friction? Do they have the right to work in Germany, or will the company need to sponsor a visa?

If you fail any of these checks, you will not proceed. And because HR professionals handle dozens of screening calls per week, they pattern-match fast. You have roughly the first five minutes to establish credibility. The rest of the call either confirms or overturns that initial read.

HR Round vs. Technical Round: What Each Tests🔗

One of the most common mistakes is preparing for the HR call the same way you prepare for a technical interview. The evaluation criteria are entirely different.

The technical rounds test whether you can do the job. The HR round tests whether the company wants to work with you. Both are elimination rounds, but the HR round comes first, and there is no partial credit.

The Six Questions You Will Almost Certainly Get Asked🔗

German HR interviews follow a remarkably consistent script. The specific phrasing varies, but the underlying questions are the same across startups, Mittelstand companies, and corporations. Here is what to expect and how to handle each one.

”Erzählen Sie etwas über sich” (The Selbstpräsentation)🔗

This is always the opening question. In German interview culture, the Selbstpräsentation is not small talk. It is a structured self-introduction that HR uses to evaluate your communication skills, career narrative, and professionalism. You are expected to speak for two to three minutes without rambling.

The most effective framework for developers is Present-Past-Future:

Present: Start with your current role and what you do. “I’m a backend developer at [Company], where I work primarily with Java and Spring Boot on a payments microservice.”

Past: Briefly explain how you got here. Focus on decisions, not a chronological résumé recitation. “Before that, I spent three years at a fintech startup where I transitioned from full-stack to backend because I found I was most effective when I could focus on API design and data modeling.”

Future: Connect your trajectory to this specific role. “I’m looking to move into a larger engineering organization where I can work on higher-scale systems, which is why this position caught my attention.”

Keep it under three minutes. Do not start with your university degree unless it is directly relevant. Do not list every technology you have ever used. The Selbstpräsentation is a story, not a specification sheet.

”Warum dieses Unternehmen?” (Why This Company?)🔗

HR asks this to filter out candidates who are applying indiscriminately. A generic answer like “I admire your company culture” or “I’m excited about your mission” signals that you did not bother researching.

The fix is specific research. Read the company’s tech blog if they have one. Check their engineering talks on YouTube. Look at their open-source contributions on GitHub. Read recent press coverage or funding announcements. Then connect something concrete to your own experience or goals.

A strong answer sounds like: “I read your engineering blog post about migrating from a monolith to event-driven architecture. I’ve been working on a similar migration at my current company, and I’d be interested in working with a team that has already navigated the challenges I’m currently facing.”

This takes 15 minutes of research. It makes you stand out from candidates who clearly Googled the company five minutes before the call.

”Was sind Ihre Gehaltsvorstellungen?” (Salary Expectations)🔗

This question comes up in almost every German HR screening, often within the first ten minutes. Many companies even require salary expectations in the application itself.

The trap is answering too precisely too early. At this stage, you lack information about the role’s full scope, the team, and what the company actually budgets. But refusing to answer at all can feel adversarial in the German context, where directness is valued.

The middle ground: give a researched range and signal flexibility. “Based on my research for this role and experience level in [city], I’d expect something in the range of X to Y gross annually. I’m open to discussing this further once I understand the full scope of the position.”

Always state gross annual salary (Bruttojahresgehalt). Never quote net figures. And make the bottom of your range a number you would genuinely accept. For a deeper walkthrough of salary negotiation tactics, including when and how to counter-offer, see our guide to salary negotiation in German tech.

”Warum wollen Sie wechseln?” (Why Are You Leaving?)🔗

HR is not asking this out of curiosity. They are screening for red flags. A candidate who complains about their current employer, talks about internal conflicts, or describes their manager negatively raises an immediate concern: will this person say the same things about us in a year?

Frame your departure around growth, not escape. “I’ve learned a lot in my current role, but I’ve reached a point where the technical challenges are not growing with me. I’m looking for an environment with larger-scale systems and a stronger engineering culture.”

Even if you were fired, restructured out, or leaving a genuinely toxic workplace, the HR call is not the place for the full story. Keep it professional and forward-looking. The goal is to show that you are moving toward something, not running from something.

”Wo sehen Sie sich in fünf Jahren?” (Five-Year Plan)🔗

International candidates sometimes find this question odd. In many markets, five-year plans feel outdated or overly corporate. In Germany, this question serves a specific function: HR wants to know whether you intend to stay.

German hiring processes are expensive and slow. Companies invest heavily in onboarding. If your answer suggests you see this role as a stepping stone to something else entirely, or that you plan to leave Germany, HR will note it as a risk.

The best answers connect your growth plans to the company’s trajectory. “In five years, I’d like to have grown into a senior engineering role where I’m mentoring junior developers and contributing to architectural decisions. I see that path here given the team structure you described.” You do not need to commit to a decade. You just need to demonstrate that your plans and the company’s investment in you are aligned.

”Haben Sie Fragen an uns?” (Your Questions)🔗

In German interview culture, this is not a courtesy. It is evaluated. Having no questions signals either low interest or poor preparation. Having only logistical questions (“How many vacation days?”) signals that you are already negotiating before you have earned the offer.

Strong questions demonstrate curiosity about the role itself:

• “What does a typical sprint cycle look like for this team?”
• “How does the engineering team handle technical debt alongside feature work?”
• “What is the onboarding process for new developers?”
• “What prompted the opening for this role?”

Prepare three to four questions. You will likely get to ask two or three of them before time runs out. Asking about the team’s working style also gives you valuable information for deciding whether you actually want the job.

Cultural Norms That Trip Up Candidates🔗

Sie vs. Du: Reading the Room🔗

German has two forms of “you”: the formal Sie and the informal Du. In traditional companies and most Mittelstand firms, the interview will use Sie throughout. At Berlin startups and international tech companies, the switch to Du might happen in the first email.

The safe default: use Sie until the interviewer explicitly offers Du. If the job posting uses Du, you can mirror that in your application and interview. If you are unsure, err on the side of formality. Nobody has ever lost a job offer for being too polite. The reverse is not true.

Directness Is Not Rudeness🔗

German interviewers tend to be more direct than what candidates from the US, UK, or many Asian countries expect. If an HR person says “That does not answer my question,” they are not being hostile. They are redirecting you because your answer was off-target.

The flip side: German interview culture also values honest self-assessment over self-promotion. Saying “I’m not deeply experienced with Kubernetes, but I’ve worked with Docker extensively and I’m confident I can ramp up quickly” is a stronger answer in Germany than claiming expertise you do not have. HR professionals here are trained to probe claims, and getting caught in an exaggeration is worse than admitting a gap.

Punctuality and Process🔗

For video calls, “on time” means your camera and microphone are tested and you are ready at the scheduled minute. For in-person interviews, arriving five minutes early is standard. Arriving late without advance notice is a serious negative signal in German business culture.

The interview itself will typically follow a structured format: introductions, the company presents itself briefly, your Selbstpräsentation, their questions, your questions, next steps. Do not be surprised if it feels procedural. That structure is intentional. German HR departments often use standardized evaluation forms (Bewertungsbögen) to score candidates consistently across interviews.

How to Prepare (Concretely, Not Generically)🔗

Research the Company Like You Would a Codebase🔗

Before any HR call, spend 30 minutes gathering intelligence. Start with Kununu (Germany’s largest employer review platform) to read employee reviews. Cross-reference with Glassdoor. Check whether the company has a tech blog, a GitHub organization, or recent conference talks from their engineers. Read their careers page carefully, paying attention to the language they use about culture and values.

For publicly listed companies, skim the most recent annual report or investor presentation. For startups, check Crunchbase for funding history and recent press mentions. This research gives you material for the “Why this company?” question and helps you ask better questions at the end of the call.

Practice Your Selbstpräsentation Out Loud🔗

Reading your self-introduction silently is not practice. You need to say it out loud, ideally to another person, at least three times before the interview. Time yourself. If you run past three minutes, cut something. If you stumble at the same point twice, restructure that section.

Record yourself on video if you can. Watch it back with the sound off and check your body language. Then watch it with sound and listen for filler words, unnecessary hedging (“I think maybe I was kind of involved in…”), and pacing issues. This feels uncomfortable. It is also the single highest-return preparation activity for the HR round.

Prepare Your Salary Range Before the Call🔗

Do not go into an HR screening without a researched salary range. Cross-reference at least two sources: StepStone Gehaltsreport, Glassdoor Germany, levels.fyi, or Kununu salary data. Adjust for your city (Munich pays 15-20% more than Leipzig for equivalent roles) and company size (large companies typically pay more than startups on base salary).

Have your gross annual number ready. If the question comes up and you are caught unprepared, you lose credibility. The HR person talks about compensation every day. They will notice if you are guessing. Our salary negotiation guide walks through the full research process and data sources.

Common Mistakes That Get You Rejected🔗

Treating the HR Round as a Speed Bump🔗

“I’ll just be myself and see what happens.” This is the most common approach to HR interviews, and it produces the most common outcome: rejection without clear feedback. The HR round rewards preparation just as much as the technical round does. The preparation is different (research and rehearsal instead of coding problems), but skipping it has the same result.

Badmouthing Your Current Employer🔗

This is universally bad advice to follow, but it is especially damaging in the German market. German business culture places high value on loyalty and discretion. If you criticize your current employer in the interview, HR will assume you will do the same when you eventually leave their company. Keep your reasons for leaving professional and growth-oriented, even if the reality was messier.

Not Having Questions Ready🔗

In many markets, “No, I think you covered everything” is an acceptable response when asked if you have questions. In Germany, it is a minor red flag. It suggests you are either not serious about the role or you did not prepare. Always have at least three questions ready, focused on the team, the work, and the growth path.

How CodingCareer Helps You Pass the HR Round🔗

Knowing the theory is one thing. Sitting in a video call with an HR professional, answering questions about your career narrative while trying to project confidence in a language or culture that may not be your own, is something else entirely.

CodingCareer’s mock behavioral interviews simulate the actual HR screening at German tech companies. The session is conducted by someone who has been through these interviews as a developer, not an HR consultant reading from a textbook. You practice your Selbstpräsentation, work through the standard question set, and get direct feedback on where your answers lose clarity or raise red flags. The session is recorded so you can review it afterward.

This is part of a broader approach that covers the entire pipeline. The Germany Market Entry package, for example, combines application strategy, CV optimization for German standards, online presence review, and a mock behavioral interview in a single coaching engagement. For candidates who also need technical interview prep, the Junior Kickstart and Salary Jump packages cover both sides.

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

Book your free 15-minute diagnostic session and get specific feedback on your interview readiness.