Turn the job description into a requirement–evidence–gap grid. For each responsibility, write one real example, explain the connection and state what your example does not establish. This prepares you to discuss fit without copying the employer's language into achievements you never had.
RRC Polytech advises candidates to study the job description, identify core competencies and have examples of displaying the relevant behaviour.[74] The worksheet below is InterviewRep's editorial way of doing that work. It is not an employer rubric, an applicant-tracking-system score or a prediction of whether you will be hired.
Separate the requirement from your interpretation
Save the public posting and its date in your own preparation notes. Read any attached person specification or interview instructions. If you have different versions, identify which one the recruiter is discussing rather than silently combining them.
Copy a short requirement accurately, then describe the work it appears to involve. Keep those in separate columns. “Manage stakeholders” might involve customer communication, internal coordination or executive reporting; the phrase alone does not tell you which matters most in this role.
Look for scope as well as verbs. “Support a renewal” is not “own a renewal portfolio.” “Contribute to incident response” is not “lead the on-call programme.” Technical names, customer types, decision authority and required qualifications can change whether an example is direct or merely adjacent.
Treat repeated language as a clue worth investigating, not proof of interview weighting. If the role's priorities are unclear, prepare a question: “Which of these responsibilities needs the most attention in the first few months?”
Fill the requirement–evidence–gap grid
The worked rows below describe a fictional applicant considering a fictional customer-facing operations role. They are not claims about any real candidate or vacancy.
| Requirement as written | Interpretation to confirm | Real evidence to select | Honest connection | Gap or limit | Question or next step |
|---|---|---|---|---|---|
| [Exact short requirement] | [What you think it involves; update after clarification] | [Your actual event] | [Action that connects] | [Scope you have not demonstrated] | [Check a fact or clarify the work] |
| Coordinate cross-functional work | May involve handoffs between several teams | Organised a student event with facilities and volunteers — fictional | Agreed handoffs and tracked unresolved tasks | Not paid enterprise delivery experience | Ask how many teams and projects the role coordinates |
| Explain technical issues to customers | May mean external customer support rather than internal help | Explained a spreadsheet error to colleagues — fictional | Used a simple example to explain the cause | Colleagues were internal, not external customers | Prepare the example with that boundary stated |
| Use the named support platform | Which workflows and depth of hands-on use? | Used a different ticketing tool — fictional | Categorised issues and tracked ownership | No hands-on use of the named platform | Say so and ask which workflows matter |
| Own commercial renewals | May require commercial accountability and approval responsibility | No direct example — fictional | None established | Has not held renewal responsibility | Ask whether direct ownership is essential; do not invent it |
The last row is useful precisely because it stays blank on evidence. Preparation should reveal a material gap while there is still time to decide how to address it.
If you cannot find the event behind a claim, return to your interview story bank. If you have an event but cannot explain it clearly, expand it using the one-bullet STAR worksheet. Those are different tasks from mapping the role.
Classify evidence without pretending to calculate fit
Use three plain labels. Put the relevant label at the start of each row's Honest connection cell, before your explanation:
- Direct: you performed substantially the work described, and can explain the relevant scope.
- Adjacent: you performed related work, but a meaningful condition differs.
- Not demonstrated: you cannot support the requirement with your current experience.
These are preparation labels, not a numerical ranking. Do not add them up into a “match percentage.” A missing required credential cannot be offset by counting several unrelated soft skills, and only the employer can clarify its hiring requirements.
For an adjacent example, name both the connection and the boundary. “I have used a different ticketing system to manage issue ownership; I have not used your named platform” is more informative than “I am experienced in all major support tools.” It gives the interviewer something concrete to investigate.
A direct label also needs checking. Were you responsible for the whole project, one account, a workstream or a supporting task? If the role expects a scale you have not handled, record that instead of hiding it in a broad verb.
Turn one row into an answer
Use this editorial sentence frame: “You are looking for [requirement]. In [real setting], I [specific action]. The relevant result was [supported outcome]. The difference I would need to learn is [actual gap].” It is a preparation aid, not text you must deliver verbatim.
A fictional example:
“Your posting mentions coordinating handoffs. For a student event, I kept a shared list of facilities and volunteer tasks and followed up when an owner was missing. The event used the final agreed setup. That was a small volunteer project, not a commercial delivery programme, so I would want to understand your escalation process and project scale.”
The answer does not disguise the setting. It also avoids claiming the candidate caused the entire event's success. If the interviewer asks about a larger scale, the candidate can discuss the gap directly.
Yale's career guidance recommends tying your skills to the needs of the position, rather than giving a vague statement of interest.[50] Your connection sentence should make that relationship visible. It should not imply that an employer has already accepted the comparison.
Handle a requirement you do not meet
First, confirm what is actually required. Distinguish an explicit essential qualification from a preference, but do not downgrade a requirement because it is inconvenient. Where the posting or recruiter is unclear, ask.
If you lack direct experience, avoid switching tense or borrowing someone else's work. “I would approach it by…” describes a hypothetical plan. “I handled it by…” describes past experience. Make the difference audible.
You can offer related evidence and a realistic learning question without promising instant competence. For example: “I have not owned renewals. I have supported customer issue follow-up, and I can explain that work. Does this position require prior commercial ownership from the start?” The employer may still need experience you do not have. Honest preparation cannot remove that constraint.
Do not change a factual application answer to sound closer to the role. This grid is a discussion tool, not permission to claim a qualification, language proficiency, clearance or work authorisation you do not possess.
Use the grid to prepare questions, not only answers
A useful unanswered question belongs beside the relevant row. If “customer-facing” could mean scheduled account reviews or a high-volume support queue, ask about the working pattern. If the posting names a technology, ask how it is used rather than claiming experience with the label.
After the interview, update the interpretation column with what the employer actually said. Keep your original requirement and evidence intact. A new understanding of the role may change which example is most relevant; it should not change what happened in your past.
For team examples, the contribution worksheet helps separate shared outcomes from personal actions. That protects the evidence column from quietly becoming a list of everything the team achieved.
Common questions
Should I repeat the job description's keywords?
Use the employer's terms when they accurately describe your experience, then explain the work in plain language. Matching a word is not proof of matching the responsibility. No search, screening or ATS outcome is promised by this exercise.
Can an academic project count?
It can provide relevant evidence, but identify it as academic and state its scope. Do not present a class assignment as paid customer work or production experience.
What if most rows show gaps?
Check whether you misunderstood the role, then decide whether to clarify fit with the recruiter or focus on a better-aligned opportunity. Do not manufacture coverage to make the table look complete.
Keep your facts ahead of any suggestion
The live assistance guide explains a separate, permission-dependent workflow. InterviewRep's public instructions describe user-requested suggestions as a starting point for your own words and warn that they can be inaccurate.[16] If permitted assistance is useful, try 10 free minutes; the public offer currently states no credit card is required.[16] A suggestion cannot turn adjacent experience into a qualification you have earned.
Method: public university and college guidance supports connecting experience to role requirements. The classification labels, fictional matrix and sentence frame are original editorial aids, not validated assessments or employer selection criteria.
Sources
- InterviewRep | Live interview help, in your own words
- The Behavioral Interview – Office of Career Strategy – Yale University
- Interview Preparation : RRC Polytech: Career Services
10 minutes for new accounts. No credit card required. Use only where assistance and capture are permitted. Check current plans and terms.