Questions to Ask on First Day of Work
Questions for your first day in a new job: what to ask your manager, your new teammates, and whoever handles accounts and access, plus what the answers tend to tell you about how the place actually runs.
The questions
Open any question for the note
Where should I sit, and is there anything I need to know about getting into the building?
Why ask it
Trivial until the second morning, when reception is empty and nobody has issued you a badge. The seating answer also tells you whether the team sits together or scattered, which decides how much you overhear and how fast you learn.
What do I need set up today so I'm not blocked tomorrow: laptop, accounts, access?
Why ask it
Access requests sit in queues for days, so asking on day one is what stops week one becoming waiting. If nobody can list the systems your role needs, that means nobody has onboarded into this seat recently, and you will be assembling the list yourself.
Which meetings am I expected at this week, and are there any I can skip?
Why ask it
A recurring invite you were added to by default can eat four hours a week for a year, and it is far easier to opt out on day one than in month three. The answer also shows whether attendance here is about information or about being seen.
How do you prefer I reach you: chat, email, or just coming over?
Why ask it
Managers differ sharply here. Some read chat within seconds and treat email as an archive; others never open chat. Getting it wrong reads as unresponsiveness. If the answer is 'whatever works', watch for a week which channel actually gets replies.
What does a normal day look like for you here?
Why ask it
Ask a peer rather than your manager, because the honest version includes the interruptions and the system everyone works around. If the description sounds like the job posting, they are still being careful with you, so ask again in a week or two.
Who will I be working with most, and who should I introduce myself to this week?
Why ask it
You want names with reasons attached. If the list stops at your own team, ask who outside it signs off on things, because those are the people capable of holding your work up for a month.
Is there documentation I should read, and is any of it out of date?
Why ask it
The second half of the question is the useful half. Every workplace has a wiki; asking which pages are stale saves you from carefully following a runbook written two reorganizations ago.
What hours does the team actually keep?
Why ask it
You are asking about the pattern, not the policy: when people arrive, whether anyone works evenings, whether leaving at five is normal. 'Flexible' is ambiguous and can mean either genuinely relaxed or reachable at all times, so ask what time the last messages usually land.
How will work usually reach me: a queue, something you hand me, or something I go and find?
Why ask it
The answer describes how the team is organized. A ticket queue means demand is managed; work handed over personally means it runs through one person; 'you'll find it' means there is no intake process and your first month will involve inventing one.
When something is unclear, who should I ask first?
Why ask it
New people lose whole weeks stuck rather than look slow, and one name solves it. If your manager says to ask them anything but has no gaps in their calendar, quietly get a second name from someone on the team.
What's the first thing you'd like me to finish, and by when?
Why ask it
You want one concrete deliverable with a date, not a theme. If nothing specific exists, the role was probably approved without a plan attached, and you would rather learn that on day one than at your first review.
What's on your plate this week that I could take a piece of?
Why ask it
Taking a slice of your manager's live work puts you into something real faster than any onboarding checklist, and what they hand over first tells you which parts of the job they find least rewarding.
What would you like me to have figured out by the end of my first month?
Why ask it
This converts goodwill into something you can be measured against. A usable answer names systems, people, or a process you should be able to run. 'Settle in' leaves you guessing what counts as progress, so push once for specifics.
What's the state of the work I'm joining: is it starting, mid-flight, or being rescued?
Why ask it
Joining a rescue is a different job from joining a launch, and the version described in interviews is rarely complete. Ask what has already been tried, because that is what tells you which of your suggestions will land badly.
How fast do people usually reply here, and what counts as urgent?
Why ask it
Every workplace runs on an unwritten clock, and mismatching it reads as either careless or frantic. Ask the urgency half explicitly: if the answer is that everything is urgent, you have learned something important about the team on day one.
How will I know whether I'm doing well before my first formal review?
Why ask it
Most people find out at the review, by which point corrections are expensive. You are asking for a checkpoint: a weekly one to one, a thirty-day conversation. If no mechanism exists, propose the thirty-day check yourself and put it in the calendar.
What do new people here tend to get wrong in their first couple of months?
Why ask it
The safest way to ask about unwritten rules, because it is framed around other people. Answers are usually oddly specific, like copying in the wrong person or changing something that looked unused, and there is no way to learn them except by being told.
Is there history behind how this works that I should know before I suggest changes?
Why ask it
Most teams have a graveyard: the tool that failed, the restructure nobody mentions. Knowing about it stops your first proposal sounding like it ignores three years of context, and it usually explains a process that looked irrational.
What surprised you about how this team works when you joined?
Why ask it
Asking about surprise gets past the values poster, because a surprise is a fact rather than an aspiration. Answers range from harmless (nobody uses the desk phones) to load-bearing (real decisions get made in a Thursday call you are not in).
What do you wish someone had told you on your first day here?
Why ask it
A good closing question because it hands the other person control and needs no preparation from them. Ask several people separately: whatever two of them mention independently is the thing to act on this week.
Asking these on day one without looking lost
Practical guidance for the conversation itself
Who to ask what
Your manager
Priorities, the first deliverable, how success gets judged, and which meetings you can drop. These are the only questions where their answer is the authoritative one, so do not spend the limited time you get with them on badge logistics.
The person sitting nearest you
Hours, reply speed, which documentation lies, who to ask when stuck, what new people get wrong. A peer will tell you the working version rather than the official one, and they lose nothing by being frank.
IT, facilities, or HR
Accounts, access, building entry, expenses, payroll, holiday booking. Get the list of what is still outstanding in writing on day one, because these requests move at the speed of a queue rather than the speed of your enthusiasm.
Pacing it across the day
- 1Morning: logistics only. Access, seating, what is already booked in your calendar.
- 2Before lunch: ask your manager for the first deliverable and the date. Everything else can wait; this cannot, because it shapes the rest of the week.
- 3Over lunch or coffee: the peer questions. Normal day, real hours, who to ask, what trips new people up.
- 4Late afternoon: the two reflective ones, about surprises and what they wish they had known. People answer these better when the day is winding down.
- 5End of day: write down what you were told, including names. On day two you will have met thirty people and remember four.
Keep it to a handful
You do not need to ask all twenty on the first day, and working through a printed list makes an interrogation of what should be a conversation. Pick the four or five that apply to the job you are actually starting, ask them when the moment fits, and keep the rest for your first weekly one to one. Questions asked in week two land better anyway, because by then you can point at something concrete you saw.
What the answers can tell you early
- No first deliverable, no thirty-day expectation, and no documentation usually means the role was created in a hurry. Expect to define the job yourself, and get your version agreed in writing.
- If several people separately mention the same difficult person or the same broken system, treat it as fact rather than gossip, and plan around it.
- A manager who cannot name who signs things off outside the team is a sign your work will stall at approvals. Find those names another way.
- Vagueness on hours and urgency in the same conversation tends to mean the boundary is set by whoever asks last. Watch the timestamps for a week before you settle into a pattern.
- If nobody can say how you will be assessed before the review, write your own summary of what you did after thirty days and send it to your manager. It is much easier than reconstructing it later.