Your First 90 Days — And How to Talk About Them in the Interview

When the hiring manager asks 'what would your first 90 days look like?', they're not testing your knowledge of their codebase. They're testing whether you've thought about the role like an operator. The answer should sound like an internal memo, not a wishlist.

Three phases, with intent

1. Days 1–30: listen and map. Meet every direct collaborator, understand the on-call rotation, read the last six months of incidents and design docs.
2. Days 31–60: ship something small but visible. A bug fix that helps the team trust you, a doc that clarifies something everyone agreed was confusing.
3. Days 61–90: take ownership of one piece of the roadmap and propose how you'd evolve it.

What signals seniority

Junior candidates rush to ship. Senior candidates lead with listening, name the people they'd meet, and explicitly defer big decisions until they've earned context. The willingness to do nothing visible for the first month is often what separates a senior plan from a mid-level one.

Don't promise what you can't know yet

Avoid promising specific deliverables in the first 30 days. You don't have the context yet, and the manager knows it. The strongest 90-day plans are deliberately humble in the early phase and increasingly concrete in the later phase, mirroring the actual shape of an effective onboarding.