45 Job Interview Questions for Developers in Germany

Developer interview questions in Germany: sample answers, technical and practical questions, illegal questions under German law, smart questions to ask.

A developer job interview in Germany is rarely one conversation. Usually it is three to five rounds: a recruiter call, a conversation with the engineering manager, a technical round and a final chat with the team. Each round asks different questions, and the generic “Where do you see yourself in five years?” lists only cover part of them.

Often the decision depends less on your technical skills than on the answers around them. According to Bitkom’s 2026 IT labour market study, 97 percent of German companies with IT vacancies struggle to fill them. Missing skills are only one reason. Companies also cite salary expectations that don’t match qualifications (59 percent), missing German skills (47 percent) and unwillingness to relocate (42 percent). These are exactly the topics that come up in the interview.

This guide covers the seven questions you will almost certainly get, with sample answers for developers. It adds 38 more questions by category, explains what German employment law says about practical and illegal questions, and lists the questions worth asking as a developer.

In short: which questions do developers get in German interviews?

Developer interview questions fall into five groups:

  1. Motivation and background: Who are you, why are you leaving, why this company?
  2. Technical depth: Explain a project, an architecture decision, a bug. Plus live coding, a take-home task or system design.
  3. Team behaviour: Conflict, mistakes, prioritisation, working with product and design.
  4. Practical questions: Salary, notice period, start date, remote share, location, language, work permit.
  5. Your own questions: What you want to know about the team, the codebase and how they work.

Who asks what? The typical process in Germany

The process differs between startups, mid-sized companies (Mittelstand) and corporations, but the roles are similar. Once you know who is in the room, you know which questions to expect.

RoundWho asksTypical questionsWhat they look for
Recruiter call (20–30 min)Recruiting or HRReason for leaving, salary, notice period, language, locationDo you fit on paper and on budget?
Hiring manager interview (45–60 min)Engineering manager or team leadProjects, decisions, behavioral questionsHow do you really work?
Technical round (60–90 min)Senior engineersLive coding, code review, system design, take-home reviewHow do you think and communicate while doing it?
Team or final interviewTeam, head of engineering, sometimes leadershipCollaboration, values, your questionsDo you want to work here, do they want to work with you?

The durations are typical, not a standard. After the first call, ask the recruiter which rounds follow and who takes part. To research a specific company’s questions in advance, see our guide on finding your target company’s interview questions.

How to answer interview questions convincingly

Five rules carry you through almost every question:

  • Answer with a real case, not an intention. “I would raise the issue openly” is not an answer. “In our last release, I …” is.
  • Name your own contribution. Teamwork matters, but the interviewer needs to know what you decided and built. Say “I” when it is your work.
  • Use numbers where real ones exist. Latency, error rate, build time, users, cost. Don’t invent them: technical interviewers will dig.
  • Explain trade-offs. Developers rarely get hired for the “right” solution. They get hired for knowing the alternatives and choosing for a reason.
  • Structure behavioral answers with STAR. Situation, Task, Action, Result. Action is the longest part. See our guide to behavioral interview questions for developers.

7 typical interview questions with sample answers

1. “Tell me about yourself.”

This is not an invitation to read out your CV. They want a 60 to 90 second summary: your current role, a career arc of two or three steps, and why this job is the logical next one.

“I’m a backend developer with five years of experience, currently at a logistics startup in Hamburg. I split our tracking API from a monolith into three services and have run them since, including on-call. Before that I spent two years at an agency, where I started many projects but never ran one long term. That is what I want now: a product I develop over years. That’s why your platform team interests me.”

Our self-introduction guide walks through the four-step framework behind this.

2. “Why do you want to leave your current job?”

This checks whether you are running away from something or moving towards something. Don’t badmouth your employer, even if you have reasons. Say what you are missing and connect it to the new role.

“I’ve learned a lot at my current company, but our team has shrunk to three developers and I mostly do maintenance. I want to shape architecture again. Your job ad describes building a new event pipeline, which is exactly the work I’m looking for.”

If you are leaving after a short time or were laid off, see our guides on changing jobs after one year and job searching after a layoff.

3. “Tell me about a project you’re proud of.”

This is the most important technical question outside live coding. The interviewer will keep asking until they reach your own contribution. Pick a project you can explain down to the details and prepare three levels: the business problem, your technical solution, the measurable result.

“Our invoice generation ran as a nightly batch job that took four hours. I rebuilt it on a queue with idempotent workers. It now runs in 25 minutes, and failed invoices are retried individually instead of restarting the whole run. I learned the most from the migration: we ran both systems in parallel for two weeks and compared the output.”

4. “Describe a technical decision where you had to weigh alternatives.”

