AI AI Tools Guidebook
AI Use Cases

How to Use AI to Write a 60-Second Interview Self-Introduction

Write a self-intro that doesn't sound like everyone else's — 1 line background + 2 metrics-anchored highlights + 1 line on why this role — timed to 60 seconds.

Published: Author: AI Productivity Guide Team 🌐 查看中文版本

The task

First-round interview. “So, tell me about yourself,” and you have about 60 seconds before they form an impression that shapes the rest of the conversation. The failure mode is reciting your CV in chronological order, ending with “and that brings me here today.” The job is a self-intro that earns specific follow-ups, not generic ones, in 60 seconds, and that hooks back to this role.

When AI helps — and when it does not

AI is excellent at structuring a 60-second arc, tightening adjectives, and varying registers. It is bad at picking your two highlights; that decision is yours, based on the role. Feed AI the JD; otherwise you get a generic intro that fits everyone and convinces no one.

What to feed the AI

  • Your background in one sentence (role, years, domain)
  • The JD you are interviewing for
  • 2 highlight stories with concrete metrics (users, revenue, time saved, scope)
  • One specific thing about this role / company that excites you (researched, not generic)
  • Banned tics: “passionate about,” “self-starter,” “fast learner”
  • Whether the panel is technical or non-technical (changes vocabulary)

Copy-ready prompt

Write a 60-second interview self-introduction.
Background (one sentence): <line>
JD I am interviewing for: <paste>
Highlight 1 (with metrics): <line>
Highlight 2 (with metrics): <line>
One specific reason this role excites me: <researched, specific>
Banned tics: <list>
Panel type: <technical / non-technical>

Structure:
- One sentence background (current state + adjacent expertise)
- Highlight 1 — 15 seconds, anchored in metric
- Highlight 2 — 15 seconds, anchored in metric (different skill from highlight 1)
- One sentence on why this role specifically

Constraints:
- Total ≤ 160 words (60 seconds when read out loud at interview pace)
- Each highlight earns a specific follow-up (a number, a trade-off, a decision)
- Last sentence must reference the JD specifically — name a product, a metric, a value

Variant for senior roles: “Same structure but assume the panel knows my level. Lead with one strategic contribution, not two tactical wins.”

Three short paragraphs, ≤ 160 words total. A timing note at the end (your reading speed in seconds). Two alternate openers for nerves.

How to check the output is usable

  • Time it out loud at interview pace, then adjust to 55-65 seconds
  • Each highlight has a number, a trade-off, or a decision the interviewer can ask about
  • The “why this role” line could not be pasted into another company
  • No banned tic
  • The intro earns follow-ups the interviewer would have asked anyway

Common mistakes

  • Listing every job you’ve had: the panel has your resume
  • No metrics: claims without numbers are filler
  • Generic “why this role”: interviewers detect copy-paste in 5 seconds
  • Adjective stack (“driven, passionate, collaborative”): strip every adjective on second pass
  • Over 75 seconds: cut adjectives, not stories
  • Reciting from memory: sounds rehearsed and triggers skepticism

Practical depth notes

For How to Use AI to Write a 60-Second Interview Self-Introduction, the difference between a usable AI result and a generic one is the input packet. Give the model the audience, the current draft or raw material, the desired format, the decision you need to make, and two examples of what good and bad output look like. Ask it to preserve facts first, then improve structure or wording second.

After the first response, do a separate review pass. Look for missing constraints, invented details, weak calls to action, and language that sounds plausible but does not match the real situation. The best final output should be easy to use immediately: clear owner, clear next step, and no hidden assumption that someone else has to untangle. A stronger version of this workflow also defines the handoff. Decide who will use the output, what they should do next, and what information would make them reject it. If the deliverable is copy, test whether it has a single clear action. If it is analysis, test whether it separates observation from recommendation. If it is planning, test whether dates, owners, and tradeoffs are explicit enough for someone else to execute. One final check: compare the finished result against the original goal in a single sentence. If that sentence is hard to write, the output is probably polished but unfocused. Tighten the goal, remove decorative language, and rerun only the weak section instead of regenerating the entire piece.

FAQ

  • One intro for all interviews? Background line can stay; highlights and “why this role” change per company.
  • Should I open with a hook? Only if it actually fits. Most don’t, so default to direct.
  • What if they cut me off? Plan a “skip to highlight 2” path. Practise the ending without highlight 1.

Tags: #AI writing #Job search #Workflow

Related Articles