Your First 90 Days at a Startup: The Only Thing That Actually Matters

Every startup onboarding deck talks about culture, stack, goals, OKRs, vibes. None of them tell you the real truth — in your first 90 days, you are being quietly categorised by everyone around you, and most of the categorisation happens in week two.

This is not unfair. It is just how small teams work. Everybody has a thousand things to do. Nobody has time to re-evaluate you every month. The impression you leave in the first two weeks is the impression you fight against or lean into for the next year.

What founders are actually watching

• Do you ship something small in the first week, or do you still have "setup questions" on day 12
• Do you ask clarifying questions in public, or do you stare silently at a task for three days
• Do you notice the broken thing on the side and fix it, or do you treat everything outside your ticket as "not my job"
• Do you write clearly — in Slack, in PR descriptions, in standups — or do we have to extract information from you
• Do you bring energy into the room, or do you absorb it
• Do you seem like you would still be at the company in two years, or does this feel temporary to you

None of these are on your job description. All of them are being scored.

The one habit that separates the top 10%

Ship small things quickly. Ship them messy. Ship them before anyone expected them. Fix them the next day when feedback arrives. The people who get promoted in year one are almost always the people who produced visible output in month one — not the smartest, not the most credentialed, just the ones with working PRs by Friday.

You will feel like the code is not good enough, the design is not polished enough, the writeup is not thorough enough. Ship anyway. Feedback on something is infinitely more valuable than thought on nothing.

How to be useful before you feel ready

• Pick the smallest real problem in the first week and solve it
• Write a weekly "here is what I shipped, here is what I am blocked on, here is what I want feedback on" update — unprompted
• Fix one piece of pain you personally hit in onboarding. Document it for the next person
• Ask for a 1:1 with someone on a different team in your first two weeks
• Learn exactly one piece of production context that is not on your ticket (the money flow, the customer pipeline, the deploy pipeline — pick one)

What to avoid in the first 90 days

• Large, ambitious first projects. They ship slowly and give no signal
• Complaining about the stack, the process, or the codebase. You lose permission to criticise you have not earned yet
• Saying "this is how we did it at my old company" more than twice
• Being the person with the loudest opinion in meetings before you have shipped anything
• Disappearing for a week to "go deep." The team reads it as checking out

The long-tail benefit

If you get the first 90 days right, the next two years are easy mode. People give you the interesting projects because you shipped the boring ones. Raises come easier because someone is already quietly lobbying for you. You are invited into rooms you have not earned yet because you feel like the kind of person who should be there.

If you get the first 90 days wrong, you spend 18 months climbing out of a hole that was entirely preventable. Spend the effort early. It is the highest-leverage window in your whole tenure.

Your first 90 days decide the next two years. Spend them shipping.