layiq
worthy; deserving; fitting; suitable.
A role, opportunity, or path that merits attention, time, and pursuit.
Loading LAYIQ…AI interview series, Part 3See all 6 guides
Lead with your point, answer every part of the question, say what you personally did, use numbers you can explain and close with what you learned. Clear, specific evidence is the part you control, whether a person, software or both is judging the answer.
This is Part 3 of LAYIQ’s AI interview series: what to actually say. The complete guide covers the whole process, from invitation to follow-up.
A structured interview is scored more like an exam than a chat. The U.S. Office of Personnel Management’s training for federal structured interviews describes the method: job-related questions, asked the same way of every candidate, with every answer rated on the same scale against example answers written for each proficiency level.1
Some AI interview vendors describe rubric-based scoring. HireVue says its AI-scored video interviews turn speech into text and score it against behaviorally anchored rating scales, meaning scales that describe what an answer looks like at each level.2 BrightHire says responses to its AI interviewer are “evaluated using the same rubrics and criteria.”3 Those are the vendors’ own descriptions, as of October 2026.
In a rubric-based interview, whoever or whatever scores your answer is looking for evidence it can match to a level. Make it easy to find. Not every system works this way, so Part 1 shows how to find out what yours does.
Every strong answer in this guide follows five steps. Here they are in a constructed example:
These are the same five parts as each story in your evidence bank.
Lead with the headline. An interview is not a mystery novel, and nobody wants the twist saved for the last page. Once the listener knows what the story proves, every detail after it has somewhere to land.
The middle three steps are STAR (situation, task, action, result). OPM’s training uses it so that questions draw out the situation or task, what the candidate did and how it turned out,1 and Harvard’s career center teaches a situation, action, result version that includes the outcome or what you learned.6 DDI, a talent consultancy, says it introduced STAR in 1974; that is the company’s own account.7 The headline is our addition, and the action is the main course: MIT’s career office suggests, as a rough guide, giving it about 60% of the answer.5
Prompts often come in parts. “Tell me about a time a caller was upset, what you did and what you would do differently” is really three questions. Count the parts, then signpost each one as you answer.
Skips two parts
I always stay calm and put the customer first, because every complaint is a chance to build loyalty. In the end, he was happy.
Covers all three
The caller: a man whose pharmacy delivery had gone to an old address twice. What I did: I stayed on the line while the pharmacy booked a same-day courier, then fixed the address in both systems myself. What I’d do differently: confirm the delivery address at the start of every call, not only when something has gone wrong.
Constructed example. The first answer never says what went wrong or what would change, and those were two of the three questions.
Resist the urge to say less to a machine. In one small mock-interview study (124 people, mostly German students), those told a computer would score their recorded answers gave shorter answers than those told a person would rate them.8 A skipped part leaves nothing to score, and a one-way recording cannot ask you about it.
OPM’s training tells interviewers to narrow in on a candidate’s specific role and actions, and to ask for clarification when candidates say “we did…” or “our group…”.1 A recorded interview may have nobody to ask, so do it for them.
“We implemented a new process” hides you; “I proposed the operating model, and my team implemented it” doesn’t. Part 4 shows more before-and-afters.
Say “I” for your own decisions and actions, “we” for the team’s work, and credit other people honestly. Claiming the whole project is no better than hiding inside it.
Numbers give a reader scale: how many, how fast, compared with what. MIT’s guidance spends most of an answer on your actions and says it is important to highlight quantifiable results.5 But a number you cannot explain is a liability the moment a follow-up asks how you measured it.
Take this constructed example: “I cut weekly stock-count errors from about 30 items to fewer than 10 in two months, going by the count sheets we already kept.” “About” and “fewer than” are honest approximations, and the count sheets say where the number came from.
A result shows that something went well. Judgment shows why it would go well again, so say the trade-off out loud instead of leaving the reader to guess. Four kinds of sentence do most of the work:
OPM’s structured-interview training lists related probes for hypothetical questions, including “What factors would affect your course of action?” and “What other actions could you take?”1
Some AI interviewers ask follow-ups. Talview advertises real-time follow-ups in its Ivy interviewer,4 and BrightHire says its AI interviewer generates custom questions and follow-ups, and that recruiters approve questions before they are asked.3 Those are vendor claims as of October 2026, and employers set these tools up differently.
Follow-ups differ by system, but you can rehearse for common ones. OPM’s standard probes for past-behavior questions make a useful practice checklist: Who was involved? What was your role? What was the outcome? Is there anything you would have done differently?1
Add something new rather than replaying your first answer louder. A good rehearsal is someone, or a chatbot, asking “why?” after every answer; Part 2 covers rehearsal step by step.
OPM’s training describes two core types: behavioral questions about what you actually did, and situational questions that pose a realistic job scenario, such as an angry client who says an overdue check never arrived, and ask what you would do.1 Many interviews add a few familiar others.
| Type | Sounds like | How to approach it |
|---|---|---|
| Behavioral | “Tell me about a time you…” | One real story in the five-step shape, with a result. |
| Situational | “What would you do if…” | Your first step, the factors you would weigh and the options. Add a real example if you have one. |
| Mistake | “Tell me about a time you got it wrong…” | A real, moderate mistake, what you did about it and what you do differently now. |
| Motivation | “Why this role?” | Two specifics from the posting, each tied to evidence from your work. |
| Opener | “Tell me about yourself.” | Keep it brief: what you do now, one or two proof points, why this role. |
| Technical | “How would you…” | Answer first, then your reasoning. State assumptions and define terms. |
You usually cannot know how a given interview scores “tell me about yourself”, so don’t treat it as a throwaway warm-up. For “why this role”, start from what the posting stresses most. If you have a LAYIQ account, Fit Analysis compares what a posting states with the evidence in your résumé, which is the same pairing this answer needs.
The answer shape stays the same in every format; how it lands changes. Time limits vary: in one-way video interviews, Harvard’s career center gives three minutes as an example limit per response,6 and HireVue says employers can set anything from 30 seconds to 15 minutes, or no limit, as of October 2026.2 For most stories, rehearse to land in about one to two minutes, with room to spare under whatever limit your invitation states.
Blaise Pascal, not Mark Twain, wrote in his Provincial Letters (1656–57) that his letter was long only because he hadn’t had time to make it shorter.11 Short answers take rehearsal, not luck.
Not sure what your system evaluates? Part 2 has a short script for asking. If a time limit or format is a barrier because of a disability, you can ask for an accommodation, such as more time or a different format; Part 2 has wording for that too.
Content comes first, and what the camera adds varies by system. HireVue says its AI-scored video interviews rely only on what candidates say, not on facial expressions, body language, background or tone of voice.2 Talview advertises that its Ivy interviewer uses visual cues to guide the conversation and to assess.4 Both are vendor statements as of October 2026, so ask rather than guess.
If a person interviews you while software records or takes notes, talk to the person. If an extra named participant joins the call, it is fine to ask what it records; Part 1 explains this set-up.
These are constructed examples, not transcripts from a real interview or vendor. Each shows a different format and a follow-up. Borrow the structure, not the story.
AI interviewer:Tell me about a time you had several high-priority commitments and couldn’t deliver all of them on the original schedule.
You:I protected the two riskiest customer commitments and moved the third by nine days, with that customer’s agreement.
You:All three were due in the same two weeks, just after an incident pulled about 30% of our engineering capacity away. I ranked them by contract impact, customer risk and engineering dependencies, proposed the plan with an interim workaround for the third customer, and handled the escalation with sales myself.
You:The result: the two highest-risk commitments shipped on time, and the delayed customer accepted the new plan without escalating.
AI interviewer:How did you decide which customer to delay?
You:Not by account size. I compared contract requirements, operational impact, how reversible a delay would be and whether a workaround existed. The customer we delayed had the lowest exposure and the only workable stopgap, so the decision held up even though they weren’t our smallest account.
AI interviewer:What would you change next time?
You:I’d raise the capacity problem earlier. Our planning let each commitment look feasible on its own.
Why it works: headline first, then context, the candidate’s own actions (“I ranked”, “I handled”) and a result. The follow-ups get decision criteria and a specific lesson, not a replay of the first answer. In a text box, short paragraphs let a reader find each part at a glance.
AI interviewer:Describe an important decision you made without all the data you wanted.
You:Short version: I paused a rollout before we knew the cause, which cost about a day and limited how many customers were exposed. Error rates had gone up, and our monitoring couldn’t tell a product defect from an integration problem. I paused the expansion, kept existing traffic running and put two teams on it in parallel, one reproducing the issue and one reading account-level logs. It was a configuration interaction, not a platform-wide defect, and we resumed with a new validation check.
AI interviewer:What evidence made you comfortable restarting?
You:Three things. First, we reproduced the failure under one configuration. Second, the fix eliminated it in the same test. Third, a small staged group ran cleanly before we reopened wider traffic. I didn’t treat a lack of new incidents, on its own, as proof.
Why it works: signposts like “Short version” and “Three things. First…” help a listener who cannot scroll back. The last sentence shows judgment about what counted as enough evidence, and what did not.
AI interviewer:Tell me about a time you had to influence a senior stakeholder who initially disagreed with you.
You:I persuaded our head of sales to launch in stages. They wanted to ship a feature before we had finished security controls that two enterprise customers required. Rather than argue that security should automatically win, I laid out three business options: launch to everyone and accept the contract risk, delay everything, or launch to the customers the controls didn’t affect while we finished. I recommended the third and got security and sales into one decision meeting. We launched to roughly 70% of the planned segment on schedule, finished the controls three weeks later and didn’t have to reopen either contract.
AI interviewer:What was their main objection to your recommendation?
You:That a staged launch would confuse sales and weaken the announcement. I changed the launch message and gave sales one clear eligibility rule, so nobody had to explain security exceptions customer by customer.
Why it works: the disagreement is framed in the stakeholder’s terms, the options are real and the candidate’s role is plain. What a camera adds varies by system, but the content of your answer is the part you can prepare, so skip the performance and look like yourself on a good day.
Using the posting’s words where they truthfully describe your work is fine. Repeating them instead of evidence is not. A skill name is the label on the jar; the interviewer wants to see what is inside.
Keyword-stuffed
I’m customer-focused, with strong attention to detail and a customer-first mindset, and my attention to detail puts the customer first.
Evidence
Regulars kept getting the wrong order during the Saturday rush, so I started reading each order back at the counter. Remakes fell from about a dozen a day to two or three.
Constructed example. The second answer never says “customer-focused”. It shows it.
In OPM’s structured-interview training, raters compare your answer with example answers written for each level,1 and a phrase repeated three times gives them nothing new to compare. Use the posting’s words once, inside a real example, and let the example do the work. Part 4 covers the other shortcuts that backfire in AI interviews, and what to do instead.
If you remember one thing, make it this: say the point first, then prove it with what you did. Once you’re done, Part 5 explains where your answers go and how to follow up.
Get the free, printable AI interview checklist by email, from the invitation to the follow-up.
Email me the checklistStart with a one-sentence headline, give brief context, spend most of the answer on what you personally did, then give the result and what you learned. Answer every part of the question.
It can help, as a way to make sure an answer is complete. OPM’s structured-interview training uses STAR to shape questions and MIT’s career office recommends it for answers, though neither source is about AI interviews and systems differ in how they score.15 The shape in this guide adds a headline at the start and a lesson at the end.
Long enough to cover every part of the question with evidence, and no longer; for most stories, aim for about one to two minutes. Limits vary: as of October 2026, HireVue says employers can set answer times from 30 seconds to 15 minutes, or no limit,2 so check your invitation and finish with time to spare.
Keep it brief: what you do now, one or two proof points and why this role. You usually can’t know whether a given interview scores the opener, so prepare it like any other answer.
Advice conflicts: HireVue’s tips say not to worry about eye contact with the camera,10 while Georgia’s career center says to look at the camera, not at yourself.9 Follow your invitation if it says anything; otherwise raise the camera to eye level and be natural.
Say what you know, what you don’t and how you would find out. An honest gap beats invented detail, which is hard to defend if the next question probes it.
Stop, say your headline again in one sentence and go straight to the result. A short pause is fine. If retakes are allowed, check how many before using one.