Questions to Ask at a New Job
Questions for your first weeks in a new job, to ask your manager, your teammates and the person who held the role before you. They cover what you are actually being judged on, how decisions really get made, who to know, and what nobody thinks to tell a new hire.
The questions
Open any question for the note
What would you like me to have accomplished by the end of my first month?
Why ask it
Ask this in week one and again in week four, because the answer usually changes once your manager sees you work. A manager who cannot name anything specific is telling you to pick something and tell them.
If I get one thing right this quarter, what should it be?
Why ask it
Forcing a single answer cuts through the list of priorities you were handed at onboarding. If your manager names something absent from that list, believe the answer to this question.
How will you know I am doing well before my first formal review?
Why ask it
Most reviews are shaped long before they are written, by impressions formed in the first two months. Asking for the informal signals now tells you what is actually being watched.
How do you prefer to be updated, and how often?
Why ask it
Some managers want a Friday note, some want to hear only about problems, and almost none will volunteer which. Getting this wrong is the most common early friction and the easiest to avoid.
What is the fastest way to reach you when something is urgent?
Why ask it
Channels carry different expectations, and a message in the wrong place can sit for a day. Ask what counts as urgent to them, since that definition is rarely the same as yours.
Who are the five people I should meet in my first two weeks, and why each one?
Why ask it
Asking for reasons alongside names turns a list into a map of where influence actually sits. It also gives you a legitimate opening line when you email each person.
Whose approval do things actually need around here?
Why ask it
The formal approver and the person whose objection stops work are often different people. Learning that distinction early prevents the first project that quietly dies without explanation.
How does work get prioritized when two people want the same thing from me?
Why ask it
New hires attract requests from every direction and rarely know whose to decline. Ask your manager for the rule now, so you can point at it rather than improvise a refusal.
What am I inheriting that is half finished or has been deferred?
Why ask it
Roles frequently come with an unloved project or a stalled decision nobody mentioned in the interview. Asking directly means you find it in week two rather than in month four.
What did the person before me do well, and what did they struggle with?
Why ask it
Whether the role was vacated by promotion or by exhaustion tells you something the job description will not. The struggles named are usually structural and therefore about to be yours.
What is the meeting I should not miss, and which ones could I skip?
Why ask it
Calendars fill fast for new people and much of it is inherited from your predecessor. Managers are generally happy to prune, but only if asked in specific terms.
What do people here complain about that never gets fixed?
Why ask it
Best asked of a teammate over coffee rather than of your manager. The honest answer marks the boundary between what a new person can change and what will only exhaust them.
What is the thing everyone here knows that nobody wrote down?
Why ask it
Every workplace runs partly on undocumented convention: which system is trusted, whose numbers are correct, which policy is ignored. Asking a peer plainly usually produces two or three of these at once.
What do people get wrong in their first few months?
Why ask it
Colleagues answer this readily because it costs them nothing and they have watched it happen. The pattern named is usually the difference between fitting in and being remembered badly.
Where does this team's work go, and who depends on it?
Why ask it
Understanding who is downstream of you tells you whose complaints matter and what quality actually means. It is also the fastest route to seeing your job from outside your team.
Which of my early ideas should wait, and why?
Why ask it
New hires see obvious problems that have long histories, and proposing fixes too early spends credibility. Asking your manager to filter is safer than learning by making the suggestion.
What access, tools or training am I still missing?
Why ask it
Permissions and licenses are often incomplete for weeks and nobody notices until you are blocked. A checklist in week one, chased once, saves a great deal of waiting later.
What are the working hours in practice, and when do people expect a reply?
Why ask it
Stated policy and observed behavior diverge here more than anywhere else. Ask what happens to messages sent in the evening, since the answer sets a norm you will be held to.
How do you like to give feedback, and can I ask for it early?
Why ask it
Inviting correction in your first weeks makes later feedback less loaded and gets small habits fixed while they are still small. Managers who dislike confrontation often only speak when invited.
Is there anything about how I have started that you would change?
Why ask it
Ask at the end of week two, then again at week six, and keep quiet long enough for a real answer. This is the question that catches a wrong impression while it is still easy to correct.
Your First Weeks in a New Role
Practical guidance for the conversation itself
How to Ask Without Looking Lost
Use the new-person license while it lasts
For roughly a month you can ask anything without it counting against you, and after that the same question looks like inattention. Front-load the basic questions deliberately rather than saving them.
Ask the same question of three people
How priorities get set, or who decides, will get three different answers, and the spread is the information. Where the answers agree, that is the culture; where they conflict, that is the politics.
Keep a running list of what you did not understand
Acronyms, systems, names and unexplained decisions accumulate fast. Batching them into a weekly ten-minute question is easier on your manager than interrupting six times a day.
Write down what you are told and repeat it back
Summarizing your understanding of a priority in one sentence gives your manager an easy chance to correct it. It also gives you a record when the priority changes and nobody remembers the earlier version.
Who to Ask What
- Your manager: expectations, priorities, decision rights, what to leave alone for now.
- Your teammates: how work actually happens, what is broken, who to avoid annoying.
- The person you replaced, if reachable: what surprised them and what they would do differently.
- Someone downstream of your team: what your output looks like from the outside.
- Another recent hire: what onboarding failed to explain, while it is still fresh for them.
- An administrator or coordinator: how expenses, systems and approvals really work.
Common Pitfalls
Waiting to be told
Onboarding covers systems and policies, not expectations, and many managers assume silence means things are fine. If nobody has told you what success looks like by week two, that is a question, not a signal.
Proposing improvements before you understand the history
The obvious fix has usually been tried, and saying so early costs credibility that is hard to rebuild. Ask what has been attempted before you suggest anything.
Only talking to your own team
The people who explain the organization best are usually one step away from your work. A dozen short conversations outside the team in the first month pays off for years.
Saving all questions for the formal check-in
By the thirty-day review, impressions are already set and small misunderstandings have compounded. Short, frequent questions are less costly than one long conversation.
Not asking for feedback until it is offered
Many managers avoid volunteering criticism to someone new, so the first you hear of a problem is at a review. Asking explicitly, twice in the first two months, is what surfaces it while it is still small.