A new job dumps orientation links, tool logins, and acronyms on you at once. You do not need another long essay. You need a runway: what to do this week, what to learn in the first three months, and when to branch into your function.
This page is the Starting a New Job stage hub. Use it as a path, not a reading list. Pick one lane, finish its checklist, then follow the single “read next” link. When you can explain your team’s work in plain language and ship small outcomes without guessing, graduate to the Individual Contributor hub.
Who this stage is for (and who should skip ahead)
Stay here if you are in your first role out of college or a bootcamp, changing careers into a first professional job, or anywhere in your first 0-6 months at a company and still figuring out how work actually moves.
Skip ahead if you already know the tools, the stakeholders, and what you own. Go to the Individual Contributor hub. If you already manage people, use the New Manager hub instead.
Managers: share this hub as a shared map, not a dump of twenty tabs. Point a new hire to Lane 1 for week one, then Lane 2 after they have access and a first manager 1:1.
The insight: three lanes, one “read next”
Treat this hub as a stage runway with three lanes:
- Survive week 1: access, orientation, first questions, first relationships.
- Orient months 1-3: how work moves, early mistakes to avoid, a simple plan you can show.
- Choose your function track: HR, accounting, recruiting, and role literacy once the basics stick.
Every module and outbound link below sits in one lane. Do not jump lanes because a title looks interesting. Finish the lane you are in, then take its single read-next recommendation.
Lane 1: Survive week 1
Goal: show up prepared, get unblocked, and leave Friday with clearer expectations than you had on Monday.
Module: First-week checklist (print or copy)
Use this as a worksheet. Check items off; leave blanks where your company works differently.
Access and setup
– [ ] Laptop, MFA, VPN, email, chat, and calendar work
– [ ] I know how to file an IT ticket when something breaks
– [ ] I can find the handbook / wiki / shared drive home
People
– [ ] Manager 1:1 booked (or held) with expectations for the first two weeks
– [ ] Warm intro list: 3-5 peers or partners to meet
– [ ] Buddy or onboarding contact identified (if your company uses one)
Clarity
– [ ] I wrote down what “good” looks like for week 1 and week 2 in my own words
– [ ] I know preferred update style (chat, email, doc, standing meeting)
– [ ] I shipped one tiny proof of reliability (notes, cleanup, triage, summary)
Admin (do not ignore)
– [ ] Timekeeping / badge / parking / remote norms confirmed
– [ ] Benefits enrollment window noted (dates, not details yet)
– [ ] I asked whether there is a formal 30/60/90 check-in or an informal review
Friday recap (fill in)
– Top 3 things I learned: _ / _ / _
– Open questions for my manager: _
– One small ship for next week: __
Lane 1 reads (ordered)
- Questions to ask in your first week: use before and after your manager 1:1.
- Employee onboarding checklist: employee and manager views so you know what “done” looks like.
- Benefits enrollment without panic: only after you know your enrollment window; do not let forms crowd out week-1 relationships.
- How to run a 1:1 meeting: so your first 1:1s have a simple agenda.
Read next (Lane 1 → Lane 2): Mistakes to avoid in your first month.
Lane 2: Orient months 1-3
Goal: stop treating the first quarter as one blur. Learn the system, contribute inside it, then own a defined slice.
Module: Weekly cadence (learn / meet / ship)
Copy this into a note. Fill it every Monday. Review it with your manager every Friday for the first month.
| Block | This week’s plan | Done? |
|---|---|---|
| Learn (2-4 hours) | Docs, shadowing, or jargon I will clarify: __ | [ ] |
| Meet (people time) | Who I will talk to and why: __ | [ ] |
| Ship (visible work) | One small deliverable with a finish line: __ | [ ] |
| Ask | One clarifying question for my manager: __ | [ ] |
Rules of thumb:
– If Learn crowds out Ship for three weeks, ask your manager which learning is still required.
– If Ship crowds out Learn forever, you will miss how decisions actually get made.
– Meet is not “be everywhere.” It is intentional intros tied to your work.
Lane 2 reads (ordered)
- The first 90 days at a new job: observer → contributor → owner phases.
- 30-60-90 day plan template: turn phases into a written plan you can share.
- How to read the room at work: norms, timing, and when to speak up.
- HR for humans: vocabulary for policies, people ops, and when to ask vs. guess.
Read next (Lane 2 → Lane 3): pick one function hub below that matches your role or the partners you touch most.
First job vs. experienced new hire
First job out of college / bootcamp: spend extra Lane 1 time on questions, meeting norms, and how to run a 1:1. Do not skip benefits and handbook basics. Your “ship” items can be tiny as long as they close a loop.
Experienced hire starting somewhere new: compress Lane 1 on tools and admin, but do not skip reading the room. Prior companies trained different habits. Use Lane 2 to map this company’s decision rights before you prescribe fixes.
Neither path needs a universal probation story. Some companies run formal 30/60/90 reviews. Some do not. Ask what yours does and plan to that, not to a blog default.
Lane 3: Choose your function track
Goal: add role literacy without abandoning the runway. Function hubs explain how a domain works at work. They are not a replacement for your company’s policies.
| If you… | Start here | Then |
|---|---|---|
| Need people-process literacy | HR hub | Benefits, leave, and when to talk to HR vs. your manager |
| Touch money, invoices, or budgets | Accounting hub | How companies make and spend money (from the IC hub path later) |
| Are near hiring loops | Recruiting hub | How reqs and interviews usually work |
| Want cross-functional context | Stay on Lane 2 reads, then IC hub literacy articles | Sales and finance literacy once you own outcomes |
Read next (Lane 3 exit): when you can state what you own this quarter in one sentence, move to the Individual Contributor hub and complete its scope worksheet first.
Module: Stage glossary
| Term | Plain meaning |
|---|---|
| Onboarding | The setup, training, and early support that help you do the job. Length and formality vary by company. |
| Ramp | The period while you are still building speed and context. Not a fixed number of days everywhere. |
| Probation / intro period | A company-specific trial window if it exists. Ask HR or your manager what yours means. Do not assume a universal length. |
| 1:1 | A recurring meeting with your manager (or a report) for priorities, feedback, and blockers. |
| Skip-level | A meeting with your manager’s manager. Useful for context; not a place to surprise your boss mid-crisis. |
| Benefits enrollment | Choosing health, retirement, and related plans in a defined window. Deadlines matter more than perfect first-pass choices. |
Common early mistakes this path helps you avoid
- Treating every article as equally urgent (lanes fix that).
- Waiting weeks to escalate broken access.
- Optimizing for looking busy instead of closing one small loop.
- Skipping benefits dates because “I’ll do it later.”
- Jumping into function deep-dives before you know how your team ships work.
When you are done with this hub
You are ready for the IC stage when:
– Week-1 access and orientation are mostly behind you
– You can explain what the team delivers and how work enters and finishes
– You have a written near-term plan (even a light 30-60-90)
– Your weekly cadence includes Learn, Meet, and Ship without panic
Then go to the Individual Contributor hub. If you were hired as a people manager, use New Manager after Lane 1 basics.
CTA: next stage and function pages
Next stage: How to succeed as an individual contributor
Function hubs: HR · Accounting · Recruiting
Managers sharing this tip: send Lane 1 only in week one. Add Lane 2 after the first Friday recap. One lane at a time beats a bookmark dump.