How to Answer "What Would You Do in Your First 30, 60 and 90 Days?"
How to answer the 30-60-90 day plan question in a software engineering or engineering manager interview, with a framework, sample answers for individual contributors and managers, and mistakes to avoid.
LiveHint.ai team · · 4 min read
"What would you focus on in your first 90 days?" usually comes up in a hiring-manager round. Sometimes it's phrased as "What does success look like for you after three months?" or, for senior and management roles, you may be asked to bring a written 30-60-90 day plan.
The interviewer isn't expecting you to know their codebase or their team's problems. They're checking whether you know how to ramp up in a sensible order: learn before changing, deliver something early, then take on more.
What a strong answer shows
- You learn before you act. You won't arrive and rewrite everything in week two.
- You deliver early. You plan to ship something small and real in the first month.
- You build relationships. You know your success depends on people outside your team.
- You're specific to this role. Your plan uses what you've learned about the team and the job description.
- You can measure progress. Each phase has a visible outcome.
The framework
| Phase | Theme | What it looks like for an engineer |
|---|---|---|
| Days 1–30 | Learn | Set up the environment, ship a small change, read design docs, meet the team and close partners, understand on-call |
| Days 31–60 | Contribute | Own a meaningful feature or project, join on-call, start reviewing others' code, pick one thing to improve |
| Days 61–90 | Lead | Drive a project from design to launch, propose an improvement based on what you've learned, mentor or unblock others |
The shape is the same for every level. What changes is the size of the work at each step.
Sample answer: mid-level or senior engineer
First 30 days: I'd focus on learning how the system works and how the team works. I'd aim to ship a small change in my first week or two, because it's the fastest way to learn the build, review and deploy process. I'd read the design docs for the services I'll own, sit in on an on-call shift, and have one-on-ones with the engineers I'll work with most and with our product manager.
Days 31 to 60: I'd want to own a real piece of work from the roadmap. From what you said earlier, the payments retry project sounds like a good fit given my background. I'd also join the on-call rotation and start doing code reviews regularly.
Days 61 to 90: By then I'd hope to have shipped that project and to be the person others go to for that part of the system. I'd also have a list of things I noticed while ramping up, like gaps in the docs or flaky tests, and I'd pick one to fix or propose a plan for.
The specific project in the middle ("the payments retry project") is what makes it convincing. Listen for one during the interview and use it.
Sample answer: engineering manager
First 30 days: Listen. One-on-ones with everyone on the team, with my manager, and with the product and design partners. I'd ask each person what's working, what's frustrating and what they'd change. I'd also look at how the team plans, what's on the roadmap and how incidents are handled. I wouldn't change processes in this period unless something is clearly broken.
Days 31 to 60: Share what I've heard and agree on two or three priorities with the team and my manager. Typically one delivery goal, one team-health goal and one process fix. I'd also set up a regular rhythm: one-on-ones, planning and a retro if there isn't one.
Days 61 to 90: Deliver on those priorities and start working on longer-term goals: hiring plans, career growth conversations, and the roadmap for the next two quarters.
Sample answer: new graduate
Keep it simpler and focused on learning and delivery:
In the first month I'd focus on getting productive: setting up my environment, shipping my first few small changes, and learning the team's conventions through code review. In the second month I'd take on a larger task with less guidance and start contributing to reviews. By the end of three months, I'd like to own a small feature end to end, and to have a clear picture of where I can grow, with feedback from my manager.
If they ask for a written plan
For senior, staff or management roles you may be asked to bring a one-page plan. Keep it short:
- One page. Three columns or three sections, with three to five bullets each.
- Goals and measures for each phase. "Ship first production change" is measurable; "learn the codebase" isn't.
- Assumptions stated plainly. "Based on our conversation, I've assumed the top priority is reliability. I'd confirm this in week one."
- A list of questions you'd want answered in the first month.
Mistakes to avoid
- Promising big changes immediately. "I'd migrate everything to Kubernetes" in month one is a warning sign.
- Being too generic. If your answer would fit any company, it isn't using what you learned.
- Leaving out people. Relationships with product, design and other teams matter as much as code.
- No early delivery. A plan that's all learning for 60 days sounds slow.
- Over-committing. Be ambitious but realistic. You'll be held to it.
Prepare with the real job description
The best 30-60-90 day answers draw on the job description and on details you pick up in earlier rounds. Write down the two or three problems the team mentioned, then build your answer around them. Rehearse it in an AI mock interview set to a hiring-manager round, using the actual posting. For the rest of a hiring-manager conversation, see questions to ask the interviewer and tell me about yourself.
Keep reading
13 min read
STAR Method Examples: 12 Interview Answers That Work
Twelve full STAR method examples for software engineers, from conflict and failure to tight deadlines and production incidents, plus a checklist to adapt them.
- behavioral interview
- STAR method
- interview tips
- software engineering
4 min read
How to Handle a Difficult Interviewer (Silent, Rude or Distracted)
What to do when an interviewer is silent, cold, interrupting, distracted or openly skeptical: why it happens, how to stay composed, and exact phrases that keep the interview on track.
- interview tips
- interview anxiety
- communication
- software engineering