← All posts
general

Tell Me About Yourself: Answers for Software Engineers

"So, tell me about yourself." For a software engineer it is the one interview question you can be certain of, and the one most people answer by reading their CV aloud in date order. Four minutes later the interviewer knows where you went to university and has twenty-six minutes left for everything else.

The answer rarely fails anyone on its own. What it does is set the frame for the rest of the conversation: which projects the interviewer asks about, what level they start assuming, whether they relax. A good one takes about ninety seconds and makes the next question easy for both of you. Below is a structure, three worked answers at different levels, and the adjustments for a specific company, a layoff or a gap.

What the interviewer does with your answer

Often they have only just opened your CV. The question buys them time to settle in. While you talk they are doing three things.

They are choosing follow-ups. Whatever you spend the most words on is what they will ask about. If you spend a minute on a project from 2017, expect questions on 2017.

They are estimating level. An answer built from tasks ("I worked on the checkout service") reads lower than one built from scope and outcomes ("I led the checkout rewrite for a team of five"). This first estimate is hard to shift later.

They are checking that you can summarise. Explaining something large in a short time is part of the job at every level above junior, and this is the first sample they get.

A 90-second structure

Four parts, in this order. The timings are for speaking aloud at a normal pace; ninety seconds is roughly 220 words.

  1. Now (15 seconds). Your role, the kind of system, your scope. One sentence, two at most. "I'm a senior backend engineer at a logistics company, where I lead the team that owns route pricing."
  2. Proof (40 seconds). The one or two things from the last few years that best support the job you are interviewing for. Each gets what it was, what you did and what changed. A number helps if it is true and you can defend it.
  3. The thread (15 seconds). A sentence that links the proof together and says what you are good at or drawn to. This is the part most people skip, and it is what the interviewer will remember: "The common theme is that I end up owning the system everyone else is afraid to change."
  4. Why here (20 seconds). What you want next and why this role fits it. Specific to the company. End on it, and stop.

Left out on purpose: your degree (unless you graduated in the last two years), every employer, your stack as a list, and how you got into programming. All of it is on the CV.

Start in the present. Chronological answers bury the most relevant material at the end, when attention has gone. If your early career matters (you were an electrical engineer, you ran a company), it gets one clause inside the thread.

Three worked answers

All three are invented examples, written to show the shape. Do not learn them. An interviewer who has heard a borrowed answer before recognises it within a sentence.

Mid-level engineer, about three years in, applying to a product team.

I'm a full-stack engineer at a property rental startup, mostly on the search and booking flow. For the last year I've owned search results end to end: I rebuilt the filtering backend so that results come back in under half a second instead of two to three, and I worked with our designer on the map view that most bookings now start from. Before that I spent a year on the payments integration, which is where I learned to care about what happens when things fail halfway. What I've found I like most is being close enough to users to see a change land, and that's why this role appeals: a small team that owns a whole part of the product, with a lot more traffic than I've worked with so far.

About 125 words, under a minute, which is fine at this level. One main piece of proof with a before and after, one secondary, a thread ("close to users"), and a reason for this job that admits a growth area without apologising for it.

Senior engineer, about nine years in, applying to a platform team.

I'm a senior engineer at a fintech, where for the last three years I've led the ledger team: six engineers, the system of record for every balance. The work I'd point to first is moving that ledger from a nightly batch to real-time posting. I wrote the design, sequenced it so that we never ran two sources of truth for more than a week per account type, and we finished without a reconciliation incident. The second is less visible. I set up the on-call and review practices that took us from weekly pages to about one a month. Earlier I was at a larger company on storage infrastructure, which is where the habit of designing for failure comes from. The thread is that I do my best work on systems where correctness matters more than speed of change, and where the hard part is migrating without anyone noticing. Your platform group is taking on exactly that with the account migration you described in the posting, and I'd like to do it at a larger scale.

About 170 words. The proof is chosen for a platform role, the earlier employer gets one sentence, and the close refers to something in the job posting.

Engineering manager, applying to manage two teams.

