I'm a first-time VP of Engineering. What does the first 90 days actually look like?

The hardest part of your first 90 days isn't learning the tech stack or the org chart — it's resisting the urge to prove you belong by shipping something visible before you understand what actually matters. Every new VP of Engineering who's been a strong IC or EM feels that pull. The ones who flame out at the VP level usually did exactly that: optimized for early visible wins before understanding the political terrain, the real bottlenecks, and what their boss actually needs from them.

Here's how I'd structure it:

Days 1–30: Listen, Map, and Decode What Your Boss Actually Wants

Your only job is to become the person who understands the system better than anyone assumes a new hire can. That means:

Decode your manager's operating system. Don't wait for your boss to spell out expectations — study how they communicate, what they escalate, what they ignore, and what makes their boss happy [4]. Your CTO or CEO hired you to solve a problem they may not have articulated cleanly. Your first 1:1s should be spent extracting that implicit mandate. Ask: "What does good look like in six months? What would make you regret this hire?"

Run a listening tour, but make it structured. Meet every engineering manager, every product counterpart, and at least a sample of ICs. You're not just "getting to know people" — you're building a map of where the real pain is. The best startup operators are described as "heat-seeking missiles for pain" — people who keep their antenna up for what's broken and ask enough questions to distinguish real dysfunction from normal friction [8]. That's your posture for 30 days.

Set only short-term goals. Resist the 12-month roadmap. Focus on SMART goals scoped to weeks: learn the deployment pipeline, understand the top three reliability risks, map the team's actual decision-making process versus the org chart [1]. These small, concrete targets build your confidence and credibility without overcommitting.

Build relationships before you need them. Every connection you make now — with product, design, finance, the skeptical staff engineer — is an investment that compounds later [1]. Be warm, be curious, be professional. Don't politic. Just be someone people want to talk to again.

Days 30–60: Align on What Needs to Change (and What Doesn't)

Now you have data. The move here is synthesis and alignment, not execution.

Reflect back what you heard. One of the highest-leverage things a new leader can do is hold up a mirror to the organization: "Here's what I heard from all of you. Here's what I think the real problems are. Here's what I want to do about it" [7]. This does two things — it proves you listened, and it forces the org to either confirm or correct your diagnosis before you act on it.

Align with your boss on priorities. Bring your synthesis to your manager and negotiate: "Given what I've found, here are the two or three problems I think matter most. Do we agree?" This is where you earn trust — not by having the answers, but by having the right questions and the judgment to prioritize [7].

Identify one small, visible contribution. Not a reorg. Not a new process. Something modest that signals you're already adding value — fixing a broken on-call rotation, unblocking a stuck cross-team dependency, shipping a quality-of-life improvement the team has been asking for. Beverly Jones makes this point well: no one else is going to make you successful — you have to create your own momentum, starting with realistic objectives [4].

Days 60–90: Start Executing With Permission

You've listened, you've aligned, now you move — but with organizational buy-in, not heroics.

Execute on the agreed priorities. You should be making real decisions now: staffing changes, process changes, roadmap adjustments. The key is that these feel like the natural consequence of the alignment work you did in month two, not surprises [7].

Establish your operating cadence. By day 90 your team should know how you run staff meetings, how you make decisions, how you communicate up and down, and what you care about. This is your leadership brand forming in real time.

Watch for the trap of premature impact. The pressure to "have impact" early is real but misleading. Having a plan protects you from rushing into decisions you're not ready for [7]. The best 90-day outcome isn't a shipped feature — it's an organization that trusts your judgment because you earned it methodically.

What I'd Stress-Test

This framework assumes you have a reasonably functional org and a boss who gives you space to learn. If you've been hired into a firefight — the last VP left suddenly, there's a production crisis, morale is cratering — compress the listening phase to two weeks and move to triage. The structure still holds, but the tempo changes dramatically.

Also: if your boss is the founder and this is their first time managing a VP, expect the implicit mandate to be fuzzier than usual. You'll need to do more work defining your own role boundaries.

What's the situation you're walking into — existing team with an open VP seat, or something messier? I can sharpen this significantly with that context.