Questions to Ask During Orientation for a Job
Questions for your first days in a new job, covering the admin with deadlines attached, who to go to for what, how your team really communicates, and what your manager expects by the end of the first month.
The questions
Open any question for the note
Who do I go to for what: my manager, HR, IT, facilities, payroll?
Why ask it
New starters lose days sending questions to the wrong place. Getting one name per category on day one saves you from the common pattern of waiting a week for an answer that was never coming.
What has to be set up or signed by the end of this week?
Why ask it
Orientation mixes urgent paperwork with information you can absorb later, and it rarely separates the two. Ask for the list with deadlines so tax forms and system access do not sit behind a welcome slide deck.
When does benefits enrolment close, and what happens if I miss the window?
Why ask it
Enrolment windows are usually short and often cannot be reopened until the next year or a qualifying life event. This is the one piece of orientation admin with a real cost attached to forgetting it.
How does pay work here: pay dates, first payment, timesheets, expenses?
Why ask it
First payments are frequently partial or delayed by a cycle, and knowing that in advance lets you plan rather than chase. Ask who approves expenses too, because that is where reimbursements stall.
What training or compliance modules do I have to complete, and by when?
Why ask it
These come with real deadlines and are usually the first thing anyone notices you have not done. Ask whether any of it must be finished before you get access to particular systems.
Who will I be working with most closely, and could I get introductions this week?
Why ask it
Asking for the introductions, not just the names, is what makes this useful. Ten-minute conversations in week one are easy to get and become much harder to arrange once you look settled.
How does my manager prefer to be contacted, and how often will we meet one to one?
Why ask it
Managers vary from open-door to strictly scheduled, and guessing wrong reads as either needy or disengaged. A standing one to one in the calendar from week one is the single most useful thing to secure.
Which meetings am I expected at, and which are optional?
Why ask it
Calendars fill quickly with invitations that nobody expects you to accept. Getting this straight early prevents both the overloaded first month and the accidental absence from something that mattered.
Where does the team keep its documents, and what are the first three things I should read?
Why ask it
Every team has a handful of documents that explain how the work actually runs, and they are rarely in the onboarding pack. Naming a number gets you a shortlist instead of a link to a shared drive.
When there are two tools for the same thing, which one does this team actually use?
Why ask it
Most organisations run overlapping systems, and the official answer often differs from where the work happens. Getting this wrong means your updates sit somewhere nobody reads.
What are the norms around response times and messages outside working hours?
Why ask it
Written policy and lived practice frequently diverge here, and the practice is what you will be judged by. Ask what people do about evening messages, not what the handbook says.
How does taking time off work in practice: notice, approval, and how far ahead people book?
Why ask it
The policy tells you the entitlement; colleagues tell you whether taking it is straightforward. Ask when the busy periods are, because that is when requests quietly get refused.
How does remote or flexible working actually operate on this team?
Why ask it
Company-wide policy is often overridden by team habit, and the team habit is what affects you. Ask which days people are usually in and whether anything important depends on being there.
What am I expected to have done or learned by the end of my first month?
Why ask it
This converts a vague settling-in period into something you can be judged on fairly. If your manager has no answer, propose your own list and ask them to correct it.
What is the review cycle, and when will I first be formally assessed?
Why ask it
Probation periods and review dates often sit closer than new starters expect, and the criteria are easier to ask about now than the week before. Find out whether there is a probation sign-off and what it depends on.
Who approves spending, and what is the process for buying something small that I need?
Why ask it
Knowing the threshold below which you can just buy something saves weeks of blocked work. It also tells you how much the organisation trusts people by default.
What are the rules I should be careful about: data handling, confidentiality, what can go outside the company?
Why ask it
Most compliance training covers the general case and skips the specifics of your team's data. Ask for the concrete version: which systems hold sensitive material and what should never be pasted into an external tool.
What do new people here usually get wrong in the first month?
Why ask it
You get a shortlist of local mistakes: booking over a standing meeting, cc-ing the wrong person, missing a Friday deadline. These are the things nobody documents and everybody notices.
What is something about how this place works that is not written down anywhere?
Why ask it
Every organisation has unwritten rules about who to consult before a decision and which forums matter. People enjoy answering this, and the answers save you from your first political misstep.
Is there anyone outside my team I should introduce myself to early on?
Why ask it
The person who unblocks your work is often two teams away, and nobody thinks to mention them during orientation. Asking in week one makes the introduction easy and low-stakes.
Making orientation useful rather than passive
Practical guidance for the conversation itself
During the sessions
Keep two lists, not one
One list for things with deadlines, one for things to understand later. Orientation presents both in the same tone, and only the first kind causes problems if you forget it.
Ask logistics questions in the room, judgement questions in private
Payroll dates, deadlines, and system access belong in the group session. Questions about how decisions really get made, or what your manager expects, get more honest answers one to one.
Write down names with something attached
A name alone is useless by Friday. Note what the person owns and where you met them, and you will be able to email them in week three without embarrassment.
Book your own follow-ups before the week ends
Fifteen minutes with each of the people you will work with, put in the calendar while being new is still an obvious reason to ask. This gets much harder in month two.
The first month
A workable shape for weeks one to four
- 1Week one: finish the paperwork with deadlines, get access to every system you need, and meet your immediate team.
- 2Week two: read the documents that explain how the work runs, and ask your manager to correct your understanding of them.
- 3Week three: take on something small and finish it, so that you have delivered rather than only observed.
- 4Week four: agree with your manager what the next two months should produce, and write it down where you both can see it.
Common mistakes in the first weeks
Saving up questions to avoid looking new
The period where questions cost you nothing is short. Ask the obvious things in the first fortnight rather than guessing for six weeks and getting something wrong in public.
Treating the handbook as the working reality
Written policy is the floor, not the description. On response times, hours, and time off, ask colleagues what actually happens and plan around that.
Proposing changes before you understand the history
Most obviously inefficient processes exist because of something that went wrong once. Ask why it is done this way before suggesting it should not be.
Letting the probation date arrive unexamined
If there is a formal probation period, find out in week one what sign-off depends on. Discovering the criteria a fortnight before the date is too late to act on them.