"Tell me about yourself" opens almost every interview, and most engineers answer it badly. They recite their resume in chronological order, or they ramble about hobbies, or they say "um, where do I start?"
The question isn't an invitation to tell your life story. It's a 60 to 90 second pitch for why you're a fit for this job.
What the interviewer wants
They're checking three things:
- Can you communicate clearly and concisely about your own work?
- Is your experience relevant to this role?
- Do you have a sense of direction, or did you just end up here?
For engineering roles, add: can you describe technical work in a way a non-expert follows?
The structure: Present, Past, Future
Present: your current role and what you're doing in it, with one concrete result. Past: one or two earlier experiences that explain how you got here and add relevant skills. Future: why this role and this company are the logical next step.
Aim for about 90 seconds, roughly 200 to 250 words spoken.
Example: mid-level backend engineer
"I'm a backend engineer at a logistics startup, where I own the order routing service. Last year I rewrote the matching logic, which cut median latency from 800 to 150 milliseconds and let us handle three times the volume without adding servers.
Before that I was at an agency building APIs for a range of clients, which taught me to ship quickly and talk to non-technical stakeholders.
I'm looking for a role where I can work on systems at larger scale and with a stronger engineering culture, which is why this team's work on real-time data pipelines caught my attention."
Why it works: a number, a clear role, a reason for the move that points at the company.
Example: junior engineer or new graduate
"I just finished my computer science degree, where I focused on distributed systems. For my final project I built a chat app with offline sync, which taught me a lot about conflict resolution and testing.
I also interned at a fintech company, where I fixed bugs in a payments dashboard and shipped my first feature to production, a CSV export used by the support team.
I want to join a team where I can learn from experienced engineers while contributing quickly, and your internship-to-hire path and focus on code review is a big reason I applied."
Example: senior engineer or tech lead
"I've spent the last ten years building data-heavy products, most recently as a staff engineer leading a team of six on our analytics platform. I'm proudest of moving us from a monolith to services without downtime, and of mentoring three engineers to senior.
Earlier in my career I worked at two startups where I did everything from infrastructure to front end, which is why I care about pragmatic technical decisions.
Now I'm looking for a role with more product influence, and this position's scope across platform and product is what I'm after."
Example: career changer
"I spent six years as a data analyst, writing SQL and Python every day, and increasingly I was building the pipelines rather than the reports. Two years ago I started contributing to our internal tooling, and last year I moved into a software engineering role on that team.
I bring a strong sense of what the end users of data systems need, and I've since built up solid engineering habits: testing, code review, CI.
I'm excited about this role because it sits right where engineering meets analytics."
Mistakes to avoid
- Reciting the resume. They have it. Pick the two or three things that matter for this job.
- Going too long. Past two minutes, you're losing them.
- Listing technologies. "I know Python, Go, Kubernetes..." tells them nothing. Say what you built with them.
- Being too personal. One light personal line is fine; a life story is not.
- Skipping the future. End by connecting to this role.
- Memorizing word for word. It sounds robotic. Memorize the structure and key numbers instead.
Tailor it each time
Keep a base version and adjust the last third for each company. Read the job description: if they emphasize scale, lead with scale. If they emphasize product, lead with product impact.
Practice it out loud
You can write a perfect answer and still stumble when you say it. The first 15 seconds set the tone, and that's where people hesitate most. Practice until it sounds natural, recording yourself if you can.
Or practice with a voice interviewer. Kalbeki lets you answer "tell me about yourself" and follow-ups in a real spoken conversation, and shows feedback on pacing, filler words, and clarity. Try it free.
The short version
- Use Present, Past, Future, in 60 to 90 seconds.
- Lead with your current work and one measurable result.
- Pick experiences relevant to the job.
- End with why this role.
- Tailor the last third for each company.
- Practice out loud.