Chapter 03 — "Tell Me About Yourself"
Chapter 03 — "Tell Me About Yourself"
Hey everyone! Welcome back to Namaste Behavioral Interviews! 🙏
It's usually the very first question, it sets the tone for the whole interview — and it's the one people mangle the most. They either freeze, recite their entire life story, or just read their resume aloud. There's a clean formula that makes you sound focused and confident in 90 seconds. Let's learn it.
What we will cover:
- Why they ask it (and what they don't want)
- The Present → Past → Future formula
- A weak answer vs a strong one
- The template
- Tailoring it to the role
- Traps to avoid
1. Why They Ask It (And What They Don't Want)
It's an icebreaker AND a test: can you communicate a clear,
relevant summary of yourself? It's your chance to STEER the
interview toward your strengths.
❌ What they DON'T want:
• your childhood, hometown, hobbies (unless relevant)
• a 5-minute monologue
• a robotic reading of your resume line by line
• "Um, what do you want to know?"
✔ What they DO want:
• a crisp, ~60–90 second professional snapshot
• relevant to THIS role
• that makes them curious to ask more
2. The Present → Past → Future Formula
┌─────────────────────────────────────────────────────────────┐ │ THE PRESENT → PAST → FUTURE FORMULA │ ├─────────────────────────────────────────────────────────────┤ │ │ │ PRESENT → who you are NOW, professionally. │ │ "I'm a backend developer with 3 years building APIs..." │ │ │ │ PAST → how you got here; a key achievement. │ │ "Before this I studied CS and interned at X, where I..."│ │ │ │ FUTURE → what you want NEXT — and why THIS role fits. │ │ "Now I'm looking to work on large-scale systems, which │ │ is exactly why this role excites me." │ │ │ └─────────────────────────────────────────────────────────────┘
This structure feels natural, stays short, and ends by connecting you to their job — a smooth hand-off into the rest of the interview.
3. Weak vs Strong Answer
❌ WEAK: "So, I was born in Pune, I have two siblings, I did my schooling there, then engineering, I like cricket and gaming, I know Java, Python, React, Node, MongoDB, SQL, Docker... and yeah that's basically me." → Life story + a keyword dump. No focus, no relevance, no hook.
✅ STRONG (Present → Past → Future):
[Present] "I'm a full-stack developer with about two years of
experience, currently focused on building React and Node
applications."
[Past] "I started in web development during college, and in my
last role I led the rebuild of our checkout flow, which cut
load time by 40% and reduced cart abandonment."
[Future] "Now I'm looking to take on bigger backend challenges
at scale, and since your team works on high-traffic systems,
this role feels like a perfect next step."
→ Focused, shows impact (a number!), and ends pointing at
THEIR job. In ~45 seconds. Perfect.
4. The Template
"I'm a ______ (role) with ______ (experience), currently
______ (what you do now).
I got into this when ______ (past), and one thing I'm proud
of is ______ (a concrete achievement, ideally with a number).
Right now I'm looking to ______ (goal), which is exactly why
______ (this role/company) caught my attention."
→ 3 short paragraphs. Practice until it flows in ~60–90 seconds.
5. Tailor It to the Role
The SAME person emphasizes DIFFERENT things for different jobs:
Applying for a BACKEND role?
→ highlight your API, database, and scaling experience.
Applying for a FRONTEND role?
→ highlight your UI, React, and user-experience work.
→ Read the job description, pick the 2–3 things they clearly
care about, and make sure your "Present" and "Past" spotlight
exactly those. Same story, aimed at the target. 🎯
6. Traps to Avoid
┌─────────────────────────────────────────────────────────────┐ │ TRAPS ❌ │ ├─────────────────────────────────────────────────────────────┤ │ • Personal life story → keep it professional & relevant. │ │ • Reciting the whole resume → they've read it; give the │ │ highlights + a hook. │ │ • Rambling past 2 minutes → aim for 60–90 seconds. │ │ • Being too modest → include one concrete achievement. │ │ • Not connecting to the role → always end with "why this │ │ role fits." │ │ • Negativity about a past job → stay positive & forward. │ └─────────────────────────────────────────────────────────────┘
Key Points to Remember
| Concept | Key Takeaway |
|---|---|
| Purpose | Crisp, relevant professional snapshot that steers the interview. |
| Formula | Present (who you are now) → Past (how you got here + a win) → Future (why this role). |
| Length | ~60–90 seconds. Not your life story, not your whole resume. |
| Include a win | One concrete achievement, ideally with a number. |
| Tailor + connect | Spotlight what the role cares about; end by linking to their job. |
What's Next?
Season 1 done — you have the foundation. Now the classic stories begin. Chapter 04 tackles "Why this company / why this role?" — the question that exposes who actually did their homework.
Keep growing, keep interviewing! See you in the next one!
Post a Comment