This is not about the technology but about how you weigh options. Name at least two options, your criteria, your choice and what you would do differently today.

“We had to decide whether to introduce Elasticsearch for search or stay with Postgres full-text search. Elasticsearch would have given better relevance, but it was a second system nobody on the team could operate. We stayed with Postgres and a trigram index and agreed to reassess past one million documents. In hindsight that was right, because we needed the time for other features.”

For senior-level architecture questions, see our guide to system design interviews in Germany.

5. “Tell me about a mistake you made.”

In Germany, honest self-criticism lands better than a polished success story. A fake weakness like “I’m too much of a perfectionist” sounds evasive. A production incident works well, as long as you are clear about your part and what changed afterwards.

“I rolled out a database migration without a lock timeout. It blocked the orders table for twelve minutes and checkout went down. I did the rollback and wrote the postmortem. Since then our migrations run with a timeout and get tested against a staging copy with production volume. I wrote the check script for that.”

6. “How do you keep up technically, and how do you use AI tools?”

The second half of this question is becoming common. According to Bitkom, 42 percent of German companies with IT positions already use AI in their IT work, and another 36 percent plan to. They want a considered answer: what you use AI for, where you don’t trust it and how you check its output.

“I use an AI assistant for boilerplate, tests and getting into unfamiliar code. For security logic and data migrations I write the code myself and at most let it suggest test cases. Generated code goes through the same review as mine.”

More in our guide on AI skills in interviews.

7. “Why should we hire you?”

Summarise in three sentences where the job’s requirements and your experience overlap. Take the two or three most important points from the job ad and back each one with an example that already came up in the interview.

“You’re looking for someone who doesn’t just build a distributed system but also runs it. I’ve done that for three years, including on-call and postmortems. You also mentioned the team is moving from Java to Kotlin. I helped lead that migration at my current employer.”

38 more common questions by category

Motivation and company

  • What do you know about our product?
  • Which feature of our product would you improve first?
  • Why this role and not one at a bigger company?
  • What are you looking for in your next team that you don’t have today?
  • Where do you see yourself in three to five years: staff engineer or engineering management?
  • Which other companies are you interviewing with?
  • What caught your attention in our job ad?

Technical skills and ways of working

  • What does your path from ticket to deployment look like?
  • What makes code good, in your view?
  • What do you look for in code review, and how do you handle criticism of your code?
  • How do you test? Where do you stop?
  • What do you do when you can’t reproduce a bug?
  • When would you split a monolith, and when not?
  • How would you scale [core component of the product]?
  • How do you get into a large, unfamiliar codebase?
  • How do you handle technical debt when the product team wants features?
  • What is the last technology you deliberately decided not to adopt, and why?

The monolith-versus-microservices question is common enough that it has its own guide. In live coding rounds, thinking out loud matters more than speed. See our live coding tips.

Teamwork and behaviour

  • Tell me about a conflict in your team. How did you resolve it?
  • How did you explain a technical problem to a non-technical person?
  • What do you do when requirements are unclear?
  • How do you prioritise when two stakeholders want something urgent at the same time?
  • Have you onboarded or mentored someone?
  • Tell me about a time you disagreed with your lead.
  • How do you work in a partly remote team?
  • How do you handle time pressure before a release?

Practical questions

  • What are your salary expectations?
  • What is your notice period? When can you start?
  • How many days a week do you want to be in the office?
  • Are you willing to relocate?
  • How good is your German? Can you run meetings in German?
  • Do you need a visa or work permit?
  • Are you willing to be on call?
  • How do you feel about overtime before important releases?

The next section explains the rules behind these questions.

Unusual questions

  • Explain what happens when I type a URL into the browser.
  • How would you explain your job to a child?
  • What did you last build without being paid for it?
  • What question did you wish we had asked you?
  • Which book, talk or blog post changed the way you write code?

These questions test whether you can bring complex things down to the right level. Take two seconds, ask how deep they want you to go, and answer in a structured way.

Practical questions: what German law says

The practical questions are legitimate, but your answers have legal consequences. This section is not legal advice. It is an overview of the rules worth knowing before you give numbers in an interview.

Notice period and start date

Under Section 622(1) of the German Civil Code (BGB), the statutory notice period for employees is four weeks to the 15th or the end of a calendar month. Many employment contracts set longer periods, and your contract is what counts. During an agreed probation period of up to six months, Section 622(3) sets two weeks. Check your contract before the first call and give a realistic start date. A wrong answer will surface at the latest when the contract is drafted.

Salary expectations

In Germany, salary is negotiated as gross annual salary. Give a range with a lower end you would genuinely accept and back it with market data. In the Bitkom study, 59 percent of companies said applicants’ salary expectations don’t match their qualifications, and 48 percent said they don’t fit the existing pay structure. A well-reasoned number sets you apart from many other applicants. Current ranges are in our developer salary guide for 2026, and phrasing is in our salary negotiation scripts.

