“Tell me about yourself.”
It's one of the simplest questions in an interview.
And somehow, it can make your brain go:
Where do I even start?
Should you talk about school?
Your first job?
Every project?
Every course?
Every tool you know?
No.
The interviewer doesn't need your autobiography.
They need a clear professional story.
What Your Answer Should Do
A strong answer should quickly help the interviewer understand four things:
Who you are as a designer.
What you've done that's relevant.
What you do well today.
Where you're going and why this role makes sense.
Think of your answer as:
PAST → PRESENT → FUTURE
1. Past — How Did You Get Here?
Don't list every job you've ever had.
Instead, choose the experiences that explain how your design journey developed.
For example:
“I started in visual design, moved into product design, and gradually became more interested in solving complex user problems.”
That's much more useful than giving a chronological list of every position you've held.
Your past should provide context, not your complete history.
2. Present — What Do You Do Well Today?
Now bring the conversation into the present.
Talk about your current strengths.
For example:
“Over the last few years, I've focused on user-centred product design, working across research, interaction design and prototyping.”
Then connect those strengths to the role you're interviewing for.
The interviewer shouldn't have to figure out why your experience matters.
Make the connection for them.
3. Future — Why This Role?
This is where many candidates become too generic.
Avoid:
“I just want a new opportunity.”
Instead, explain where you're heading.
For example:
“I'm now looking for a role where I can work more closely with product and engineering teams and contribute to larger product decisions.”
The opportunity should feel like the next step in your story, not a random application.
The 60-Second Formula
When you're under pressure, remember:
1. PAST
How did I get into design?
↓
2. PRESENT
What am I focused on now?
↓
3. FUTURE
Why does this role make sense for me?
↓
CONNECT IT TO THE ROLE
Your story should have a direction.
A Copy-Paste Structure
You can use this as a starting point:
“I started in [your previous area], and over time moved into [your current area].
In my recent work, I've focused on [your strengths / type of problems], particularly in [relevant domain].
I'm now looking for an opportunity where I can [what you want to do next], which is why this role caught my attention.”
The important part isn't memorising the words.
It's understanding the story structure.
What Should You Leave Out?
You don't need:
Your entire childhood story
Every job you've ever had
Every course you've completed
Every tool you know
Every project in your portfolio
A five-minute introduction
Instead, prioritise:
✓ Relevant experience
✓ Your current focus
✓ Strengths relevant to the role
✓ What you're looking for next
Relevance > completeness.
What Should the Interviewer Remember?
By the end of your answer, they should have a simple picture:
Who are you?
What have you done?
What do you do well?
Why this role?
If those four things are clear, you've done your job.
Your Final Test
Ask yourself:
Could I answer “Tell me about yourself” in 60–90 seconds without talking about:
My entire life
Every project
Every software tool
…and still communicate:
PAST → PRESENT → FUTURE?
If yes, you're ready.
If not, it's time to practise your story.
Your career has a story.
Your interview answer needs a structure.
Comments