Tell Me About Yourself, and Why This Company

This is nearly always the first question. It is also the question people prepare least, because it seems too easy. "It is just about me, I know me."

Then the interviewer says, "So, tell me about yourself," and the candidate talks for five minutes about their school, their hometown, their first computer, and a job from four years ago. The interviewer's pen has not moved.

This note gives you a simple shape for that answer, then covers the other questions that come in the same warm-up part of the interview: why you are leaving, why this company, and strengths and weaknesses.

What the question is really asking

"Tell me about yourself" does not mean "tell me your life story". It means something closer to "Give me a short tour of who you are as an engineer, and show me why you are sitting in this chair."

Think of a shop assistant who greets you at the door of a small bookshop. They do not hand you the whole catalogue. They ask what you like, and point you to one shelf. Your answer is that pointing. You are choosing which shelf of your life to show.

The interviewer is also using this answer to decide where to go next. If you mention a payments project, they might ask about it in ten minutes. So whatever you say here is a doorway. Only mention things you are happy to be asked about.

The shape: present, past, future

A simple order works for almost everyone, and it fits in about 90 seconds.

1. Present: what you do now, in a sentence or two.
2. Past: one or two earlier steps that explain how you got here, with the skills you picked up.
3. Future: what you are looking for next, and why this role fits it.

Why this order? Because the present is the most relevant thing and the interviewer wants it first. The past is the proof. The future connects the two and leads straight to the next question, "why do you want this job?"

About 90 seconds is roughly 200 words. Shorter is fine. Longer is a risk.

A few small rules help.

• Start from your work, not your birth. Your school can be one phrase.
• Name one or two real things you built or fixed, with a small number if you have one.
• Leave out things that are not about work, unless they make you easier to remember. One short line about a hobby is fine. A paragraph is not.
• End on the future and stop. Do not trail off with "yeah, so, that is me".

Three examples to learn the shape from

These are made up, to show the shape. Do not copy them. They will sound wrong in your mouth because they are about someone else. Take the order of the parts, and fill in your own facts.

Example 1: a fresher

Say you are a final year student looking for a first job.

"I am finishing my final year in computer science. For the past year, my main project has been a college event app with three friends. I built the backend in Node, with a Postgres database, and about 400 students used it during our fest. The part I enjoyed most was fixing a bug where two people could book the last seat at the same time, which taught me about database transactions.

Before that, I did a three month internship at a small company, where I wrote tests for an existing service and fixed about a dozen small bugs. That is where I learned how code review works in real life.

Now I am looking for a first role where I can work on a real product with a team that reviews my code honestly. This role looked like a good fit because it is a backend team and the work with orders and payments is close to what I enjoyed in my project."

Notice that it has only one project with detail, a number, and a lesson. It is honest about size: a college event app, not a "large scale system".

Example 2: a mid level engineer

Say you have about four years of experience.

"I am a backend engineer with four years of experience. At the moment I work on the checkout service at an e-commerce company. I own the order creation flow, and last year I cut its failure rate from about three percent to under one percent by fixing how we retry payment calls.

Before this I spent two years at a smaller company building internal tools, where I learned to work with whatever the team needed, from APIs to deploy scripts. That is where I got comfortable owning things end to end.

I am now looking for a team where I can work on a larger scale, with more people depending on the system. I saw that you are moving to event based services, which is something I have only touched lightly and want to learn properly."

Look at the last line. Saying what you want to learn is fine. It makes you sound honest, not weak.

Example 3: someone switching domain

Say you spent five years in mobile testing and want to move into backend development.

"For the last five years I have worked in quality engineering on a mobile banking app. Most of my time went into automation, and over time I started reading the backend code to find the root cause of bugs, then writing small fixes myself. In the last year, I wrote about thirty backend pull requests, mostly bug fixes and a couple of small endpoints, all reviewed by the backend team.

That made me realise I enjoy building more than checking. I have been studying system design and building a small side project, a booking API with tests, to practise.

So I am looking for a junior or mid level backend role where my testing background is useful, because I know how things break. I understand I will be starting lower in some areas, and I am fine with that."

The thing that makes this work is that it does not hide the switch. It states it, shows evidence (thirty pull requests), and says plainly what the person is willing to accept.

The mistakes in this answer

• Reading out your CV from top to bottom. The interviewer already has it.
• A twelve minute story that ends before it reaches the present.
• Complaining about a past employer.
• Saying "I am a hard working team player who is passionate about technology". Everyone says this, and it tells them nothing. A fact beats an adjective.
• Starting with "So, um, basically..." and then reading from memory in a flat voice. Practise until it is natural, but do not memorise the exact words.

Why are you leaving