A change is on the way. Article 5 of the EU Pay Transparency Directive 2023/970 gives applicants the right to know the starting pay or its range before the interview. It also bars employers from asking about your pay history. The transposition deadline was 7 June 2026, and Germany missed it. In its answer of 8 July 2026 (Bundestag printed paper 21/7026), the federal government wrote that a draft bill had been prepared and that the legislative procedure was still to be started. Until the German law exists, a company can still ask about your current salary. You don’t have to give it, though. A sentence like “I’m orienting myself on the range for this role, not on my current contract” is enough.

Remote work, relocation and language

These questions are allowed, and for employers they are often decisive. In the Bitkom study, 42 percent of companies cite unwillingness to relocate as a hurdle, 35 percent can’t meet applicants’ remote-work requirements, and 47 percent cite missing German skills. Be honest and specific: “Two office days a week work for me, four don’t.” For German, a level with an example helps more than “good”: “B2. I can follow meetings and write tickets in German, but I prefer architecture discussions in English.” How much language matters for international applicants is covered in our guide to finding tech jobs in Germany.

Work permit

Asking about your visa or residence permit is not discrimination. Under Section 4a(5) of the Residence Act (AufenthG), employers must check that you are allowed to work in Germany and keep a copy of your residence permit. If you need a Blue Card, say so early and show you know the process. Our Blue Card guide summarises requirements and timeline.

Overtime and on-call

The Working Hours Act (Section 3 ArbZG) limits working time to eight hours per working day. It can be extended to ten hours if the average over six months or 24 weeks stays at eight hours per working day. So you don’t have to answer “How do you feel about overtime?” with a flat yes. Better: “I’m flexible before a release. I’d like to know how overtime and on-call are compensated here.” The statutory minimum holiday under Section 3 of the Federal Holiday Act (BUrlG) is 24 working days based on a six-day week, which equals 20 days in a five-day week. Anything above that is in your contract.

Illegal questions: what you don’t have to answer

The General Equal Treatment Act (Section 1 AGG) protects against discrimination based on ethnic origin, sex, religion or belief, disability, age and sexual identity. Questions aimed at these characteristics are generally not allowed in a job interview. Typical examples:

  • Are you pregnant, or are you planning to have children?
  • What is your religion?
  • Where are your parents from?
  • How old are you? Would you still fit into a young team at 50?
  • Do you have a disability or chronic illness?
  • Are you a union member?

The union question touches freedom of association under Article 9(3) of the Basic Law, which declares agreements restricting that right void. On pregnancy, the Federal Labour Court ruled in 2003 (case 2 AZR 621/01) that the question is inadmissible and that the applicant may answer untruthfully. The employer could not void the contract afterwards for fraudulent misrepresentation.

How to react in the interview: You don’t have to push back sharply. A calm question usually works: “Could you tell me how that’s relevant to the role?” Many interviewers then realise themselves that the question shouldn’t have been asked. Afterwards, write down the date, the question and who asked it.

If you are rejected afterwards: Anyone not hired because of a protected characteristic can claim compensation under Section 15 AGG. The claim must be made in writing within two months of receiving the rejection. If you would not have been hired even without discrimination, compensation is capped at three monthly salaries. For an assessment of your case, contact the Federal Anti-Discrimination Agency or an employment lawyer.

Which questions should you ask as a developer?

At the end of almost every round comes: “Do you have any questions for us?” Having none looks uninterested. For developers it is also the best chance to learn what the job is really like. Two to four questions per round are enough. Ask them to the person who can answer them.

For the engineering manager

  • How will you know I’ve been successful after six months?
  • What is the team’s biggest technical problem right now?
  • How much time goes into technical debt, and who decides?
  • Why is the role open: new headcount or replacement?
  • How do promotions work, and are there engineering levels?

For the engineers on the team

  • How does code get to production, and how often do you deploy?
  • How long does a pull request typically wait for review?
  • Is there on-call? How often are you on, and how is it compensated?
  • What was the last major outage, and what changed afterwards?
  • What would you change in your codebase right away if you could?

For the recruiter or HR

  • Which rounds are left, and when can I expect a decision?
  • What is the remote-work policy, and is it written into the contract?
  • Is there a training budget or conference days?
  • Is there a works council (Betriebsrat)?

Before you sign

Some questions don’t belong in the first interview but must be answered before you sign:

  • Post-contractual non-compete: Under Section 74(2) of the Commercial Code (HGB), it is only binding if the employer pays compensation of at least half your last remuneration for each year it applies.
  • Side projects and open source: Can you work on your own projects, and who owns the code?
  • Probation and notice periods after probation.

