To prepare for a first 90 days interview, build a short, flexible plan around three things: what you would learn, who you would listen to, and what early progress you could reasonably show. If you are wondering how to prepare for a first 90 days in a new job interview, the short version is that interviewers asking "What would your first 90 days look like?" are rarely after a polished script. They want to see how you think when you don't yet have the full picture. This guide gives you a simple structure, example phrasing and a checklist so your answer sounds practical, not rehearsed or overconfident.
The question shows up across digital marketing, product, data, technology and AI roles, and it tends to appear late in an interview, when the panel is picturing you in the seat. That makes it a good moment to be specific, calm and honest about what you would need to find out first.
What Is an Interviewer Really Asking When They Raise Your First 90 Days?
On the surface, the question is about your plan. Underneath, the interviewer is usually testing a few things at once: whether you can prioritise, whether you listen before acting, and whether you understand that every team has context you can't see from the outside.
The strongest answers aren't the most ambitious ones. They separate what you know from what you'd need to confirm, and they link early actions to the evidence in your own work history. That is what makes a plan believable. A candidate who promises to "overhaul the funnel in month one" without having seen the data sounds risky. A candidate who describes how they would audit, ask questions and then propose a focused first project sounds like someone a team could actually work with.
Interviewers may also be checking for fit with how the team works. Some want someone who will move quickly on a small win. Others want someone who will absorb a complicated system before touching it. You usually can't tell which from the job ad alone, which is one reason your answer should leave room for adjustment.
Here is what a hiring panel is often listening for:
- Prioritisation: do you pick a few things rather than listing everything?
- Humility with confidence: do you acknowledge unknowns without sounding unsure of your skills?
- Evidence: can you point to a time you did something similar?
- Collaboration: do you plan to work with people, not around them?
How to Build a Simple Learn, Listen, Contribute Structure
A good first 90 days interview answer is a framework for learning and contributing, not a promise of results. The simplest framework to remember under pressure has three parts: learn, listen, contribute. You can map them loosely onto a 30-60-90 day plan if the interviewer uses that language, but you don't need to be rigid about the dates.
Learn (roughly the first month)
Describe what you would want to understand: the product or service, the customers, the tools and data, the goals the team is already working towards, and how success is currently measured. Keep it concrete. "I'd want to understand how leads move from first touch to a sales conversation, and where the current reporting gets stuck" is far better than "I'd get up to speed."
Then attach a real example. For instance: "In my last role I spent my first few weeks mapping our campaign reporting before changing anything, which stopped me duplicating work the team had already tested."
Listen (roughly the second month)
Name the people you would talk to and why. That might be your manager, adjacent teams such as sales, engineering or customer support, and a few customers or end users if access allows. Say what you would ask them. Good listening questions are about friction: what slows people down, what has been tried before, and what they wish was different.
An example line: "I'd book short conversations with the people who rely on this work, ask what's working and what isn't, and use that to sense-check my early assumptions."
Contribute (roughly the third month)
This is where many candidates overreach. Rather than naming a big outcome, describe the type of early progress you could reasonably show: a small project delivered, a process improved, a clearer set of priorities agreed with your manager, or a proposal for the next quarter backed by what you've learned.
For example: "By the end of the first 90 days, I'd aim to have delivered one contained improvement and agreed a plan for the next quarter with you, based on what I've found."
Use this as a quick template to draft your own answer:
- State your overall approach in one sentence.
- Give two or three specifics for learn, listen and contribute.
- Tie one real past example to each part.
- Name what you'd need to confirm.
- Invite the interviewer to adjust the plan.
Can You Give a Plan Without Knowing the Business Yet?
Yes, and you should say so. Interviewers know you are working from a job description, a website and a couple of conversations. Pretending otherwise is the fastest way to sound overconfident. A better approach is to name your assumptions out loud and treat them as things to test.
You might say: "Based on what I've seen so far, I'm assuming the priority is improving retention rather than acquisition. I'd want to confirm that with you, because it changes where I'd spend the first month." This shows you've done your research, you have a view, and you are willing to be corrected. All three are useful signals.
Context can also help. News about the sector, a funding round, a regulatory change or a restructure can shape what a team needs from a new hire. If something genuinely relevant is in the public eye, such as recent coverage of how an Australian AI business has fared, you can acknowledge it lightly and ask how it affects the team's priorities. Only do this if it connects to the role. Dropping headlines into your answer for the sake of it can read as padding.
Avoid these common mistakes:
- Promising numbers. Saying you would lift a metric by a set amount before you've seen the baseline is hard to defend.
- Criticising the current setup. You haven't seen the constraints the team works under.
- Staying vague. "Build relationships and learn the business" is true of every role and tells the panel nothing.
- Reciting a template. A generic 30-60-90 day plan copied from the internet usually sounds like one.
If you are asked to present a written plan, keep it to a single page. Use the same three headings, list a few activities under each, and add a short "assumptions to confirm" section. That last section is often what makes the plan feel honest and grown up.
Your own history is the best raw material. Look back at a time you joined a new team or took on an unfamiliar project. What did you do in the first few weeks? Who helped you? What did you deliver, and what did you get wrong? Real examples, including small stumbles you learnt from, are more convincing than polished claims. A line often attributed to Mark Twain says the secret of getting ahead is getting started, and for this answer that means starting from what you have actually done.
Which Questions Should You Ask About the First 90 Days?
After you give your answer, turn it into a conversation. Asking good questions about onboarding and early expectations shows you are thinking about how to succeed in the role, not just how to get the offer. It also helps you decide whether the job is right for you.
Questions worth considering:
- What would you hope to see from the person in this role by the end of their first three months?
- What does onboarding usually involve, and who would I work with most closely?
- Are there any projects already in motion that I'd be expected to pick up?
- How does the team measure success for this role, and how often is progress reviewed?
- What has helped previous new starters settle in well, and what has made it harder?
- Which part of my plan would you change, based on what you know about the team?
That last one is particularly useful. It invites the interviewer to adjust your plan, and how they respond tells you a lot about how they give feedback and how open the team is to new ideas.
Listen carefully to the answers. If the expectations are vague, or the interviewer describes goals that seem unrealistic for a new starter, that is useful information. You are also interviewing the employer, and clear answers about onboarding are usually a good sign. Socrates is often credited with the idea that the unexamined life is not worth living, and a version of that applies to job offers: it is worth examining what you are stepping into.
Before Your Next Interview, Practise the Answer Out Loud
Reading a plan in your head is different from saying it to another person. Practise your first 90 days interview answer aloud, ideally with a friend or by recording yourself, and aim for roughly two minutes. If you go much longer, trim it back to the points that matter most for that specific role.
Use this checklist before you walk in:
- Reread the job ad and highlight the two or three outcomes the role seems to care about.
- Write a three-part answer: learn, listen, contribute.
- Attach one real example from your past work to each part.
- List the assumptions you would need to confirm.
- Prepare two questions about onboarding and early expectations.
- Practise a shorter one-minute version in case the conversation is moving quickly.
If you are applying for several roles, adjust the plan for each. A product role, a data role and a marketing role will emphasise different stakeholders and different early wins, even if the structure stays the same.
The takeaway is simple: a believable plan is one that shows how you would learn, who you would listen to and what you could reasonably contribute, grounded in things you have already done. If it helps, seav.ai's resume improvement and career coaching tools can help you pull those examples out of your experience and practise saying them clearly, so you walk into the room with a plan you can explain and adapt.
seav.ai
Practical career tools for Australian candidates — resumes, job matching, and clearer next steps.
Ready to optimise your resume?
Join the Seav.ai private beta and get your AI-powered resume review free.
Get Early Access — Free