Questions to Ask Your Manager on the First Day
Questions for your first conversations with a new manager, covering what to do this week, how you will be judged, who to meet, and where the line sits between deciding and checking.
The questions
Open any question for the note
What would you like me to focus on this first week?
Why ask it
Day one answers are usually logistical: accounts, reading, introductions. If your manager has nothing at all, expect to structure the week yourself.
Is there a task or project you'd like me to pick up first?
Why ask it
A concrete first assignment beats a week of reading. Managers who can name one have thought about your ramp; those who say settle in often have not.
What are your priorities for me over the first thirty, sixty and ninety days?
Why ask it
The gaps in the answer are informative. A detailed first month and a blank third usually means the role is still being defined around you.
What does good work look like in this job, and how will you know?
Why ask it
Push until you hear something observable. Being a team player is not a measure; the weekly report going out without anyone chasing it is.
How do you prefer to communicate, and how often should we talk?
Why ask it
Settles whether you message during the day or save things for a booked slot. Mismatched assumptions here cause most early friction with a new boss.
How do you like to hear about progress, and in what format?
Why ask it
Some managers want a written Friday summary, others want it out loud in a stand-up. Guessing wrong makes a diligent new hire look quiet.
What tools and access will I need, and who arranges them?
Why ask it
Access requests can take weeks in a large organization. Starting them on day one prevents a second idle week.
Who should I meet in the next couple of weeks, and why each of them?
Why ask it
Ask for the reason alongside the name. It maps who actually holds the work, which rarely matches the org chart.
What is the team working on right now, and where do I fit?
Why ask it
Tells you whether the role exists to absorb known work or is expected to invent its own.
What's the hardest problem the team is dealing with at the moment?
Why ask it
Honest answers point at where the job really is. If you hear nothing but good news on day one, ask again in a month.
When should I decide something myself, and when should I check with you?
Why ask it
Getting this line wrong in either direction is what makes early weeks uncomfortable. Ask for one example of each.
If two deadlines collide, how do you want me to choose?
Why ask it
Reveals whether priorities are genuinely ranked. A manager who says both matter now will say it again in week six.
What's the best way to ask questions while I'm getting up to speed?
Why ask it
Some managers prefer a batched list once a day, others want to be interrupted in the moment. Knowing saves you from feeling like a nuisance.
How do decisions usually get made here?
Why ask it
Answers surface the informal route: the meeting where things are really agreed, or the one person who has to be convinced first.
What should I know about how the team works together that isn't written down?
Why ask it
Norms about hours, reply times, cameras and which channel is for what are invisible until you break one.
How does what this team does connect to what the company is measured on?
Why ask it
If your manager cannot draw the line, expect priorities to move around more than you would like.
What tends to trip up people who are new here?
Why ask it
Easier to answer than a question about mistakes, and the answers name a specific system, process or approval step.
What's expected around hours, responsiveness and time off?
Why ask it
Better asked on day one than assumed. Listen for the gap between the written policy and what your manager describes.
What would you like me to be able to do in six months that I can't yet?
Why ask it
Turns development from a vague promise into something specific enough to plan around, and shows whether they have a path in mind for you.
Is there anything else I should know that I haven't thought to ask?
Why ask it
A good closing question on a first day, because your manager can see the gaps in your picture better than you can.
Using your first day well
Practical guidance for the conversation itself
Pacing the questions
Don't ask all twenty on day one
A first day is mostly paperwork, tours and introductions. Pick four or five, and save the rest for your first proper one-to-one later in the week.
Write the answers down
You will be told dozens of names and systems before lunch and remember almost none of them. Notes also give you something to check against in a month.
Ask for examples, not principles
Hearing that the team is collaborative tells you nothing. Hearing that you should talk to Priya before touching the deployment pipeline is usable.
What to listen for
- Whether the goals for your role already exist in writing, or are being invented as you ask about them.
- Whether your manager describes the team's problems, or only its plans.
- Whether the stated process for decisions matches the examples they give.
- Which names come up repeatedly without appearing on the org chart.
- Whether anyone can tell you why the role is open.
Common mistakes
Nodding through an explanation you didn't follow
Pretending to understand a system on day one costs far more in week three, when everyone assumes it was covered.
Treating the day as an interview you're still in
Rapid-fire questions read as anxiety. Leave silence, and let your manager talk past their first answer.
Skipping the small talk
Useful context arrives sideways: who is leaving, what failed last quarter, which project is unpopular. None of it comes in response to a direct question.