The interview

‘Can you tell us something about yourself.’ — Where interviews go wrong.

‘Tell me about yourself’ as opening question sounds simple. But it isn’t. This is where many candidates lose control of the interview almost immediately. They retell their CV. They drift into personal biography. Or they give a vague, forgettable answer that tells the interviewer nothing.

The question is not an invitation to talk. It is a test: Who are you professionally → What can you actually do → Why should this employer care? If your answer doesn’t deliver that, you’re wasting much more than just the opening minute.

Never walk through your CV.

The interviewer has already read your CV. If you repeat it chronologically, at best, you force them to do the work of finding relevance. Most probably, you bore them to death. Instead, lead with your professional identity — fast and clear: ‘I’’m a B2B growth marketer focused on digital acquisition and conversion, mostly in international tech environments.’

One sentence. Your territory is established. You’re in control. Your CV is the timeline. Your answer is the meaning.

Start with where you are now

Use a structure that keeps the interviewer exactly where you want them: Present → Relevant past → Why this role now. Start with what you do today and what you’re strongest at. Add only the experience that shaped that strength. Then connect it directly to the role.

Example: ‘I’m a cloud engineer specialising in AWS automation. Over the past five years I’ve worked in high‑growth environments, improving deployment speed and reliability. I’m now looking for a role with deeper architectural ownership, which is what attracted me to this position.’

This is not storytelling. It’s positioning.

Read the job post strategically

Don’t skim the vacancy. Dissect it. Identify the competences the role actually requires. Prepare three examples that prove you have them.

If the role requires stakeholder management → choose an alignment example.
If it requires ownership → choose a moment you stepped in early.
If it requires problem‑solving → choose a situation where the answer wasn’t obvious.

That’s enough. You don’t need to predict every question. You need evidence and intent.

Give evidence, not adjectives

Adjectives are useless: ‘I’m ambitious, analytical and a team player.’ Anyone can say that. No one can evaluate it. Replace adjectives with proof: ‘Most of my recent projects involved engineering, product and commercial teams, so I’ve become comfortable translating between different priorities.”

Values are behaviours. Behaviours live in examples.

Structure examples clearly

If your example is messy, your thinking looks messy. Use: Situation → Action → Result

Brief context.
What you did.
What changed.

Example:’Our product and engineering teams used different reporting methods, which slowed prioritisation. I introduced a shared framework and aligned both teams around weekly metrics. Within two months, planning became faster and decisions clearer.’

Spend most of your answer on the action. That’s where your value is.

Make it relevant to this interview

You’re not introducing yourself at a dinner party. You’re making a case. Your introduction should shift slightly from one vacancy to another.

Same facts. Different emphasis. That’s not manipulation. That’s professional intelligence.

Keep it under two minutes

If your answer to ‘Can you tell us something about yourself?’ is longer than two minutes, you’re losing the room.

Explain who you are. Prove it with the competences you’ve analysed and one or two examples. Connect everything to the role.
Stop.

Let the interviewer respond. Control requires space.

Don’t make it too personal

Personal details can warm the conversation — later. Not in the opening. You don’t need to start with where you were born, your family situation or your hobbies.

Professional first.
Personal second.
Always.

Handle difficult questions without becoming defensive

Some questions are designed to make you uncomfortable.

• gaps
• failures
• weaknesses
• reasons for leaving
• salary expectations

The mistake is not having an imperfect history. The mistake is dodging it. Keep things factual. Acknowledge what happened. Explain what changed.
Then, move forward.

Example: ‘I underestimated the stakeholder alignment needed. The launch was delayed, and I learned to involve commercial teams earlier. Three months later, I changed that approach in the next project, which ran much more smoothly.’

Reflection beats perfection.
Every time.

If you don’t know the answer, don’t bluff. Say how you would find it.

Remember: the interview goes both ways

An interview is not an exam. It’s a negotiation of fit.

They’re evaluating your skills, behaviour and motivation.
You should be evaluating their expectations, team dynamics and environment just as sharply.

Ask about:

• what success looks like
• how the team works
• the biggest challenges in the first six months

You’re not simply trying to get the job. You’re trying to make a good decision.

Ask questions that show what the role is really like

Don’t waste time asking questions answered on the company website. Ask about things you cannot easily find elsewhere. Do your research and use what you find to ask better questions:

“What distinguishes people who do particularly well in this team?”
“What is the hardest part of this role that isn’t obvious from the job description?”
“What would you want the person in this role to have achieved after six months?”

These questions show seriousness.
They also protect you from surprises.

Let some personality through, within reason

Professional does not mean generic. Your examples should sound like you. Not like a job description.

Example: ‘I’m at my best when something messy needs structure. In my current role, that meant rebuilding our reporting process and giving three teams one shared view of performance.’

Compare that with:’I’m a results‑oriented professional with strong organisational skills.’

One is human.
One is wallpaper.

Close the interview well

Don’t let the conversation fade out. Before you finish, make sure you understand the next steps.
Then clear up anything important.

Ask:’Is there anything in my background you’d like me to clarify before we finish?’ This gives you one last chance to remove doubt.

Then close with intent: ‘The role fits well with where I want to go next, especially the mix of technical ownership and stakeholder work. I’d be interested in continuing the conversation.’

Clear.
Direct.
Not desperate.