Sample Interview Questions and Answers for Effective Hiring

In human resource management, a job discussion is the structured conversation between an employer and a candidate or employee about a role: what the work involves, what good performance looks like in it, and whether the person and the job actually suit each other. It is not a formally defined term the way job analysis, job description and job specification are, which is why you will see the same phrase used for a hiring interview, a performance conversation and a career check-in. This guide separates it from the terms it gets confused with, then works through the questions that make the conversation worth the hour, with example answers and what a good interviewer listens for.

Last reviewed September 2026.

What a job discussion means in human resource management

Ask ten HR practitioners to define a job discussion and you will get answers that all circle the same thing: a two-way conversation about a role, held between the person accountable for the work and the person who might do it. Some textbooks use it as a plain-English label for the selection interview. Others use it for the conversation a manager has with an existing employee when a role changes shape. Both uses are defensible, because the phrase describes an activity rather than a document.

That is the part worth holding on to. Job analysis, job description and job specification are artefacts. They get written down, versioned, signed off and filed. A job discussion is the live conversation those artefacts feed, and the quality of the conversation depends almost entirely on how well the paperwork behind it was done. Walk in without a clear picture of what the role requires and you end up with an hour of pleasant chat that tells you nothing you can defend later.

The confusion with job description is understandable. The two phrases differ by one syllable and they sit next to each other in the hiring process. A useful way to hold them apart: the description says what the job is, the discussion tests whether this person can do it.

If your organisation uses the phrase internally, write down which of these you mean. A policy that says "hold a job discussion before confirming the appointment" is ambiguous enough to be ignored, and ambiguity in hiring documentation is exactly the thing that causes trouble when a decision is later questioned.

Job discussion or job description: telling the two apart

A job description is a document you can email. It lists the purpose of the role, the duties attached to it, who the person reports to, the conditions of employment and the results the role exists to produce. It stays reasonably stable between reviews and it does double duty across advertising, onboarding and performance management. Our guide to what a job description is and what belongs in one covers the components in detail.

A job discussion cannot be emailed. It happens in a room or on a call, it has a beginning and an end, and the record of it is whatever notes and scores the participants keep. When people search for the term, they are usually trying to work out whether a colleague meant the paperwork or the conversation. In most Australian and New Zealand workplaces the answer is the conversation, and the paperwork is what they should have sent you beforehand.

One practical consequence follows from the difference. A job description that is out of date quietly misleads everybody: candidates apply for work that no longer exists in that shape, and the interviewer tests against duties that moved to another team eighteen months ago. Refresh the description before the discussion, not after.

Where job discussions happen across the employee lifecycle

Hiring is the obvious one, and it is where most of the attention goes. A selection interview is a job discussion with higher stakes, tighter timing and a legal obligation to treat every applicant consistently.

The less obvious ones matter more than they get credit for. When a role changes shape, because a team restructures or a system replaces half the manual work, the employee deserves a proper conversation about what the job now is rather than a revised position description dropped in their inbox. Development conversations are job discussions too: the subject is the job the person wants next and what stands between them and it. So are stay conversations, where a manager asks a valued employee what would make them leave and what would make them stay, well before a resignation letter arrives.

Exit conversations sit at the other end. They are the only job discussion where honesty costs the employee nothing, which is precisely why the answers are worth recording and reading in aggregate rather than one at a time.

Across all of these, the discipline is the same. Decide what you are trying to learn, ask every person the same core questions, write down what you heard rather than how you felt, and separate the evidence from the judgement until you have all of it.

How to prepare before the discussion

Preparation is where most interviews are won or lost, and it takes both sides about the same amount of effort.

If you are running the discussion, start from the job specification and pick the four or five capabilities that actually predict performance in the role. Write one or two questions for each. Agree in advance what a weak, adequate and strong answer sounds like, so you are scoring against a standard rather than against whoever you interviewed last Thursday. Decide who on the panel asks what, and give candidates the questions in advance if the role rewards considered thinking rather than improvisation. A structured interview is not a script to be read robotically; it is a guarantee that everyone got the same opportunity to show you the same things.

If you are the one being interviewed, read the job description properly and mark the three or four duties that carry the weight of the role. Prepare a specific example for each, with the situation, what you actually did and how it turned out. Know your salary range and be able to say it without flinching. Have questions ready that you genuinely want answered, because an hour spent learning nothing about the team you are about to join is an hour wasted.

What to send before the conversation, and how long to allow

Candidates who arrive informed give better answers, and better answers make better decisions. The minimum worth sending is the current job description, the names and roles of everyone on the panel, the format of the conversation and roughly how long it will run. If there is a work sample, a presentation or an assessment involved, say so in the same email rather than sprinting it on the day.

