Interview guide
How to answer “Tell me about yourself”
For senior IT professionals, the opening question is not an invitation to retell your resume — they already read it. It's two minutes to prove you can fix their problem and that you want to fix it here.
“Tell me about yourself” opens almost every screening call, and most experienced candidates waste it on a chronological tour of their career. That's the one answer the interviewer doesn't need — they have your resume open in front of them. What they don't have yet is the connection between your experience and their situation. The candidates who make that connection in the first two minutes set the frame for the entire interview.
What the question is actually checking
A screening interview exists to double-check two things — and this question is where the interviewer starts collecting evidence on both. Answer it as if those two checkboxes were printed on the wall behind the camera.
Relevance: will this person fix our problem?
- The role exists because something specific needs doing — and they're paying serious money for it.
- They're checking how closely your experience matches that exact need.
- Evidence: you've solved problems like theirs before, with outcomes.
Motivation: does this person want to be here?
- Why this company and this role — not any company with this title.
- Whether you'll stay engaged past the honeymoon quarter.
- Cultural fit: how you talk about teams, conflict, and past employers.
Everything in your answer should feed one of those two checks. Anything that feeds neither — the year you graduated, the full list of employers, the technology tour — is time taken from the best persuasion slot you will get in the whole process.
Don't retell your resume — they already read it
You were invited to this interview because your resume passed. Walking through it again out loud adds nothing, takes minutes, and signals that you haven't thought about what this conversation is for.
- Keep it short. Aim for about two minutes. Long answers don't sound senior — selective ones do. If they want more depth on anything, they will ask; leaving them room to ask is part of the design.
- Skip the chronology. “I started in 2008 at…, then moved to…” is the resume read aloud. Open instead with one positioning sentence — who you are professionally and what you're reliably good at — and spend the rest on evidence.
- Bring specific examples, not adjectives. “I'm a results-oriented leader” checks no boxes. “Last year I took over a delayed platform migration and shipped it in four months” starts checking the first one.
- Choose the examples for this role. Two or three problems you solved that mirror the problem this company is hiring to fix. The rest of your career — however impressive — stays in reserve for later questions.
This answer is prepared, not improvised
You cannot aim at their problem if you don't know what it is. The preparation for this one question is the same research that powers the whole interview — done before the call, not discovered during it.
- Understand why the opportunity exists. Growth, a backfill, a struggling system, a new product line — each implies a different problem, and a different two minutes.
- Extract what they're actually looking for. Re-read the job description for the requirements that are repeated, detailed, or listed first. That's the need they're paying for; that's what your examples must hit.
- Match your evidence to it. From your career, pick the two or three problems you solved that most resemble theirs — with the outcome each one produced.
- Research the company well enough to want it out loud. Product, stage, customers, direction. Real motivation quotes specifics; generic motivation (“I'm excited about your mission”) reads as a mass mailing.
The shape of a strong answer
About two minutes, in four moves. Not a script to memorize — a structure to fill with your own evidence for each specific company.
- 1. Position yourself in one sentence. Who you are professionally, at what level, and the kind of problem you're known for solving. One sentence, not a biography.
- 2. Prove it with two or three relevant examples. Problems you solved that mirror what this role is hiring to fix — each with a concrete outcome. This is the core of the answer and where most of your two minutes goes.
- 3. Say why you're here. The researched, specific reasons you want this company and this role — the product, the stage, the problem itself. Name real things.
- 4. Close with the summary that checks both boxes. “Given my experience with exactly this kind of problem, and what I understand you're looking for, I know I can deliver here — and here's why I want to do it at this company specifically.” Said in your own words, this lands both checkmarks in the interviewer's notes at once.
What to avoid
- The chronological career walkthrough — it's the resume they already read.
- Personal life stories, unless the company culture explicitly invites them.
- Generic motivation that would fit any company if you swapped the logo.
- Running past three minutes. The interviewer stopped taking notes at two.
- Sounding memorized. Rehearse the structure and the examples out loud, not a word-for-word script.
In short
The opening question is the screen in miniature.
- The interviewer is verifying two things: you can fix their problem, and you want to fix it here.
- Don't retell your resume — bring two or three specific, relevant problems you solved, with outcomes.
- Prepare it: know why the role exists and what they're paying for, and research the company until your motivation names real things.
- Stay near two minutes, and close by connecting your experience to their need — and your reasons to their company.
When they turn it around and ask what questions you have, that's its own opportunity — see what to ask in a screening interview. And for where this whole round fits in the wider process, see the job search strategy guide for experienced professionals.
Two minutes decide the frame. Prepare them.
Save the job, get the company brief, and build a “tell me about yourself” that aims your real experience at their real problem — before the recruiter calls.