Job Interview Questions and Answers
By Judy M. Wallis, Founder and Interview CoachLast updated
The 14 most common job interview questions — the behavioural questions that come up in almost every Australian interview — with a full sample STAR answer, what the interviewer is actually scoring, and the mistake that costs candidates the most marks. Written by a recruiter with more than 15 years in HR and recruitment.
How behavioural questions are scored
Interviewers are not listening for a good story. They are marking specific evidence against a capability: what the situation demanded, what you personally decided, and what measurably changed. That is why the STAR method works — it puts the evidence where the scoring happens.
Two rules cover most of the gap between a 2/5 and a 5/5 answer: use "I" instead of "we" when describing your actions, and finish with a number.
How recruiters score your answer (1–5)
Hypothetical or general ("I usually…"), mostly "we", no clear result.
A real example with some personal actions, but a vague or unmeasured result.
A specific example, clear "I" actions with reasons, and a measurable result.
All of the above, plus what you learned or changed afterwards, pitched at the level of the role.
14 most common interview questions (with sample answers)
Tell me about a time you worked in a team to achieve a goal.
The interviewer is testing whether you can name your own contribution without either hiding behind "we" or claiming the whole win.
Situation: our claims team had a 9-day backlog after a system migration. Task: I owned the triage process for the three worst queues. Action: I built a simple priority rule, paired two assessors per queue, and ran a 10-minute morning huddle to reassign volume. Result: the backlog cleared in 11 days and average handling time stayed flat.
Saying "we" for every sentence. Interviewers cannot score a story with no "I" in it.
Describe a time you disagreed with your manager.
They want evidence you can challenge upwards professionally and then commit to the decision either way.
Situation: my manager wanted to launch a pricing change with no customer testing. Task: I needed to raise the risk without stalling the launch. Action: I put the risk in writing with two options, proposed a 2-week pilot on 5% of accounts, and committed to the full launch if the pilot held. Result: the pilot found a billing edge case that would have hit 300 customers; we fixed it and launched two weeks later.
Choosing a story where you were right and your manager was foolish. Pick one that shows judgement, not scorekeeping.
Tell me about a time you failed.
They are scoring self-awareness and what you changed afterwards — not the size of the failure.
Situation: I ran a supplier tender and shortlisted on price without weighting delivery capacity. Task: I owned the selection. Action: when the supplier missed the first two milestones I escalated within a week, moved 40% of volume to the runner-up, and rewrote the scoring matrix to weight capacity at 30%. Result: we recovered the schedule with a 6-day slip, and the new matrix is still used for tenders.
A fake failure ("I work too hard"). It reads as evasive and burns the question.
Give me an example of working under pressure to a tight deadline.
They want your prioritisation method, not proof that you can be busy.
Situation: a regulator requested a data submission with 5 business days notice during end-of-month close. Task: I coordinated the submission across three teams. Action: I cut the scope to the mandatory fields, booked two 30-minute daily checkpoints, and negotiated a 2-day extension on an internal report to free up the analysts. Result: we submitted a day early with zero data queries returned.
Describing chaos without a decision. Name the trade-off you made.
Tell me about a time you led a team through change.
They are checking whether you can bring sceptical people with you rather than just announce a plan.
Situation: two product teams merged with conflicting roadmaps and a release six weeks out. Task: I led the combined team. Action: I ran a two-day alignment workshop, cut 30% of scope against a written rubric, paired one engineer from each side on every workstream, and met 1:1 with the four most sceptical people in week one. Result: we shipped on the original date with zero P1 bugs, and team eNPS moved from -8 to +42.
Talking only about the plan. Interviewers score the people work.
Describe a complex problem you solved.
They want to see how you break down ambiguity and how you knew the fix worked.
Situation: online conversion dropped 18% in a fortnight with no release. Task: I owned the investigation. Action: I split the funnel by device, browser and payment method, isolated the drop to one wallet provider on iOS, reproduced it on a test device, and shipped a fallback within 48 hours. Result: conversion recovered to baseline in three days and we added a synthetic check for that payment path.
Jumping to the answer. Show the elimination steps — that is the signal.
Tell me about a time you turned around an unhappy customer.
They are testing ownership and whether you fix the cause, not just the mood.
Situation: a key account escalated after three missed reporting deadlines. Task: I took over the relationship. Action: I called the same day, gave a written recovery plan with dates, moved their reporting to an automated pipeline, and sent a weekly one-page status for six weeks. Result: they renewed for 24 months and referred two teams internally.
An apology story with no structural fix. Name what changed permanently.
Give me an example of going beyond your role.
They want to know your judgement about when to step outside scope — and that you did it with permission.
Situation: onboarding new starters took an average of 12 days and nobody owned it. Task: not my role, but it was slowing my team. Action: I mapped the steps, got my manager to sponsor a two-week fix, built a checklist and pre-provisioning request, and trained two team leads to run it. Result: onboarding dropped to 4 days and the checklist was adopted by three other departments.
Framing initiative as ignoring your manager. Show the sponsorship.
Tell me about a time priorities changed suddenly.
They are checking that you renegotiate commitments rather than silently dropping them.
Situation: two weeks into a reporting build, a compliance audit was brought forward by a month. Task: I had to deliver audit evidence without abandoning the build. Action: I paused the two lowest-value dashboards, reused the same data model for the audit extract, and told stakeholders in writing what would slip and by how long. Result: the audit closed with no findings and the build landed nine days late against a re-agreed date.
Saying "I just got it all done". It sounds like you have no priorities.
Describe a time you influenced someone without authority.
Common for senior and cross-functional roles — they want your method, not your persistence.
Situation: I needed the finance team to change a month-end cut-off that broke our forecasting. Task: I had no authority over their process. Action: I quantified the rework in hours per month, brought a one-page option set to their team lead, and offered to absorb the transition work for the first two cycles. Result: they moved the cut-off by two days, saving roughly 20 hours of rework a month.
Describing pressure instead of value. Influence answers need a number.
Tell me about a time you managed competing stakeholder expectations.
They want to see how you balance people who want different things, and whether you keep them informed.
Situation: sales wanted a new feature in the next release, while operations wanted the release frozen for stability. Task: as project lead I had to agree a scope both would accept. Action: I met each group separately to find their non-negotiables, then proposed shipping a smaller version of the feature behind a switch that operations controlled. Result: both groups signed off in one meeting, the release went out on time and there were no incidents.
Presenting it as winning an argument. The panel scores how you kept both sides on board.
Describe a time you had to do the right thing when it was not easy.
Common in government and regulated roles. They are testing judgement and whether you speak up.
Situation: I noticed a colleague had approved a supplier invoice with no matching purchase order. Task: I needed to raise it without assuming bad intent. Action: I asked my colleague about it first, then logged it with my manager under our procurement policy when the paperwork could not be found. Result: the invoice was found to be a duplicate, $14,000 was recovered and a matching check was added to the approval process.
Choosing a story with no real tension. It must show a decision that carried some personal cost.
Give me an example of when your attention to detail prevented a problem.
They want your checking method, not a claim that you are careful.
Situation: I was preparing a board report two days before it was due. Task: I owned the final figures. Action: I checked every total against the source system rather than the previous report, and found a formula that had excluded one region. Result: I corrected a $1.2 million understatement before the board saw it, and added a reconciliation step to the monthly checklist.
Saying "I am a perfectionist". Describe the check you ran and what it caught.
Tell me about a time you had to explain something complex to a non-expert audience.
They are checking whether you adapt your message to your audience rather than repeating the technical version.
Situation: our team needed community support for a change to how local water charges were calculated. Task: I had to explain it at a public information session. Action: I replaced the rate tables with three example household bills, tested the slides on two colleagues outside the team, and left 20 minutes for questions. Result: feedback forms rated the session 4.6 out of 5, and complaints after the change were half the level of the previous rate review.
Describing what you said, not how you knew they understood it.
Frequently asked questions
Behavioural interview questions ask you to describe a specific past experience — "Tell me about a time…", "Describe a situation where…", "Give me an example of…". Interviewers use them because past behaviour predicts future performance better than hypothetical answers.
Use the STAR method: Situation, Task, Action, Result. Keep Situation and Task to about 20% of the answer and spend the rest on your Actions and a measurable Result. Aim for 60 to 90 seconds spoken.
Most panels score each answer on a 1–5 scale against the capability being assessed. A 4 or 5 needs a specific example, clear personal actions and a measurable result.
Usually four to eight in a 45–60 minute interview, often one per capability in the job description or selection criteria.
Five to seven strong stories covering leadership, teamwork, conflict, failure, problem-solving, pressure and influence. Each story can be re-angled to answer several different questions.
Use the closest relevant example — study, volunteering, casual work or a project — and be explicit about the transfer: what the situation demanded and how you would apply the same approach here. Never invent an example.
Yes. Behavioural and capability-based questions are the default in Australian public sector, corporate and graduate recruitment, usually mapped against a published set of capabilities or selection criteria.