How Do I Prepare for an Interview?

Interview preparation is not about memorising answers. It is about being able to prove three things on the day: that you understand what the job actually involves, that you have done the work before, and that you are someone the panel would be comfortable hiring. Everything else, the research, the STAR stories, the questions you bring, exists to make those three things obvious in under an hour.

This guide covers the whole sequence: what interviewers are testing, how to research the organisation, what to wear and when to arrive, how to build answers with STAR, the question types you will face, phone and video formats, panel and second interviews, the questions to ask them, and what to send afterwards.

The short answer. Spend your preparation on six STAR stories that cover achievements, a problem you solved, a conflict, a failure and a time you led something. Then research the organisation until you can talk about one current project, one current pressure, and how the role helps with both. That combination answers most of what gets asked.

Interviews

The interview starts with the resume that got you there.

Every question on the day traces back to a claim on your resume. If the claims are vague, the answers will be too.

Emma Anderson Emma Anderson  |  Rewrite Guarantee  |  Servicing all of Australia

What the interview is actually testing

Put yourself in the interviewer’s position. They are about to put their own reputation behind you, so the interview is really four questions running underneath the conversation.

  • Can you do the job? Evidence of comparable work, at a comparable level of complexity.
  • Will you actually do it here? Motivation, notice period, commute, visa status, and whether you will still be there in a year.
  • How will you behave when it gets hard? Pressure, feedback, conflict, mistakes.
  • Would I want to work with you? How you listen, how much you talk, whether you are honest about what you do not know.

Almost every question maps to one of those four. When an answer feels like it is not landing, check which of the four it was meant to answer and whether it actually did.

Before the interview: research the organisation

Two hours of research will carry you through an hour of questions, and most candidates do almost none. Work through this list in order.

  1. The website, properly. Read the about page, the leadership page and the current products or services. Note the language they use about themselves, because you can reuse it without sounding like you copied it.
  2. Recent news. Search the company name plus the current year. Look for a contract win, an acquisition, a restructure, a new executive, an expansion. One current item you can discuss is worth more than a recital of their mission statement.
  3. The job advertisement again. It tells you what they are worried about. If the ad repeats “stakeholder management” three times, that is the gap they are trying to fill.
  4. The people. Look up your interviewer on LinkedIn. Where did they work before, how long have they been there, what have they built. It gives you something specific to ask about.
  5. Employee reviews, read carefully. Reviews reveal the problems that will shape the job, such as high turnover in the team or unclear management. Do not raise them as accusations in the interview. Use them to decide what you ask.
  6. Financial or public information. For a public company, read the latest annual report summary. For a not for profit or government body, look at the annual report and the current strategy document. Both give you the pressures the hiring manager is under.

By the end you should be able to answer two questions without notes: what does this organisation do and for whom, and what is the biggest thing it is dealing with right now.

What to wear

The rule is one step above what you would wear in the role, not two. A suit for a warehouse role looks like a misunderstanding; chinos and a collared shirt for an office role looks careless.

  • Ask the recruiter or the contact on the advertisement what the dress code is. That is a normal question and nobody holds it against you.
  • If you cannot ask, look at photos of the team on the company’s website or LinkedIn and match them.
  • Neutral colours, clean shoes, minimal accessories. The aim is that nobody remembers what you wore.
  • Video interviews count. Dress from the waist up, and check how the collar and any pattern read on camera, not in the mirror.
  • Test the full outfit the day before. New shoes and an untested iron are the two classic failures.

More detail for remote rounds sits in what to wear to a video interview.

When to arrive, and what to bring

Arrive about ten minutes early, and walk in five. Earlier than fifteen minutes and you become a problem for reception, which sets the wrong tone before the interview starts.

Plan backwards from the arrival time: travel time plus a buffer for a delayed train, a missed exit or a lost car park. If you are very early, find a cafe or sit in the car and review your notes instead of going in.

Bring a printed copy of your resume, the position description if it was sent as a file, and the names of your referees with their contact details. Bring a notepad and a pen. Notes you actually glance at look prepared; notes you shuffle through look unprepared. For timing detail and how to handle a delay, see how early to show up for an interview.

