Surviving Week One Without Pretending You Already Know
Five things to do, three things to avoid, one question to ask. Day-by-day for the first 5 working days at any new job.
Week one of a new job is a strange test where the prompt is hidden and the proctors are watching. Most advice tells you to "be curious" and "take initiative," which is true and useless. Here is the day-by-day version.
Day 1: Get logged in. That is the day.
If your laptop is set up, your SSO works, and you can find your team's Slack by lunch, you are doing better than half of new hires. Spend the rest of the day in introductions and let yourself be tired. Mental fatigue from learning 30 names and 12 acronyms is real and it is not a sign of weakness.
One thing that pays off: at the end of day 1, write down 5 questions you do not want to ask twice. Save them for week 2 once you have done a little reading. The act of writing them down already cuts your "wait what do I do?" anxiety in half.
Day 2-3: Read what nobody told you to read
Your manager gave you a list of docs. Read them. Then read the docs they did not give you: last quarter's all-hands deck, the team's most recent retrospective, the README of the repo you will eventually own.
The signal you are looking for is not "what does this team do?" It is "what does this team complain about?" The repeated complaints are where the work lives.
Day 4: First 1:1 with a peer, not your manager
Your manager 1:1 is scheduled for week 2. That is correct. The week-1 conversation that pays off is with a peer who has been on the team 6-18 months. They remember being new. They will tell you the unspoken rules. Buy them coffee.
Two questions: "what is something you wish someone had told you in your first month?" and "who do I need to be friends with that is not obvious?" That second question is gold. Every team has 2-3 invisible glue people whose blessing matters. Your peer will name them.
Day 5: Ship something, even tiny
The smallest thing. A typo fix. A README update. Pinning a dependency. The point is not the artifact, it is the practice round of the team's review process. You learn how the team gives feedback by giving them something to feed back on.
End of week 1: you have your laptop set up, you have read the docs, you have had one peer 1:1, you have shipped something tiny. That is the bar. Anything more is bonus. Anything less is fine if it is honest about what got in the way.
What to avoid in week 1
Big opinions. The codebase is not bad, you just do not understand it yet. Strong recommendations on tooling. They picked the tools for reasons that will become clear in month 2. Skipping introductions because you are introverted. The half-hour you spent on a Zoom you did not enjoy is one of the highest-ROI activities of the entire quarter.
The one question to keep asking
"What is something you would do differently if you were starting in this role today?"
It is open-ended, it implies you respect their experience, and the answers are usually surprisingly honest. Ask it of every senior person you 1:1 with for the first 30 days. The patterns in the answers are your unwritten onboarding plan.