What should I say when introducing myself on the first day?

Three beats, under a minute: what you're joining as and what you'll be doing, one line of relevant background, one human detail people can start a conversation with later. Then stop, or hand the room back with an invitation to come and talk. Length is the commonest failure — a short introduction never damaged anyone's first week.

How do I introduce myself to a new team remotely?

Post a short written hello in the team's main channel, matching the tone of the messages already there, and then ask your manager for fifteen-minute video calls with the people you'll work with most. Remote teams run on deliberately created contact, so the one-to-one round matters more than it would in an office, not less — the corridor won't do it for you.

Should I mention my previous job title or achievements when I introduce myself?

Where you've come from, yes — one line of it, because it helps colleagues place you. Achievements, almost never: the interview needed evidence, but the team meeting reads a credentials list as either insecurity or a challenge. Let competence emerge from the work; in week one, warmth and curiosity buy far more than proof does.

How soon should I set up one-to-ones with new colleagues?

Start in week one, with your immediate team and the people your role most depends on, and let your manager suggest the wider list — asking them to help sequence it is itself a good early conversation. Fifteen to twenty minutes each is plenty, and going to people's desks or diaries rather than waiting to be approached reads as exactly the right kind of initiative.

What if I get my introduction wrong — too long, too stiff, a joke that fell flat?

It costs far less than it feels like it does. First impressions in workplaces are running averages, not verdicts — they get revised every day by how you actually work and treat people. If something genuinely landed badly, one light acknowledgement the next day resets it; what you shouldn't do is spend the week relitigating a minute the room has already forgotten.

Start

Introducing yourself in a new job: the first lines that set the tone

Updated 12 August 2026

Nobody remembers a good workplace introduction and everybody remembers a bad one — which tells you exactly what the job of week one's introductions is. You are not trying to impress; you are trying to be easy to place. A team meeting introduction that lands gives eight busy people three things their brains can file — what you'll be doing, roughly where you've been, and one human detail — and then stops. The catastrophes all come from misreading the assignment: the five-minute career recital, the joke that needed a friendlier room, the impressive credentials list delivered to colleagues who now feel measured against it.

There is a structural trap here worth naming. You have just spent weeks in interviews, polishing a self-introduction designed to sell. Week one needs the opposite register: the interview answer was for people deciding whether to hire you; these introductions are for people deciding whether they'll enjoy sitting next to you. Same facts, entirely different job. Carrying the interview version into the team meeting is the single most common way new starters get the temperature wrong.

The other thing the first fortnight's introductions quietly decide is how easy you are to help. A new starter who says plainly what they don't know yet gives colleagues a way in; one who arrives fully formed gives them nothing to offer. The worked lines below are all built on that trade — a little openness now for a lot of goodwill later — because goodwill is the actual currency of a first ninety days.

Your career — see how Start connects to the stages before and after it.

What your manager is weighing

Whether you can read a room's temperature. The same introduction that works in a nine-person stand-up dies in a forty-person all-hands; colleagues notice calibration — length, formality, humour — before they notice content.
Signals about what you'll be like to work with. Every introduction is scanned for one thing: colleague or competitor? Warmth, curiosity about their work, and an absence of credential-listing all file you as the first kind.
Whether you make yourself helpable. Naming what you don't know yet — the systems, the acronyms, the history — invites the help that shortens your learning curve; polished completeness politely declines it.
Consistency across audiences. The version the team hears, the version your manager hears, and the version the director hears should be the same person at different lengths — people compare notes more than new starters imagine.

The team meeting moment — 'everyone, this is the new starter; do you want to say a few words?'

Why it's asked: The classic ambush, usually arriving mid-meeting with zero warning, and the introduction most worth having ready. The working shape is three beats and under a minute: what you're here to do, one line of where you've been, one human detail that gives people a conversation to start later.

Model answerTeam meeting, new management accountant, housing association

"Thanks — I'll keep it short because I know you've got an agenda.