How to answer: the STAR method

Behavioural questions (“tell me about a time when…”) are the backbone of Australian interviews, and in the public sector they are usually tied to selection criteria. The answer format that works is STAR: Situation, Task, Action, Result.

  • Situation. One sentence. Where you were, what the context was, why it mattered.
  • Task. One sentence. What you specifically were responsible for. This is the part most candidates skip, and it is the part that separates you from the team.
  • Action. Three or four sentences. What you actually did, in sequence, including the decision you made and why.
  • Result. One or two sentences, with a number if one exists. Then one line on what you would do differently.

Here is the shape of a complete answer, at about ninety seconds:

Question: Tell me about a time you had to deliver under pressure.

Situation: Our two largest customers both moved their delivery dates forward in the same week, and we had six staff including two on leave.

Task: I was the shift supervisor, so the roster and the customer communication were mine, but I could not change the warehouse budget.

Action: I re-sequenced both jobs by dispatch window instead of order date, moved two people from receiving to picking for four days, and told both customers which orders would slip by one day rather than letting them find out.

Result: Both jobs shipped inside the revised dates, we had no customer escalations, and the re-sequencing became the standard process. What I would change is telling the receiving team earlier, because they absorbed most of the disruption.

Build six of these before any interview and you will cover most of what gets asked: an achievement, a problem you solved, a conflict with a colleague or customer, a failure, a time you led or influenced without authority, and a time you improved a process. Write them out once, then say them out loud until they take ninety seconds rather than three minutes.

For the longer treatment used in government applications, see STAR method for selection criteria.

The question types you will face

Most interviews mix five types, and each needs a different preparation.

  • Behavioural. “Tell me about a time…” Answer with STAR and a real example from the last five years.
  • Technical or role specific. How you would do a task the job involves. Answer concretely, name the tools and the sequence, and admit the parts you would look up.
  • Hypothetical. “What would you do if…” There is no right answer, so structure it: what you would check first, who you would involve, what you would do, how you would know it worked.
  • Motivation and fit. Why this role, why now, why us. Vague enthusiasm is the most common failure here.
  • Self assessment. Strengths, weaknesses, feedback you have received. The weakness answer only works if you name a real one, say what you did about it, and show the change.

See behavioural interview tips for more on the first type, which is the one that decides most Australian interviews.

The questions almost every interview opens with

Tell me about yourself. Ninety seconds, in this order: what you do now, the two things you are best at, one result that proves it, and why this role is the next step. Do not narrate your whole career, and do not start at the year you finished school. Fuller version in tell me about yourself.

Why do you want this role? Name something specific about the organisation, then connect it to something you have done. “I want to grow with a good company” answers nothing. See why are you interested in this position.

Why are you leaving your current job? Forward looking, short, and never a complaint about a manager. Two sentences on what you want that the current role cannot offer. If you were fired, see explaining being fired. If you are job hunting while employed, see why are you leaving your current job.

What are your strengths and weaknesses? Two strengths, each with an example of when it produced a result. One weakness that is real, not a disguised strength, plus the specific thing you changed. “I am a perfectionist” is read as evasive.

What do you know about us? One sentence on what they do, one on a current pressure or project, one on how your experience relates. This is where the research pays off.

What are you passionate about? Answer with something true and work adjacent, not a hobby that has no bearing on the job. See what are you passionate about.

Where do you see yourself in five years? Growth inside the role, not a job above your interviewer. The version that lands is: “better at this than I am now, taking on X, and still here.”

Explaining gaps, layoffs and short stints

Awkward history is only awkward if you treat it that way. The format that works is facts, then pivot, in under thirty seconds.

  • Laid off. “My role was made redundant when the company restructured the national sales team in March. I have spent the time since contracting for two former clients, and I am looking for a permanent role with the same customer base.” No blame, no long explanation.
  • Several short stints. Group them honestly: “I moved three times in four years, each time for a step up in scope: team lead, then national account, then this kind of role.” Show the pattern was deliberate, or show what you learned about the wrong fit.
  • A long gap. Say what you were doing with a neutral fact, then move to what you can do now. Do not apologise for it.
  • Being managed out or fired. One sentence on the reason, one on what changed in how you work, then move forward. Never blame a named manager.

