MokchiInterview Stress Testing

Posts / Research & Thinking

How to answer “tell me about yourself” without rambling

David4 min read

“So, tell me about yourself.”

It’s almost always the first thing they ask, and it’s the question people fumble most. Not because it’s hard, but because it feels like it has no edges. You start somewhere, a memory pulls you sideways, you double back to add context, and ninety seconds later you’re explaining your sophomore year while the interviewer’s eyes go flat.

The answer wasn’t wrong. It just never landed.

Learning how to answer “tell me about yourself” is really learning to resist that pull. You say less, on purpose, in a shape you’ve decided in advance.

They’re not asking for your life story

The mistake is treating it as an open invitation. It isn’t. “Tell me about yourself” is a soft-focus version of a sharper question the interviewer is too polite to ask outright: why are you sitting in this chair, and should I keep listening?

So they don’t want chronology. They don’t want your hobbies unless the hobbies are the point. They want a quick, confident case for why your path leads naturally to this role, delivered in a way that shows you can organize a thought under a little pressure.

That reframe does most of the work. Once you’re answering “why me, for this” instead of “who am I,” the rambling has nowhere to go.

A structure that keeps you tight: present, path, why here

The most reliable shape is three beats, in this order:

  • Present. Where you are now, in one line. Your current role and the thing you’re known for. “I’m a product designer, and for the last three years I’ve owned the onboarding experience at a fintech startup.”
  • Path. The short version of how you got here, chosen to point at this job. Two or three moves, each earning its place. Skip everything that doesn’t build the case.
  • Why here. Why this role, this team, now. This is the beat most people drop, and it’s the one that makes you memorable. It turns a summary into an argument.

Three beats, roughly ninety seconds. If you can’t say it in ninety seconds, you haven’t decided what it’s about yet, and deciding is the whole job.

What to cut

Most rambling is just uncut material. A few reliable offenders:

  • The full timeline. You are not obligated to start at graduation. Start where the story that matters starts.
  • Caveats and hedges. If something “might not be relevant,” cut it. If it is relevant, say it plainly.
  • The second example. One vivid, specific instance beats three vague ones. Pick the best and let it carry.

The goal isn’t to sound rehearsed. It’s to sound like someone who knows what they think, which, not coincidentally, is what the rest of the interview is testing too.

Tailor the “why here” every time

The present and path stay fairly stable. The “why here” should change with every company. Read the role, find the one thing that genuinely draws you, whether that’s the problem, the stage, or the team, and name it specifically. “You’re rebuilding your design system from scratch, and that early-foundations work is exactly what I want to be doing next” beats any amount of “I’m passionate about great products.”

Specific is believable. Generic is noise.

Then practice it out loud, not in your head

Here’s the part that separates a good answer from a good answer that survives contact with a real interview. You have to say it out loud, more than once, before it counts.

Rehearsing in your head is a trap. In your head there are no filler words, no lost threads, no moment where your mind goes blank three sentences in. The room has all of those.

This is the exact gap that made us build Mokchi. Reading advice and rehearsing silently didn’t recreate the hard part: being asked a question, hearing yourself answer, and finding your way back when a follow-up knocks you off script. So practice the way it will actually happen. Say your answer aloud, once, without restarting. Then do it again. By the third pass it stops being a script you’re trying to remember and starts being something you just know.

“Tell me about yourself” isn’t the hard question. It’s the one you can fully prepare, a ninety-second case for why you’re the obvious fit, tightened until there’s nothing left to cut. Get that one right and you walk into every interview having already won the first minute.

David · Co-founder, Mokchi

Building Mokchi. Writes about interview practice and thinking clearly under pressure.

Keep reading

Follow the work

Occasional notes as we build Mokchi. No cadence promise, and we won’t use this for anything else.