This question makes people nervous because they think there is a trap. There is a small one: do not make your current job sound terrible.

The interviewer is checking two things. Are you running away from something that you would bring with you? And are you moving towards something that this role actually offers?

A good honest answer has a short reason for leaving and a longer reason for joining. Move the weight to the second half.

Instead of this:

"My manager is bad and the codebase is a mess and nobody listens."

Try something like this:

"I have learned a lot here, mostly about running a service at small scale. But the work has settled, and I want to take on larger systems and learn from a bigger team. That is why I started looking."

If the real reason is harder, such as a layoff, a long gap, or a very bad manager, you can still say it plainly and without drama. "My team was part of a layoff in March. Since then I have been finishing a course and building a side project." People understand layoffs. What they dislike is hearing a long defensive story.

You do not need to share every truth. But whatever you say must be true, because the reference check or a follow up can reveal the difference.

Why this company

This is the question where most people give a generic answer, such as "You are a market leader with a great culture". The interviewer has heard it so many times that it sounds like noise.

A better answer has three small parts: one thing about what the company does, one thing about the role or team, and one link to you.

You cannot do this without a little research. Spend thirty minutes before the interview. Look at:

• The company's engineering blog, if it has one.
• The product itself. Use it, if you can. Notice one thing you liked and one thing that annoyed you.
• The job post. Which words repeat?
• Any talks or open source work from the team.

Then say something like this:

"I used your app last month to book a repair, and I liked that I could track the technician on a map. I read on your blog that you moved that tracking to a separate service, and I would like to work on problems like that, where the data changes every few seconds. The job post mentions on call and ownership, and I enjoy that kind of responsibility."

Notice that it is specific, uses a real detail, and links to the person's interest. It does not need to be long. Three or four sentences are enough.

If you have not used the product, do not pretend you have. Say, "I read about it and tried the demo", and mention what you actually looked at.

If you are applying to many companies and honestly do not have a special reason for this one, be plain about it. "I am looking for a backend team that works on a product with real users, and your team fits that. What drew me in specifically was..." and then give one true thing you found in your research, even if small.

Strengths and weaknesses

People hate this pair of questions, and the dislike is fair. They tend to produce rehearsed answers. "My weakness is that I work too hard" has become a joke.

Strengths

Pick two. Make them real, and back each with one short example. Skip the long list.

Weak: "I am a good communicator and a fast learner."

Better: "I am good at explaining technical things in simple words. Last year I wrote a one page guide for our payments flow, and two new joiners told me it saved them a week."

The pattern is simple. Name the strength, then give a small proof. If you cannot think of proof, it may not be a strength yet.

Weaknesses

Pick a real one, small enough that it will not stop you doing the job, and say what you are doing about it. This works better than a fake weakness, because interviewers are looking for self awareness more than perfection.

Some honest examples:

• "I used to say yes to every request and then run late. I now write down what I am dropping before I take on something new."
• "I am slow to ask for help, because I want to try everything first. I have set a rule for myself: if I am stuck for more than an hour, I ask."
• "I get nervous in big meetings and speak less than I should. I have started sending my points in writing beforehand."

Avoid weaknesses that are core to the job, such as "I find it hard to write code". Avoid fake ones too, such as "I care too much". And do not choose a flaw that you have not actually worked on, since the next question will be "What have you done about it?"

Keep it to about thirty seconds. Name the weakness, one short example, and what you do about it now.

What not to say

A short list, since these show up often.

• Anything negative about a past manager or company, even if it is fair.
• "I just need a job" or "any company is fine", even if it is half true.
• Salary as the first reason for leaving or joining.
• "I do not have any weaknesses."
• Rehearsed lines that you clearly learned from a video. Interviewers can hear the difference.
• A long apology about your gaps, your grades, or your college.

On the other hand, it is fine to say, "I am nervous, this job matters to me." One honest line like that often relaxes the room.

How to practise without sounding stiff

Write your three or four key points on a card, not a full script. Say the answer out loud ten times over a couple of days, once in the shower, once while walking, once to a friend. Each time it will come out a little differently. That is the goal. You are learning the shape, not the sentences.

Record yourself once. Listen for filler words, for the point where you speed up, and for any place you drift into the past without reaching the future.

Try it yourself

• Write one sentence for each of these: what I do now, how I got here (two steps at most), what I want next.
• Say the three sentences out loud as one answer. Time it. Is it under 90 seconds?
• Find one number from your own work that you can put in the present part.
• Spend thirty minutes on a company you like. Write down one thing you noticed about its product and one thing about the team.
• Write your honest answer to "why are you leaving" in two sentences, with the weight on what you are moving towards.
• Name one real weakness and write down one thing you have done about it in the last three months.