Your First 90 Days: How to Actually Start Strong in a New Job

The first 90 days of a new job are more important than most new hires realise. Your manager forms a durable impression of you in that window. Your peers decide whether you're someone they want to collaborate with. Your patterns — how you ask questions, how you communicate, how quickly you ship — are getting set. Do the first 90 days well and you compound credibility for years. Do them badly and you spend the next year recovering.

Weeks 1–2: Listen More Than You Talk

The single biggest mistake new hires make — especially senior ones — is arriving with strong opinions about what's broken. Even when you're right, nobody wants to hear it in week one. You haven't earned the context yet.

Your job in the first two weeks is to ask, observe, and write things down. Specifically:

• Book 30-minute intro calls with everyone your manager suggests, and a few they don't. Ask each person the same four questions: what are you working on, what's going well, what's frustrating, who else should I talk to?
• Read the docs, PRs, and retros from the last six months. You'll learn more about how the team actually works from one month of pull requests than from any onboarding deck.
• Keep a running notes file of terminology, acronyms, and questions you can't ask yet. Review it weekly.

Have the Expectations Conversation Early

By the end of week two, have an explicit conversation with your manager about what success looks like at 30, 60, and 90 days. Don't wait for them to raise it — most managers won't. Write it down and confirm in writing.

The answer gives you a rubric. You'll use it to decide what to say yes to, what to say no to, and whether you're on track.

Weeks 3–6: Ship Something Small and Real

You need a first win. Not a huge one — a visible, finished piece of work that proves you're a real contributor. The best first projects are:

• Small enough to finish in two to three weeks.
• Useful to someone you're not technically reporting to.
• Legible to people outside your immediate team.

Engineers: a small quality-of-life improvement to a tool the team uses every day. PMs: a cleanly written brief for a well-scoped upcoming initiative. Designers: a small polish pass on a surface the team cares about. Nothing heroic, just finished.

Finishing matters more than choosing. A half-done ambitious project in month one signals poor prioritisation. A completed small one signals reliability.

Figure Out Who the Trusted Voices Are

Every team has a formal hierarchy and an informal one. The informal one is the map of who other people actually check with before making decisions. You can't see it from the org chart.

Watch for the patterns:

• Who gets @-mentioned when something's important?
• Whose opinion does your manager quote in meetings?
• Whose PR or doc reviews carry extra weight?

Those are the people whose trust matters most. Make sure you have at least one short one-on-one with each of them in the first six weeks. Not to ingratiate yourself — to actually learn how they think.

Weeks 7–12: Start Forming Opinions, Carefully

By two months in, you've earned some credibility. You can start to voice perspectives — but the framing still matters.

The second version gets a conversation. The first version gets you ignored. Even when the first is what you actually mean, the second is what you should say. Save the blunter version for after you've earned it.

Common Traps

Doing Your Last Job Here

If you were a senior engineer at your previous company, it's tempting to replicate the practices you ran there. Sometimes it works. Often it doesn't — context matters more than best practices. Ask "how does this team currently handle [X]?" before you propose a change.

Over-Promising to Prove Yourself

New hires tend to accept too much early, because saying no feels like weakness. It isn't. Over-committing and under-delivering is far worse than committing to less and exceeding. Protect your scope in the first 90 days.

Avoiding the Awkward Questions

Ask the basics. Where is the deploy runbook? Who owns this repo? Why do we do stand-ups at 9:30 instead of 10? The embarrassment of asking is always smaller than the cost of not knowing.

Ignoring the Peers-to-Peers Graph

Most of your job happens through lateral relationships, not vertical ones. A new hire who's good with their manager but invisible to peers will struggle in year two. Invest in the relationships with the engineers, designers, and PMs next to you — even the ones outside your immediate team.

The 30-60-90 Check-In

At each milestone, have an explicit conversation with your manager. Five minutes is enough. Three questions:

1. "What am I doing well?"
2. "What would you like me to do more or less of?"
3. "Is there anything I should know that nobody's told me yet?"

That third question is the one most new hires don't ask and most managers will actually answer. You'll learn something useful roughly half the time.

The First Real Mistake

You will, eventually, break something or make a bad call. When it happens, own it fast and cleanly. "I shipped X, it caused Y, here's what I did to fix it, here's what I'll do differently." New hires who handle their first mistake well are remembered for the handling, not the mistake. New hires who deflect or minimise are remembered for the opposite.

The Bottom Line

The first 90 days aren't about proving you're smart — the hiring process already decided that. They're about building trust. Listen more than you talk early. Ship one small visible win. Map the informal hierarchy. Earn the right to have opinions before you voice them. Handle your first mistake with grace. Do those, and by day 91 you're a known quantity — which is when the real work starts.