Our guide to the German employment contract goes through these clauses one by one.

Which questions should you avoid in the first interview?

Many guides say never to ask about salary or holiday in a first interview. In tech hiring that is too strict. Salary comes up in the recruiter call anyway, and asking about remote share is legitimate because it can decide whether the role works for you. Other questions are the real problem:

  • Questions the website answers: “So what does your company actually do?” shows you didn’t prepare.
  • Questions that sound like an exit plan: “How soon can I move internally?” in the first conversation with the team trying to hire you.
  • Questions only about perks: If you only ask about holiday, home office and gadgets, it looks like the work doesn’t matter to you. Ask them, just not exclusively.
  • Questions that put the interviewer on the spot: “Why is your app so slow?” Better: “I noticed search took a few seconds for me. Is performance a topic for the team right now?”

How to prepare in 6 steps

  1. Break down the job ad. Mark the three to five requirements that really count. You need an example from your work for each one.
  2. Write five core stories. A project, a technical decision, a mistake, a conflict, a situation with unclear requirements. Almost every behavioral question can be answered with one of them.
  3. Use the product. Sign up, try the core feature, read the engineering blog and other teams’ job ads. That is where the best questions come from.
  4. Know your numbers. Salary range, notice period, earliest start date, remote preference, visa status. These answers must be ready before the recruiter call.
  5. Practise out loud. Say your introduction and two stories out loud, record yourself and listen back. What sounds smooth in your head is often twice as long when spoken. A mock interview with someone who digs deeper helps most.
  6. Check the logistics. For remote interviews, test camera, microphone and screen sharing for live coding. For on-site interviews, check the invitation for a rule on travel costs. Under the Federal Labour Court’s case law (judgment of 29 June 1988, 5 AZR 433/87), applicants invited to an interview are generally entitled to reimbursement of necessary expenses such as travel and accommodation. Some companies explicitly exclude this in the invitation, though.

After the interview: if you hear nothing for weeks, see our guide on being ghosted after an interview.

Conclusion: prepare stories, not answers

The list of questions is long, but the preparation is manageable. Five well-told stories from your work cover most motivation, technical and behavioral questions. Clear numbers on salary, notice period and location handle the practical part. Three prepared questions per round show that you are evaluating the job, not just hoping to get it.

What you can’t prepare alone are the follow-up questions. That is where your stories either hold up or don’t. In a mock interview with CodingCareer, we run the round with you the way German tech companies do it, and you get specific feedback on every answer.

Legal and market information as of 15 November 2026. This guide is not legal advice.

FAQ

What questions do developers get most often in a German job interview?

Almost every interview has the same building blocks: a self-introduction, why you want to change jobs, a project you explain in detail, a technical decision with trade-offs, a mistake or production incident, and the practical questions about salary, notice period and location. Depending on the company, you also get live coding, a take-home task or a system design discussion. Prepare one concrete story from your work for each block instead of memorising answers.

Do I have to answer every question in a German job interview?

No. Questions about characteristics protected by the General Equal Treatment Act (AGG), such as ethnic origin, religion, disability, age or sexual identity, are generally not allowed, and neither are questions about pregnancy or union membership. In 2003 the Federal Labour Court ruled that an applicant asked the inadmissible pregnancy question does not have to answer truthfully. You can politely ask how the question relates to the role. This is not legal advice: for a specific case, contact the Federal Anti-Discrimination Agency.

How should I answer the salary expectations question as a developer in Germany?

Give a range as gross annual salary, with a lower end you would genuinely accept, and back it with market data for your role, level and city. In Bitkom's 2026 study, 59 percent of companies with IT vacancies said applicants' salary expectations do not match their qualifications, so a well-reasoned number sets you apart. The EU Pay Transparency Directive will ban employers from asking about your current salary, but Germany has not transposed it yet.

What questions should I ask at the end of a developer interview?

Ask about things that shape your day: how code gets to production, how code review works, whether there is on-call and how it is compensated, how the team measures success in your first six months, and how much time goes into technical debt. Before signing, also check the rules on remote work, side projects and open source, and any post-contractual non-compete clause. Two to four good questions per round are enough.

Will a German employer reimburse my travel costs for an interview?

Usually yes, if the company invited you. The Federal Labour Court bases this on Section 670 of the German Civil Code: the employer has to reimburse the expenses you could reasonably consider necessary, such as travel and accommodation. Some companies explicitly exclude reimbursement in the invitation, so read it carefully and clarify the question before booking an expensive trip.

I use Umami for privacy-friendly analytics.

If you'd like to help me improve this site, please consider disabling your adblocker.