Questions to Ask First Day of Work
Questions for the first day of a new salaried or office job, sorted by who can actually answer them: your manager, the colleague sitting nearest you, and whoever handles accounts and access. Written for the day itself rather than the first quarter.
The questions
Open any question for the note
What would you like me to have done by the end of this week?
Why ask it
Most managers have not thought past getting you a laptop, so asking forces a first week into existence. It also gives you something small and finishable, which matters more than a plan for the first quarter that nobody will remember.
What is already on my calendar this week, and which of those do you actually want me in?
Why ask it
New starters get added to recurring meetings by default, and a full first week of calls is the most common reason people learn nothing in it. Getting explicit permission to skip two of them frees the time you need to read.
What accounts and access am I still missing, and who requests them?
Why ask it
Access requests often sit in a queue for days, so raising the gaps on day one rather than day four saves a wasted week. Ask for the name of the person or the ticket queue rather than a general assurance that it is being handled.
Where do I find the documents people talk about as though I have already read them?
Why ask it
Every team has three or four canonical documents, a strategy deck, a roadmap, a runbook, and knowing their names is what stops you sounding lost in week two. Ask for links rather than descriptions.
What is the first thing you would like me to read?
Why ask it
Managers usually have a specific answer, and their choice tells you what they think the job is. If the answer is a general onboarding portal, ask which two documents in it matter.
Who do I go to when you are not available?
Why ask it
This gets you a named second point of contact before the first time you need one. It also quietly reveals the informal structure of the team, which rarely matches the org chart.
Who should I book half an hour with this week, and what should I ask them?
Why ask it
Introductions that come with a suggested topic go far better than a diary invitation for a coffee with no agenda. Ask your manager to name three people, then send the invitations the same day while being new is still a reason.
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.
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.
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.
How do you like to hear from me, and what would you rather I just handled?
Why ask it
The second half is where the real information is. Managers differ enormously in how much they want to see before it goes out, and getting that wrong in either direction is the most common early friction.
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 meetings should I sit in on and just listen to for a while?
Why ask it
Some rooms are for learning the context and some expect contribution, and misjudging which is which is memorable for the wrong reasons. A colleague can usually tell you in one sentence.
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 hours do people actually keep, and what is expected in the evenings?
Why ask it
Written policy and real practice diverge, and the gap is best learned from a peer rather than a manager. Ask what happens if a message arrives at nine in the evening, because the answer to that is the culture.
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.
What do new people here tend to get wrong in the first month?
Why ask it
Ask a peer rather than your manager. The answers are usually specific and unwritten, such as which senior person needs to be told about things in advance, and they are hard to find any other way.
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 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.
Six months from now, what would make you glad you hired me?
Why ask it
A good closing question because it asks for the outcome rather than the task list, and managers often answer with something that was never in the job description. Write the answer down and reread it before your first review.
How to actually use a first day
Practical guidance for the conversation itself
Ask the right person
Your manager
Priorities, the first week, one to one cadence, what the previous person left behind, internal context, and how they want to be kept informed. You will have less of their attention than you expect on day one, so lead with the week's priorities and book the recurring meeting before you leave the room.
The colleague sitting nearest you
Channels, unwritten rules, which meetings to stay quiet in, where people eat, what new starters get wrong. Peers are more candid than managers about all of it, and asking them costs you nothing socially because helping the new person is a welcome break.
Whoever runs accounts and equipment
Access, hardware, the ticket process, and how long things normally take. Get the name of the queue and the reference number for anything outstanding. This is also the person to ask where the printer, badge reader and building access rules sit.
Human resources or the people team
Payroll dates, benefit enrollment windows with real deadlines, probation length, and expense process. Enrollment deadlines are the only genuinely time-critical admin on a first day, so check whether any of them fall inside your first month.
Pacing the day
- 1Keep one running note in a single place, with names and roles at the top. You will meet more people than you can hold, and asking someone's name twice is fine while asking their job twice is worse.
- 2Ask three or four questions of any one person, then stop. Spreading questions across five people gets you better answers and five relationships.
- 3Write down anything you are told about process, then check it against the documentation later. Verbal instructions on day one are often one person's version.
- 4Leave the day with two things booked: your recurring one to one, and at least one introduction meeting for later in the week.
- 5Do not try to add value on day one. Read, ask, and note the things you would change without saying them yet.
If your first day is remote
- Ask for a named person you can message with small questions. Without one, remote starters go quiet for a week because nothing is worth a scheduled call.
- Ask what the team's convention is for cameras, status and response times. Getting this wrong is invisible in an office and conspicuous online.
- Ask for read access to the last few months of the main project channel and any recorded meetings. Scrolling back is the remote equivalent of overhearing the room.
- Book shorter introductions, twenty minutes rather than an hour, and more of them. Remote first weeks fail through isolation rather than workload.
- Confirm how hardware, expenses and any home office allowance are handled, including who to contact when something does not arrive.
Save these for week two
- Anything about promotion, pay review or job title. Asking on day one reads badly and the answer will not have changed by week three.
- Anything that sounds like a proposed change. Note it, wait until you understand why the current version exists, then raise it.
- Requests for training budget or conference approval. Ask once you can say what it is for.
- Detailed questions about a specific project. They land much better once you have read the documents you were pointed at on day one.
- Comparisons with how your previous employer did things. Useful eventually, corrosive early.