Prepare With Evidence, Not Memorised Answers
A practical guide to preparing for interviews, understanding what common questions are testing, building credible answers from your own experience and handling the details that affect interview performance.
Start With the Role, Not With a Script
The most useful preparation starts with the vacancy you are actually interviewing for. Read the job description line by line and separate the requirements into three groups: responsibilities you have already performed, skills you understand but have used in a different environment, and requirements where your exposure is limited. Your preparation should then concentrate on evidence from your own work.
Identify the five or six responsibilities that appear most important. For each one, write down a real example from your work. If you cannot find an example, prepare an honest explanation of how your existing experience transfers.
Anything written on your CV can become an interview question. Be ready to explain job changes, promotions, gaps, major projects, achievements, systems used, team size, geography, volumes and the scale of your responsibility.
Know what the organisation does, what the relevant business or function does and why this particular opportunity interests you. Research should help you ask sensible questions; it should not become a memorised speech about the company.
Prepare examples involving achievement, problem solving, conflict, pressure, mistakes, improvement, collaboration, leadership and stakeholder management. A strong example can often be adapted to several questions.
Be clear about notice period, current location, preferred location, work mode, availability, compensation and any constraints relevant to the vacancy. Avoid giving contradictory information at different stages.
Prepare at least three questions that show you understand the role. Ask about priorities, success measures, team structure, current challenges or what the person joining the role is expected to improve.
What the Question Is Really Trying to Understand
There is no single perfect answer to an HR question. A good answer is relevant to the role, consistent with your CV, supported by real evidence and delivered clearly. Use the guidance below to prepare your own answer rather than memorising a script.
What they are trying to understand: whether you can summarise your professional background clearly and identify the experience relevant to the vacancy.
How to prepare: build a 60–90 second structure: current or most recent role → relevant experience → two or three strengths connected to the vacancy → why this opportunity is a logical next step.
Avoid: starting with your personal history, repeating your entire CV or speaking for several minutes without connecting your experience to the role.
What they are trying to understand: your motivation, professionalism and whether the reason for changing is consistent and credible.
How to prepare: explain what you are seeking next — broader responsibility, a different functional challenge, career progression, a new environment or another genuine reason. Keep the focus on the future.
Avoid: attacking your manager or employer, exaggerating problems or giving a reason that conflicts with what you have told the recruiter.
What they are trying to understand: whether your experience actually matches the requirements and whether you can explain that match with evidence.
How to prepare: select two or three important requirements from the job. For each, explain what you have done, in what environment and what the outcome was.
Useful structure: “The role requires X. I have handled X in Y environment, where I was responsible for Z, and the outcome was …”
What they are trying to understand: whether you understand your own working style and whether the strengths you mention are relevant to the role.
How to prepare: choose strengths that matter for the position and attach evidence. “Problem solving” is a claim; explaining how you identified the cause of a recurring issue and what changed is evidence.
What they are trying to understand: self-awareness, honesty and whether you take responsibility for development.
How to prepare: choose a genuine development area that is manageable and explain what you are doing to improve it. The improvement action is more important than finding a clever-sounding weakness.
Avoid: artificial answers such as “I am a perfectionist” unless you can explain the actual behaviour and what you are doing about it.
What they are trying to understand: whether you have a reason for applying beyond simply wanting a job.
How to prepare: connect the work itself, your relevant experience and what you want to develop next. Mention specific responsibilities from the vacancy rather than generic praise.
What they are trying to understand: whether you have researched the employer and whether your interest is genuine.
How to prepare: identify one or two specific aspects of the business, role or opportunity that connect with your experience and career direction. Do not repeat the company website word for word.
What they are trying to understand: whether expectations are broadly aligned with the role and whether you can discuss compensation professionally.
How to prepare: know your current compensation, fixed and variable components, notice period and a realistic range for the target role. If the employer has not disclosed the budget, you can ask for the range before committing to a number.
Avoid: inventing competing offers or giving figures you cannot justify if asked about your expectations.
What they are trying to understand: the factual reason for the gap and whether there is anything relevant they should understand about it.
How to prepare: give the real reason briefly, then explain what you did during the period if it is relevant — job search, study, family responsibility, relocation, project work or another genuine activity.
Avoid: creating a complicated explanation that could later conflict with your application or background information.
What they are trying to understand: judgement, ownership, communication and how you behave when normal processes are not enough.
How to prepare: use one real example. Explain the problem, your responsibility, the options you considered, what you actually did and what changed as a result.
What they are trying to understand: accountability and learning rather than perfection.
How to prepare: choose a genuine but appropriate example. Do not blame others. Explain what caused the problem, what you did after discovering it and what control or behaviour you changed afterwards.
What they are trying to understand: whether your previous scope is relevant to the new scope.
How to prepare: use scale and complexity: team size, transaction volume, geography, systems, deadlines, stakeholders, process ownership or measurable improvements. Concrete scale is more persuasive than adjectives.
Turn Experience Into Evidence
A strong answer normally has three layers: enough context to understand the situation, a clear explanation of what you did and an outcome or learning point. For behavioural questions, STAR is useful, but it should guide your thinking rather than become four headings that you recite.
Give only enough context to understand the problem. What was happening, what was at risk and what was your responsibility?
State what you personally needed to achieve. Make your role clear instead of describing everything the wider team did.
This is the most important part. Explain what you actually did, why you chose that approach, what alternatives you considered if relevant and how you worked with others.
Give the outcome where possible: time saved, errors reduced, positions closed, service improved, deadline met, risk reduced or stakeholder issue resolved. If there was no measurable number, describe the practical result.
Weak vs evidence-based answer
Weak: “I am very good at handling pressure and I always complete my work on time.”
Better: “In my previous role, we had a month-end reporting deadline while two team members were unavailable. I reviewed the outstanding activities, separated critical dependencies from lower-priority work, agreed priorities with the stakeholders and tracked completion twice a day. We completed the reporting cycle within the deadline and did not carry the unresolved items into the next period.”
The second answer gives the interviewer something they can evaluate: the situation, the candidate's decisions, the action taken and the outcome. It also creates natural opportunities for useful follow-up questions.
Build an evidence bank before the interview
Write down at least one real example for each area below. You do not need to memorise the wording. Remember the facts and the sequence of events so you can explain them naturally.
- A difficult problem you solved and how you found the root cause.
- A process you improved, including what changed after your intervention.
- A mistake you made and the control or behaviour you changed afterwards.
- A disagreement with a colleague or stakeholder and how you reached a workable outcome.
- A tight deadline, high-volume period or unexpected workload.
- A situation where you influenced someone without formal authority.
- An achievement you can explain with a measurable or observable result.
- A situation where you had incomplete information and had to make a decision.
- A skill you are currently developing and how you are developing it.
Use numbers carefully
Numbers can make an answer more credible, but only when they are accurate. If you say you reduced errors by 30%, closed 50 positions or managed a team of 20, be prepared for the interviewer to ask how you measured it. If you do not know the exact number, use an honest approximation or describe the outcome without inventing precision.
When the Interview Does Not Go According to Plan
Do not invent one. State what you know, identify what you are unsure about and explain how you would verify or solve it. For a technical or functional question, showing a sensible method can be more useful than guessing.
It is acceptable to ask, “Could you clarify whether you mean X or Y?” A short clarification is better than giving a confident answer to the wrong question.
Stay professional. Explain your reasoning and evidence rather than trying to prove the interviewer wrong. If the question is based on an assumption, ask about the assumption first.
Answer factually. If a CV statement was unclear or overstated, correct it rather than defending wording you cannot support. Credibility is more important than appearing perfect.
Explain the facts briefly and focus on what you learned and what you are looking for now. Avoid blaming the previous employer or giving a different reason to different interviewers.
If a question is not relevant to the role or you are uncomfortable answering it, you can redirect the conversation toward your professional availability, experience or suitability for the position.
Use This the Day Before and Again One Hour Before
Role
- Can I explain the main responsibilities in my own words?
- Which three requirements match my experience most closely?
- Which requirement is weaker and how will I address it honestly?
- Which two examples best demonstrate my suitability?
Company
- Can I explain what the organisation does?
- What interests me about this specific opportunity?
- Have I checked reliable, current information available from the employer?
- Do I have two sensible questions about the role or team?
My CV
- Can I explain every major role and transition?
- Can I describe my key projects, systems and responsibilities?
- Do I know the numbers behind the achievements I have listed?
- Are my dates, titles and other details consistent with my application?
Interview Setup
- For a virtual interview, have I tested camera, microphone and connection?
- Do I have a quiet, professional space and a backup contact method?
- For an in-person interview, have I confirmed the location, travel time and contact details?
- Is my phone on silent and are the required documents ready?
Questions for Them
- What would success look like in the first six months?
- What are the biggest challenges in this role today?
- How is the team structured and who would I work with most closely?
- What are the next stages of the selection process?
Final Check
- CV and relevant documents ready.
- Notice period and compensation details clear.
- Two or three strong examples prepared.
- One-minute introduction prepared without memorising every word.
- Professional clothing and interview location confirmed.
Professional Communication Continues After the First Answer
Listen to the full question before answering. If a question is unclear, ask for clarification rather than answering a different question. Keep your answer structured, but allow the interviewer to ask follow-up questions. Do not interrupt simply because you think you know where the question is going.
If you need a few seconds to think, take them. A short pause is generally better than filling the space with unrelated information. When discussing a team achievement, make your own contribution clear. When discussing a problem, avoid turning the answer into a criticism of other people.
After the interview, note down the questions that challenged you while they are still fresh. Record what evidence you used, where your answer was weak and what you would improve next time. This creates a personal interview-preparation library instead of forcing you to start from zero for every interview.