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

To answer "tell me about yourself" in a tech interview, give a 60 to 90 second professional summary, not a life story: one line on who you are at work, two specific pieces of proof with results, and a bridge to why this role is your next step. In our view, the best answers sound prepared in structure and natural in delivery.

Definition: "Tell me about yourself" is an open-ended opening question that asks you to summarize your professional background and motivation, and it often sets the agenda for the rest of the interview.

It sounds like small talk. It's closer to a trailer for everything that follows.

What interviewers are really asking with "tell me about yourself"

In practice, the interviewer is usually trying to learn three things.

Can you communicate? Tech work runs on explaining things: a trade-off, a bug, a customer problem. A rambling answer to the easiest question in the loop is a small red flag for the harder ones.

What's relevant? You know your background better than anyone in the room. The interviewer wants to see whether you can pick the parts that matter for this job and leave the rest out.

Where should we dig? Your answer hands the interviewer a menu, and whatever you mention, they'll likely ask about next.

The pressure here is real. Ashby's 2026 recruiter productivity report (published April 2026, covering about 109 million applications since 2021) found that each hire in 2025 took more than 300 applications on average, and that candidates are roughly 50 percent less likely to get an interview than five years earlier. If you've made it into the room, the opening minute is worth rehearsing.

Do interviewers really decide in the first 30 seconds?

You've probably heard that interviewers make up their minds in seconds. The research supports a softer version. A 2010 study in the Journal of Applied Psychology by Murray Barrick, Brian Swider and Greg Stewart looked at the rapport-building stage at the start of interviews. Candidates who made stronger initial impressions went on to receive higher interview ratings and more internship offers. The interesting part: the early judgments that carried over to other evaluators were about competence, not likability or similarity.

So the opening matters, but mostly as a signal of capability, not charm.

There's a second wrinkle. Many tech companies use structured interviews, where every candidate gets the same questions scored against a rubric. Google's re:Work guide to structured interviewing describes rubrics that spell out what poor, borderline, solid and outstanding answers look like, and reports that structured interviews predicted job performance better than unstructured ones in Google's own data. Iris Bohnet, writing in Harvard Business Review, makes the same point from the other side: unstructured interviews feel effective to hiring managers but are weak predictors of performance.

Our read: the opener may not be scored directly, but it frames how the scored questions land. Treat it as setup, not as the whole game.

How to answer "tell me about yourself": headline, receipts, bridge

Here's a structure we like because it's short enough to remember under pressure.

1. The headline (one or two sentences)

Who you are professionally, right now, in plain words. Lead with the identity that matches the job.

"I'm a backend engineer who's spent three years building payment systems" works. "So, I grew up in Ohio" usually doesn't, unless Ohio is somehow the point.

2. Two receipts (three to five sentences)

Pick two specific things you've done that prove the headline. Each one gets a situation, what you did, and a result with a number if you have one. Two is enough. A third tends to blur the first two.

Choose receipts that match the job description. If the role stresses reliability, tell the outage story. If it stresses customers, tell the one where you talked to users. The NACE Job Outlook 2026 Spring Update, a survey of employers that hire new graduates, found 85 percent look for teamwork on resumes and stressed that employers want to see examples, not lists of skills. Receipts are examples.

3. The bridge (one or two sentences)

Why this role, at this company, is the logical next step. Connect something real about the company (its product, its stage, its technical problem) to the direction your receipts point. Interview coach Erika Gemzer, in a guest post for Lenny's Newsletter, suggests one decisive reason rather than several, and keeping pay, commute and complaints about past employers out of it.

That's it. Roughly 150 to 220 words on paper. Read it aloud with a timer; if it runs past 90 seconds, cut a receipt down, not the bridge.

Optional: leave a hook

End a receipt with one detail that invites a follow-up question you'd love to answer. "We eventually rewrote the queue, which was its own adventure" practically begs the interviewer to ask. You've just picked your next topic.

