"Tell me about yourself" is usually the first question in an interview, and it's the one engineers prepare least. It sounds like small talk, so people improvise, and the improvised version is almost always too long, too chronological, and missing the one thing the interviewer wanted to hear: why you're a fit for this role.
It's most important in the recruiter screen (see our guide to what to expect in a recruiter screen), but versions of it open many rounds. A little preparation makes it one of the easiest questions in the loop.
What the question is really asking
The interviewer isn't asking for your life story or a recital of your CV, which they've probably read. They want to know:
- Who you are professionally, now. Your current role and what you work on.
- How you got here. The thread that connects your experience.
- Why this role makes sense next. The link between your story and their job.
And they're watching how you communicate: whether you can summarise, choose what matters, and stop.
How long should "tell me about yourself" be?
Aim for about 90 seconds, and certainly under two minutes. That's roughly 200 to 250 words spoken at a comfortable pace. Long enough to give a clear picture; short enough that the interviewer can steer the conversation to whatever interests them.
Most unprepared answers run three to five minutes. Timing yourself once is usually enough to see the problem.
A structure: present, past, future
- Present (about 30 seconds). Your current role, the kind of work you do, and one specific thing you've done recently that's relevant.
- Past (about 30 seconds). Two or three moves that explain how you got here. Not every job: only the ones that build the thread.
- Future (about 30 seconds). Why this role is the logical next step, using something specific from the job description.
Ending on the future matters. It hands the conversation back to the interviewer at the point where they're most interested: why you fit.
An example
Here's an illustrative answer for a backend engineer applying to a payments team:
"I'm a backend engineer at a logistics company. For the last three years I've worked on our routing service, and most recently I led its move from a batch job to an event-driven design, which cut the time for route updates from minutes to seconds.
I started out at a web agency building client apps, mostly frontend. I found I enjoyed the server side much more, especially the reliability problems, so I moved into a backend role and then to my current team.
What drew me to this role is that it's the same kind of work, high-volume event processing, but in payments, where correctness matters even more. The posting mentions the move to exactly-once processing, which is close to what I've been doing, and it's a domain I've wanted to work in for a while."
That's around 150 words. It has a specific achievement, a clear thread (frontend to backend to event-driven systems), and a reason for this job that couldn't be copied into any other application.
Adapting it for each round
The core stays the same, but the emphasis shifts with who's asking:
- Recruiter screen. Plain language, and a clear "why this role". The recruiter may not be technical, so "I led a move to an event-driven design" works better than a list of technologies.
- Hiring manager. More about scope and impact: what you owned, who you worked with, and what changed because of your work.
- Technical interviewers. A sentence or two more on the technical side, ending with something you'd be happy to go deep on. Interviewers often pick up whatever you mention, so mention the project you know best. If a technical deep dive is coming, that project is your best material (see the STAR method for software engineers for structuring it as a story).
Common traps
- Starting at the beginning. University and your first job rarely belong in the first 30 seconds. Start with now.
- Listing technologies. A string of languages and frameworks says little about what you can do. One concrete achievement says more.
- No ending. Answers that trail off ("...and yeah, that's about it") lose the strongest part. End on why this role.
- Reciting a script. A memorised paragraph sounds memorised. Prepare bullet points, not sentences, and say it a little differently each time.
- Criticising a current or past employer. If asked why you're leaving, keep it forward-looking: what you want next, not what's wrong now.
How to prepare your answer
- Write three bullets for present, past, and future. Include one specific achievement and one detail from the job description.
- Say it out loud and time it. Cut until it's under two minutes.
- Say it again, five or six times, until it comes out naturally from the bullets without a script.
- Prepare for the follow-ups. Whatever you mention, the interviewer may ask about: "You said you led the move to event-driven. What did you personally own?" Have a sentence ready for each thing in your answer.
The same answer, slightly adjusted, works for every interview in the process. It's a small amount of preparation for a question you'll be asked many times.
Hardmode's recruiter screen round opens with this question and follows up on whatever you say, the way a recruiter who has read your CV would, so you can hear how your answer lands before the real call.