{"id":386,"date":"2026-01-01T00:00:00","date_gmt":"2026-01-01T00:00:00","guid":{"rendered":"https:\/\/springgreen-curlew-885344.hostingersite.com\/blog\/tell-me-about-yourself-interview\/"},"modified":"2026-06-19T05:46:38","modified_gmt":"2026-06-19T05:46:38","slug":"tell-me-about-yourself-interview","status":"publish","type":"post","link":"https:\/\/lastroundai.com\/blog\/tell-me-about-yourself-interview","title":{"rendered":"The 90-Second “Tell Me About Yourself” Answer That Doesn’t Sound Like a Resume"},"content":{"rendered":"

“Tell me about yourself” is the most-asked question in tech interviews and the most poorly answered. Candidates either read their resume aloud for four minutes or freeze and mumble for thirty seconds. Both ways lose the room before the real interview starts.<\/p>\n

The fix is 90 seconds, structured in three parts. Past, present, why-here. That’s it. Practise this once and you’ll never wing the opening question again.<\/p>\n

What the interviewer is actually asking<\/h2>\n

They’re not asking for your life story. They’re asking for context. Specifically: are you a credible candidate, do you communicate clearly under low-pressure prompts, and do you know why you’re in this room.<\/p>\n

The question is intentionally vague because the panel wants to see what you choose to talk about. That choice is the signal. Spending two minutes on your high-school robotics club tells them you don’t know what’s relevant. Spending ten seconds on a job you held for three years tells them you can’t synthesise.<\/p>\n

The 30\/30\/30 structure<\/h2>\n

Three buckets, 30 seconds each. Slightly less on the past, slightly more on the why-here if you have to flex.<\/p>\n

\n
\n
    \n
  1. 30s, past:<\/strong> One sentence on what you studied or where you started, then one or two sentences on the role(s) that got you to today. Skip the chronology. Pick the through-line.<\/li>\n
  2. 30s, present:<\/strong> Your current role in concrete terms. What you build. What you’ve shipped lately. One specific number if you have one.<\/li>\n
  3. 30s, why here:<\/strong> One specific reason this company and this team. Not “I love your mission”. Reference a real product decision, blog post, or open-source repo of theirs.<\/li>\n<\/ol>\n<\/div>\n<\/div>\n

    A worked example (backend engineer)<\/h2>\n

    Here’s what a real 90-second answer sounds like for a mid- level backend engineer interviewing at a payments company:<\/p>\n

    \n
    \n

    “I studied computer science at IIIT Hyderabad and started out writing data pipelines for a fintech in Bangalore. I’ve spent the last three years at Razorpay on the payments-routing team, building the service that picks which payment processor a transaction goes to in real time. The most interesting thing I shipped last quarter was a failover system that cut our checkout drop rate by about 18% during processor outages.”<\/p>\n

    “I’m here because I read your engineering post on multi-region idempotency last month and your architecture is almost identical to the one I’ve been working on. The scale you’re at is the next step up for me, and the routing problems you’re solving are exactly what I want to spend the next few years on.”<\/p>\n<\/div>\n<\/div>\n

    Notice what this answer does. One specific previous role, one specific number, one specific reason for this company. It buys the interviewer thirty real questions they can ask follow-ups on. It also signals that you’ve read their engineering blog, which most candidates don’t.<\/p>\n

    What candidates get wrong<\/h2>\n

    Across the candidates LastRound AI<\/a> sees in mock rounds, four failure modes account for most weak openers:<\/p>\n