Structured Hiring

Job interview questions: what actually helps you decide?

What employers should ask, how candidates can answer in their own words, and which questions help both sides make a better decision. With a guide to legal boundaries in Germany.

12 min read

“What are your weaknesses?” “Where do you see yourself in five years?” “Why should we hire you?” One person asks, the other tries to guess the correct answer. Somewhere, a rehearsed perfectionist is waiting for their cue. A good job interview is not an exam. Both sides should leave with better evidence for a decision.

For the hiring team, that means learning whether someone can do the relevant work, what they already know, what they can learn and how they approach real situations. For candidates, it also means finding out whether the work, expectations and conditions fit what they are looking for. Evidence means concrete information you can explain — not a feeling you have to defend afterwards.

What can hiring teams ask in Germany?

Start with the work: what legitimate requirement or employment decision does this question help clarify? Curiosity about someone’s private life is not a job requirement. Ask the same role-related questions of people facing the same requirements, rather than making assumptions from their name, appearance or family situation.

The General Act on Equal Treatment (Allgemeines Gleichbehandlungsgesetz, AGG) protects applicants against discrimination on grounds of race or ethnic origin, gender, religion or belief, disability, age and sexual identity. Questions touching these grounds can create discrimination risks. The Federal Anti-Discrimination Agency’s publication “Was Arbeitgeber fragen (dürfen)” explains why questions about protected personal characteristics are generally problematic in recruitment. General Act on Equal Treatment (AGG), including protections for applicants · Federal Anti-Discrimination Agency: Was Arbeitgeber fragen (dürfen) (German PDF)

Section 8 AGG allows differences in treatment where a characteristic is an essential and decisive occupational requirement because of the work or its conditions, with a lawful purpose and a proportionate requirement. This is a narrow justification to examine in the specific role, not permission to ask anything that seems interesting. Other statutory exceptions may also matter; get qualified advice if you intend to rely on one. Section 8 AGG: occupational requirements

Section 26 BDSG ties the processing of applicants’ personal data to necessity for deciding whether to establish an employment relationship. That applies to collecting information as well as keeping interview notes. Record relevant observations rather than private details or speculative diagnoses. Sensitive data can involve additional legal requirements. Section 26 BDSG: employment-related data processing

Replace private curiosity with a concrete requirement

Problematic questionDo you have children?: Better role-related approach“The role involves about two business trips a month. Is that generally possible for you?” State the actual requirement and ask everyone concerned.
Problematic questionAre you planning to have children?: Better role-related approachLeave family planning out of the interview. If availability matters, explain the working hours or travel requirements instead.
Problematic questionWhere are you originally from?: Better role-related approachIf language ability matters: “Which language skills would you bring to this role?” Do not use origin as a substitute for assessing ability.
Problematic questionIs German your first language?: Better role-related approach“This role requires German at C1 level. How confidently do you use German at work?” Check that the level is genuinely needed.
Problematic questionHow old are you?: Better role-related approach“What experience do you have with this type of work?” Assess the relevant experience, not age as a proxy.
Problematic questionAre you physically and mentally resilient?: Better role-related approachDescribe the concrete essential task and ask whether it can be fulfilled, including with appropriate adjustments. Do not turn this into a blanket question about health or disability.

A legal question can still tell you very little

“What are your weaknesses?” is not automatically unlawful or worthless. But a vague question can reward preparation, confidence and knowing the socially expected answer. You may learn more about someone’s interview practice than their work. Try: “Tell me about a situation where you realised you were missing knowledge or experience. What did you do?”

Every question needs a purpose. Before asking it, finish this sentence: “I want to learn whether…” Tie the answer to a requirement defined before the interview. Follow up on what the person actually did, what help they had and what happened. Do not treat a polished story as proof on its own.

Start with a criterion, then choose a question

Handling conflicting expectations

Weak question: Are you a good communicator?
Better question: Tell me about a situation where two stakeholders expected different things from you. How did you approach it?
What to listen for: How they understood the situation and competing interests, what they did and communicated, the result and what they learned. Ask what remained unresolved.

