What to Ask in Your First Week (by Role)
You start Monday with a laptop that almost works, a chat channel full of nicknames, and a calendar that looks like someone else built it. By Thursday you’ve asked “how do I…?” six times and still don’t know what “good” means in this job. That gap isn’t a personality flaw. It’s missing questions, asked of the right people, early enough to steer week two.
This is a practical bank of questions to ask in the first week of a new job: who to talk to, what to ask once, how to capture answers, and what can wait. Managers can hand the same bank to new hires so onboarding isn’t improvisation. Cultures and industries differ, so treat this as a starting set, not a script.
The three calibration questions (ask everyone)
Here’s the move that beats any mega-list: ask every key person the same three questions, then compare answers.
- What does great look like for someone in my seat at 90 days?
- What would make you worried about me in the first month?
- Where do people in this role (or team) get stuck here?
Ask your manager, one strong peer, your buddy if you have one, and one cross-functional partner. Write each answer with the person’s name. The gaps are the gold. If your manager says “ship the Q4 deck” and a peer says “don’t touch it until you know customer objections,” you found the real onboarding problem. One answer is opinion. The spread is the system.
How many questions per meeting
Five to seven strong questions beat twenty polite ones. In a 20 to 30 minute chat, plan on three must-asks plus two backups. If someone is mid-fire-drill, reschedule.
Frame it simply: “I’ve got a short list of orientation questions. Got 15 to 20 minutes this week?”
Capture answers so you don’t ask twice
Use one living note. For each item, record:
| Field | What to write |
|---|---|
| Question | Exact wording you asked |
| Who | Name + role |
| Answer | Short paraphrase in their words |
| Conflict | Where this clashes with someone else |
| Follow-up | What you’ll verify or ask next |
Sample (fictional names): “Great at 90 days = own Friday status without me rewriting it – Maya (manager). Peer Jordan: know which metrics Sales trusts. Conflict: format vs. metric credibility. Follow-up: ask Ops for source-of-truth dashboard.”
Review every Friday. Carry conflicts into your next 1:1 instead of re-asking the same person.
Questions to ask your manager first week
These questions to ask manager first week clarify success, priorities, and how you’ll work together.
- What are the top one to three outcomes you want from me in the next two weeks?
- What does “on track” look like at 30 and 90 days for this role?
- What should I protect even when other requests pile up?
- Who should I meet this week, and will you make warm intros?
- How do you like updates (chat, email, doc, live)? How often?
- What’s already in motion that I should not disrupt?
- When should I escalate vs. keep working the problem?
Tie these to the three calibration questions. You’re building a shared picture of success, not collecting trivia.
Questions for teammates first week
Peers know how work actually moves. Ask questions for teammates first week that your manager may not phrase the same way.
- How does work typically enter this team and get finished?
- Which tools or docs are “real,” and which are outdated?
- What’s the unwritten rule that surprised you when you started?
- Who do people go to when something is stuck (not the org chart answer)?
- If I want to be helpful this week without creating cleanup work, what should I do?
Stay curious, not critical. Map the machine; don’t grade it.
Questions to ask HR first week
Save policy and benefits for HR or People Ops. Good questions to ask HR first week:
- What’s due in my first week (paperwork, training, compliance)?
- Is there a formal 30/60/90 or check-in cadence?
- Who is my onboarding buddy or go-to for logistics?
- Where do I find the handbook or intranet home for time off, holidays, and expenses?
- What’s the process if IT access is still blocked after day two?
Skip peer time for policy basics. Read the docs first; use HR for gaps and deadlines.
What to ask on day one at work
Day one is setup and signal-reading. Keep what to ask on day one at work short:
- Is my access complete (laptop, MFA, VPN, chat, email, core systems)?
- Who is my first-week point person if something breaks?
- What’s the team’s preferred channel for quick questions?
- Is there anything I should read before tomorrow’s meetings?
Ship one tiny proof of reliability by Friday (cleaned notes, fixed doc link, triage summary). Questions open doors; small delivery builds trust.
Culture questions without the negativity
You can learn norms without sounding like you’re hunting for drama.
Try: “What behaviors get respected here over time?” “How do people disagree productively on this team?” “What does ‘urgent’ usually mean in practice?” “When is async preferred vs. a meeting?” “What should I never surprise my manager with?”
Avoid: “Who’s toxic?” “What’s wrong with this place?” “Who should I watch out for?” Those put people in a bad spot and often get you gossip instead of guidance.
Tools, process, and how work gets done
New hire questions for onboarding should cover the team’s operating system:
- What’s the source of truth for priorities (board, roadmap, OKRs, spreadsheet)?
- How do we hand work across teams, and where do decisions get recorded?
- What’s the expectation for chat and email response?
- Which meetings are optional for me in week one?
If answers conflict, ask your manager which system wins when “the process” and “how we actually do it” disagree.
How success is really measured
Ask directly, then verify with examples.
- Which metrics or outcomes will we look at in my first review conversation?
- What does a strong week look like vs. a busy week that didn’t move anything?
- Who else weighs in on whether I’m doing well (skip-level, partners, customers)?
If your manager talks about “ownership” and peers talk about “speed,” write both down. Week one is for noticing the gap, not fixing the whole company.
Customers and stakeholders
Ask about customers and partners early:
- Who are the primary customers or partners for this role, and what do they complain about most?
- Who can say yes or no to work that hits my plate?
- Which stakeholder should I meet before I form strong opinions?
- What’s safe to try in week one vs. what needs air cover?
Build a short outreach list and pair it with your question log.
People manager vs. individual contributor
If you’re an IC: prioritize manager clarity, peer workflow, tools, and one small delivery. Skip redesign talk.
If you’re a people manager: add listening-tour questions in 1:1s with reports:
- What’s working that we should protect?
- What’s draining the team that I shouldn’t “fix” blindly in week one?
- How do decisions get made today, and where do people feel stuck?
- What do you need from me in the next two weeks?
Managers: week one is still observer mode. Share a short listening summary with your boss on Friday. Hold big reorg ideas until you understand what the team is optimizing for.
Role add-ons: onboarding questions by role
Add a few role-flavored questions on top of the core bank.
Sales: What’s the pipeline quality story (not just the number)? Which deals are sacred this quarter? How do we hand off won deals? What discount or exception needs approval, and from whom?
Finance: What’s the close calendar, and where do new people slow it down? Which reports are leadership-facing vs. drafts? What’s the escalation path when numbers don’t reconcile? Who owns forecast vs. actuals with Sales or Ops?
HR / People: What’s live in the next 30 days (hiring, reviews, training, compliance)? Where is employee data the source of truth? What should managers never invent on their own? How does this team partner with legal, finance, and leaders?
Operations / product ops: Where do tickets get stuck most often? What’s the definition of done for our main workflow? Which metrics are leading vs. lagging vanity? Who can change a process, and who only suggests?
Engineering-adjacent ICs (support, solutions, QA, technical PM): What’s the incident or escalation path? Which tools can I touch in week one? How do we document decisions after a partner call? What’s the bar for “good enough” before release or handoff?
Sample first-week question schedule
| Day | Who | Focus |
|---|---|---|
| Mon | Manager + HR/IT | Access, two-week priorities, paperwork; ask calibration questions of manager |
| Tue | Buddy or peer | Tools that are real, unwritten norms, one small helpful task |
| Wed | 1-2 teammates | How work enters and finishes; where people get stuck |
| Thu | Cross-functional partner | Customer/stakeholder view; same three calibration questions |
| Fri | Manager | Recap answer conflicts, open access issues, week-two plan |
If you manage people, swap one peer slot for two short report 1:1s. Keep them listening-heavy.
What can wait until week two or three
Park these so week one stays high-leverage: deep strategy debates you can’t yet evidence; compensation and promotion mechanics beyond the first check-in timing; redesigning meetings or someone’s pet process; broad networking outside your critical path; perfect documentation of every acronym.
Week two and three are for testing what you heard: sit in the workflow, update notes when reality disagrees, and tighten “great at 90 days” with your manager.
First-week checklist (quick)
- [ ] Access and HR deadlines cleared or escalated
- [ ] Manager: priorities, update style, people list, calibration answers
- [ ] Peer/buddy: real tools, unwritten rules, stuck points
- [ ] One partner: customer/stakeholder view + same three calibration questions
- [ ] Living note with conflicts flagged
- [ ] One small delivery by Friday
- [ ] Friday recap: what I learned, what’s still fuzzy, next week asks
Done looks like this
By Friday you should know what you’re protecting for the next two weeks, how your manager defines “on track,” where peer answers diverge from that, and what you’re not touching yet. That’s enough to start your first 90 days with direction instead of noise.
FAQ
How many people should I talk to in the first week?
Aim for your manager, one peer or buddy, and one cross-functional partner at minimum. Add report 1:1s if you manage people. Quality beats a parade of intros you can’t remember.
What if my company doesn’t assign an onboarding buddy?
Ask your manager for one peer who’s strong at “how we work.” If that isn’t available, treat a helpful teammate as your unofficial guide and keep questions short and scheduled.
Should I ask the three calibration questions in the same meeting?
Yes when you can. Asking them as a set makes comparison easier. If time is tight, ask “great at 90 days” and “where people get stuck,” then catch “what would worry you” in the next 1:1.
Is it OK to write notes during these chats?
Yes. Say you’re capturing onboarding notes so you don’t ask twice. Offer to share a short recap if that fits the culture.
Suggested internal links
- The First 90 Days at Work
- New Hire hub
- 30-60-90 Plan
- Stakeholder map play (when published)
- First 1:1 with a new report (manager play, when published)
- How to read the room at work (when published)