I manage the growth engineering team at a subscription company: eight engineers, a product manager and a designer I work with closely. I've been a manager for four years, after six as an engineer on the same kind of product. Two things I'd highlight. First, when I took the team over it was shipping about one experiment a month; we rebuilt the experiment tooling and changed how we plan, and it now runs six to eight, which is what moved our trial conversion last year. Second, people: I've promoted two engineers to senior and helped one move into management, and I've also managed someone out, which taught me more than the promotions did. I'm still technical enough to review designs and I choose not to write production code. What I'm looking for now is a broader remit, more than one team and managers reporting to me, and that's the role you've described.

About 150 words. A manager's proof is the team's output and its people. For what follows that opening, see the bank of engineering manager interview questions.

Tailoring it to the company

You need one answer with two movable parts, not a new answer per company.

The first movable part is which proof you choose. Keep three or four candidates ready and pick the two that match the job description. For an infrastructure role, the migration and the incident work; for a product role, the feature with the measurable user effect. The facts stay the same, the selection changes.

The second is the closing. "Why here" should contain something that is only true of this company: the problem named in the posting, the product you use, the scale, a talk one of their engineers gave. If the sentence would work unchanged for their competitor, it is not finished.

Depth differs by listener. For a recruiter, keep the proof at headline level and make "now" and "why here" very clear. For an engineer, add one technical detail to the proof.

After a layoff or a gap

The structure holds; only the first part changes. "Now" becomes "most recently", and the layoff takes one clause, stated as a fact.

Invented example of the opening: "Most recently I was a senior engineer at a travel company, leading the pricing team, until the company cut its engineering group by about a third in September."

Then go straight to the proof. Do not explain, defend or comment on the company, and do not save the layoff for the end, where it sounds like a confession. The longer treatment of that question, and of the weeks around it, is in the guide to interviewing after a layoff.

A gap works the same way. Name it, give its length, and move on: "I took eight months out to care for a parent, and I've been back in the market since October." If you did something relevant during it (a course, an open source contribution, contract work), one sentence. If you did not, say nothing more.

Mistakes that lose the first five minutes

  • The chronological tour. Starting at university and reaching the present in minute four. The interviewer has stopped listening by the second employer.
  • The stack recital. "Java, Kotlin, Postgres, Kafka, Kubernetes, AWS." That is a list of tools, and it leaves the interviewer with nothing to ask about.
  • No scope. "I worked on the payments team" could mean anything from fixing typos to leading it. Say what was yours.
  • Running long. Past two minutes, every extra sentence lowers the estimate of your communication. If they want more, they will ask.
  • Ending on nothing. "And, yeah, that's me." Finish on why you are here, then stop talking and let the silence be theirs.
  • Modesty by pronoun. "We" throughout. Use "we" for the team's result and "I" for your part of it.

Practising it aloud

Written down, almost every draft looks fine. Spoken, it runs forty seconds over and has a sentence you cannot get through in one breath. So the practice is spoken from the first day.

Write the four parts as bullet points, not sentences. Say it aloud and time it. Record the third attempt on your phone and listen once; the padding is obvious on playback. Cut until it is under ninety seconds, then say it on five different days, letting the wording change each time.

Then try it on a person, because the real test is what they ask next. If their first question is about the thing you most wanted to discuss, the answer works. If they ask something you did not expect, the emphasis is wrong. A friend can do this; someone who interviews engineers for a living does it better, and an opening answer is a good thing to bring to a first session with a behavioral interview coach, since it takes ten minutes and shapes every round after it.

Where coaching fits

Start alone: the practice interview runs a voice behavioral round with an AI interviewer and gives a written recap of what worked and what to drill. It is free; sign in to start. When you want a person to react to the answer, the behavioral interview coaches page shows each coach's background (27 of the 40 coaches on techinterview.coach list the specialty as of November 2026), so you can pick someone who has hired for your kind of role. A session with a coach of that background can cover the opening answer, the stories behind it and a mock round that starts the way real ones do.

Related guides