Questions to Ask on First Day of Work
What kinds of question to ask on your first day in a new job, and who to put them to: practical ones for whoever handles accounts and access, ones about priorities for your manager, and ones about how the place actually runs for your new teammates, plus what the answers tend to tell you.
Want questions from the whole vault instead? Try the random question generator.
The questions
Each question, and why to ask it
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 out-of-date half is the one worth asking. 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.
Who handles payroll, benefits, and my paperwork, and what deadlines am I already on?
Why ask it
Benefits enrollment windows and tax forms often close within a few weeks of a start date, and nobody chases you. Ask on day one, when it is expected, rather than discovering the deadline afterward.
Of the things in my job description, which is most urgent right now?
Why ask it
The gap between the advert and the actual need is often large, particularly if the role went unfilled for a while. Asking on day one avoids spending a month preparing for the version of the job that was written six months ago.
Who was doing this work before me, and are they still here?
Why ask it
If the role is new, expect ambiguity and say so early. If someone left, whether they are reachable and why they went both matter, and the way the question is answered tells you as much as the answer.
What did the person before me leave half-finished?
Why ask it
Half-finished work is where you will spend your first month, and nobody volunteers it because it is slightly awkward. If the seat is new rather than vacated, ask who has been covering the work instead and start there.
Is there anything my role is expected to fix?
Why ask it
Colleagues often know exactly why a position was opened, and it may not match what you were told in interviews. If two people give you the same answer, treat it as the real brief.
Is there anything currently on fire, and am I expected to touch it?
Why ask it
New hires are sometimes hired specifically because of a problem nobody has named yet. Clarifying whether the fire is yours prevents both accidental ownership and accidental neglect.
How often do we meet one to one, and can we put them in the calendar now?
Why ask it
Recurring time with your manager is much easier to establish on day one than to request in month two. Booking it in the room rather than agreeing to do it later is the whole point of asking.
What can I decide on my own, and what should come to you first?
Why ask it
Ask this before you need it. The answer maps the boundary you will otherwise learn by crossing it, and a manager who cannot answer is telling you something about how much rework to expect.
Who signs off on what around here?
Why ask it
Approval routes are almost never documented and they are the thing that most slows a new starter down. Ask for the two or three decisions you are likely to need and who has to say yes to each.
What does good look like in this role at thirty, sixty, and ninety days?
Why ask it
The three-part framing makes vagueness obvious. If all three answers sound the same, there is no plan, and you should write one and get it agreed rather than wait for one to arrive.
Who outside this team will judge my work?
Why ask it
This surfaces the stakeholder nobody warned you about: a finance lead, a regional manager, a long-tenured engineer whose approval is informal but decisive. Their name almost never appears in an org chart.
Which channels and threads actually matter, and which can I mute?
Why ask it
By the end of a first week most people are in thirty channels and reading none of them properly. Asking someone experienced to name the four that matter is the cheapest possible advice.
Which of these tools do people really use, and which are just installed?
Why ask it
Most companies have three chat tools, two wikis, and one place where decisions genuinely get recorded. Asking a peer, not a manager, is the only way to find out which is which.
How long have you been here, and what were you doing before this?
Why ask it
The safest opener because everyone can answer it, and the length of tenure tells you how to weight everything else they say. Someone three months in remembers what confused them; someone nine years in knows why things are the way they are.
Who will I work with a lot who isn't on this team?
Why ask it
Cross-team dependencies are invisible on day one and are where most of the delays live. Getting the names now means you can introduce yourself before you need something from them.
Who's the person everyone quietly relies on?
Why ask it
Rarely the most senior person, and rarely on an org chart. It might be an office manager, a long-serving analyst, or a support engineer. Knowing the name early prevents you from underestimating them.
What's the busiest stretch of the week or the month?
Why ask it
Every team has a rhythm: a Monday planning crush, a month-end close, a Thursday release. Knowing it stops you from booking a long introductory chat with someone on the worst possible afternoon.
Where do people eat, and is there a normal time?
Why ask it
A small question with a large payoff on a first day: lunch is where you meet people who are not on your introductions list. Anyone who says they usually eat at their desk has just told you something about the team as well.
Is there anything going on internally that I should know before I start meeting people?
Why ask it
A reorganization, a departure, a project that just got cancelled or a tense relationship between two teams all shape how your first conversations land. Most managers will tell you if asked directly on day one and will not think to volunteer it.
What happens here when something goes wrong?
Why ask it
Listen for whether the answer describes a process or a person's mood. "We do a write-up and fix it" and "we all keep our heads down" describe two entirely different places to work.
What does the team put up with that nobody has got round to fixing?
Why ask it
This is a better version of asking about challenges, because it invites an honest complaint rather than a strategic summary. It also gives you a candidate for a first useful contribution, though it is worth waiting a few weeks before offering one.
What's the unwritten rule here that people only learn by breaking it?
Why ask it
Every workplace has one, whether it is not messaging a certain director directly or never scheduling anything on Friday afternoon. The person who tells you this is worth staying close to.
If you were me, what would you spend the first month learning?
Why ask it
A good closer because it asks for a recommendation rather than an opinion, and it flatters without flattery. Collect the answers from several colleagues and start with whatever more than one person named.
Asking these on day one without looking lost
Practical guidance for the conversation itself
Which kind of question goes to whom
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 of these 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.