In short
- Start every answer with the point, then give one concrete example, then stop.
- Replace adjectives about yourself with what you actually did, and say "I" when it was you.
- When you don't know an answer, say so, show how you would think it through, and move on.
You know your experience. You have read the job ad twice. Then the interviewer asks a simple question and you hear yourself talk for three minutes without landing anywhere.
Most interview advice is about which questions come up. This article covers the other half: what to say in a job interview and how to say it, from the opening to the close, with weak and strong phrasings you can adapt.
What to say in a job interview: the basic pattern
Almost every answer gets better with the same three moves:
- Point. Answer the question in the first sentence.
- Proof. Give one specific example that shows it.
- Stop. End on the result or on why it matters for this role.
If your first sentence answers the question, everything after it reads as evidence. If it is background, the interviewer is still waiting.
Say the answer first. Everything after it is evidence.
This works for "Why this role?" and for technical questions alike. For behavioural questions you can use a fuller structure, but still lead with what happened in one sentence before you tell the story.
How to open the interview
The first minutes set the tone before any real question is asked.
The greeting
Be on time, or a few minutes early for an on-site interview. For a video call, join a couple of minutes early and check your sound. A short, plain greeting is enough: "Hello, thanks for taking the time today." You don't need a prepared line.
Small talk
If you're asked how your day is going, answer in one or two friendly sentences and hand the conversation back. Small talk is not a test, but rambling here sets a pattern.
The first real question
The first question is often a version of "Tell me about yourself" or "Walk me through your CV". Treat it as a short summary aimed at this job, not a biography. Keep it to around a minute and end with why you are in this conversation.
How long your answers should be
There is no official rule, but a common rule of thumb is one to two minutes for most answers. Shorter can sound thin. Much longer usually means the point got lost.
Three habits keep you in range:
- Answer, then offer more. After your main point and example, you can say "I can go into the technical side if that's useful." The interviewer decides whether to go deeper.
- Pause before you answer. Two or three seconds of silence feels long to you and normal to the listener. It is better than starting with "So, basically, um..."
- Watch for signals. If the interviewer starts nodding quickly or glances at the time, wrap up with your result.
A short answer with room for follow-up beats a long answer with no exit.
Make it concrete: examples instead of adjectives
"I'm organised", "I'm a team player" and "I'm a fast learner" are claims every candidate makes. They are not wrong, they are just not evidence.
Swap each adjective for something you did:
- Instead of "I'm organised", name the system you set up and what it changed.
- Instead of "I'm a team player", describe one moment where you helped another person or team move forward.
- Instead of "I learn quickly", say what you learned, in what time, and what you then delivered with it.
Use numbers only when they are real and you can explain them. An honest "it cut our weekly report from a full afternoon to about an hour" is stronger than a percentage you can't defend in a follow-up question.
Say "I" when it was you
Saying only "we" hides your part. Use "we" for the team's result and "I" for your own actions: "We shipped the new checkout. I built the payment form and wrote the tests."
When you don't know the answer
Every interview has a question you can't fully answer. How you handle it matters.
- Don't bluff. Interviewers often ask a follow-up, and a guess falls apart quickly.
- Say what you do know. "I haven't used that tool, but I've worked with a similar one, and this is how I'd approach it."
- Think out loud. For problem-solving questions, your reasoning is often what is being assessed. Say your assumptions and the steps you would take.
- Ask a clarifying question. "Do you mean in a team setting or on my own projects?" gives you a moment and a better target.
- Buy a few seconds honestly. "Good question, let me think for a moment" is fine. Silence while you think is not a weakness.
"I don't know yet, and this is how I'd find out" is a real answer.
Weak and strong phrasing, side by side
The examples below are illustrative, not taken from real candidates. Adapt the structure, not the words.
| Moment | Weak phrasing | Stronger phrasing |
|---|---|---|
| Strengths | I'm a real team player. | When two teams kept arguing about release scope, I set up a short weekly sync and the disputes stopped reaching our manager. |
| Your role | We improved the onboarding. | I rewrote the onboarding emails. The team handled the in-app part. |
| Hedging | I kind of helped with the migration, I guess. | I planned the migration and moved three of the services myself. |
| Unknown topic | Um, no, I don't know that. | I haven't used it yet. The closest thing I know is a similar tool, and I'd start with its documentation and a small test project. |
| Leaving a job | My old manager was impossible to work with. | I'm looking for a role with more ownership of the product side, and this one offers that. |
| Closing questions | No, I think you covered everything. | Yes. What would success look like in this role after the first three months? |
The stronger versions are specific, use "I" for your own work, and drop hedges like "kind of" or "I guess".
How to close the interview
Most interviews end with "Do you have any questions for us?" Say yes, and have two or three ready.
Good closing questions are about the work itself:
- What would success look like in the first few months?
- What is the biggest challenge the team is facing right now?
- What are the next steps in the process?
Then close in one or two sentences: thank the interviewer and say plainly that you are interested in the role. Questions about salary and conditions are legitimate, but they are often easier to raise once the company has signalled real interest.
Practise saying it out loud
Reading a table is not the same as using it under pressure. To find out whether your answers start with the point and stop in time, say them out loud.
A TalentVP mock interview has seven questions. The first is an opening question, and in the last one you ask the questions. The five in between are generated from the job title, your seniority, the job ad and your earlier answers. You can type or speak your answers. Spoken answers are transcribed and assessed as text. Interviews run in English, German or Turkish.
After each answer you get a score from 0 to 100, your strengths, areas to improve and a model answer. A free account includes your first mock interview.
The opening question deserves its own preparation: How to Answer "Tell Me About Yourself" shows how to build a short, job-specific summary for it.





