Conversation guides · First day · New coworkers
What to Say on Your First Day at a New Job (and the First Week After)
The first day at a job is a rare social event: a room of people who have all already decided to like you — hiring you was their choice — and you still feel like an intruder. Every conversation is a first impression, but the bar is dramatically lower than it feels: new hires are expected to know nothing and ask everything.
That expectation is a temporary superpower. This guide covers the self-introduction, the questions that build relationships while you learn, lunch and coffee politics, and the remote-onboarding version of all of it.
How do you introduce yourself on the first day of a new job?
Name, one line of background, one line of genuine enthusiasm, one human detail — delivered warm and short. Nobody remembers new-hire credentials; everyone remembers new-hire vibe.
You'll give some version of this introduction fifteen times in week one — standups, intro meetings, hallway collisions. The résumé recital is the common failure: it's what the room already knows (they read your CV) delivered in the tone of a visa interview. The human detail is what sticks, because it gives people a handle that isn't your job title.
“I'm Sam — just joined the platform team, coming from about five years in fintech. Genuinely excited about what you're doing with the data pipeline, which I realize is a nerdy thing to be excited about. Outside work I'm mostly trying to keep a sourdough starter alive. Very open to advice on both fronts.”
What questions should a new hire ask in week one?
Week one licenses every question — 'walk me through how this actually works,' 'who should I meet,' 'what's the unwritten rule I'll trip on' — and asking them builds relationships faster than competence displays do.
The instinct is to prove the hire was right by demonstrating knowledge. Invert it: every question you ask a colleague is a small gift — it says their context matters, and people bond with those they've helped. The 'who should I meet' question is the compounding one; each answer hands you a warm introduction, and the map it builds is the org chart nobody writes down.
“Can I grab twenty minutes for you to walk me through how the release process actually works — not the wiki version, the real one? I'd rather learn it from you than reverse-engineer it badly.”
“Who are the two or three people outside our team I should get to know early? And is there anyone I should meet just because they're great?”
How do you get included in lunch and coffee routines?
Say yes to every invitation in week one, and issue your own by attaching to routines — 'I'm getting coffee, anyone want anything?' builds inclusion faster than waiting to be adopted.
Early invitations are tests of the pleasant kind: the team probing whether you're joinable. Accept them even when you'd rather decompress — week-one presence buys months of goodwill. And don't only wait: the coffee-run offer is the lowest-stakes invitation that exists, gets someone to walk with you roughly a third of the time, and marks you as someone who initiates.
If no invitation comes by day three, it's almost never rejection — established teams simply forget their routines are closed. Invite yourself cheerfully once, and the routine absorbs you.
“Is the noon lunch crew an open club? I'm still at the eating-alone-at-my-desk stage and I'd like to graduate.”
How do you handle a remote first day?
Book fifteen-minute intro calls with everyone your manager names, keep your camera on in week one, and say something in every meeting — remotely, silence reads as absence, and absence is the only first impression that's hard to fix.
In an office, proximity does the introduction work for free. Remote, there is no ambient exposure — every relationship starts as a calendar event, so send the invites without embarrassment; receiving an intro-call request from a new teammate is universally read as conscientious, not needy. In meetings, one small contribution per call — a question counts — is enough to register as present.
The Slack version of the human detail matters too: a short intro post with something answerable ('tell me your sourdough secrets') gives twenty people a zero-cost way to say hello, and the replies are your first map of who's friendly.
“Hi! New on the platform team as of Monday. My manager said you're one of the people who actually knows how things work here — could I steal 15 minutes this week for an intro? No agenda beyond putting a person to the avatar.”
Frequently asked questions
I forgot everyone's names by day two. What now?
The amnesty window is long: 'I'm sorry — week-one name overload, tell me yours once more?' works for a full month and nobody minds. Write names down after meetings, and use the org chart photos shamelessly. The only mistake is avoiding people to dodge the admission.
How much should I talk in meetings during week one?
Ask clarifying questions freely; hold prescriptions until you have context. 'Is there history behind why it works this way?' is the perfect week-one register — engaged, humble, and it often surfaces exactly the context that would have made your suggestion wrong.
My onboarding buddy is unresponsive. Do I escalate?
Route around before escalating: the map question ('who should I meet?') asked of anyone friendly generates replacement guides within a day. If the buddy's silence is blocking actual access or accounts, tell your manager factually — 'I still need X, who's the right person?' — which gets you unblocked without filing a complaint about anyone.
When does the 'new person' license expire?
Basic how-does-this-work questions feel natural for a month or two; the 'unwritten rules' and 'who should I meet' questions are honestly good forever. The real expiry is on silence — the longer you wait to start asking, the harder asking gets. Spend the license while it's fresh.