Your goal: design a retrieval system you could defend: what is stored, how it is found and
ranked, how it stays fresh, how you would know it works, and what you would give up.
How this works (about 30 minutes)
- Felix asks which role you are interviewing for (product, engineering or other), then one
design question, and goes deep. Ask him about the catalogue, the shoppers and the assistant;
he hands over what he has, one line at a time. The details are made up for the exercise.
- Follow-ups, one curveball, then a trade-off turn: relevance up, but something else gets
worse. Ship, hold or change?
- If you want to sketch the system or jot, say "can I use the notepad?"
- No hints and no scores during the call. Your report comes after.
What scores well
- Questions about the shoppers, the catalogue and the assistant before any design
- A plain one-line account of what the search does and why meaning helps
- Reasoned choices: what to embed, what to filter, hybrid search, how many results, rerank
- A failure named before you are asked, and a fix
- A way to test retrieval on its own, with a bar set in advance
- A call when the numbers disagree, with a line that would reverse it
Tips
- Take Gen AI Coach · RAG first.
- Ask Felix what data he has for testing.