What to actually do in your first three months at your first job — how to onboard well, what managers expect from a new graduate, and how to build a reputation that compounds.
The first ninety days set a tone that's hard to change later — not because you're expected to be productive immediately, but because impressions of how you work form fast and stick. The good news: doing well early is almost entirely within your control and has little to do with technical brilliance.
Nobody expects you to be productive yet — they expect you to learn. The biggest source of new-graduate anxiety is feeling useless early. That feeling is universal and misplaced. Your job in month one is to absorb — the codebase, the systems, the team — not to output.
Learn how things work here before trying to change them. Every team has its own ways, usually for reasons. Coming in and immediately suggesting how everything should be different, before understanding why it's that way, lands badly even when you're right. Understand first, then contribute.
Reliability and communication beat brilliance early. Doing what you said, flagging when blocked, not going silent — entirely within your control, and they matter more in the first ninety days than any display of skill.
Ask questions, take notes, don't ask twice. You'll have endless questions early — ask them, but write down the answers so you're visibly learning rather than re-asking.
Build relationships deliberately. Get to know teammates as people, understand what everyone works on, be pleasant and grateful for help. These relationships become your support network and the people who advocate for you.
Seek feedback early and act on it. Don't wait for a formal review. Ask your manager, within the first month, how you're settling in and what you could do better. Acting on feedback early builds trust fast.
In your first week, set up a personal notes document and record how things work as you learn them. It costs minutes, accelerates onboarding, and by month three you'll be the person who never needs telling twice.
The mindset behind these ninety days is covered in From Student to Employee: What Changes. As you settle in, From Support Work to Systems Thinking is the natural next step.
Part of: Final Year