Culture

The Job Posting Is Your Question List: Match Every Line to Something You Did

Prep time is limited. Consider spending it here: match each requirement in the job posting to something you actually did, a story that still holds up after follow-up questions. Includes a practice worksheet and a labeled hypothetical example.

2026.10.15 · By dvdmaru · ~8 min read · 1,774 words
中文版

In a CNN story that WRAL republished on October 4, 2024, a job seeker walked out of her interview sure she had blown it: too nervous, not prepared enough. She was hired as a paralegal. By her account, her boss praised how well she communicated and her steady eye contact.

It’s one person’s story, and it shows one thing: how an interview feels from the inside can be very different from what the employer saw.

So where should limited prep time go? The UK government’s careers site, Get careers information and advice, says in its interview guide that a few nerves on the day are normal and that preparing helps you feel more confident. The effort pays off most here: take every requirement in the job posting and match it to something you personally did, something you can still explain after two follow-up questions like “Which part did you do yourself?” and “How do you know how it turned out?” That’s practical advice, not a measured result, and it doesn’t guarantee an offer.

Six steps follow. You can start each one today.

Use the job requirements to practice behavioral questions

Harvard’s career center (the Mignone Center for Career Success) guide to interviewing says many employers decide in advance which competencies a role needs, such as teamwork or communication, then design open questions around those competencies that ask for a specific past situation. The GOV.UK careers site’s STAR page notes that a job description lists the skills and qualities the employer wants. That makes the posting a well-grounded place to start guessing the questions.

Do this: paste the posting into a document and split it line by line. Under each line, write one sentence: “If the interviewer wanted one story to prove this line, how would they ask?” What you write is your own question list.

Here is a hypothetical posting to work with. The job is “event planning assistant,” and it asks for three things: coordinating many people’s schedules, handling unexpected problems around an event, and delivering on deadline. These questions are my own wording:

  1. Tell me about a time you had to fit many people’s schedules together. How did you settle on a plan?
  2. Tell me about a time something went wrong while preparing for or running an event. What did you do right then?
  3. Tell me about a time you delivered something by a deadline. How did you organize the work?

Match each requirement to something you did

The GOV.UK careers site breaks this kind of answer into four parts, STAR: Situation, Task, Action, Result (including what you learned). It says to keep examples short and be ready for follow-ups.

The worksheet below folds situation and task into one sentence in the “My action” column, as a shortcut for this exercise. It’s a practice tool I made up, not a universal employer scoring rubric.

Harvard also says that, unless the interviewer specifies otherwise, your examples can come from work, school, activities, or volunteering. So the hypothetical case below uses a club. Ann is an invented person, a university junior who helped run a club orientation. The person and events are made up, and there are no data behind them.

Job requirementMy actionResult or lessonLikely follow-up
Coordinate many people’s schedulesWith differing schedules, collected officers’ and speaker’s availability in a shared sheet and chose an overlapping evening.No rescheduling. Lesson: collect availability before proposing dates.Someone never replied. How did you confirm they had seen it?
Handle unexpected problems around an eventFound a replacement speaker after a cancellation and notified attendees of the topic change.The event went ahead. Lesson: prepare a backup list for future events.Why was there no backup at first? What would you do differently?
Deliver on deadline(No full example yet. See the section on having no matching experience.)

Fill in the “likely follow-up” column early. Writing those questions down is a way of guessing the interviewer’s second sentence in advance.

Do this: pick the requirement you feel surest about and fill in one whole row.

After “we,” explain what you personally did

A team story can start with what the team achieved, as long as your own part follows. Say Ann’s first practice answer goes like this:

Hypothetical answer: “For the orientation, everyone worked hard together, and in the end it went really smoothly.”

The friend practicing with her asks, “Which part did you do yourself?” Ann can’t say, because her answer has no action of hers in it.

Split the answer into two lines:

  • What the team did.
  • What I did, and why.

