How to Answer "Tell Me About Yourself" in a Tech Interview

It's usually the first question, and it sets the tone for everything after it. "Tell me about yourself" sounds like small talk, but it's really a request for a 90-second pitch: who you are professionally, what you're good at, and why you're in this conversation.

Here's a structure that works for almost any tech role, with examples you can adapt.

What the interviewer wants to hear

They aren't asking for your life story. They want to know:

• What you do now, and at what level.
• The one or two things you're strongest at, with evidence.
• Why this role makes sense as your next step.

Everything in your answer should support those three points. If a detail doesn't, leave it out.

The present, past, future structure

1. Present: your current role in one or two sentences

Lead with your title, the kind of product you work on, and what you own.

"I'm a backend engineer at a fintech startup, where I own the payments ledger service. It processes around two million transactions a day."

2. Past: the path that explains your strengths

Pick one or two highlights that show how you built the skills this role needs. Use numbers.

"Before that I spent three years at a logistics company, where I moved our routing engine from a monolith to services and cut p99 latency from 900 milliseconds to 200. That's where I got hooked on making systems both fast and correct."

3. Future: why you're here

Connect your strengths to the job. Be specific about the company, not generic.

"I'm looking for a team where reliability and scale are the core problem, which is why your infrastructure team caught my attention, especially the work on multi-region consistency you wrote about."

That's it. Three parts, around 90 seconds, then stop and let the interviewer steer.

Example answers by level

New graduate

"I just finished my computer science degree, where I focused on distributed systems. My favorite project was a fault-tolerant key-value store I built for a class. It survived random node failures in testing, and I wrote about the consensus bugs I hit along the way. Last summer I interned on the search team at a SaaS company, where I shipped a caching layer that cut average query time by about 30%. I'm excited about this role because your team works on exactly that kind of infrastructure, and I'd learn a lot from the people building it."

Mid-level engineer

"I'm a full-stack engineer with five years of experience, mostly in TypeScript and Go. Right now I lead the checkout squad at an e-commerce company. Last year we rebuilt checkout and lifted conversion by 6%. Earlier in my career I worked at an agency, which taught me to ship quickly for very different clients. I'm looking to go deeper on a single product with real scale, and your growth team's focus on experimentation is a great fit for how I like to work."

Senior or staff engineer

"I'm a staff engineer at a cloud monitoring company, where I lead the architecture for our ingestion pipeline, about 40 engineers across four teams. My biggest recent win was cutting our infrastructure cost by about a third while doubling throughput, mostly by redesigning how we batch and compress data. Over twelve years I've moved from building features to shaping systems and growing engineers, and I've mentored several people into senior roles. What draws me here is the chance to set technical direction at an earlier stage, where those decisions still have a lot of leverage."

Tailor it to every company

Keep the same skeleton, but swap the highlights to match the job description:

• If the role stresses scale, lead with your biggest system.
• If it stresses product, lead with a feature and the user impact it had.
• If it's a leadership role, lead with people and decisions, not code.

A good exercise is to write three versions of your answer and keep them next to each other in your notes, so you can choose the right one before each interview.

Mistakes to avoid

• Reading your resume aloud. They have it. Tell the story behind it instead.
• Starting too far back. Unless it's directly relevant, skip childhood, school clubs and your first job.
• Going over two minutes. Long answers suggest you can't prioritize.
• Being vague. "I'm passionate about technology" says nothing. A specific project with a number says a lot.
• Ignoring the "why here". Without it, your answer could be for any company.

Rehearse until it sounds natural, not memorized

Write it out, then say it out loud until you can deliver it from bullet points rather than a script. Record yourself once: most people find they speak faster and add more filler than they think.

Your answer will set up the next questions, so make sure every project you mention is one you can explain using the STAR method if the interviewer asks for more detail.