Sending the questions in advance is more contentious than it should be. The argument against is that preparation masks ability. The argument for is that almost no job rewards thinking on the spot under observation by strangers, so testing for it selects for confidence rather than competence. Where the work involves considered judgement, send the questions. Where the work genuinely is improvisation under pressure, such as a frontline service role, keep them back and say why.

On timing, an hour is the practical standard for most roles: about ten minutes to set the scene and put the person at ease, thirty-five to forty on the questions themselves, and the rest for their questions and the next steps. Senior appointments usually need a second conversation rather than a longer first one, because attention degrades badly after about ninety minutes for everyone in the room.

Close by telling the candidate what happens next and when. A named day beats "we will be in touch", and if the day slips, send a short note rather than silence. The way an organisation behaves between interview and offer is the only evidence a candidate has about how it behaves as an employer, and word travels in small markets.

Fifteen questions for a job discussion, with example answers

The answers below are illustrative. They are written to show the shape of a strong response rather than to be memorised, and an interviewer can tell the difference within about two sentences. Each question includes what a good interviewer is listening for, which is the part most question lists leave out.

Tell me about yourself

The opener exists to settle nerves and to see what someone chooses to put first. It is not an invitation to recite a résumé from school onwards.

Example answer: "I have spent about six years in marketing, mostly on campaign work for consumer brands. The part I have got good at is turning a vague brief into something measurable, which is what drew me to this role. Before that I worked agency side, which taught me to work fast with incomplete information."

Listen for: relevance and editing. A candidate who gives you three tidy minutes has thought about what you need to know. One who talks for nine minutes without reaching the present decade is telling you something about how they run a meeting.

What do you know about our organisation?

This tests preparation, and preparation is a reasonable proxy for how much someone wants the job.

Example answer: "You work mainly with mid-sized employers across Australia and New Zealand, and from your recent announcements it looks like the growth is coming from the services side rather than the original product. I noticed your careers page talks a lot about evidence, which matches how the role is written."

Listen for: whether they read past the homepage. Specifics about your customers, your market or a recent change count for more than a compliment about your values statement.

What interests you about this position?

Motivation predicts tenure better than enthusiasm does. You are looking for a reason that will still be true in eighteen months.

Example answer: "Two things. The role owns the whole project rather than one stage of it, which is what I am missing at the moment. And it is a small enough team that I would be doing the work as well as planning it, which suits how I like to operate."

Listen for: reasons connected to the work itself. "It is closer to home" is honest but fragile, because a closer job will come along.

How is your previous experience relevant?

This is the question the job specification was written for. The candidate should be joining dots you can verify.

Example answer: "The last role was the same function at a smaller scale. I ran the client relationships and the reporting, which is most of what this position covers, and the main difference is that you have a formal governance layer I have not worked inside before. I have worked with auditors, so the discipline is not foreign."

Listen for: honesty about the gap. Candidates who name the difference between their experience and your requirement, then explain how they would close it, are usually the ones who cope when the job turns out to be harder than advertised.

What are your strengths?

The most predictable question in interviewing, and the one most often answered badly. There is a longer treatment further down this page.

Example answer: "Getting clarity out of messy situations. When a project stalls, I am usually the person who writes down what we actually disagree about, which tends to unstick it. My last manager used me for that deliberately on two accounts that had gone quiet."

Listen for: a strength with evidence attached and a strength that the job needs. "I am a perfectionist" is neither.

What are your weaknesses?

Asked well, this tests self-awareness. Asked badly, it produces a rehearsed humblebrag that tells you nothing.

Example answer: "I am slow to delegate. I know why, I like knowing the detail, but it means I have been the bottleneck on work that did not need me. I have started handing over the first draft rather than the final review, and it has helped."

Listen for: a real limitation, named without drama, with something being done about it. If you get a non-answer, follow up with a question about feedback they have received rather than pushing on the same question.

What is your preferred work style?

Work style questions are where fit either shows up or hides. The useful version asks about conditions rather than adjectives.

Example answer: "I do my best thinking early and alone, then I want people in the room to pull it apart. I would rather have a short daily check-in than a long weekly one, and I am comfortable with written updates instead of meetings where that works."

Listen for: compatibility with how your team actually operates, not with how your team describes itself. A candidate who needs deep focus in a role built around constant interruption will struggle regardless of skill.

What are your salary expectations?

Where pay transparency rules apply, you may already have published a band. Asking anyway confirms you are in the same territory before either side spends more time.