Learning unfamiliar work

Weak question: Are you a fast learner?
Better question: When did you last have to learn something unfamiliar to complete a task? How did you work out what to learn first?
What to listen for: How they identified the gap, chose resources or support, checked their understanding and applied it. A learning example can come from study, volunteering or another setting.

Prioritising under pressure

Weak question: Can you work under pressure?
Better question: Tell me about a time you could not complete everything requested. How did you decide what to do and what did you tell people?
What to listen for: The trade-offs, relevant constraints, who was involved and what changed. Working longer is not the only acceptable answer.

Judgement in the actual job

Weak question: How many tennis balls fit in a plane?
Better question: Imagine two important customer issues arrive just before a release. What information would you need before deciding what to do?
What to listen for: Whether they ask useful questions, identify risks and explain a workable next step. Give enough context and use the same scenario for comparable candidates.

Concrete examples make answers easier to assess; they do not remove uncertainty. Avoid demanding confidential details from previous employers. If someone has no comparable past example, a role-related scenario or a proportionate work sample may be more useful. Decide beforehand what would count as weak, adequate or strong evidence, and record uncertainty instead of filling it with intuition.

Common questions: answer as yourself

Weak questions will not disappear tomorrow. Candidates still need a way to handle them. Try a flexible pattern: your point → a concrete example → what it means for this role. You can change the order, pause or ask for clarification. The aim is to give the other person enough information to understand you, not to memorise a flawless speech.

Tell me about yourself.

What they may want to learn: Which parts of your background matter here.
Common trap: Reciting your whole CV or sharing personal details you would rather keep private.
A useful structure: Today → relevant past → next step. Pick the thread that connects to this role.
One possible answer: “I currently coordinate customer onboarding. Before that I worked in support, where I learned which handovers caused problems. I’d now like to own the onboarding process rather than only individual cases.”

Why do you want to leave or change roles?

What they may want to learn: What you need from your next job and whether this role can offer it.
Common trap: Only explaining what you want to escape, or pretending everything is wonderful.
A useful structure: Give a brief, factual reason, then explain where you want to go. You do not owe a detailed account of a difficult private situation.
One possible answer: “My current role has become mostly reporting. I want to spend more time solving customer problems directly. That’s why the implementation work in this role interests me.”

Why do you want to work here?

What they may want to learn: Whether you understand the work and have a specific reason for considering it.
Common trap: Generic praise that could be sent to any company.
A useful structure: What have you understood? What interests you? How does that connect to your experience or interests? Check assumptions.
One possible answer: “From the job ad, I understand you’re moving from one-off projects to a shared product. I’ve helped standardise recurring support issues before, and enjoyed that work. Is that transition really a big part of this role?”

What are your strengths?

What they may want to learn: Which capabilities you can bring to the work.
Common trap: A list of flattering adjectives without examples.
A useful structure: Name a relevant strength, show it in action and explain where it helps.
One possible answer: “I’m good at making complicated handovers clear. In my last team, I put recurring questions into a short checklist and tested it with two new colleagues. It helped us spot missing information before passing work on.”

What is your biggest weakness?

What they may want to learn: How you recognise limits and manage development.
Common trap: Perfectionism disguised as a strength, or a confession with no context.
A useful structure: Self-awareness → how you manage it → what you are developing. Choose something real; do not invent a weakness for the occasion.
One possible answer: “In large meetings I sometimes wait too long to raise a concern. I now write down my main point beforehand and make sure I bring it up early. It’s improving, though I still find it harder in unfamiliar groups.”

Tell me about a conflict.

What they may want to learn: How you handle disagreement and your own part in it.
Common trap: A story with a villain and you as the person who was right all along.
A useful structure: Explain the competing needs, your contribution, what you did and the outcome. A compromise can be a credible result.
One possible answer: “Sales wanted a custom feature; engineering needed to finish the release. I initially pushed for a quick workaround, then realised support would inherit it. We agreed on a smaller change after the release and told the customer what would have to wait.”

Where do you see yourself in five years?

