Almost every interview opens with some version of "tell me about yourself" or "walk me through your background." It feels like an easy question and most candidates answer it badly — either rambling through an unstructured life story, or freezing because the question is so open-ended.
Nobody wants your full biography. The real question is narrower: why are you relevant to this role, in a way I can follow in under a minute? Treat it as that question, not the literal one.
A reliable shape: where you are now (briefly) → what got you into this field (briefly) → what you've built or learned that's relevant (the main part) → what you're looking for now (a short close that connects to this role).
Weak (unstructured): "So I was born in... I went to school... then I
got interested in computers... my family... then I joined this
course... it was really interesting... um..."
Structured: "I finished a web development course a few months ago,
focused on React and Node. Before that I was drawn to programming
because I liked figuring out how things worked, not just using them.
During the course I built a couple of projects on my own — a task
manager with a REST API I wrote myself — and that's when I realised
I wanted to focus on frontend work specifically. I'm looking for a
junior role where I can keep building on that and learn from a real
team."Sixty to ninety seconds is the right length. Longer and the interviewer's attention drifts before you get to anything relevant to the job at hand; shorter and it can feel dismissive of a genuine opening question. Time yourself while practising — this is one of the easiest things on this list to over- or under-shoot without noticing.
Structure it, do not script it
Do not memorise it word for word. A rehearsed answer delivered like a recitation sounds stiff and unnatural, and it audibly breaks if you get interrupted or asked a follow-up mid-answer. Know the shape and the key points; let the exact wording vary naturally each time.
The middle of the answer — your background and what you've built — stays roughly the same across interviews. The close should shift slightly toward the specific role: mention something about the company or the position that connects to what you just said, using the research from the preparation lesson.