Example answer: "I am looking in the range of eighty-five to ninety-five thousand plus superannuation, depending on how the leave and flexibility sit. If the band for this role is different, I would rather know now."

Listen for: a number, not a dodge. And check your own house first: if the answer is well outside your band, say so in the room rather than progressing someone you cannot afford.

Can you give an example of a time you led something?

Leadership shows up long before a title does. Ask for the example rather than the philosophy.

Example answer: "We had a launch that was going to miss its date and nobody wanted to say it. I mapped what was actually blocking us, took the two-week slip to the sponsor with a plan attached, and reallocated the testing work so we could hold the new date. We shipped on the revised date with no defects raised in the first month."

Listen for: "I" and "we" in sensible proportion. Candidates who never say "I" may be hiding a modest contribution. Candidates who never say "we" may be hard to work alongside.

How do you handle stress?

Every role has pressure somewhere. You are checking whether they know where theirs comes from.

Example answer: "Volume does not bother me much; ambiguity does. When I have too much on, I cut the list to what has to happen this week and tell people what is moving. When the brief is unclear I go and ask rather than guessing, which I learned the expensive way."

Listen for: a method rather than a mood. "I just push through" is a warning sign in any role with sustained load.

How would you handle conflict at work?

Conflict questions work better in the past tense, because hypotheticals invite the textbook answer.

Example answer: "A colleague and I disagreed about how much testing a release needed, and it got tense in front of the team. I asked for ten minutes afterwards, we found we were solving different risks, and we agreed on a middle position I would not have reached alone. I should have taken it offline sooner."

Listen for: ownership without self-flagellation, and evidence that the working relationship survived.

Where do you see yourself in five years?

The question is dated but the intent behind it is not. You want to know whether this role sits on their path or beside it.

Example answer: "Running a team, probably four or five people, still close enough to the work to be useful. This role gets me the operational depth I am missing, and I would expect that to take a couple of years before I am ready for the step up."

Listen for: a direction that your organisation can plausibly offer. If the honest answer is that you cannot, say so; candidates who leave for a promotion you promised and never delivered are expensive twice.

Tell me about a challenge you worked through

Near-identical to the conflict question, which is why you should ask one or the other rather than both.

Example answer: "We lost half the team to a restructure four months into a build. I rescoped to what a smaller team could actually deliver, negotiated the cut features with the sponsor, and brought two contractors in for the parts nobody left knew. It landed six weeks late instead of failing."

Listen for: whether the outcome is described honestly. Six weeks late told plainly is more credible than a story where everything went perfectly.

How do you adapt to change?

Useful in any organisation that is growing, shrinking or replacing a core system, which is most of them.

Example answer: "We changed reporting tools twice in three years. The second time I volunteered to learn it first and run the sessions for the rest of the team, mostly because I was tired of the complaining. I do not love change for its own sake, but I would rather be inside it than have it done to me."

Listen for: a concrete change they lived through, including the bit they found hard. Everyone claims to be adaptable.

What questions do you have for us?

Treat this as a scored question rather than a wind-down. What a candidate asks reveals what they have been thinking about for the past hour.

Example answer: "What does the first ninety days look like if it goes well? And what is the thing about this team that people find hardest when they join?"

Listen for: questions about the work, the team and how success is judged. Someone who asks only about leave and flexibility has not been imagining themselves doing the job.

How should you answer when the interviewer asks about your strengths?

Pick strengths the job needs, then prove each one with something that happened. Two well-evidenced strengths beat five adjectives, and the evidence is the whole point: an interviewer cannot score "I am a good communicator", but they can score "I rewrote our monthly client report and the account manager stopped getting follow-up calls about it".

A workable structure runs in four parts. Name the strength in plain words. Give one example with enough detail to be checkable. Say what the result was. Connect it to the role you are interviewing for. That last step is the one candidates skip, and it is the one that does the work.

Two traps are worth avoiding. The first is the disguised weakness, where "I care too much" is offered as a strength and lands as a rehearsed line. The second is the strength nobody asked for: being brilliant at spreadsheets is genuinely valuable, but not in a role where the actual difficulty is managing difficult stakeholders. Read the job specification and answer the job in front of you.

If you struggle to name your strengths at all, the useful prompt is not "what am I good at" but "what do colleagues come to me for". The answer to the second question is usually specific, evidenced and easy to say out loud. Understanding your own work preferences helps here too, because strengths that come naturally are the ones you can sustain under pressure. Compono's work personality framework describes eight ways people prefer to work: Doer, Auditor, Helper, Advisor, Pioneer, Campaigner, Evaluator and Coordinator.

Skills, abilities, values and experience: which word means what

