Questions to Ask on the First Day of Work
A first day is mostly paperwork, introductions, and being shown where things live. These twenty questions are the ones to put to your new manager while you still have their attention and before the calendar fills up.
The questions
Open any question for the note
What would a good first week look like from where you're sitting?
Why ask it
Managers rarely say this out loud unless asked, and their answer is often much smaller than you expect: read these docs, meet these four people, do not break anything. That is permission to stop trying to impress.
Which systems and accounts do I need, and who actually sets them up?
Why ask it
Access is the single most common thing that stalls a first week. Getting the name of the person who provisions it, rather than the name of the ticket queue, can save you three days of waiting politely.
Who should I meet this week, and in what order?
Why ask it
Asking for an order forces a ranking, which tells you who your manager considers important. A list of twelve names with no sequence usually means they have not thought about your onboarding yet, which is useful to know on day one.
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.
What's the first thing you'd like me to take off your plate?
Why ask it
Turns a vague job description into one concrete task. It also shows what your manager is personally drowning in, which is where you will build the most credit in the first month.
Which recurring meetings am I in, and which ones can I skip?
Why ask it
New hires get added to everything by default and then spend a year in meetings nobody expected them to attend. Asking on day one gives your manager an easy moment to prune the list.
How do you like to be updated, and how often?
Why ask it
The mismatch here is a common early friction: you send a weekly summary, they wanted a quick message when something changes. Ask for the format and the frequency, not just the preference.
When something is genuinely urgent, how do I reach you?
Why ask it
Every manager has a real channel and a nominal one. Knowing whether urgent means a phone call, a direct message, or tagging a group chat prevents a bad first incident.
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.
Where's the documentation, and how much of it is out of date?
Why ask it
The second half is the honest part. A candid "the wiki is two years stale, ask Priya instead" is worth more than a link, and it identifies where the knowledge actually lives.
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's the team dealing with right now that I should know about?
Why ask it
Open enough that a manager can mention a reorganization, a difficult client, or a deadline that has already slipped. Better than asking about challenges in the abstract, which invites a rehearsed answer.
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.
What should I resist changing for the first few months, even if it looks wrong?
Why ask it
The best answers come with history: something was tried, or a specific person cares deeply about it. It also signals that you plan to look before rearranging, which buys goodwill with the people already there.
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.
How is my work reviewed, and on what cycle?
Why ask it
Probation dates usually arrive well before the first formal review, and the two are often run by different people. Ask what you are expected to produce for it, a self-assessment, agreed goals, a written summary, so you are not reconstructing six months from memory in the final week.
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.
What's tripped up people who joined this team before?
Why ask it
Asking about other people rather than about yourself gets a straighter answer. What comes back is usually specific and repeatable: moved too fast, went around someone, wrote to the wrong channel.
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.
What do you wish someone had told you when you started here?
Why ask it
A good closing question because it moves your manager from onboarding mode to remembering their own first weeks, and the answer tends to be the most candid thing you hear all day.
How to use these on day one
Practical guidance for the conversation itself
Sequencing the day
- 1Handle access and paperwork first. Laptop, accounts, badge, payroll forms, benefits deadlines. These are the only things that get worse if you delay them.
- 2In your first conversation with your manager, ask three questions and no more: what a good first week looks like, who to meet, and what to take off their plate.
- 3Spend the middle of the day listening. Sit in whatever meeting you are invited to and write down names, acronyms, and system names you do not recognize.
- 4Save the questions about assessment, unwritten rules, and what tripped up previous hires for the end of the first week, once you have context to make sense of the answers.
Who to ask what
Your manager
Priorities, decision boundaries, how they want to be updated, how your work is assessed, and who outside the team has a say. These are the questions only they can answer, and their availability drops sharply after week one.
The person who has been here longest
Unwritten rules, which documentation to trust, why a process is the way it is, and who really approves things. Buy them a coffee in the first fortnight rather than the first afternoon.
Whoever is assigned as your buddy or onboarding partner
The small mechanical things you will otherwise burn a week on: how expenses work, which channel is for what, where the shared drive is, how to book a room, what the acronyms mean.
Human resources or the people team
Enrollment deadlines, probation terms, time-off accrual, and any policy you were told about verbally during hiring. Get the version in writing while asking is still routine.
Keeping what you hear
- Start one running document on day one. Names with roles, acronyms, systems, open questions. Nobody remembers thirty names from a single morning of introductions.
- Write down every question you cannot answer yourself and batch them. One message with six questions is easier to answer than six messages.
- Note the answers about priorities in your manager's words, not yours. In six weeks you will want the exact phrasing when priorities have quietly moved.
- Keep a list of things that look wrong to you but that you have agreed not to change yet. Revisit it at ninety days, when you have enough standing to raise the ones that still look wrong.
What goes wrong
Trying to add value before you understand anything
Proposing changes in week one reads as arrogance even when the observation is correct, and it is often not correct because you cannot yet see why something exists. Ask what you should not change instead.
Waiting to be onboarded
Many onboarding plans do not exist. If nothing arrives in the first few days, write your own version of a thirty day plan, send it to your manager, and ask whether it looks about right.
Asking nothing so as not to look lost
The window where questions are free closes in a few weeks. Whatever you avoid asking now, you will ask later at a higher cost, or worse, guess.
A remote start with no scheduled contact
Starting remotely without meetings in the calendar means whole days of silence. Ask on day one for a short daily check-in for the first week and a list of people to introduce yourself to in writing.