How to Answer "What Would You Do in Your First 30 Days?"

"What would you do in your first 30 days?" tests whether you can onboard effectively and start contributing quickly without overstepping. It reveals your approach to new environments: are you someone who listens and learns, or someone who charges in with solutions before understanding the context?

The best answer balances humility (you don't yet understand their world) with agency (you have a plan for getting up to speed and adding value quickly).

What Interviewers Are Really Assessing

• Strategic thinking: Do you have a structured approach to getting started?
• Listening orientation: Will you learn before trying to change things?
• Relationship building: Do you prioritize connecting with key stakeholders?
• Bias for action: Can you identify and deliver early wins?
• Self-management: Can you onboard yourself without excessive hand-holding?

How to Structure Your Answer

Use the Listen-Learn-Leverage framework:

Week 1: Listen (30%)

Meet key stakeholders, understand priorities, and absorb the company culture and current challenges.

Weeks 2-3: Learn (40%)

Dive deep into processes, data, and systems. Identify gaps and opportunities. Build relationships across teams.

Week 4: Leverage (30%)

Deliver a quick win, present initial observations to your manager, and outline your priorities for the next 60 days.

Sample Answers by Career Level

Entry-Level Example

Situation: Starting a first professional role. Answer: "In my first week, I'd focus on building relationships. I'd schedule brief introductions with everyone I'd work with directly and ask each person what they wish they'd known when they started. I'd also thoroughly review any onboarding materials, documentation, and recent project work to understand the team's standards and processes. In weeks two and three, I'd shadow team members and start taking on small tasks to build context. I'd ask my manager for a specific project I can own early to start contributing. By week four, I'd aim to have completed that initial project, have a clear understanding of how my role fits into the team's goals, and present my manager with a list of priorities I'd like to focus on going forward."

Mid-Career Example

Situation: Joining as a senior product manager. Answer: "My first 30 days would center on understanding three things: the customer, the team, and the current strategy. In week one, I'd meet with my manager to align on expectations and priorities, then schedule conversations with every cross-functional partner I'd work with, engineering leads, designers, sales, and customer success. In weeks two and three, I'd immerse myself in the product. I'd go through the user experience as a customer, review analytics data, read support tickets, and listen to recent customer calls. I'd also review the product roadmap and understand the rationale behind current priorities. By week four, I'd synthesize what I've learned into a brief document sharing my observations, questions, and proposed focus areas for the next quarter. I'd also aim to identify one process improvement or quick win to deliver, even something small, to build credibility and momentum."

Senior-Level Example

Situation: Starting as VP of Sales. Answer: "In the first 30 days, I'd focus on diagnosing before prescribing. Week one: align with the CEO on expectations, success metrics, and the biggest open questions. Meet every direct report one-on-one and ask them what's working, what's broken, and what they'd change if they were in my seat. Week two: dive into the data. I'd review pipeline metrics, win/loss analysis, rep performance distribution, and compensation structure. I'd also join several customer and prospect calls to hear the sales conversation firsthand. Weeks three and four: synthesize everything into an honest assessment. Where are the biggest revenue levers? What needs immediate attention versus longer-term investment? I'd present this to the CEO and my team with specific 90-day priorities. I'd also aim for at least one visible early win, perhaps closing a stalled deal or fixing an obvious process bottleneck, to build trust with the team."

Common Mistakes to Avoid

• Promising to fix everything immediately: Claiming you'll transform the team in 30 days shows naivete about organizational complexity.
• Being entirely passive: A 30-day plan with no deliverables suggests you won't add value quickly enough for a fast-moving organization.
• Ignoring relationships: Plans that focus only on tasks and metrics without mentioning people and stakeholder management miss a critical success factor.

Tips for Different Industries

Technology: Emphasize understanding the tech stack, codebase, or product architecture early. Technical credibility often determines how quickly you can influence decisions.

Consulting: Focus on client relationship building and understanding current engagement status. Speed to productivity matters enormously in consulting.

Finance: Prioritize understanding the portfolio, risk positions, and team structure. Show that you'd get up to speed on compliance requirements immediately.

Healthcare: Emphasize credentialing, protocol review, and patient safety procedures. Healthcare organizations need confidence that you'll prioritize safety from day one.

Practice This Question

Ready to practice your answer with real-time AI feedback? Try Revarta's interview practice to get personalized coaching on your delivery, structure, and content.