The job posting tells you which STAR interview questions to prepare

Your interview is days away and you have a long list of STAR interview questions to rehearse. Expect a tool you used, something others relied on, and a colleague who disagreed with you.

Read the posting, predict the four or five questions it will produce, and prepare one true story for each.

Employers who interview well ask every candidate the same questions, each tied to a skill

An employer who runs a structured interview starts from the job. They pick the few skills the work needs and write one question for each, asking for a real past example: "Tell me about a time you..."

Every candidate gets the same questions, and each answer is scored against the skill its question was written for.

Employers have a reason to work this way. A 2023 peer-reviewed review of hiring research found that the hiring method with the most support behind it is the structured interview, though how well it predicts job performance ranges widely across employers.

One experiment points to what consistency can do. In a field experiment in the Philippines, reported in a 2026 working paper, about 70,000 call-centre applicants were interviewed by an AI voice agent or a human recruiter. Those interviewed by the AI agent received offers 12% more often, which the authors credit to more consistent, structured interviews.

Both studies measured how well structured interviews work. Neither counted how many employers use them, so take this as the kind of interview to prepare for.

The questions come from the job, so the posting is your list of questions

If each question is tied to a skill the job needs, the place those skills are written down is the posting you applied to.

Public guidance already ties the answer to the posting. 2025 guidance from the UK National Careers Service and Civil Service says STAR stands for Situation, Task, Action, Result, and that answers should map to the skills in the job description.

TeaKo's view goes one step further: each posting line points to a question you can prepare. No study shows that interview questions can be predicted from the posting, so this is how we see it.

Take a data analyst a few years into the job, with an interview for a Data Analyst role. They copied a long generic list and polished one answer to "Tell me about a challenge you faced", about a busy month-end close. The posting says four things:

• "Required: strong SQL."
• "Build and maintain dashboards in Power BI."
• "Partner with Finance and Operations to define metrics."
• "Explain findings to non-technical stakeholders."

Each posting line points to a question you can prepare. The SQL line becomes "Walk me through a time you used SQL to answer a real question", and the month-end answer now has a place, under the line about explaining findings.

Prepare first the skills the posting labels required or repeats

A posting lists more than one interview can ask about, so you need a way to choose four or five.

TeaKo's view is that a posting is read for what it labels required, what it repeats, and what matches the title and the daily duties. In the example, SQL is the one line labelled required, so its question is prepared first.

Start from your own posting. A 2018 study of US professional job postings found that the same occupation asks for different skills at different firms.

What the role asks for across employers helps you order the rest. SQL is the tool data analyst postings name most. On 12 November 2026, on the employer career sites TeaKo reads in the US and Canada, more than 1,400 open Data Analyst jobs posted within 30 days listed skills. Of these, 69 in 100 named SQL, 46 in 100 Python, 42 in 100 Power BI and 40 in 100 Tableau.

These shares say how often the role's postings name a tool. They rank what to prepare first, and they never replace your own posting: what it asks for is read from its own lines.

One of your stories should show how you work with others

The predicted questions are mostly about tasks. The interviewer is judging more than tasks.

A 2025 meta-analysis of 37 studies found interviews predict both task performance and how well someone supports the team, so interviewers are judging both even when they ask about tasks.

That study measured what interviews predict. It says nothing about how to answer, so the advice is TeaKo's view: keep one of your four or five stories for work you did with another person.

In the example that is the fifth question, the one no posting line asks for: "Tell me about a time you helped a colleague get unstuck."

One resume line already holds half an answer, so build each story from one

You now have four or five questions and need one true story for each, fast. The material is already written down.

MIT and Yale career offices, in 2025 guidance, tell students to write resume bullets as action, project and result in one or two lines.

TeaKo's view is that one resume line already holds half an answer. The line starts the action and the result. You add the situation and the task.

The analyst's line reads "Built a Power BI dashboard that Finance used to track weekly churn", and it answers the dashboard question. What they add is the situation, that Finance had no shared view of churn, and the task, to build one. The line starts the action; they fill in that they met the Finance lead to agree one definition when the teams' numbers disagreed.

Keep each story to what really happened. A follow-up question is easier to answer when every detail is one you lived.

The questions to prepare, grouped by what each one tests

Each question is shown with the kind of posting line that points to it.

About a task:

• A tool the posting names: "Walk me through a time you used SQL to answer a real question." Put your posting's tool in place of SQL.
• Something the posting asks you to build or maintain: "Tell me about something you built that others relied on."
• A line about explaining work to non-technical people: "Tell me about a time you used data to change a decision."
• A tool the posting names and you have not used: "Tell me about a time you had to learn a new tool fast." In a 2019 Robert Half survey of more than 300 US HR managers, 84% said they would hire and train someone who lacks a required skill. That is what managers said they would do, and it is from 2019.

About working with others:

• "Tell me about a time a colleague disagreed with you."
• "Tell me about a time you helped someone else succeed."

Five steps turn one posting into four or five stories

1. Open the posting and mark every line that is labelled required, is repeated, or matches the title.
2. Rewrite three or four of those lines as the question each would produce.
3. Add one question about working with others.
4. For each question, pick one resume line and turn it into a story: situation, task, action, result. TeaKo's STAR coach does this step with you, one question at a time, from the line you pick.
5. Say each story aloud once. For how to shape the answer itself, see how to use the STAR method.

A long list is written for every job at once. Your interview is for one job: its posting names the skills, and your resume already holds the start of each story.