What they may want to learn: Your direction and whether the role offers room for it.
Common trap: Inventing a precise title or promising to stay forever.
A useful structure: Describe work or responsibility you want to grow into, and what you still need to learn.
One possible answer: “I’d like to take responsibility for larger implementation projects. First I need more experience with planning and difficult customer decisions. I don’t have a fixed title in mind, but that’s the direction I’d like to explore.”

Why should we hire you?

What they may want to learn: How your experience and interests match their requirements.
Common trap: Claiming to be the best candidate when you have never met the others.
A useful structure: Summarise the match with concrete evidence, and be honest about a remaining gap.
One possible answer: “You need someone who understands support and can improve onboarding. I’ve done both, including coordinating handovers across teams. I’d need to learn your product, but the day-to-day problems sound familiar.”

These are examples of shape and detail, not scripts to copy. Your experience may come from paid work, education, care responsibilities or voluntary work. Explain your own contribution and avoid exposing other people’s private information. If you need a moment, “Let me think of a relevant example” is a perfectly usable sentence.

Candidates need evidence too

An interview works in both directions. Choose questions that test what matters to you, then ask for a recent example if the answer stays abstract. “We’re very collaborative” is a promising beginning, not the information you came for.

How would you know after six months that someone in this role is successful?: Reveals expectations and whether success is defined clearly enough to work towards.
What is currently the hardest challenge in this role?: Shows the practical difficulty behind the attractive description. Ask what support is available.
How are decisions made when people in the team disagree?: Helps you understand authority and how disagreement actually works. Ask about a recent decision.
How do you normally give feedback?: Clarifies whether feedback has a regular place in the work, who gives it and how concerns are raised.
Why is the role currently open?: Distinguishes growth, a replacement and a changed role. They may need to protect a previous employee’s privacy; ask about the role rather than personal details.
What should the person ideally achieve in the first three months?: Makes onboarding, priorities and resources visible. Check whether the expectations sound achievable.
What should I know about this role that I cannot learn from the job ad?: Invites an honest discussion of working conditions, constraints and surprises.

Fair interviews need more than a confident performance

Speaking quickly, sounding confident, being charismatic and answering spontaneously are not automatically evidence of job performance. Where live communication is genuinely part of the work, assess the specific task. Otherwise, do not let presentation style quietly become the main selection criterion.

In their 2023 paper, Sackett and colleagues discuss their 2022 reanalysis of meta-analytic evidence, which placed structured interviews highest among the selection procedures compared for predicting job performance. They also explain why earlier estimates for many procedures were overstated. This supports taking structure seriously; it does not make an interview a certainty machine or guarantee fairness in every setting. Sackett, Zhang, Berry & Lievens (2023): Revisiting the design of selection systems in light of new findings regarding the validity of widely used predictors

Define role requirements and evaluation criteria before meeting candidates.
Ask comparable core questions and use follow-ups to clarify evidence, rather than changing the standard for each person.
Explain the interview format and give enough context. Allow thinking time; tell candidates how to request adjustments.
Seek concrete examples and distinguish what you observed from your interpretation. Assess against the criteria before discussing overall impressions.
Do not rely solely on gut feeling, similarity or charisma. A scorecard helps organise judgement; it does not make weak criteria good.

When a question becomes too personal

You can set a boundary respectfully without turning the conversation into an argument. Ask which work requirement sits behind the question and offer to discuss that. You get to decide how much private information you share.

“I’d prefer to keep my private life separate. Could you explain which requirement of the role you’re trying to clarify?”

“If you’re asking about my availability, I’m happy to talk about that.”

How the interviewer responds is useful information too. If you are concerned about discrimination, write down what happened and seek advice, for example from the Federal Anti-Discrimination Agency. You do not have to resolve the legal position in the interview itself.

Euli’s short rule

Hiring teams: if a question tells you nothing about whether someone can succeed in the role, why are you asking it?

Candidates: don’t try to guess the perfect answer. Give the other person enough concrete information to actually understand you.

The goal is not for one side to win. Both sides should know more after the conversation than before — ideally more than simply who is particularly good at job interviews.