A useful interview checklist turns vague preparation into a set of finished tasks: evidence collected, answers practiced, questions selected, and logistics confirmed. This guide walks through those tasks in order, with a worked example you can adapt to your role and available time.
How Should You Prepare for a Job Interview?
Confirm the interview format, map the job requirements to genuine examples, practice representative tasks aloud, and check the practical arrangements. Build a short evidence bank rather than memorizing a script. Before the meeting, make sure you can explain your contribution, ask informed questions, and access the interview without avoidable technical or travel problems.
Start with a one-page interview brief
1. Confirm what will happen
Why: An invitation may not explain the whole assessment. Preparing for an informal conversation will not cover a presentation or supervised task.
How: Record the date, time zone, duration, interviewer names if supplied, format, and contact for problems. Ask whether there is a presentation, case, coding exercise, portfolio discussion, or advance reading. Confirm which tools and reference materials are permitted.
Amazon's How We Hire page separates assessments, phone screening, interview loops, and role-specific resources. This illustrates why candidates should verify their own process instead of relying on another applicant's experience.
2. Extract the important requirements
Why: A long job description can distract you with details that are not central to the role.
How: Highlight the responsibilities, required skills, and expected outcomes. Group overlapping requirements into a few themes, such as analysis, customer communication, delivery, or leadership. Keep essential qualifications separate from preferred ones and note any requirement you need clarified.
Create a brief with three columns: requirement, evidence, and gap. Where you lack direct experience, identify an honest adjacent example or a question to ask. Do not turn exposure into expertise merely to fill every cell.
Build an evidence bank, not a script
3. Select examples you can defend
Why: Specific evidence supports an answer better than broad claims such as “I work well under pressure.”
How: Choose examples covering achievement, collaboration, disagreement, a setback, and learning. The same project can support different questions, but avoid using it for every answer. Include employment, study, volunteer, or personal projects where relevant, and describe their context accurately.
For each example, write brief notes using Situation, Task, Action, and Result. This STAR structure is an organizing aid, not a rule about equal time for each part. Keep the background short enough that your decisions and actions remain visible.
| Evidence field | What to write | What to check |
|---|---|---|
| Situation | The setting and relevant constraint | Can a listener understand it without insider knowledge? |
| Task | Your responsibility or goal | Is it separate from the team's overall goal? |
| Action | Decisions and steps you personally took | Can you explain why you chose them? |
| Result | Outcome and supporting evidence | Is the claim accurate and attributable? |
| Reflection | What you learned or would change | Does it show judgment rather than hindsight perfection? |
4. Check the accuracy of every claim
Why: Follow-up questions can expose vague ownership or unreliable numbers.
How: Separate team results from your contribution. Use metrics only when you know what they measured and can discuss them without breaching confidentiality. If a result was qualitative, explain the observable change instead of inventing a percentage.
Prepare a safe version of confidential examples. Remove client names and sensitive figures, and explain that certain details cannot be shared. An honest boundary is preferable to disclosing protected information or fabricating a substitute result.
Research enough to ask useful questions
5. Learn what the organization actually does
Why: Research should improve the relevance of your answers, not create a recitation of company facts.
How: Start with official product pages, the job description, and published company updates. For a public company, an annual report can explain priorities and risks, but distinguish company-wide statements from assumptions about the specific team.
Write a short summary of the customer, product or service, and problem the role appears to address. Label uncertain points as questions. For example: “The posting mentions reducing onboarding delays; which part of that process would this role own?” is stronger than claiming to know an internal problem from an external announcement.
6. Prepare questions that affect your decision
Why: The interview is also an opportunity to evaluate the role.
How: Ask about expected outcomes, team interfaces, feedback, and constraints. Prepare more questions than you expect to use because some will be answered during the conversation. Avoid asking only questions already answered clearly in the job posting.
Useful questions include: “What would good progress look like in the first few months?” and “Where do handoffs most often become difficult?” Ask the recruiter about process details and direct role-specific questions to someone positioned to answer them.
Rehearse the work and the conversation
7. Practice a representative task aloud
Why: Knowing a concept privately is different from applying it while another person asks questions.
How: Use a fresh task that resembles the expected format. For technical work, clarify inputs, explain an approach, check edge cases, and discuss limitations. For a business problem, define the decision, identify missing evidence, compare options, and make a qualified recommendation.
Do not assume every interview rewards constant narration. Explain the important reasoning and ask for a moment to think when needed. The aim is to make your decisions understandable, not to fill every pause.
8. Run one focused mock and revise
Why: Feedback is useful only if it produces a concrete change.
How: Ask a partner to interrupt with follow-up questions. Review whether you answered the question, supported your claims, and stayed understandable. Select a small number of changes, then repeat with a different prompt. If working alone, record yourself and check for missing context or unexplained jargon.
Keep a short correction log. Replace “be better at cases” with “state the objective before calculating” or “separate facts from assumptions.” This makes the next practice session specific and prevents endless, unfocused rehearsal.
Worked example: turning a job posting into a plan
Consider a hypothetical candidate interviewing for an operations analyst role. The posting emphasizes spreadsheets, stakeholder communication, and process improvement. The candidate has a hypothetical four evenings available; these timings illustrate sequencing, not a universal schedule.
On the first evening, they confirm that the interview includes a spreadsheet discussion and a behavioral conversation. They map the three job requirements to a student project, a part-time work example, and a volunteer scheduling task. They mark one gap: explaining why they chose a particular metric.
On the second evening, they prepare concise evidence notes. For the scheduling example, they describe the recurring problem, their own changes, and the documented outcome. They do not invent a financial saving because they did not measure one.
On the third evening, a peer asks them to interpret an unfamiliar table. The candidate initially calculates before clarifying the question. Their correction is to identify the decision first, check definitions, and then choose a calculation.
On the final evening, they repeat that task with a new table, review employer instructions, and test the meeting setup. Their output is a brief, a small evidence bank, a correction log, and informed questions—not a folder of memorized answers.
Close the logistics loop and follow through
9. Check access, timing, and materials
Why: Preventable friction can consume attention you need for the conversation.
How: For a remote interview, test the required application, camera, microphone, headphones, and connection. Check screen-sharing permissions and close private tabs and notifications. Google's virtual interview tips are an example of official employer guidance; follow the instructions supplied for your own interview.
For an in-person meeting, confirm the address, entrance, travel plan, and any identification requirements. Keep the recruiter's contact accessible. Ask early about accessibility adjustments or alternative arrangements, rather than relying on a last-minute workaround.
10. Prepare a short post-interview record
Why: Your impressions fade, and later rounds may revisit the same topics.
How: Afterward, note what you learned, questions still open, and any promised follow-up. If you send a thank-you message, keep it brief and accurate. Send requested material through the agreed channel, and respect the expected decision timeline before checking in.
Questions About Job Interview Preparation
What if I only have one evening to prepare?
Prioritize the confirmed format, the main job requirements, a few defensible examples, and logistics. Complete one short practice task rather than attempting an entire course. Focus on relevance and avoid staying up so late that preparation undermines readiness.
Can I bring notes into the interview?
Ask what is permitted. A short list of questions may be acceptable in a conversation, while notes or outside tools may be restricted during an assessment. Never assume permission because a meeting is remote.
How should I discuss a result that cannot be measured precisely?
Describe what changed and how you know. An approved process, a resolved complaint, or a completed handoff can be meaningful without a percentage. Make clear when an observation is qualitative rather than a measured improvement.
What should I do if the connection fails?
Use the contact and backup plan agreed beforehand. Rejoin if possible and communicate promptly through the specified channel. Avoid improvising an unapproved recording or sharing sensitive materials through a personal account.
Prepare Examples and Practice Clearly
Preparation is complete when you have relevant evidence, have practiced explaining it, and know how the interview will run. A short checklist that you actually finish is more useful than exhaustive research you cannot apply.
Next steps: Understand the main interview formats, choose a suitable preparation method, or browse the Interview Preparation hub.
Sources
- Amazon Jobs — How We Hire
- Google Careers — Virtual interview tips
This guide is general education, not professional career advice.