I'm Ryan, I've joined as the management accountant, so over the next few months I'll be the one asking you slightly annoying questions about budget codes — I apologise in advance. I've come from about six years in care-sector finance, most recently at a group running forty homes, so month-end under pressure is familiar territory; what's new for me is housing specifically, and I'm genuinely looking forward to learning how this sector thinks.

Outside work I'm mostly either running or talking about running, so if anyone does parkrun, I'll see you Saturday.

Mostly, though — I'd rather hear about what you all do than talk about myself, so please come and grab me, or I'll be doing the rounds this week anyway."

The closing hand-back is the professional move: it returns the meeting to its agenda, and it converts the introduction into an invitation. The one human detail is doing real work too — three weeks from now, 'the parkrun one' is how half the room will remember your name, and that is a feature.

The one-to-one rounds — introducing yourself to colleagues individually in week one.

Why it's asked: The round of fifteen-minute hellos is where the real map of the organisation gets drawn, and the mistake is making them about you. The strong version flips the ratio: two lines of you, then genuine curiosity about them — what they own, how your work will touch theirs, what they wish the last person in your seat had known.

Model answerOne-to-one, new service desk lead meeting a senior engineer, university IT

"Thanks for making the time — I'm doing a lap of everyone the desk works with, and you were top of the list.

The thirty-second version of me: I'm the new service desk lead, I've done the same job at a college about half this size, and I know the desk here has had three leads in two years — so part of why I'm here is to be the one that stays. That's genuinely the whole pitch.

What I'd really like is to hear this from your side. When the desk works well for your team, what does that look like? And when it doesn't — what's the failure that costs you most? You don't need to be diplomatic; I didn't build any of it.

[Later, closing:] That's really useful — especially the bit about escalations dying in the queue. Can I come back to you in a few weeks once I've seen the pattern myself? And what's your preference generally — do you like a heads-up message before things land, or just fixed things?"

The last question — how do you like to work — is the one people remember being asked. Almost nobody asks it, it costs five seconds, and the answer saves months of accidental friction.

'So what were you doing before this?' — the backstory without the CV recital.

Why it's asked: The most common social question of week one, and a trap for the recently interviewed: the polished career narrative is sitting right there, rehearsed, and it is the wrong answer. Colleagues asking this want a human summary and a hook or two — not evidence of suitability. You already got the job.

Model answerKitchen conversation, new marketing manager, food manufacturer

"Short version? Nine years in marketing, the last four at a drinks company up in Leeds — mostly running product launches, which taught me that everything in this industry comes down to whether the retailers give you shelf space, and that nobody ever has enough photography budget.

Before that I actually started out in journalism, which sounds glamorous and mostly meant writing about roadworks for a local paper — but it's weirdly the most useful training I've had. It's where I learned to write fast and get to the point.

What about this place — you've been here a while, right? What's the thing about working here that nobody puts in the induction pack?"

Three moves worth stealing. The self-deprecating texture — roadworks, photography budgets — does more social work than any achievement could; it signals you don't need the room to be impressed. The one genuine insight shows competence without listing it. And the question back is the real point of the exchange: the answer to 'what does nobody put in the induction pack' is the beginning of actually understanding the place, and people love being asked for the unofficial version.

Introducing yourself to senior people — the director in the corridor, the skip-level hello.

Why it's asked: Senior introductions have a different economy: less time, more consequence, and a strong pull toward either overselling or invisibility. The working version is calm, specific, and slightly forward-leaning — it names what you're here to do in outcome language and leaves one memorable hook, without pitching.

Model answerCorridor introduction, new supply chain analyst meeting the operations director, distribution firm

"Morning — we haven't met yet. Nadia Rahim; I joined Priya's team on Monday as the supply chain analyst.

I'm the one who'll be rebuilding the stock forecasting — I gather the current spreadsheet is held together with goodwill and one formula nobody's allowed to touch, so my job for the next few months is making that boring and reliable instead of exciting and fragile.