Rehearse these out loud. They are the answers most likely to unravel in the room, because they carry emotion the other answers do not.

Phone interviews

Phone rounds screen for the basics: right to work, salary expectations, notice period, location, and whether you can talk about your experience coherently. Treat it as a real interview.

  • Take it sitting down, somewhere quiet, with your resume and the position description in front of you.
  • Stand if it helps your energy, but do not walk around, because the audio moves.
  • Speak slightly slower than feels natural. There are no visual cues, so pauses read as thought rather than hesitation only if you keep your answers structured.
  • Ask what the next step is and when, before the call ends.

More in phone interview tips.

Video interviews

Video rounds come in three forms: a live call, a one way recorded set of questions, and a platform specific test. Each has its own failure modes, and almost all of them are technical rather than personal.

  • Camera and light. Camera at eye level, light in front of you, never behind. Test the camera and the microphone on the actual device the day before.
  • Framing. Head and shoulders, roughly a third of the frame. Sit far enough back that your hands are visible when you gesture.
  • Background. Plain wall or a tidy room. A door behind you that might open mid answer is a distraction you can remove in advance.
  • Notes. A single page of bullet points taped next to the camera is fine. Reading a script is obvious and it flattens your delivery.
  • Recorded interviews. You usually get one attempt per question with a short preparation window. Practise answering out loud to a camera beforehand, because the format feels different from talking to a person.
  • Backup plan. Have the interview phone number and a mobile hotspot ready. If the connection drops, call immediately rather than waiting.

Platform specifics live in Google Meet and Microsoft Teams tips, and the general rules are covered in video interview tips. If it is a recorded round, start with one way video interview tips and how to prepare for a recorded video interview, and test your setup using how to test your camera.

Panel interviews

Panel interviews are standard in government, education, health and larger corporates. Usually three people: a chair, the hiring manager, and someone from another team or HR.

  • Answer the person who asked, then finish by including the others with your eyes. Do not swivel between panellists mid sentence.
  • Use names once, early, and then sparingly. Overusing names sounds rehearsed.
  • Expect follow up questions from a different panellist than the one who asked. That is testing whether the story holds under pressure, so keep the facts identical.
  • Bring enough copies of your resume for everyone, plus any portfolio or work sample if it was requested.
  • Send one thank you email to the chair, referencing something each panellist said. One email is right; three reads as campaigning.

For people management roles, expect the panel to push on how you handle underperformance, how you set priorities when everything is urgent, and what you inherited from the previous manager.

Panel interview in progress

Second interviews and the 30-60-90 plan

A second interview means you passed the screening. It is usually less about competence and more about risk: whether the team wants to work with you, whether you understand what the job really involves, and whether you will stay.

Expect deeper versions of the same questions, more scenario work, and a meeting with someone you would work alongside. Prepare by revisiting what was discussed in round one and building on it rather than repeating it: “Since we spoke, I read the annual report you mentioned…”

Some employers, especially for manager and above roles, ask what you would do in your first ninety days. A 30-60-90 plan answers that in three blocks:

  • First 30 days: learn. Meet each stakeholder, map the systems and processes, understand how performance is measured, and avoid changing anything yet.
  • Days 31 to 60: fix and build. Pick two or three quick wins you can deliver with the team, and start the relationship building that makes the harder work possible.
  • Days 61 to 90: deliver. Own a result, propose one process change with evidence, and set the measures you will be judged on for the rest of the year.

Keep it to one page and tie each block to something in the position description. Build it from the position description, not from your last job, and be ready to say what you would drop if the first thirty days went badly.

Questions to ask them

