Treat it as a 60 to 90 second pitch, not a life story: who you are now, one or two pieces of work that prove it, and why this role is the logical next step. Write it once, tailor the last line for each company, and practise it aloud until it sounds natural rather than memorised.
What people tell me
Almost every interview starts with "tell me about yourself" and I never know what to say. Sometimes I recite my resume from school onwards, sometimes I ramble for five minutes and can see the interviewer losing interest. I am applying for junior developer roles and I do not have much work experience, so I am not sure what is worth mentioning. It sets a bad tone for the rest of the interview.
A composite of the messages behind this question, with personal details left out.
Key takeaways
- It is a pitch for this role, not a biography. Aim for 60 to 90 seconds.
- Use present, proof, future: who you are now, what you have built, why this job.
- One specific project with a number or outcome beats a list of technologies.
- Tailor only the final part per company; keep the core stable so it sounds confident.
- Practise aloud and record yourself. Memorise the structure, not the sentences.
What the question is really asking
"Tell me about yourself" sounds casual, but it is the interviewer asking three things at once:
- Can you communicate clearly without a script?
- Are you the kind of engineer this role needs?
- Why are you in this room, for this job?
It also sets the agenda. Whatever you mention, they will probably ask about next. So your answer is not just an introduction; it is you choosing the topics you are strongest on.
The structure: present, proof, future
| Part | Time | What to say | Example (junior backend) |
|---|---|---|---|
| Present | 15 to 20 seconds | Who you are professionally right now | "I am a recent computer science graduate focused on backend development, mostly Node.js and PostgreSQL." |
| Proof | 30 to 45 seconds | One or two pieces of work with outcomes | "For my final year project, I built an appointment system used by a small clinic. I designed the database, built the API and cut their double bookings to almost zero." |
| Future | 15 to 20 seconds | Why this role fits the path | "I want to work on systems with real traffic, and your team's work on payments is exactly the kind of problem I have been reading about." |
That is about 90 seconds. Stop there. If they want more, they will ask, and that is a good sign.
What to leave out
- Your school history. Unless it is directly relevant, begin at your degree or the point you started coding.
- Personal details such as hometown, family or hobbies, unless the interviewer clearly invites it.
- A list of technologies. "I know React, Node, Mongo, Docker, AWS, Python, Java" tells them nothing. One project that uses three of them tells them a lot.
- Apologies. "I do not have much experience, but" is the weakest possible opening. Start with what you have.
- Anything negative about a previous employer or university.
Writing yours in five steps
- Write a one-line identity. Role plus focus: "a frontend developer who likes building accessible interfaces" or "a backend engineer with a year of experience on internal tools".
- Pick your best two pieces of evidence. Projects, internships, freelance work, open source. For each, write one sentence on what you did and one on the result.
- Add a thread. What connects them? Maybe you keep choosing data-heavy problems, or you like working close to users. This makes you sound deliberate instead of random.
- Write the future line for the company. Read their careers page, engineering blog or product. Link something real to your thread.
- Cut it to 200 to 230 words. Read it aloud with a timer. If it goes past 90 seconds, cut the least specific sentence.
Variations for different situations
If you have no work experience
Use your strongest project as if it were a job. Talk about decisions you made, problems you hit and what you would do differently. If you feel you have almost nothing to show, this answer covers how to build that evidence.
If you are switching careers
Your previous career is an asset, not something to hide. One sentence on it, then the bridge: "I spent three years in accounts, automated our reporting with Python, and realised I enjoyed building the tools more than using them."
If you have a gap
Mention it briefly and move to what you did or learnt. Do not over-explain. Interviewers care much more about the present than the gap.
If it is a screening call with a recruiter
Make it shorter, around 45 to 60 seconds, and lean on role title, key skills and why you applied. Recruiters are checking fit against a list.
Practise it properly
- Say it aloud ten times over three days, not in one sitting. By the third day it will feel natural.
- Record yourself on your phone. Watch for filler words, speed and whether you sound like you are reading.
- Memorise the structure and key facts, not the exact sentences. Word-for-word memorisation sounds robotic and breaks if you are interrupted.
- Do it in front of someone, then ask what they remember. If they cannot repeat your main project, it was not clear enough.
A one-week preparation plan
| Day | Task |
|---|---|
| 1 | Write the full draft using present, proof, future |
| 2 | Cut to 90 seconds, record and review |
| 3 | Write company-specific future lines for your next five interviews |
| 4 | Practise with a friend; ask what they remember |
| 5 | Prepare follow-up answers for each project you mention |
| 6 | Record again and compare with day 2 |
| 7 | Rest, then one final run before the interview |
Common mistakes
- Reciting the resume. They have read it. Give them the story behind it.
- Going on for five minutes. Long answers suggest you cannot prioritise, which matters for engineers too.
- Mentioning a project you cannot discuss in depth. Every project you name is an invitation for technical questions. Only mention what you can defend.
- Sounding identical for every company. The last line should prove you know why you are there.
- Forgetting it leads somewhere. End with a line that hands the conversation back, such as "happy to go deeper into any of that".
How it connects to the rest of the interview
A strong opening makes the technical part easier, because the interviewer already sees you as organised and relevant. If the technical round is where you struggle, this answer on failing technical rounds covers the practice that helps, and if nerves are the issue, see getting comfortable being evaluated.
If you are still stuck
The free Job search roadmap puts interviews in the context of the whole search. If you would like someone to listen to your version and tell you honestly how it lands, join Sefism (free to learn, with credits on joining) and, as a member, book a 1:1 session or ask your own question.
Was this answer helpful?
Your situation is not quite this one?
Members get written answers to their own questions, a roadmap built for them and feedback on their projects. Early access is open: sign up and your account is active shortly after. Prefer to talk? A free call works too.