Direct answer
Use present → proof → why this job: your current focus, one relevant contribution, and the requirement you can help meet.
Try roughly 60–90 seconds unless given a limit: Robert Walters and Revarta recommend that starting range [1–2]; the comparison below shows why it is not universal.
End on the job's top requirement with evidence you can defend, so the first follow-up can land where you are strongest.
How long should it be — and why does the advice disagree?
| Source | Length it gives | Context | Read date |
|---|---|---|---|
| [1] Robert Walters | 60–90 seconds | Brief professional introduction. | 2026-10-28 |
| [2] Revarta | 60–90 seconds | Editorial rehearsal target, not a scoring rule. | 2026-10-28 |
| [3] SEEK NZ | 2–3 minutes | Main advice: selected career highlights. | 2026-10-28 |
| [3] SEEK NZ | 1–2 minutes | FAQ on the same SEEK page; a different range. | 2026-10-28 |
| [4] LockedIn AI | 60–90 seconds; under 2 minutes | Body advice, despite ‘3-minute rule’ in its URL. | 2026-10-28 |
Three context changes explain why a single target is unsafe: a brief introduction is different from ‘walk me through your resume’; a recruiter screen and a panel may need different detail; an explicit limit overrides either. These sources do not establish a universal optimum. SEEK even gives two ranges on one page; do not average them into a new rule.
Measure your own pace: read your draft aloud for one minute and count the words actually spoken. Call that count W. At that pace, 60 seconds is W words and 90 seconds is 1.5 × W. Leave room for pauses, then record the whole version; arithmetic is a planning aid, not a delivery target.
For an English-language opening, use the short version as a starting point and ask if a fuller career walkthrough is wanted. Language alone does not determine the employer's time limit.
- [1] Robert Walters — read 2026-10-28
- [2] Revarta — read 2026-10-28
- [3] SEEK NZ — read 2026-10-28
- [4] LockedIn AI — read 2026-10-28
Build it from the job description
- Underline the two requirements most central to the work, not every keyword in the advert.
- For each, choose one true example: your action, its scope, the result and how you know it happened. Mark gaps honestly.
- Order it as present → proof → why this job. Finish on the requirement your strongest example supports.
- Cut details that do not help this employer assess that requirement. Say the draft aloud and keep one detail ready for a follow-up.
Illustrative, fictional job and answer. Replace the details with evidence from your own work.
JD line
Maintain accurate stock records and investigate discrepancies with warehouse teams.
Weak introduction
I am organised and good with people. I have worked in several businesses and always do my best.
Why it fails
There is no stock-record example, no personal action and no link to the vacancy. The adjectives cannot be checked.
Rewrite
I work in retail stock control, checking receipts against shelf counts. When an item kept showing as available after it sold out, I traced the mismatch to returns entered under a similar product code. I corrected the affected entries with the supervisor and wrote a code-check step for the next count. I did the reconciliation; warehouse colleagues checked the physical stock. I want this role because it combines accurate records with investigating discrepancies across teams.
Same question, five interviewers
Disclosure: MockLive is our practice product. These are translations of what our interviewer scripts ask, not an industry norm or a guarantee of identical generated wording. Every MockLive session opens with a self-introduction turn; the wording changes by interviewer.
| Interviewer | Scripted opening prompt | Stated opening limit |
|---|---|---|
| HR recruiter | Please introduce yourself and briefly talk about your experience. | Under two minutes (stage goal). |
| Hiring manager | Please introduce yourself, focusing on experience relevant to this job. | None specified. |
| Technical expert | Briefly introduce the direction you have been working in recently. | None specified. |
| Department head | Take three minutes to describe your recent work and why you want to move. | Three minutes in the prompt. |
| Executive | Leave the resume aside; first tell me about you as a person. | None specified. |
Recording stops automatically at 3 minutes per answer. That is a stop, not a target: finish earlier when you have answered the question.
What a graded introduction looks like
A report generated from a demo session (synthetic voice, demo role and history; criticism is unverified model output). The session was in Chinese; the quoted answer and feedback below use the published English walkthrough's translations.
Question
Please introduce yourself, and describe your most relevant hands-on experience for this role's focus on an enterprise knowledge base and disaster-recovery operations.
Quoted answer
Demo report, first question — English translation of the Chinese transcript
“As I see it, the enterprise knowledge base and “ops cultivation” scenarios in the JD match my experience. I've shipped RAG, and I've done on-premises deployments. At two companies I took AI capabilities from zero to launch, so delivering large models for “ops cultivation” here is a pace I know well.”
Model critique — unverified
The candidate shows a serious lack of understanding of the core business scenario, misreading “ops disaster recovery” as “ops cultivation”, and stays at slogan-level claims without giving any concrete approach to the core steps — knowledge-base chunking, retrieval, evaluation or on-premises deployment.
The transcript reads 「运维栽培」 (“ops cultivation”) where the test audio said 「运维灾备」 (“ops disaster recovery”, the job-description term) — a speech-recognition slip. The report below criticises it as if the candidate had said it; it is left as generated.
Model's suggested better answer
First get the business right. Then, for data-centre disaster recovery and operations inspection, state the concrete engineering work and metrics from your on-premises RAG pipeline — for example document splitting and cleaning, hybrid vector and full-text retrieval, and long-context handling on self-hosted open-source models.
Prepare for at most three introduction-triggered checks here: Which part was yours? How was that number measured? Why this job now? Your opening should make those answers easy to support.
Sample answers for four situations
All four samples are fictional, compact starting drafts, not timed scripts or personal claims to borrow. Expand only with true details and measure your own spoken take.
No experience / first job — fictional
I am finishing a business course and looking for my first purchasing assistant role. For our student exhibition, I compared suppliers, checked what each quotation included and kept a shared order log. When the delivery date changed, I confirmed it with the supplier and updated the organisers before they printed the programme. I have not used your purchasing system yet, but I can bring careful checking and clear updates to the work.
The follow-up it invites
What did you check before choosing a supplier?
Experienced / senior — fictional
I lead a maintenance planning team. My work is deciding which faults need immediate attention and which can wait for a planned shutdown. On a recent shutdown I reconciled the fault log with inspection notes, challenged duplicate work orders and agreed priorities with production. Technicians made the repairs; I owned the plan and handover. Your role interests me because it adds responsibility for coordinating that planning across sites.
The follow-up it invites
How did you decide which faults could wait?
Career changer — fictional
I teach adult learners and am moving into customer training. I already break unfamiliar processes into steps and adjust a session when people get stuck. For an evening class I replaced a long demonstration with a short task and a troubleshooting sheet; learners could show me the step they could not complete. I am new to your software, so I would need product training. The connection is helping customers use a tool independently.
The follow-up it invites
How did you check whether learners could work independently?
Interviewing in a second language — fictional
I coordinate appointments at a repair centre. I confirm the fault description, check parts availability and tell customers what happens next. When a repair was delayed, I wrote a clear update and checked that the customer understood the revised collection date. I am practising explaining this work in English because your service desk supports customers in several countries. I can bring reliable case notes while I learn your product range.
The follow-up it invites
How would you check a customer's understanding without repeating everything?
Practise it out loud
Record a timed take. Listen for your own action, one checkable piece of evidence and a clear link to the job. Cut one detour and record again. With MockLive, the session opens with an introduction turn built from your resume and job description; the report quotes your words as transcribed. Open the sample report to see how a claim can shape feedback.
Speech recognition can mishear; check disputed words against the recording. Interviews may be temporarily paused. The verdict is a practice assessment, not an employer's score. First interview free — one scored mock, no card; availability still applies.
Frequently asked questions
What is the best answer to ‘Tell me about yourself’?
The one that makes your fit for this job understandable and checkable: current focus, relevant proof, reason for applying. There is no best paragraph for every candidate.
Is 2 minutes too long?
Not automatically: SEEK's FAQ allows 1–2 minutes. If the interviewer asked for one minute, two is too long. Practise a shorter cut so you can adapt.
Is 3 minutes too long?
It may be too much for a brief opening, but a requested career walkthrough can need more detail. Our department-head script explicitly asks for three minutes; that does not make it a general hiring rule.
What if I have no experience?
Say that plainly, then use a relevant school, volunteer, caring or personal-project example. Explain your contribution without presenting it as paid employment.
What should I avoid saying?
Avoid a full life story, unsupported adjectives, confidential details, invented numbers and claims that give you credit for other people's work. Do not criticise a previous employer to explain your move.
- HR screening practice
- Read the localized sample report
- Develop a proof story with STAR
- Prepare for a job interview in English
- Understand interview follow-up questions