You will be offered the chance to ask questions, and this is scored more than candidates realise. Three good questions beat ten. Aim for one on the work, one on the team, and one on what success looks like.

  • What does a good first six months look like in this role?
  • What is the biggest pressure on the team at the moment?
  • How is performance measured, and by whom?
  • Why is the role being filled now: growth, backfill, or a change in direction?
  • What would you want me to have fixed by the end of the first year?
  • How does the team handle competing priorities when everything is urgent?

Skip anything about leave, flexibility or salary in a first interview unless they raise it, and never ask a question whose answer is on the first page of their website. If you genuinely cannot think of one, ask about the next step in the process. For a longer list including questions suited to later rounds, see questions to ask HR.

Nerves, and how to keep them out of your answers

Interview nerves are normal and most interviewers read them as interest rather than weakness. What damages an interview is not the shaking hands, it is the answers that collapse under pressure: talking too long, filling silence, and guessing at a question you did not understand.

  • Prepare until the first answer is automatic. Confidence comes from having said the words out loud before, not from feeling calm.
  • Pause before answering. Two seconds of silence reads as thought. Rushing reads as panic.
  • Ask them to repeat or clarify if a question is vague. “Do you mean how I handled the deadline, or how I managed the client?” is a good answer, not a weakness.
  • Slow your breathing in the waiting room: in for four, out for six, five times. It lowers your heart rate faster than telling yourself to relax.
  • Bring water. It gives you a legitimate pause and something to do with your hands.
  • Do not over-rehearse. Rehearsed to the word, answers sound read. Rehearsed to the structure, they sound like you.

The pattern across all of these is the same: the answers that land are the ones you have said out loud before, to a person or to a camera, until the structure is automatic and the words are still yours.

After the interview: the thank you email and follow up

Send one email within a day, to the person who chaired or interviewed you. Four sentences: thank them, reference something specific that was discussed, restate one reason you fit, and confirm you are interested and available. Keep it under 150 words.

Subject lines that get opened rather than skimmed:

  • Thank you, Operations Coordinator interview, [your name]
  • Following up from today, [role], [your name]
  • Thanks for your time this morning, [your name]

If you have not heard anything by the date they gave you, send one short follow up to the recruiter, in the same thread, and then wait. A single polite nudge is professional; three in a fortnight is not. The full set of templates and etiquette sits in thank you email after a job interview.

Writing a follow up email after an interview

Reading the signals afterwards

You cannot read an outcome from body language, but there are patterns worth knowing so you can plan rather than refresh your inbox.

  • They spent time selling you the role, asked about notice period and start dates, or introduced you to the team: those are genuine positive signals.
  • They were polite, brief and specific about the timeline: neutral. Most interviews feel like this and still produce offers.
  • Silence past the stated date usually means a delay in the process, not a rejection. See post interview silence and how long it takes to hear back.
  • No reply after two follow ups is a soft no. Treat it as one and keep applying. See ghosting after an interview.

If several interviews produce no offers, the problem is usually earlier than the interview. Why you are not getting interviews covers the resume and application side.

Declining or cancelling an interview

If you have accepted another offer or the role is wrong, withdraw properly. One short email to the recruiter, a clear reason, and thanks. Do it as soon as you know, because they are holding a slot for you. Templates sit in how to cancel an interview.

Interview questions

How long should I prepare for an interview?

About two hours for a first interview: one hour on the organisation and the job advertisement, one hour building and saying your six STAR stories out loud. Double it for a panel or a second round.

How many STAR stories should I have ready?

Six covers most interviews: an achievement, a problem you solved, a conflict, a failure, leading or influencing without authority, and a process improvement.

Should I bring notes to an interview?

Yes, one page of bullet points, and refer to them openly if you need to. Reading a script is different and it shows.

What if I do not know the answer to a question?

Say so, then show how you would find out. “I have not done that with that system, but here is the closest thing I have done and how I would get up to speed” is a good answer.

Is it rude to ask about salary in the first interview?

Let them raise it. If they ask what you are seeking, give a researched range based on the role and city. Our salary guide by industry and the section on answering that question will give you the range.

Walk in able to prove what your resume claims.

Get my resume written, from $97

Where to go next

Leave a Comment

Your email address will not be published. Required fields are marked *

Scroll to Top