Onboarding Questions to Ask
Questions for your first weeks in a new job, sorted by who can actually answer them: your manager, the person assigned to help you settle in, and the peers who know how things really work. They cover what success looks like at thirty days, where your remit ends, which decisions are yours, access and tooling, the history behind the work you inherited, and the unwritten rules nobody documents.
The questions
Open any question for the note
What should I have done by the end of my first month for you to feel good about this hire?
Why ask it
Managers rarely volunteer this and almost always have an answer. It also exposes a mismatch early: if their thirty-day expectation involves shipping something and yours involved reading documentation, better to find out in week one.
What was the last person in this role good at, and what got left undone?
Why ask it
The leftovers are your real inbox. You also learn which parts of the job were shaped around one person's strengths, which is why the written description often bears little resemblance to the work.
Which three people should I meet in the first two weeks, and what should I ask them?
Why ask it
Asking for names plus questions gets you a warm introduction rather than a list. Note anyone your manager hesitates over, since that hesitation usually marks a relationship you will need to handle carefully.
Who owns the work next to mine, and where does the boundary get blurry?
Why ask it
Almost all early friction happens at these seams. A manager who cannot describe the boundary is telling you it is contested, which means you should get any overlap confirmed in writing with the other team.
What can I decide on my own, and what do you want to see before I act?
Why ask it
Ask for examples at three sizes: a small spend, a change to something customer-facing, a commitment on a deadline. Vague answers about using your judgment tend to be followed by a correction after the first decision.
How do you prefer to hear from me?
Why ask it
Preferences vary far more than people admit: a written Friday summary, a standing one-to-one, or nothing until something is wrong. Getting this right early buys you more latitude than any early result does.
What's on fire right now that I could take off your hands this week?
Why ask it
Offering in week one is unusual and remembered. It also gets you inside a real problem faster than any onboarding plan, and small unloved tasks are how you learn where the systems and the people actually are.
Which meetings do I genuinely need to be in, and which can I drop after a fortnight?
Why ask it
New starters get added to everything and then stay there for a year. Agreeing an exit date up front makes leaving a meeting an agreed step rather than a slight to whoever runs it.
Where does the team keep its documentation, and how out of date is it?
Why ask it
Ask for the honest answer on staleness, because the confident answer is usually wrong. What you learn is which document is actually maintained and who maintains it, which tells you where institutional knowledge really lives.
Which systems do I need access to, and who approves each one?
Why ask it
Access is the most common cause of a slow first month. Get the list and the approver names on day one, request everything at once, and expect at least one thing to require a second request a fortnight later.
Which tools do people say they use and actually don't?
Why ask it
Every organization has an official system that everyone bypasses with a spreadsheet or a chat thread. Learning which is which stops you putting important work somewhere nobody looks.
What does a good week look like for this team, in numbers?
Why ask it
This converts culture talk into something measurable: tickets closed, calls made, releases shipped, cases reviewed. If nobody can name a number, the team is judged on impressions, which is worth knowing before your first review.
How is my performance reviewed, when, and by whom?
Why ask it
Find out the cycle dates, whether peer input counts, and whether your probation has a formal end point. New starters frequently discover an assessment window has passed while they were still learning names.
What do new people here consistently get wrong in their first month?
Why ask it
Everyone who has watched a few new starters has a list: emailing a director directly, missing a Thursday deadline nobody mentions, deploying on a Friday. This is the cheapest way to avoid the mistake everyone remembers.
Whose opinion of my work matters outside this team?
Why ask it
Reputations are often set by a finance partner, a support lead or a client contact rather than by your manager. Ask what those people usually complain about, then make sure they do not have to complain about you.
What are the unwritten rules about hours, replies and time off?
Why ask it
The written policy and the practice differ everywhere: whether messages at 9pm expect an answer, whether cameras go on, whether anyone actually takes the full holiday allowance. Ask a peer rather than your manager for the accurate version.
What's the history behind the project I'm inheriting?
Why ask it
Every inherited project has a backstory that explains its odd shape: a cancelled acquisition, a departed executive, one customer's demand. Without it you will propose something obvious that was tried and rejected two years ago.
Which past attempts at this failed, and why?
Why ask it
The reasons are usually organizational rather than technical: no budget, a blocking team, a sponsor who left. Learning them protects your first proposal, and asking signals that you are not planning to arrive and start over.
What should I not change in my first ninety days?
Why ask it
This is a considerate way to find the protected areas, whether that is one person's process, a legacy system holding revenue together, or a decision your manager fought for. Ignoring it is the fastest way to lose goodwill you have not yet earned.
How do you want me to tell you if something isn't working?
Why ask it
Agree the channel while nothing is wrong. Some managers want an immediate message, others want it raised in the one-to-one with a suggested fix. Settling this early makes the first hard conversation much easier for both of you.
Working through your first month
Practical guidance for the conversation itself
Ask the right person
Your manager
Expectations at thirty days, decision rights, how they want updates, review timing, and what not to change. These are the questions only they can answer, and they are the ones worth using your first one-to-one on.
Your assigned buddy or a friendly peer
The unwritten rules, which tools people actually use, which meetings are optional, and which documents are current. Peers give the honest version, and asking them costs nothing politically.
The team next door
Where the boundary between your work and theirs sits, what the last person in your role did that annoyed them, and what they need from you. A twenty-minute call here prevents months of friction.
Someone two levels up
Worth one meeting in your first six weeks: ask what would make their year easier and how your team is seen from where they sit. Keep it short and do not use it to complain about anything.
A workable order
Week one
- 1Get the access list and submit every request the same day.
- 2Ask your manager the thirty-day question and write the answer down verbatim.
- 3Meet the three people they name, and ask each what they wish the last person in your role had done differently.
Weeks two and three
- 1Take one small piece of real work end to end, however unglamorous.
- 2Map who owns what next to you, and confirm the blurry parts by message so there is a record.
- 3Start a private document of everything that confused you, with the answer once you find it.
Week four
- 1Check your thirty-day list against what actually happened, and raise any gap yourself.
- 2Ask for early feedback rather than waiting for the review.
- 3Turn your confusion document into onboarding notes for the next person. It is the highest-value thing a new starter can produce.
What new starters get wrong
- Proposing a reorganization of everything in week two, before knowing why the current arrangement exists.
- Comparing everything to your last employer out loud. Do it once and people stop listening.
- Saving up questions to avoid seeming slow. A month of silent confusion costs more than ten questions.
- Only talking to your own team, then discovering in month three that the people who judge your work are elsewhere.
- Accepting every meeting invitation and every side request, then having no time for the work you were hired for.
- Taking the org chart literally. Ask who actually gets things unblocked, because it is often not the person with the title.
If you are joining remotely
Nothing arrives by accident when you are not in a building, so replace overhearing with scheduling. Book fifteen minutes with everyone you will work with in your first fortnight and ask each of them what they are working on and what gets in their way. Ask which channel matters and turn the rest off, since remote onboarding fails through noise as often as through silence. Write your questions down and batch them into one message rather than sending eight, and say plainly when you are stuck, because nobody can see you staring at a screen.