The 'First 90 Days' Question: How to Answer It

"What would you do in your first 90 days?"

This question shows up in almost every final-round interview for senior roles. And most candidates blow it by either being too vague ("I'd learn the codebase") or too aggressive ("I'd rewrite the backend by week 6").

Here's the framework that lands.

The 30-60-90 Framework

Break your answer into three phases:

Days 1-30: Listen and Learn

"In the first month, my focus would be on understanding — the codebase, the team, the product, and the users. I'd pair with team members, read documentation, set up my local environment, and ship small PRs to build context. I'd also have 1:1s with key stakeholders to understand priorities and pain points."

Why this works: It shows humility. You're not assuming you know everything on day one. Hiring managers are terrified of senior hires who try to change everything before understanding anything.

Days 31-60: Identify and Contribute

"By month two, I'd start contributing more independently — picking up meaningful tickets, identifying patterns in the codebase, and flagging any quick wins or pain points I've noticed. I'd also start forming opinions on technical debt, process improvements, or architectural concerns worth discussing."

Why this works: You're shifting from observer to contributor. You're also showing you can identify problems without waiting to be told.

Days 61-90: Drive and Impact

"By the third month, I'd aim to own a meaningful feature or initiative. Based on what I've learned, I'd propose at least one improvement — whether that's a technical upgrade, a process change, or a new approach to an existing problem. I'd also be starting to mentor if there are junior engineers on the team."

Why this works: You're demonstrating that you don't just fill a seat — you make things better.

Customize It

The framework is generic by design. To make it compelling, research the company and tailor:

• If they recently migrated to a new stack → mention learning that stack deeply in month 1
• If they have scaling challenges → mention contributing to scalability in month 2
• If they're growing the team → mention mentoring and onboarding in month 3

Common Mistakes

Being Too Tactical

Don't list specific tickets or PRs you'd work on. You don't know enough yet, and it sounds naive.

Being Too Strategic

Don't talk about reorgs or process overhauls. You're interviewing for a job, not staging a coup.

Ignoring Relationships

The best 90-day plans prioritize relationships alongside technical contributions. Mention 1:1s, cross-team collaboration, and stakeholder communication.

Forgetting to Ask

End your answer with: "Of course, I'd adjust based on the team's current priorities. What are the biggest challenges you'd want a new hire to focus on?"

This flips the conversation and shows you're collaborative.

---

Acing the interview starts with getting the interview. Make sure your resume is dialed in — JobSlayer AI scores it across every dimension recruiters care about.