I won't keep you — but I'm doing my listening round at the moment, so if there's ever ten minutes in your diary, I'd genuinely value hearing what you'd want from forecasting that you're not getting. Either way, good to put a face to the name."

What this does deliberately: it gives the director a one-line handle for you — 'the one fixing forecasting' — which is exactly how senior people index new names. The light joke about the spreadsheet shows confidence without claiming anything yet. And the ask is perfectly weighted: a ten-minute listening request flatters their expertise and costs them almost nothing, whereas a pitch about your plans would cost them attention they haven't decided you've earned. Senior goodwill is built in exactly these thirty-second increments.

The written introduction — your first message on the team channel or email thread.

Why it's asked: Increasingly the introduction most colleagues actually meet first, especially in hybrid teams — and it obeys different physics: no tone of voice, infinite re-readability, and an audience reading at three different moments. Keep it to a short paragraph in the channel's existing register — read ten previous messages before writing yours — with the same three beats as the meeting version and one line that makes replying easy.

When you were hired to change things — introducing yourself without announcing a revolution.

Why it's asked: The hardest introduction in the set: the team knows why you were hired, and week one is not the moment to confirm their fears with a vision statement. The strong opener names the brief honestly but small — 'I'm here to work on how we do X, and I'm starting by understanding how it works now' — and spends its remaining words on respect for what exists. Announcing conclusions before doing the listening is how incoming change-makers manufacture the resistance they were warned about.

Names — the system for remembering thirty of them, and the line for when you've forgotten one.

Why it's asked: Small, human, and disproportionately noticed. Nobody minds a new starter forgetting names; the awkwardness comes from pretending. The honest line — 'I'm so sorry, week-one brain: tell me your name once more and this time it'll stick' — is charming precisely because it's ordinary, and the notes-after-each-meeting habit (name, role, one detail) means you only need it twice per person.

The external introduction — meeting customers, suppliers, or partner organisations in week one.

Why it's asked: Externally you are not introducing yourself; you are representing the organisation while new at it, and the register shifts accordingly. Two rules carry it: give the relationship continuity — 'I've picked this up from Martin, I've read the file, nothing gets dropped in the handover' — and never trade in your newness for sympathy or candour about internal matters. The reassurance an external contact wants is that the change of face changes nothing for them.

FAQ

What should I say when introducing myself on the first day?: Three beats, under a minute: what you're joining as and what you'll be doing, one line of relevant background, one human detail people can start a conversation with later. Then stop, or hand the room back with an invitation to come and talk. Length is the commonest failure — a short introduction never damaged anyone's first week.
How do I introduce myself to a new team remotely?: Post a short written hello in the team's main channel, matching the tone of the messages already there, and then ask your manager for fifteen-minute video calls with the people you'll work with most. Remote teams run on deliberately created contact, so the one-to-one round matters more than it would in an office, not less — the corridor won't do it for you.
Should I mention my previous job title or achievements when I introduce myself?: Where you've come from, yes — one line of it, because it helps colleagues place you. Achievements, almost never: the interview needed evidence, but the team meeting reads a credentials list as either insecurity or a challenge. Let competence emerge from the work; in week one, warmth and curiosity buy far more than proof does.
How soon should I set up one-to-ones with new colleagues?: Start in week one, with your immediate team and the people your role most depends on, and let your manager suggest the wider list — asking them to help sequence it is itself a good early conversation. Fifteen to twenty minutes each is plenty, and going to people's desks or diaries rather than waiting to be approached reads as exactly the right kind of initiative.
What if I get my introduction wrong — too long, too stiff, a joke that fell flat?: It costs far less than it feels like it does. First impressions in workplaces are running averages, not verdicts — they get revised every day by how you actually work and treat people. If something genuinely landed badly, one light acknowledgement the next day resets it; what you shouldn't do is spend the week relitigating a minute the room has already forgotten.