What a Job Interview Is For
A job interview gives an employer and a candidate time to discuss whether a particular role could be a good match. The employer can assess how your experience and skills relate to the work, while you can ask about the responsibilities and workplace. The conversation may be formal or informal, and its structure depends on the employer and position. It can also clarify expectations that are not obvious from a job posting. Considering what each side is looking for helps you take part with a clearer sense of the role.
Assessing role fit
An employer may use an interview to compare your experience and skills with the work a position requires. For a payroll role, that could mean discussing familiarity with reconciliations, confidential records and meeting a pay-cycle deadline. For customer support, the focus may be on handling service issues and documenting resolutions. The aim is to assess how your experience relates to relevant tasks, rather than relying only on whether your previous job title matches.
Employers gather this evidence in different ways. One may use the same scored criteria for each applicant; another may have a conversation with a hiring manager, a panel or a role-related exercise. The number of stages, participants and evaluation criteria varies by employer and occupation. An interview at a large financial institution, for example, may follow a different process from one at a small technology company. Communication, judgement or collaboration may also matter when those capabilities are part of the role.
Role-specific discussion helps make the comparison meaningful. When an employer can relate what you have done to actual duties—such as coordinating supplier deadlines or resolving a client issue—it can consider your evidence against the position’s requirements. A focused conversation is more useful than a general discussion because it keeps attention on the work and the capabilities needed to do it.
A two-way conversation
An interview also gives you a chance to clarify what the job involves beyond its title and posting. You might ask how responsibilities are divided between a supervisor and individual contributors, which priorities take up a typical week, or how the team coordinates work across locations. For a hybrid position, for instance, the discussion can clarify how often staff attend the workplace and which tasks are handled collaboratively.
You can use the conversation to clarify expectations that affect your decision, such as the reporting relationship, schedule, performance measures or likely start date. Asking what a successful first few months would involve can reveal whether the employer expects you to follow an existing process, manage a defined workload or help build a new one. The employer, in turn, considers whether your interests and circumstances align with the responsibilities and working context described.
This exchange does not guarantee an offer. An employer may still compare applicants, complete other interview stages or decide that another candidate better meets its requirements. You may also decide that the duties, schedule or team environment do not suit your needs. Clarifying these details during the discussion helps both sides make a more informed decision about whether to continue with the hiring process.
Prepare Before the Interview
A focused job interview guide starts with a clear picture of the role and the employer, then turns that information into a practical plan. A dedicated guide to interview preparation can help you review a posting, choose relevant examples and confirm meeting arrangements. Keep your notes brief enough to scan shortly before the conversation, such as a one-page summary of priorities and questions. The steps below help you use preparation time deliberately, whether your meeting is in person, by phone or online.
Reviewing the role
Read the complete posting rather than relying on its job title; responsibilities, required qualifications and preferred experience may appear in separate sections. Use the employer’s own wording to focus your preparation.
Make a short role checklist, grouping related duties and noting where the posting leaves details open. These points will give your preparation a clear focus.
- Mark the central responsibilities, such as serving clients, preparing reports or coordinating projects, and note the verbs that show what you would be expected to do.
- Separate required qualifications from preferred ones, then record specific credentials, software, languages or years of experience named in the posting.
- Check the employer’s careers pages and available public information for its services, locations and current priorities; use details that relate directly to the advertised position.
- For a public company or institution, review a recent annual report or official overview when available, rather than relying on unverified summaries or outdated profiles.
- Flag wording that needs clarification, such as an undefined reporting line, travel requirement or shift pattern, and keep each point tied to the job description.
Finish with a compact checklist of the role’s main duties, essential requirements and employer-specific details. It will help you direct preparation toward what the posting actually emphasizes.
Planning examples and logistics
Choose a small set of work, volunteer or project examples that connect to the role checklist, and prepare questions that address genuine unknowns. Then confirm the meeting format and practical details.
- Select two or three examples from different situations, such as completing a project, resolving a client issue or working with a new system, so you can draw on relevant experience.
- For each example, note your specific contribution, the people or tools involved and a concrete outcome, such as a completed deadline or process improvement.
- Prepare two or three questions to ask an interviewer about priorities, team processes or the next stage; tailor them to details in the posting and employer information.
- Confirm whether the meeting is in person, by phone or video, and check the date, start time, expected duration and time zone in the invitation.
- For an in-person meeting, verify the street address, building entrance, transit or parking options, and plan to arrive about 10 minutes early.
- For a phone or video meeting, check the listed number or platform, test your microphone and camera, and choose a quiet spot with a charged device.
Do a final readiness check the day before: keep the invitation, role notes and questions together, and confirm any access instructions or contact details. For online meetings, test the connection from the same device and location you plan to use.
Common Interview Question Types
Interview questions often focus on your work history, reasons for applying, or judgement in a particular situation. Their wording can vary, even when employers are assessing similar points, such as how your experience relates to the role. Some prompts ask what you would do in a hypothetical scenario; others ask what you did in the past. Recognising the difference helps you identify what kind of information each question is seeking.
Experience and motivation
Questions about experience may focus on duties you have handled, skills you have used, or results relevant to the position. An interviewer could ask how your previous customer-service work prepared you to manage a busy service desk, or which part of a project you were responsible for. These prompts help clarify the scope of your contribution, the level of responsibility you have held, and whether your skills match the work described in the posting.
Motivation questions ask why you applied and what interests you about the work. An employer might ask what drew you to a particular role, which responsibilities you find engaging, or how the position relates to your career direction. The aim may be to assess your priorities and whether your expectations are compatible with the role’s day-to-day duties, rather than to hear a prescribed phrase. Questions about what you value in a workplace can also reveal how you communicate your preferences.
Some interviewers combine these areas, asking you to connect a specific skill from your background with an aspect of the job. Others may ask about a career transition or a change in responsibilities to clarify how your experience developed. The balance between qualifications, motivation, and work history depends on the position: a technical role may emphasize hands-on tools or systems, while a supervisory role may focus on team responsibilities. Common interview questions and answers are therefore useful to consider as categories, not as a fixed script that applies to every interview.
Situational and behavioural prompts
Situational prompts describe a possible work challenge and ask how you would respond. Behavioural questions ask about an event that has already happened and the actions you took. The comparison below shows how the two formats differ in the information they may help an interviewer assess.
| Aspect | Situational prompt | Behavioural question |
|---|---|---|
| Time frame | A future or hypothetical workplace event | A specific past event from work, study, or volunteering |
| Evidence requested | Your proposed steps, priorities, and judgement | Your actual actions, decisions, and contribution |
| Possible purpose | To assess how you might handle a task, conflict, or changing priority | To clarify how you handled a comparable challenge and what role you played |
| Response focus | A plausible course of action and the reasoning behind it | The sequence of events and your part in the outcome |
A situational example might describe two urgent requests arriving at once and ask how you would decide what to address first. A behavioural prompt might ask about a time you had to manage competing deadlines. The first asks for your stated judgement in a proposed scenario; the second gives the interviewer details about past conduct and the circumstances in which it occurred.
Employers may use these prompts to clarify problem-solving, communication, adaptability, or how you work with colleagues. The same topic can appear in either format: a conflict with a teammate could be framed as a hypothetical or as a request to describe a past event. Your response approach should reflect the wording and time frame of the prompt. Neither format predicts a guaranteed answer or outcome; question choices and the information sought vary by role and interview.
Shape Clear, Truthful Answers
Strong interview answers connect a specific example to the skill or judgement the question is testing. A clear structure helps you give enough context without letting background details crowd out your contribution. Use facts you can explain honestly, including what you did, what others did and what happened afterward. The aim is not a polished performance; it is a credible answer that makes your evidence easy to follow.
Give context and evidence
Start by setting out the situation in one or two sentences: name the task, constraint or problem, then explain your responsibility. A hiring manager does not need the entire history of a project; they need enough detail to show why your actions mattered. For example, identify whether you were coordinating a handoff, resolving a client issue or completing a technical task, and clarify your role rather than implying you led work that belonged to the whole team.
Describe your actions with specific verbs and a clear sequence. Explain what you decided, communicated or produced, and why that response fit the circumstances. If colleagues contributed, distinguish their work from yours: “I analysed the file and recommended a change; my supervisor approved it, and the team updated the process.” This is more credible than claiming sole responsibility for a shared result. Using the STAR method in interviews can help you keep situation, task, action and result in order, but the framework should support a natural account rather than become a formula you recite.
State the outcome when you know it, using a verified measure if one is available; otherwise describe a concrete, observable result without estimating. For instance, a hypothetical answer about a customer handoff could explain that you clarified ownership and that the next shift received the required notes, if that is what actually happened. If the result was mixed or is not known, say so and describe what your action changed. A concise evidence-based example moves from context and responsibility to your own actions, then to the known outcome.
Keep the response focused
A focused answer addresses the wording of the question, then supports its main point with one relevant example. If asked how you handled competing deadlines, choose an instance that shows how you assessed priorities and communicated a change; an unrelated success story may be impressive but will not answer the prompt. Select details that help the interviewer assess your judgement, contribution or result, and leave out background that does not affect those points.
Memorized scripts can sound stiff when the question differs from the one you expected, while unsupported claims such as “I am an excellent communicator” give the listener little evidence to assess. Prepare flexible examples and recall the key facts rather than memorizing full sentences. A useful sequence is a brief context, your responsibility, two or three actions, and the outcome. Keep dates, tools or constraints only when they make the example clearer; do not add technical detail simply to make an answer sound more impressive.
After making your point, stop. Repeating the same result in different words can blur the evidence and make a concise example feel unfocused. Before answering, identify the prompt’s central request; while speaking, keep each detail connected to it. At the end, check whether you have answered that request and supplied a specific fact or action to support your claim. If both are clear, finish rather than adding a second example or an unrelated qualification.
After the Conversation
The interview may be over, but the details can still help you evaluate the role and prepare for any later discussion. A brief record made soon after the meeting is more useful than relying on memory days later. You can also send a concise, professional note when it fits the employer’s process. Keep your reflection factual and your follow-up courteous; neither needs to be lengthy.
Reflecting on the discussion
Once you have left the interview, capture a short record before the details blur; a few minutes in your calendar or notes app is enough. Separate what you heard from your interpretation.
- Questions asked: Record the wording or main point, especially a prompt that surprised you, so you can see which parts of your experience the interviewer asked about.
- Examples used: Note the project, challenge, or result you described, including any figures, to keep details consistent if another conversation revisits it.
- Role details clarified: Write down specific information about responsibilities, reporting relationships, or priorities that the interviewer explained.
- Unresolved points: List what remains unclear, such as a duty or requirement you could not fully discuss during the meeting.
- Stated next steps: Record any process details the employer gave, using their wording rather than assuming a date or decision.
- Your observations: Note which parts of the conversation increased or reduced your interest, and connect each impression to something actually discussed.
These notes give you a factual basis for considering whether the role matches your priorities and for responding consistently in a later conversation. A useful review practice is to reread them once, mark one strong point and one open question, and keep the record private and professional.
Appropriate follow-up
A brief follow-up can be appropriate when you want to thank the interviewer for their time, reinforce your interest, or clarify a relevant point that was left unresolved. A concise thank-you note after a job interview can refer to one specific topic you discussed, such as a responsibility or project, rather than restating your qualifications in full. If you need to correct or add a detail, keep it factual and explain it in a sentence or two.
Use the communication channel established during the process when practical, and address the person by the name and title they used. Keep the message courteous, check spelling, and make the purpose clear; a short paragraph is often enough. Avoid adding new questions simply to prompt a reply or sending repeated messages when you have not received one. If the employer stated when or how they would be in touch, take that guidance into account. Otherwise, timing depends on the employer and its hiring process, so there is no universal interval that guarantees a response. A professional follow-up can express appreciation and maintain a respectful record of your interest, but it cannot guarantee an interview, an update, or a job offer.