Your Career Story and Why This Company

Topics Covered

The Tell Me About Yourself Answer

Why the opening question matters

What the interviewer wants to learn

Keep it to about two minutes

Use a present, past, future structure

Start with the present

Explain the past selectively

Include one highlight

End with the future

Find the thread

Tailor to the role

Tailor to the interviewer

Avoid common mistakes

Sound natural, not memorised

Include a little personality

Be ready for the follow ups

Practise the first ten seconds

Lead with what is most relevant

Mention your level clearly

Practise with a timer and a listener

Almost every interview loop opens with some version of tell me about yourself, and many include why this company and why are you leaving. These questions look simple, but they set the frame for the whole conversation. This lesson covers how to build a clear career story, how to answer why this company and why this role, how to explain moves and gaps and how to close the loop with good questions of your own.

Why the opening question matters

Tell me about yourself usually comes first, which means it shapes the first impression. A clear, confident answer makes the interviewer expect a strong conversation and gives them hooks to ask about. A long, wandering answer makes them work harder to find what matters. The opening question is also one of the few you can prepare almost word for word.

What the interviewer wants to learn

Interviewers use this question to learn who you are professionally: what you have worked on, what you are good at, what you care about and why you are here. They also listen for how you organise information and how well you communicate. They are not asking for your life story or a reading of your resume.

Keep it to about two minutes

A good answer usually takes ninety seconds to two minutes. Shorter answers can feel thin and leave the interviewer with little to work with. Longer answers use time that the interviewer planned for other questions and suggest that you struggle to prioritise. Time yourself in practice, because most people underestimate how long they talk.

Use a present, past, future structure

A simple and effective structure is present, past, future. Start with what you do now, then explain the path that led you there, then explain what you want next and how this role fits. This structure is easy to follow, puts your most relevant experience first and ends naturally on why you are interviewing, which leads into the rest of the conversation.

Start with the present

Open with your current role in one or two sentences: I am a senior backend engineer at a payments company, where I lead a team of four building the systems that move money between banks. Include your level, your area and one detail that shows scope. This immediately tells the interviewer where you are in your career.

Explain the past selectively

The past section explains how you got here, but it should be selective. Mention two or three earlier roles or turning points that explain your skills and interests, not every job you have held. Each point should connect to the next: I started in a small startup, where I learned to own systems end to end, which is why I moved into platform work.

A present, past, future answer in under two minutes left the interviewer with clear hooks to ask about.

Include one highlight

Include one short highlight that shows your best work: the project you are proudest of, with one number. I led the migration of our ledger to a new database with no downtime, which cut reconciliation time from hours to minutes. A single highlight gives the interviewer something concrete to remember and often becomes the subject of a later deep dive.

End with the future

Finish with what you are looking for and how this role fits: I am now looking for a role where I can work on larger scale distributed systems, which is why this platform team appeals to me. Ending on the future connects your story to the interview and gives the interviewer a natural next question.

Find the thread

The strongest career stories have a thread that ties them together: a theme such as reliability, developer tools, data or customer facing products. The thread explains why your moves make sense and why this role is a natural next step. If your career has changed direction, the thread might be a skill you carried across, such as owning systems end to end.

Tailor to the role

Adjust your answer for each role. For a platform role, emphasise your infrastructure work. For a product role, emphasise the user facing parts of your experience. The facts stay the same; the emphasis and the highlight change. Two versions of the answer, prepared in advance, cover most of the roles a typical engineer applies for.

Tailor to the interviewer

Adjust also for who is asking. A recruiter may want a shorter, simpler version that focuses on role fit and logistics. A hiring manager may want more about how you work and what you want. A senior engineer may want more technical detail. Watch their reactions and adjust the depth as you go.

Avoid common mistakes

Common mistakes include starting from university, listing every job, using heavy jargon, focusing on personal details unrelated to work and sounding over rehearsed. Another is undervaluing yourself with phrases such as I just did some backend work. Be accurate and confident about what you have done, without exaggerating it.

Sound natural, not memorised

Prepare the structure and key points, but do not memorise every word. Fully memorised answers often sound flat and can fall apart if you lose your place. Practise until the structure is automatic and the words come naturally. A small variation each time you tell it is a sign that it sounds conversational rather than recited.

Include a little personality

A sentence that shows what you enjoy can make the answer more memorable: I love the moment when a confusing incident finally makes sense. Keep it brief and related to work. Interviewers remember candidates as people, and a hint of genuine enthusiasm helps them remember you positively.

Be ready for the follow ups

Expect the interviewer to ask about whatever you mention. If you mention a migration, be ready for a deep dive. If you mention leaving a role after a year, be ready to explain why. Before the interview, review every point in your answer and prepare a short follow up for each, so nothing you say catches you out.

Practise the first ten seconds

The first ten seconds matter most for nerves and impressions. Practise your opening sentence until it comes easily. Once you have started confidently, the rest of the answer usually follows. A strong opening line also helps you settle into the interview and speak more naturally for the rest of the round.

Three versions shared the same facts with different emphasis, and practice brought the answer under two minutes.

Lead with what is most relevant

If your current role is less relevant to the job than an earlier one, you can adjust the structure. Start with the present briefly, then spend more time on the earlier role that matters most. The goal is to put the most relevant experience where the interviewer will notice it, while keeping the story in an order that is easy to follow.

Mention your level clearly

Make your level and scope clear early, because interviewers use the opening to calibrate their expectations. Phrases such as I lead a team of four, I own the architecture for our payments services or I am a mid-level engineer on a team of eight help the interviewer understand where you are and which questions to ask next.

Practise with a timer and a listener

Practise the answer with a timer and, if possible, a listener who does not know your background. Ask them what they remember afterwards and whether they understood why you are interested in this role. If they remember the wrong things, adjust the emphasis. A fresh listener quickly shows which parts of your story land and which do not.

Present, past, future in two minutes

Open with your current role and scope, explain two or three linked turning points from your past, include one highlight with a number and close with what you want next and how this role fits. Find the thread that ties your career together, tailor the emphasis to the role and practise until it sounds natural.