How to prepare for an interview for one specific job posting

Most interview advice is general: be on time, research the company, be yourself. It is not wrong, but it does not tell you what to do this evening with the posting you have open in another tab. The posting is the best clue you will get to what the employer cares about. The method below turns it into a plan you can finish in an evening or two.

1. 1

   Read the posting twice

   The first time, read it as a candidate: do you still want this job? The second time, read it as a detective. Underline the verbs (“own”, “coordinate”, “analyse”) and any word that appears more than once. Repetition is usually priority.

2. 2

   Sort requirements into themes

   Separate the must-haves from the nice-to-haves, then group them into four to six themes, for example “stakeholder communication”, “working with data”, “running a project”. A long list becomes a short, memorable one.

3. 3

   Match each theme to your evidence

   For every theme, find one real example from your work, studies or projects: what you did, what came of it. If you have none, write that down too. You will come back to it in step four.

4. 4

   Name the gaps, and decide what you will say

   Almost every candidate has one or two. Prepare an honest sentence for each: what you have not done, what is closest to it, and how you would get up to speed. A calm, specific answer about a gap often goes down better than a stretched claim.

5. 5

   Research the employer for a reason

   Do not collect facts for their own sake. Look for what the company makes, who pays for it, what they have announced recently and how the team you would join fits in. For each finding, write the question it raises for you or the connection to your experience.

6. 6

   Predict the questions

   For each theme, write one or two likely questions: a behavioural one (“tell me about a time…”), a practical one (“how would you approach…”) and the inevitable “why this role, why us?”. They do not have to be perfect, because the exercise is what prepares you.

7. 7

   Draft short answers, then say them out loud

   Write bullet points rather than paragraphs, with a story from step three behind each. Then practise speaking them; the next articles explain how to practise answers out loud and how to structure stories with STAR.

8. 8

   Prepare your own questions

   Pick three that this posting makes you curious about, and leave them in your notes. There is a list of ideas in questions worth asking the recruiter.

What a posting tells you between the lines

A posting is written by several people with different aims, and it shows. Some lines are the real work and some are decoration. A few habits help you read them:

• Order often signals priority. The first requirements are usually the ones the hiring manager wrote; the last ones are often added by HR or copied from a template.
• Tools are easier to learn than habits. A named tool matters less than a phrase such as “works independently with unclear requirements”, which describes how the job feels day to day.
• Wish lists are not checklists. If you meet most of the must-haves, it is normally worth applying. The rest is a conversation.
• Vague lines are questions for the interview. “Fast-paced environment” can mean anything. Ask what a typical week looks like.

A one-page prep sheet

End with something you can look at in the last ten minutes before the call, and nothing longer than one page. It might contain:

• The four to six themes, each with the story you would use for it, in three or four words.
• Your two honest answers about gaps.
• Two or three facts about the employer and what you would say about them.
• Your three questions.
• The practicalities: the time zone, the names of the people you will meet, the link, and who to contact if it does not work.

If you are applying to several roles at once, repeat the method for each. It gets quicker, because your stories and your gaps carry over, and only the emphasis changes.