Knowing how to prepare a one-minute self introduction in English is one of the most practical things you can do for your professional life. Job interviews, networking events, conference introductions, video calls with a new team — all of them open the same way, with someone asking who you are. Sixty seconds is a short window, and most people either fill it badly or fail to use it at all.
This article gives you a structure that works, the language to populate it, and a method for practising until the words come out the way you intended.
Why sixty seconds is harder than it sounds
Most people, asked to introduce themselves, either say too little ("I'm Maria, I work in finance") or far too much — a rambling account that loses the listener somewhere around the third job title. Neither serves you.
A well-shaped sixty-second introduction does three things: it tells people who you are, what you do, and why it matters to them in this context. That last part is what most learners leave out. The introduction is not a biography; it is a beginning of a conversation.
The four-part structure
Think of your introduction as four beats, each doing a specific job.
1. Name and current role (one sentence)
Begin clearly. Say your name at a pace your listener can actually register — many non-native speakers rush their own name out of habit or nerves, and it is the one word the room most needs to catch.
Example: "My name is David Kwon, and I lead the customer success team at a mid-sized SaaS company in Berlin."
2. Your specific expertise or background (one to two sentences)
This is where you give your introduction substance. Be specific. "I have experience in marketing" tells nobody anything. "I spent five years helping European startups build their first English-language content strategies" tells a story and implies a skill.
If you have a relevant academic background or a career shift worth noting briefly, put it here. Keep it to the point — this section is context, not a CV.
Example: "Before that, I trained as a civil engineer, which is why I tend to think about systems before I think about words."
That small detail is memorable. One telling fact outperforms a list of credentials.
3. What you bring or what you are working on now (one sentence)
This is the value statement — the answer to the listener's silent question, so what? Frame it in terms of what you do for others, not what you have achieved for yourself.
Example: "Right now I'm focused on helping technical teams communicate their work to non-technical stakeholders — which turns out to be most of the job."
If you are at an interview, this sentence should connect directly to the role. If you are at a networking event, it should be something a stranger can latch onto and ask you a question about.
4. A brief forward-facing close (one sentence)
End with something that opens the conversation rather than closing it. This does not need to be dramatic — a simple statement of what you are interested in, hoping for, or working towards is enough.
Example: "I'm here today because I'm interested in how companies at this scale handle internal knowledge management, and I'd welcome any thoughts on that."
If this is a job interview and the interviewer has asked "Tell me about yourself," your close can simply signal that you are ready to go deeper: "I'm happy to go into any of those areas in more detail."
Putting it together: a complete worked example
Here is the full introduction, spoken in approximately 140 words — right in the target range:
"My name is David Kwon, and I lead the customer success team at a mid-sized SaaS company in Berlin. I spent five years helping European startups build their first English-language content strategies before moving into this role — and before that, I trained as a civil engineer, which is why I tend to think about systems before I think about words. Right now I'm focused on helping technical teams communicate their work to non-technical stakeholders, which turns out to be most of the job. I'm here today because I'm interested in how companies at this scale handle internal knowledge management, and I'd genuinely welcome any thoughts on that."
Read it aloud now. It should take between 50 and 65 seconds at a measured pace. If it rushes past in 35, you are going too fast.
How to adapt it for different situations
The structure stays the same; the content shifts.
- Job interview: Section 3 should mirror language from the job description. If they want "stakeholder communication," use that phrase.
- Networking event: Section 3 can be more open-ended and curious. You want to invite a response.
- Conference or seminar introduction: Section 2 should lean towards your relevant expertise in the field. Section 4 can state what you are hoping to learn.
- First day in a new team: Keep it warm rather than formal. Section 3 might say what you are looking forward to, not just what you bring.
The delivery: where most introductions fail
Content is only half the work. The way you say it shapes how it lands entirely.
Pace. Most people speak faster when they are nervous. Mark two pause points in your script — after your name, and after your main role — and treat them as obligatory. A one-second pause feels enormous to you and perfectly natural to a listener.
Stress. Every sentence has one or two words that carry its meaning. Stress those words; let the others sit quietly around them. In the sentence "I help technical teams communicate their work to non-technical stakeholders," the words that matter are technical, communicate, and non-technical. Flatten those into the same level as everything else and the sentence loses its shape.
Eye contact and body. If you are speaking in person, look at your listener — not at your own hands or the middle distance. In a video call, look at the camera, not at the person's face on screen. The difference is noticeable.
Ending cleanly. Many speakers trail off at the close, either rushing the last sentence or ending on a rising intonation that sounds like a question. Finish your final sentence with a falling tone and let it land. It signals that you are done, confident, and ready.
How to practise
Write your script. Count the words — you want 130–150 for one minute at a comfortable pace.
Then practise in this order:
- Read it aloud three times, just to get the words into your mouth.
- Record yourself on any phone. Listen back. Note where you rush, where your voice drops flat, where a word gets swallowed.
- Fix those moments specifically. Do not re-record the whole thing — go back to the line that needed work and practise only that line, five or six times, until it sounds right.
- Practise without the script. Not word for word — the ideas and key phrases. If you can say it without the page, you own it.
- Say it to a real person. A colleague, a friend, anyone. Real presence changes things.
You can find more on the mechanics of delivery — pace, breath, and intonation — in our piece on how ummute works.
On sounding like yourself
There is a version of this preparation that produces something polished but oddly inert — an introduction that sounds like it was written by a committee. Avoid it. The goal is not to perform confidence; it is to be clear. Use your own vocabulary. If you would never say "dynamic professional" in conversation, do not say it in your introduction. The sentence that represents you best is one you could say again, differently, without losing its meaning — because you understand it, not just because you rehearsed it.
A clear, honest sixty seconds in natural English will do more for you than a sophisticated but hollow one. Structure gives you the shape. Your own voice fills it.