
Guide 08 · 28 pages · 13 chapters
When You Don't Know the Answer
A playbook for answering questions outside your experience.
By PixioLab
Included in the full program and the guide library. See the 45-day roadmap.
What's inside
- 01
The real problem with “I don't know”
Saying you haven't used something rarely costs you the offer. What you say next decides it.
What a strong answer proves
- 02
The five-step answer
One structure for every gap. Learn it once, then practice it out loud until you no longer have to think about it.
One answer, start to finish · Each step, in detail · Keep it to 60–90 seconds, then hand it back · What changes with seniority
- 03
Triage: which situation are you in?
The five steps always apply. What you connect depends on the kind of gap.
How the steps flex
- 04
You haven't used their tool
The most common version. They name a tool on their stack, and you've used something next to it. Connect the two through the job they both do.
Worked example: an agent framework · Worked example: an eval library
- 05
You've never built that system
The whole product is new to you, but the engineering problems inside it probably aren't. Think about those instead.
A moment inside the round, not the whole round · The template · Worked example: ticket booking · Worked example: a multi-agent system
- 06
You don't recognize the term
You can't make a useful connection until you know what they're asking. So don't guess. Ask, restate it in your own words, then connect.
Worked example: a workflow engine · Worked example: a retrieval technique
- 07
You partly know it
The most common gap in AI interviews isn't a tool you've never heard of. It's a formula, a mechanism or a number you half remember.
The moves · Worked example: a formula · Worked example: a technique you know from reading · Worked example: a number
- 08
AI-specific unknowns
The AI stack changes faster than any other part of the job. The five steps stay the same, but AI gaps fall into a few patterns worth preparing in advance.
An inference stack · A training technique · A model you haven't used, and a paper you haven't read
- 09
No parallel, other rounds, and recovering
The same structure carries you through the harder moments: nothing close in your experience, a round that isn't about tools, or a mistake to repair.
When there's no parallel at all · Behavioral rounds: when you don't have that exact story · Coding rounds: when you're stuck · Correcting yourself, and the follow-up note · When the unknown is a hard requirement
- 10
Mistakes, phrases and drills
Weak gap answers fail in a handful of predictable ways. Here they are with the fix, then lines for every step, then the drills that make it all automatic.
Common mistakes · Phrase bank · Practice drills
- 11
Your story bank
You can't connect to experience you can't remember under pressure. Fill these worksheets in once, before your loop starts.
Step 1 · Write down 3–5 projects · Step 2 · Pull the unfamiliar tools from the job description · Step 3 · Map them by function · Step 4 · Match stories to behavioral prompts
- 12
One-page cheat sheet
- 13
Sources and further reading
The method is practical interview advice, not research. The technical claims inside the example scripts rest on these sources.
In this series · Papers referenced in the example scripts · Documentation