These four words get used interchangeably in job ads and they mean genuinely different things. Skills and talents that help someone in a career are examples of abilities, which is the category covering what a person is capable of doing. The other three describe different territory.

• Abilities are what someone can do: writing clearly, reading a balance sheet, running a crew safely, learning a new system quickly. Skills and talents both sit inside this category, with skills usually meaning capabilities that were trained and talents meaning capabilities that came more easily.
• Values are what someone cares about: fairness, autonomy, security, recognition. Values predict whether a person will be happy in your organisation, not whether they can do the work.
• Experience is what someone has done: roles held, years served, projects delivered, industries worked in. Experience is evidence of ability rather than ability itself, which is why two people with the same five years can be wildly different hires.
• Background is the broader context a person brings: education, sector, geography, the kind of organisations they have worked inside. It shapes how quickly someone will find their feet in yours.

The distinction matters in interview design. Questions about experience get you a history. Questions about ability need a demonstration, a work sample or a properly validated assessment. Questions about values need a conversation about what the person has chosen and turned down, not a direct ask, because nobody answers "do you value integrity" with a no.

How to score a job discussion so the decision holds up

An unstructured interview produces a strong feeling and very little you can point to afterwards. That is fine until the day the decision is challenged, or the day the hire does not work out and somebody asks how you chose.

Score against the capabilities you defined before you met anyone. Use a simple scale, three or four points, with written anchors describing what each point looks like. Have every panel member score independently before discussing, because the first opinion spoken aloud drags the rest of the room with it. Record the evidence next to the score rather than the score alone: "gave two examples of resolving a supplier dispute, one recent" is reviewable, while "7/10" is not.

Keep the notes. Where an unsuccessful candidate asks why, or a decision is later examined, contemporaneous notes tied to job-related criteria are the difference between a process you can explain and one you cannot. This is educational guidance rather than legal advice; if you are working through a specific dispute or an obligation under Australian employment law, get advice from an employment lawyer or your industry association.

It is also worth knowing the cost of getting it wrong, because that number tends to change how much rigour a team is willing to invest. Our cost of a bad hire calculator works it out from your own salary, recruitment and ramp-up figures. And if you are weighing up where to spend effort in the process, the comparison between assessments and video interviewing covers what each method actually tells you about a candidate.

Mistakes that make a job discussion useless

Asking different questions of different candidates is the big one. It feels responsive and it destroys comparability, because you end up choosing between an apple you examined closely and a pear you barely looked at.

Talking more than the candidate is the second. A panel that spends forty minutes describing the role has learned nothing, and the candidate has learned only that you like talking. A rough guide: the person being assessed should hold the floor for about three quarters of the time.

Deciding in the first few minutes and spending the rest of the hour confirming it is the third, and it is the hardest to catch in yourself. Structured scoring is the practical defence, because it forces you to write down evidence for capabilities you have not tested yet.

Then there is the paperwork problem: interviewing against a job description nobody has updated since the last incumbent started. Before the discussion, check that the duties listed are the duties that exist.

Compono Hire is an applicant tracking system that keeps the evidence with the conversation: role requirements, structured scoring and candidate profiling against the culture and the work itself, in one record rather than four inboxes. It suits employers hiring with any regularity, and it is genuine overkill if you make two appointments a year.

Frequently asked questions

What does job discussion mean in human resource management?

It means the structured conversation between an employer and a candidate or employee about a role: what the work involves, what good performance looks like and whether the person suits the job. It is a descriptive phrase rather than a formally defined HR term, so it covers selection interviews, role-change conversations and development conversations depending on who is using it.

Is a job discussion the same as a job description?

No. A job description is a written document setting out the purpose, duties, reporting lines and accountabilities of a role. A job discussion is the live conversation that tests a person against those requirements. The description is what you send beforehand; the discussion is what you hold afterwards.

How should I answer when the interviewer asks about my strengths?

Choose strengths the role actually needs, then evidence each one with a specific example and its result, and finish by connecting it to the job you are interviewing for. Two evidenced strengths land better than a list of adjectives, and disguised weaknesses such as "I care too much" are easy to spot.

Are skills and talents that help a career examples of values, experience, background or abilities?

Abilities. Abilities cover what a person is capable of doing, and both skills and talents sit inside that category. Values describe what someone cares about, experience describes what they have done, and background describes the education and context they bring.

How many questions should a job discussion cover?

Enough to test the four or five capabilities that predict performance in the role, which usually means six to ten questions in an hour once you allow time for the candidate's own questions. Asking twenty rushed questions produces thinner evidence than asking eight and following up properly on each.