In the interview, lead with the second line. Ann’s revised answer is the first row of her sheet (hypothetical): she gathered everyone’s availability in one place, then found the evenings that overlapped.

Treat results the same way and claim only what you can explain. If the hypothetical result is “nobody had to reschedule,” say exactly that. Don’t dress it up as “greatly improved efficiency,” because the next question will be: how do you know? A result that fell short is fine to tell, with the weight on what you learned.

Do this: choose one story, turn each “we” sentence into an “I” sentence, and say it out loud. If you still can’t answer “why did you do it that way,” the story isn’t ready.

When you have no matching experience, leave the cell empty and plan one sentence

On Ann’s sheet, the “deliver on deadline” row is empty. She has no full example to put there.

Here is how I’d handle the empty cell:

  1. Say plainly that your experience here is limited.
  2. Describe the closest thing you have, such as a class paper with a due date, say where it differs from the requirement, and explain how you plan to build the rest.
  3. Don’t invent an experience to fill the cell. Once follow-ups start, the details won’t line up, and your other answers will come under suspicion too.

The empty row has one more use. It marks the question most likely to stall you, and it gives you material for the next step.

Your questions for them start with what you don’t know yet, pay and conditions included

The GOV.UK careers site suggests writing your questions down beforehand.

Start from the gaps on your sheet. Ann could ask (hypothetical):

  • Who usually decides the deadlines for this role?
  • If something goes wrong the day before an event, who makes the call?

Pay and working conditions belong on this list. You need them to decide whether to accept the job, so asking is reasonable. This article doesn’t set a fixed order for when to ask.

Before you leave the interview, ask about next steps and when you’ll hear back.

Do this: write three questions. One should come out of a gap on your sheet, one should be about a day on the job, and one should be about a condition you need confirmed before saying yes.

In a mock interview, ask your partner to do one thing: follow up

The GOV.UK careers site suggests practicing with someone you trust.

Give your practice partner one job: follow-up questions. Hand over the posting and your worksheet, and ask them to:

  1. Pick three rows and ask you in different wording. The same story might arrive as “handling the unexpected” or as “the last time a plan fell apart.”
  2. Follow up twice after each answer, for example “Which part did you do yourself?” and “How do you know how it turned out?”
  3. Afterward, tell you one thing: which sentence they didn’t understand. Asking only “how did I do?” may get you nothing but reassurance.

Do this: tonight, send the posting and your worksheet to a friend and book about half an hour.

By the end you hold two lists: what you’ve done, and what you don’t know yet

After these six steps you have two lists. One is things you’ve done, each with its follow-ups prepared. The other is things you don’t know yet, each turned into a question for them.

The nerves won’t vanish, and they don’t have to. With these two lists, even while you’re nervous, you know which story comes next.

The scope here is narrow: general job interviews and behavioral questions. Technical questions, portfolios, and written tests need their own prep. Nothing here guarantees an offer, either. Many people compete for one opening, and there are many reasons someone isn’t picked, so don’t read a rejection as proof you prepared too little.

If you have only one evening, spend all of it on three things: split the posting, match your stories, and get someone to follow up. Start with the row you’re surest of, and turn the empty row into a question for them.

FAQ

Should I try to stop being nervous before the interview?

You can put your time into content first: match each requirement in the posting to something you personally did. This is practical advice, and it doesn’t guarantee an offer.

What if I have no formal work experience?

Unless the interviewer specifies otherwise, school, club, and volunteer experience can count. What matters is what you did yourself and a result you can explain.

What if they ask about something I’ve never done?

Say plainly that your experience there is limited, describe the closest example, and explain how you plan to build the rest. Don’t invent an experience.

Can I ask about pay and working conditions?

Yes. You need that information to decide whether to accept the job. This article doesn’t set a fixed point in the interview for asking.

Sources and scope

These pages were read on October 15, 2026 (Taipei time). The CNN piece is a 2024 article, and this article uses only its opening case. The question lists, the worksheet, and Ann’s case are my own. The people and events are hypothetical and come from no source.