“Tell me about yourself” is not a warm-up. It is the prompt that sets the frame for every question that follows, because the interviewer is forming an impression of you in the first sixty seconds and using the rest of the hour to confirm it. The Present · Past · Future structure gives you a defensible, repeatable answer the room can actually use.

When to use Present · Past · Future

Use Present · Past · Future as the opening to any interview that begins with a self-introduction prompt. The cues are easy to recognize:

“Tell me about yourself” (the prompt that gives the structure its name)
“Walk me through your background”
“Why don’t you start by introducing yourself”
“Give me a quick overview of you”
Any unscripted opening on a call after the small talk

How to use it

Present (≈20 seconds). Start with what you are doing right now. Title, scope, one specific signal of impact. “I’m currently a senior backend engineer at <company>, where I lead the API platform team.”
Past (≈25 seconds). One paragraph on how you got here, told as an arc, not a CV. Two prior roles or one role plus one project, with a thread that connects to the present role.
Future (≈20 seconds). Why this role next. Make it a continuation of the arc, not a detour. Name what the role offers that your current path does not.
Stop. Sixty to ninety seconds total. Do not list everything — first impressions stick across the rest of the interview, so the discipline is more important than the scope.

Example

Them

Tell me about yourself.

On your HUD

I’m currently a senior backend engineer at Acme, where I lead the API platform team — about six engineers, all of the public-facing services.
I joined Acme three years ago from a smaller startup where I had been a generalist; the move was about going deeper on distributed systems, and the API platform work has been that. Before that I was at a fintech, where I learned what production reliability actually costs.
What’s drawing me to this role is the scale of the customer commitments you carry. My current systems run at thousands of RPS; yours run at hundreds of thousands, and the failure modes change at that scale. That’s the next thing I want to learn.

What Kennan would surface in this moment, in the same first-person bullet format as the in-app HUD.

Common pitfalls

Reciting your résumé. The interviewer has read the résumé. They are listening for what you choose to lead with.
Burying the present. Open with where you are now; the room is calibrating you against the role, not against your CV history.
Over-personalizing. Hobbies, family, where you grew up — fine as one line, not as the answer.

Where it comes from

Lily Zhang (2015) · Dougherty, Turban & Callender (1994) · Barrick, Swider & Stewart, JAP (2010)

In your next meeting

Kennan watches for the conversational pattern this framework addresses and surfaces a first-person line you can read off your HUD, in the same shape as the example above. Frameworks are receipts; the user-facing output is a sentence, not a citation.