BehavioralBeginner6 min readPart 2 of 7

Tell Me About Yourself

“Tell me about yourself” opens almost every FAANG interview, and it is the most wasted opportunity in the process. It is not a request for your life story. It is a 60-second pitch that sets the tone for the whole interview and steers the conversation towards your strengths.

The present → past → future frameworkCore idea

This is the go-to template because it moves in time order and always ends on why you are here today.

%%{init: {"look":"handDrawn","handDrawnSeed":7,"theme":"base","fontFamily":"Virgil, \"Segoe Print\", \"Comic Sans MS\", cursive","themeVariables":{"fontFamily":"Virgil, \"Segoe Print\", \"Comic Sans MS\", cursive","fontSize":"16px","primaryColor":"#fff4e6","primaryBorderColor":"#1e1e1e","primaryTextColor":"#1e1e1e","secondaryColor":"#e7f5ff","tertiaryColor":"#ebfbee","lineColor":"#1e1e1e","textColor":"#1e1e1e","mainBkg":"#fff4e6","nodeBorder":"#1e1e1e","clusterBkg":"#f8f9fa","edgeLabelBackground":"#ffffff","actorBkg":"#e7f5ff","actorBorder":"#1e1e1e","noteBkgColor":"#fff9db","noteBorderColor":"#1e1e1e"}}}%%
graph LR
  P["Present<br/>who you are now"] --> PA["Past<br/>how you got here"]
  PA --> F["Future<br/>why this role"]
  class P blue
  class PA violet
  class F green
classDef orange fill:#ffd8a8,stroke:#1e1e1e,color:#1e1e1e
classDef blue fill:#a5d8ff,stroke:#1e1e1e,color:#1e1e1e
classDef green fill:#b2f2bb,stroke:#1e1e1e,color:#1e1e1e
classDef red fill:#ffc9c9,stroke:#1e1e1e,color:#1e1e1e
classDef violet fill:#d0bfff,stroke:#1e1e1e,color:#1e1e1e
classDef yellow fill:#ffec99,stroke:#1e1e1e,color:#1e1e1e
classDef grey fill:#e9ecef,stroke:#1e1e1e,color:#1e1e1e
DiagramThree beats, about 20 seconds each, ending on this role.
Present — role, team, scopePast — 1–2 relevant highlightsFuture — why this company and role
About 60 seconds in total.

Present (~20 s)

Your current role, your team, and the scope you own: users, services, tech stack.

Past (~20 s)

One or two highlights that led here, ideally related to the job.

Future (~20 s)

Why you are interviewing for this specific company and role.

Sample answer: software engineerExample

I'm a backend engineer at X, leading a team of four building the payments service that processes $40M in annual volume for 2M users. Before that I spent three years at Y scaling their order pipeline from 5K to 50K orders a day by introducing a Kafka-based eventing layer. I'm here because I've followed your work on distributed payments and want the chance to do that at a much larger scale, which is exactly what this role offers.

Sample answer: new grad or internExample

I'm a final-year CS student who has built three full-stack projects, including a meal-planning app used by 1,000 students, and interned at Y where I cut report-generation time by 40% with a caching layer. I applied here because I want to work on the scale of Z and have been practicing system design with mock interviews to build toward that.

What interviewers evaluateIn the interview

RelevanceEvery sentence connects to the job.
Scale of impactNumbers that show users, scale or time saved.
StorytellingA clear structure, no rambling, a confident finish.
ChemistryNatural, not robotic.

Company-specific tweaksCompare

CompanyLean into
AmazonOwnership and Dive Deep, with concrete outcomes
GoogleScope and systems, plus genuine interest in the problem space
MetaMoving fast and shipping products users love
MicrosoftBuilding tools for real people, and accessibility

Common mistakesPitfalls

Reciting your resume in orderThe interviewer already has it.
Going over 90 secondsYou lose the listener.
Starting too far back“I was born in…” or a long list of courses, especially for a senior role.
Sounding memorisedKnow the beats, not the exact words.
No hook at the endAlways finish with why this company.

Frequently asked questionsFAQ

Should I prepare a different version per company?

Partly. Keep your present and past paragraphs stable so they stay fluent under pressure, then customize only the future paragraph per company. That single variable is usually what differs, and adjusting just it lets you maintain one practiced answer instead of memorizing a dozen fully distinct versions.

Do I need to mention projects and side work?

Mention them when they prove a skill the role needs, especially if you are a new grad without much professional experience. Tie each project to a measurable outcome and connect it directly to the job description. Listing side projects with no outcome signals curiosity about the work, not impact on it.

What if I have a large employment gap?

Keep the focus on what you actually did with the time: upskilling, open source contributions, or personal projects. Present those as deliberate choices in the past section rather than as a defense, then move quickly into the future paragraph. Confidence here matters more than explaining the gap in detail.

Keep readingKeep reading

Ready to practice?

Reading is step one. Saying it out loud is step two.

Start a mock interview with Alex, get pushed on the parts you skip, and see your hiring signal right after.