How to Write a One-Minute
Self-Introduction

Most people prepare a self-introduction by writing a "complete biography," then squeezing it into a minute during the interview. The result: thirty seconds of preamble before the point, or a rapid-fire list of titles the listener can't rank. The better order is the reverse — fix the 60-second structure first, fill it with content, then check pacing with one camera rehearsal.

Why the "one minute" constraint

At a normal speaking pace, one minute carries roughly 140–160 words — just enough for three things: who you are, what you've done, and why you're here. Less than 30 seconds feels thin; beyond two minutes, attention visibly drops unless the information density rises to match.

So "one minute" is not a word limit. It's an attention design: it forces you to cut preamble and keep only the parts most likely to get follow-up questions. While writing, ask yourself one question: if they remember only one sentence, which one should it be?

Three structures you can use today

1. Credentials: for multi-role or career-switch stories

The shape is "positioning → one sentence per major role → land on this opportunity." Keep only the result from each role that directly relates to the position.

Sample phrasing: "For the past five years I've done two things: owned X in industry A, taking Y from … to …; then joined team B to build Z. What drew me here is exactly where X and Z meet." The move is translating "I've done a lot" into "these connect here."

2. Competencies: for early-career and pivots

When history is short, organize by capability instead of chronology. Pick two or three competencies, and attach one verifiable mini-example to each — a project, competition, portfolio piece, or team you led.

Sample phrasing: "My core strengths are two: breaking complex problems into executable steps — in my last project I …; and deciding under incomplete information — when …". Avoid unverified adjectives like "fast learner" that carry no example.

3. Story: for creative roles, founders and pitches

Open with a 15-second concrete scene, then return to your positioning. The opening hook decides whether they invest the remaining 45 seconds.

Sample phrasing: "At a pitch last year, I watched the audience check their phones for the first 30 seconds. That's when I learned a good opening doesn't introduce you — it gives people a reason to stay. I work on X, and …" Note: the scene serves the positioning; it must not become a personal biography.

Four writing details

Then record one take

A self-introduction is the classic case of "well written ≠ well delivered." Text that reads smoothly usually fails on camera in three ways: one awkward phrase that trips you up, a pace that jumps in the nervous section, and a swallowed ending. None of these are visible until you record.

A 15-minute loop: prop up your phone at normal distance, record take one without notes; on review, watch only two things — where you stumble, and when your gaze leaves the lens; rewrite those one or two lines, record take two. Most people stabilize by the second take. For the full shooting setup and three-pass review method, see How to Practice Speaking on an iPhone.

What a phone can actually read from a take — gaze, posture, gesture timing across the timeline — is broken down in How Does an iPhone Analyze Your On-Camera Performance.

Three common mistakes

Mistake one: reciting the job description. "Strong communicator, great teamwork skills…" carries no information and no memory point. The listener wants the specific evidence only you can supply.

Mistake two: starting at birth. Hometown, high school, undergrad major — unless directly relevant, it's all attention spend on the prelude. The full one-minute budget belongs to "now" and "next."

Mistake three: handing over control at the end. "That's my introduction, thank you for listening" ends on politeness. A stronger close is active: "I'd especially like to talk about the X you're building — I just validated a related method in my last role." That closes the loop and sets up the next question.

And it still doesn't sound scripted

Prepared structure feels scripted only if you memorize words. If you memorize the path — positioning → two proofs → why here — each section can reword itself per context, and your voice won't carry the "what was the next line" tension. On where "scripted-ness" actually comes from, see Why Do You Sound Like You're Reading a Script?