Who's asking changes the answer

In a tech hiring loop, you may hear this question four times. Keep the skeleton and change the emphasis.

For founder conversations specifically, our guide on how to prepare for a startup job interview covers the formats you're likely to meet. If you're interviewing for a role that doesn't involve code, tech interviews for non-technical roles goes deeper on product sense and metrics questions.

Sample answers: new grad, career changer, experienced hire

These are illustrative. Borrow the shape, not the words.

New grad applying for a software engineering role

I'm a computer science graduate from Arizona State, and most of what I've learned that I'm proud of happened outside class. Last summer I interned on the data platform team at a logistics company, where I wrote a service that validated incoming shipment files; it cut manual fixes from about 40 a week to under 10. On the side, I built a course-planning tool for students that about 600 classmates used during registration, which taught me a lot about fixing things fast when real people depend on them. I'm drawn to your team because you're working on developer tooling at a stage where a new engineer can own a whole feature, and that's the kind of first job I'm looking for.

Why it works: the headline is honest about being new, and the receipts do the heavy lifting.

Career changer: accountant moving into a data analyst role

I'm a data analyst who spent the first five years of my career as an accountant. Month-end close is where I fell for data work: I automated our reconciliation in SQL and Python and took the close from eight days to five. After that, the controller asked me to build our first revenue dashboard, which the leadership team now uses every Monday. I've since finished a statistics course and built a churn analysis on a public dataset that's on my GitHub. Your analytics team supports finance and product together, so my accounting background is useful here rather than something to explain away.

Why it works: the headline claims the new identity first, and the old career becomes an asset. If the "why are you switching" question is likely to follow, our guide on how to explain a career change covers that answer separately.

Experienced hire: product manager moving to an AI startup

I'm a product manager with about seven years in B2B software, most recently leading search at a mid-size HR platform. The project I'd point to is our move from keyword search to a retrieval-based approach: I ran the evaluation process that decided when results were good enough to ship, and search-driven conversions rose about 18 percent in the first quarter after launch. Before that, I took a reporting product from zero to roughly 200 paying customers. What I want next is a smaller team building AI products where quality measurement is central to the product, which is exactly the problem your company describes in its job post.

Why it works: one receipt is directly about the new domain (AI quality and evals), and the other shows range. For more on AI loops, see how to prepare for an AI job interview.

A fill-in template you can copy

Swap the brackets for specifics, then say it aloud until it sounds like you.

I'm a [role or identity that matches the job] with [time or context], most recently [where or what].

One thing I'm proud of: at [place], I [specific action], which [result, ideally with a number].

I also [second action at a second place or project], which [result or what it taught you].

I'm interested in this role because [real detail about the company, product or team] lines up with [the direction your receipts point].

A quick check before you use it:

• Does the headline match the job title you're applying for?
• Do both receipts include something you personally did, with "I" rather than "we"?
• Is there at least one number?
• Does the bridge mention something specific to this company?
• Does it run under 90 seconds aloud?

Common mistakes

• Reciting the resume in order. "Walk me through your resume" is a close cousin, but even then, a curated story beats a chronology. The interviewer can read.
• Starting too far back. High school, childhood, or the first job ten years ago usually burns time you need for recent proof.
• Personal details that don't help. A hobby can be fine as a closing line if it connects to the work. Family, health or politics usually aren't worth the risk.
• No numbers. Amazon's interview prep pages ask candidates to include metrics or data where applicable.
• "We" all the way through. Credit the team, but make your own part clear.
• A generic bridge. "I'm passionate about technology" fits every company, which is the problem.

"Won't a prepared answer sound fake?"

Some interviewers would rather hear a slightly messy, genuine answer than a polished pitch.

But.

The fix for a robotic answer is practice, not improvisation. Prepare the structure and the receipts, not every word, and say it a few different ways. Most people who "wing it" end up giving the three-minute chronological version, which interviewers seem to like least.

