An interview is a chance to explain relevant experience and investigate whether a role fits. Prepare from the actual job description and your own records. A polished script cannot guarantee selection, and an impressive invented number is not a substitute for evidence.
Show the boundary between your work and the team's result
For a fictional requirement “check documentation for missing information,” a candidate's evidence is a checklist they created and three gaps they recorded. Their answer could be: “I compared the draft with the required sections, logged three omissions and sent the checklist to the editor. The editor revised the text; I then checked the three items again.”
This supports checking and documenting, not leading the project or increasing quality by 30%. A follow-up question such as “Which gap mattered most?” can be answered from the same record. If the candidate cannot describe an actual omission from their own experience, the invented story is not a script to adopt. Replace it with a truthful example, including an unresolved result when necessary.
Map the requirement to an example
For each important requirement, choose a situation you can accurately explain. Separate your own action from the team's work and state what result is supported. If a result was not measured, describe the completed deliverable or observation without manufacturing a percentage.
| Requirement | Situation and task | Your action | Supported result | Detail to clarify |
|---|---|---|---|---|
| From the actual role | Enough context to understand | Your contribution | Record or truthful observation | A gap, not an invented answer |
Speak an answer, then check it
Use situation, task, action and result as an optional organising structure, not fixed percentages of speaking time. UC Berkeley's preparation page emphasises practice and protecting personal information when using online resources. You can rehearse without purchasing a service or uploading a confidential record.
Constructed example: “I checked the draft against the requirements and documented the missing sections; the team then revised it.” That can be more accurate than claiming you led the project or cut delivery time when neither is supported. Check the facts against the version of your resume that was submitted.
Ask questions that reduce uncertainty
List what you need to learn about responsibilities, support, working arrangements and next steps. Do not assume a posting answers every question or that an interviewer can disclose all information. Keep a question unanswered when it is genuinely unresolved.
Check the practical arrangements
Confirm time zone, location or link, format, required material and any access needs through the actual invitation. Test permitted equipment if relevant. Do not share identity documents, bank details or credentials through an unverified recruiting message.
After practice or the interview, note one unclear answer and one question to follow up through an appropriate channel. The useful outcome is an accurate account you can deliver and a clearer understanding of the role, not a guaranteed offer.