Tell me about yourself
30 min · Beginner
Need help? Ask a tutor on WhatsApp (opens in a new tab)The interviewer says "Tell me about yourself" and waits. They are not asking for your life story: they are checking whether you can sum yourself up in order, in about a minute, and hand them good topics to ask about next.
Present-past-future structure in 60-90 seconds
Present-past-future is a three-part structure for a self-introduction: who you are now, two or three pieces of evidence from your past, and the role you want next. Together they take 60 to 90 seconds.
Here is the outline as keywords, then the same outline filled in for a Python fresher. Each past item carries one concrete detail the interviewer can ask about.
Example 1 · The three-part outline
PRESENT degree + branch + college + focusPAST project (tech + result) | internship or second project | achievement or roleFUTURE the role you want + why this company or role fitsPRESENT Final-year CSE, ABC Institute, focused on Python backend development PAST the Online Store API (Python, JWT, 45 tests) | intern at Pixel Apps, fixed 12 bugs | ran Python workshops for 150 juniors FUTURE backend developer role; your team builds payment APIs in Python, which is what I enjoy
What this code does
- Keywords, not sentences: you remember the points and say them naturally each time.
- Each past item has one concrete detail (45 tests, 12 bugs, 150 juniors) that the interviewer can ask about.
At a calm pace of 120-130 words a minute, 60-90 seconds is about 120-190 words: one sentence of present, three or four of past, one or two of future.
A good line for each part:
- Present: "I am a final-year Computer Science student at ABC Institute, focused on Python backend development."
- Past: main project with tech and result; an internship or second project; one achievement or role.
- Future: "I want to start as a backend developer where I can work on real services and keep learning."
- End cleanly: "That is a bit about me." Do not trail off.
Order of execution
Build the introduction
Put the four parts of the answer in the order you would say them.
Model answers: CS fresher and non-CS-branch fresher
A hook is a concrete detail in your introduction, such as a project name, a technology or a number, that invites the interviewer to ask about it next. It steers the interview towards your strengths.
Below are two model answers to the same question: one for a Computer Science fresher and one for a candidate from another branch (a non-CS fresher). Notice the hooks in each.
Example 2 · Model answer: CS fresher
Question: "Tell me about yourself."Candidate: final-year CSE, Python backend focus, the Online Store API project, internship, coding club."I am a final-year Computer Science student at ABC Institute of Technology, and I focus on backend development in Python. Over the last year I built the Online Store API, a Python REST API for an online shop with JWT login, MySQL and 45 automated tests, which I deployed with Docker. Last summer I interned at Pixel Apps, where I fixed 12 bugs in their attendance API and learned to add a test for every fix. I also lead our college coding club and have run six Python workshops for juniors. I am now looking to start as a backend developer in a team that builds real services, where I can keep improving my design and testing skills. That is a bit about me."
What this code does
- Present in one sentence, three pieces of evidence each with a detail, a one-sentence future, and a clean ending.
- Likely follow-ups are all strengths: "How does your JWT login work?", "Tell me about one bug you fixed", "What did you teach in the workshops?"
Example 3 · Model answer: non-CS-branch fresher
Question: "Tell me about yourself."Candidate: final-year ECE, moved to software, self-taught Python and SQL, two projects."I am a final-year Electronics and Communication student at PQR College. In my second year I built a small attendance system for our lab in Python, and I enjoyed it more than any circuit project, so I decided to move into software. Since then I have learned Python, SQL and Git through online courses and practice, and solved about 300 data structure problems. I built a hostel complaint API in Python and MySQL that wardens of three hostels now use, and a Python console app for our lab inventory. My electronics background helps me think about systems and debug step by step. I am looking for a developer role where I can build on this and learn from an experienced team. That is a little about me."
What this code does
- It answers the unspoken "why software?" early with a short, true story, then proves the switch with skills and projects.
- The branch is presented as a strength (systems thinking, debugging), not an apology.
The CS fresher leads with projects and an internship. The non-CS fresher must also settle the silent question "why software?", so the past part shows how they built software skills on their own.
Both answers copy the shape, not the words. Fill the shape with your own true facts; never memorise someone else's sentences.
What not to say
Here is a weak answer with three common mistakes, then the same answer fixed. Try to spot the mistakes yourself first.
Example 4 · Weak answer fixed
"Good morning sir. My name is Rahul. I am from Nagpur. My father is a businessman and my motheris a homemaker. I have one elder sister who is married. I did my schooling from St. Mary's with85% and intermediate with 78%. Now I am doing B.Tech in CSE with 7.2 CGPA. My strengths arehard work and punctuality. My hobbies are cricket and listening to music. That's all sir.""I am a final-year Computer Science student at XYZ College in Nagpur, and I am most interested in building web applications with Python. My main project is a library management system in Python and MySQL that handles issue and return for about 500 books in our department library; the librarian uses it every day. I also won second place in our college coding contest last year, and I captain our department cricket team, which taught me to plan and keep a team motivated through a season. I want to start as a Python developer and grow into building larger systems. That is a bit about me."
What this code does
- Family details, school marks and the hobby list are removed; the resume already has the marks.
- Cricket stays, but now as evidence (captaincy, teamwork) instead of a hobby. "Hard work" is replaced by things that show it.
Two traps cost the most: reciting the resume line by line, which wastes time because the interviewer has it in front of them, and a memorised script, which sounds robotic and falls apart when interrupted.
Also leave out:
- Family details, unless they connect directly to your work.
- Class 10 marks, every subject and every certificate.
- Salary, "I just need a job", criticism of your college, and claims you cannot back up ("I am an expert in all languages").
- Your name again if the interviewer just said it: start with what you do.
Find the bug
Find the weak line
Each round shows the same weak answer. Click the line that matches the question.
Which line gives family details nobody asked for?
Round 1 of 3Adapting for service vs product companies
A service company builds and maintains software for client businesses, while a product company builds and sells its own software. They often look for different strengths in a fresher.
Below are the same facts told twice: once for a service company and once for a product company. Only the choice of details changes.
Example 5 · Same facts, two emphases
Facts: final-year CSE | the Online Store API API (Python, JWT, tests) | internship bug fixes | 350 DSA problems | coding club workshopsService company emphasis: "...In my internship I picked up their codebase in the first week and fixed 12 bugs while working with a team of five. Running workshops taught me to explain technical things clearly. I enjoy learning new technologies quickly and working with different teams..." Product company emphasis: "...In the Online Store API I designed the order flow so stock could never go negative, using a database transaction and a row lock. I have solved about 350 data structure problems and enjoy finding the most efficient approach. I like owning a feature end to end, from design to tests..."
What this code does
- Nothing is invented; only the choice of details changes. The service version stresses adaptability and teamwork; the product version stresses depth and problem solving.
- These are general tendencies, not fixed rules. Read the company's careers page and the job description to decide the emphasis.
Service companies often hire in large batches and value adaptability, communication and teamwork. Product companies often go deeper on problem solving, ownership of a project and technical depth.
These are general tendencies; every company differs. Read the careers page and the job description before you choose the emphasis.
Practising aloud and timing yourself
Filler words are small empty words and sounds such as "basically", "like" and "actually" that fill pauses. A few are normal, but many make an answer sound unsure and waste your 60-90 seconds.
This program turns the word count of a written answer into an estimated speaking time and counts filler words, so you can check a draft before you record yourself.
Example 6 · Timing an answer from its word count
import re
def verdict(seconds): if seconds < 50: return "too short: add a detail" if seconds > 100: return "too long: cut to the best evidence" return "good length"
answer = ( "I am a final-year Computer Science student at ABC Institute of Technology, and I focus on " "backend development in Python. Over the last year I built the Online Store API, a Python " "service for an online shop with JWT login, a database and 45 automated tests, which I deployed " "with Docker. Last summer I interned at Pixel Apps, where I fixed 12 bugs in their attendance API " "and learned to add a test for every fix. I also lead our college coding club and have run six " "Python workshops for juniors. I am now looking to start as a backend developer in a team that " "builds real services, where I can keep improving my design and testing skills. That is a bit about me.")n = len(answer.split())words_per_minute = 130seconds = int(n * 60 / words_per_minute + 0.5)print("Words:", n)print(f"At {words_per_minute} words/min: about {seconds} seconds -> {verdict(seconds)}")fillers = ["basically", "actually", "like", "you know"]filler_count = sum(len(re.findall(rf"\b{f}\b", answer.lower())) for f in fillers)print("Filler words:", filler_count)Words: 124 At 130 words/min: about 57 seconds -> good length Filler words: 0
What this code does
- 130 words a minute is a calm interview pace; the program converts the word count into an estimated speaking time and flags answers outside about 50-100 seconds.
- It also counts common filler words in a written version. The real test is still recording yourself, because fillers usually appear only when speaking.
Practising aloud means saying the answer, not reading it in your head. Record it on your phone and check four things: time, filler words, clear project details and a clean ending.
Practise from 3-4 keywords per part, not a full script, so the answer sounds natural and survives interruptions. Do it five times over three days and it will feel easy.
Next step
Check your understanding
12 quick questions