A short practice routine

An illustrative plan for the two days before an interview:

1. Day one, 30 minutes. Pull up the job description and two or three similar listings. On the 1752vc careers board, you can filter by level and time posted to find recent roles like the one you're interviewing for; skills that show up in all of them are good candidates for your receipts.
2. Draft three lengths. A 30-second version for a recruiter call, a 60 to 90 second standard version, and a two-minute version for a founder who says "take your time."
3. Record yourself once. Cut filler, and check that your first sentence is your headline.
4. Day two, 15 minutes. Say it to a friend and ask what they'd want to ask next. If their question isn't one you want, change the hook.

Where we land

"Tell me about yourself" isn't a trick. It's an invitation to set the agenda.

Our view is that a short, structured answer with real proof beats both the memorized pitch and the ramble. That's a perspective, not a law of hiring. Some interviewers want more warmth, some only facts, so adjust to the person in front of you.

If you're still looking for the interviews to practice on, the careers board lists open roles at venture-backed startups, AI companies and VC firms, and each job has its own page you can study before you talk to the team. For the VC version of the loop, our venture capital interview questions guide covers the questions that tend to follow the opener.

The bottom line

Say who you are, prove it twice, and point to why this job is next. Keep it under 90 seconds.

They asked about you.

What they're listening for is the job.

Key takeaways

• Answer "tell me about yourself" in 60 to 90 seconds with a headline, two receipts and a bridge to the role.
• Early impressions in interviews do seem to matter, but a 2010 Journal of Applied Psychology study found the early judgments that carried over were about competence, not likability.
• Tailor the emphasis to who's asking: recruiter, hiring manager, peer engineer or startup founder.
• Use specific results and numbers, and make your own part clear with "I."
• Prepare the structure and the proof, not a word-for-word script, and practice it aloud.

Frequently asked questions

How long should a tell me about yourself answer be in a tech interview?

Somewhere between 60 and 90 seconds is a common target, which is roughly 150 to 220 words written down. That's long enough for a headline, two specific examples and a reason you want the role. Shorter can work for a quick recruiter screen. Past two minutes, many interviewers start to lose the thread.

How should a new grad answer tell me about yourself with little work experience?

Lead with an honest headline, such as your degree and the kind of work you want to do, then use internships, class projects, research, part-time jobs or side projects as your two examples. Specific results matter more than prestige. Close with why this team is a good first job for you, tied to something real about the company.

Is walk me through your resume the same as tell me about yourself?

They're close. "Walk me through your resume" signals the interviewer wants a little more chronology, so it can help to move through roles in order while still spending most of your time on the two or three most relevant ones. In both cases, a curated story tends to land better than reading out every line.

Should you mention hobbies when asked to tell me about yourself in an interview?

Usually only briefly, and only if the hobby connects to the work or shows something useful, such as building side projects, competing, or teaching. Lead with your professional story. A short personal line at the end can make you memorable, but personal details unrelated to the job tend to use up time better spent on proof.

What should you avoid saying when an interviewer asks you to tell me about yourself?

Avoid starting with childhood or very old jobs, reciting your resume line by line, sharing private details such as health or family plans, criticizing past employers, and giving a generic reason for applying. Also watch for answers that only say "we." Interviewers generally want to hear what you personally did and why this role fits.

Sources

• Ashby: Recruiter Productivity, 2026 Talent Trends Report
• Journal of Applied Psychology: Initial Evaluations in the Interview (Barrick, Swider and Stewart, 2010)
• Google re:Work: A Guide to Structured Interviewing
• Harvard Business Review: How to Take the Bias Out of Interviews
• NACE: The Key Skills Employers Seek on College Students' Resumes
• Lenny's Newsletter: How to Pass Any First-Round Interview (Erika Gemzer)
• Amazon Jobs: SDE II Interview Prep
• Amazon Jobs: Technical Product Manager Interview Prep