AI and LLMs Interview Questions and Answers
How LLMs work and how to build and test features on them: tokens, context and temperature, hallucinations, prompting, embeddings and RAG, tool use, agents and MCP, structured output, evals and LLM-as-a-judge, prompt injection and the OWASP LLM Top 10, cost, latency and AI regulation.
225 questions for AI and LLMs interviews with answers and explanations - Junior, Middle and Senior levels. Sample questions, online quizzes and coding tasks.
- LLM
- RAG
- Agents
- Evals
- Prompt injection
Questions by level
Junior
Core concepts and syntax · 50 questions
Middle
Practice, nuances and optimization · 50 questions
Senior
Architecture, internals, edge cases · 50 questions
Sample questions
A few questions from each level with the correct answer and an explanation.
AI and LLMs · Junior
- What does a large language model (LLM) fundamentally do?
Show the answer
Correct answer: Predicts the next token based on the text so far
An LLM is trained to continue text one token at a time. Useful behaviour like answering questions comes from that prediction plus training on instructions, not from a fact database.
- What is a token in the context of LLMs?
Show the answer
Correct answer: A chunk of text, often part of a word, that the model processes
Text is split into tokens by a tokenizer. In English one token is roughly three quarters of a word; other languages and code often need more tokens per word.
- Why does the same text in Ukrainian often use more tokens than in English?
Show the answer
Correct answer: Tokenizers favour English, so other languages split into more pieces
More tokens mean higher cost, slower responses and less room in the context window for the same content.
- What is the context window of a model?
Show the answer
Correct answer: The most tokens it can see at once, input plus output
Everything the model sees, such as the system prompt, history, documents and its answer, must fit in the window. Text beyond it is simply not visible to the model.
AI and LLMs · Middle
- What is "context engineering" in LLM apps?
Show the answer
Correct answer: Choosing what information goes into the context for each step
Beyond the prompt wording, results depend on which documents, history, tool results and instructions the model sees, and in what order.
- Why is chunk overlap often used when splitting documents for RAG?
Show the answer
Correct answer: So facts on chunk borders aren't cut in half
A sentence split between two chunks may never be retrieved whole. A small overlap keeps context together at the cost of some duplication.
- What is hybrid search in RAG?
Show the answer
Correct answer: Combining keyword search like BM25 with vector search
Vectors catch meaning; keywords catch exact terms like product codes and names. Combining them often improves retrieval.
- What does a reranker do in a retrieval pipeline?
Show the answer
Correct answer: Reorders retrieved candidates by relevance with a stronger model
A fast first stage fetches, say, 50 chunks; a cross-encoder reranker picks the best 5 for the prompt, improving precision.
AI and LLMs · Senior
- When is an LLM the wrong tool for a feature?
Show the answer
Correct answer: When rules or a simple model solve it reliably and cheaper
Deterministic logic, regex or a small classifier are faster, cheaper and testable. LLMs pay off for fuzzy language tasks where rules break down.
- What is eval-driven development for AI features?
Show the answer
Correct answer: Write evals with success criteria first, then iterate prompts against them
Like TDD: define what good looks like, measure the baseline and make each change prove it improves the score.
- How should success criteria for an AI feature be defined?
Show the answer
Correct answer: Specific, measurable and tied to the task, e.g. 95% accuracy
Vague goals can't be tested. Concrete targets for accuracy, latency, cost and safety guide trade-offs.
- What makes an eval dataset representative?
Show the answer
Correct answer: It mirrors real inputs, including hard, rare and adversarial cases
Sample from production (anonymized), add known failures and edge cases, and keep a held-out part you never tune against.
Coding tasks
Write your solution right in the browser, and tests check it instantly. JavaScript interview classics (debounce, deepClone, Promise.all, an LRU cache), TypeScript tasks on generics, narrowing and utility types checked by the real compiler, Node.js backend logic (middleware, rate limiters, job queues), SQL queries in real PostgreSQL, and React components and hooks like a todo list, tabs, useDebounce and useInterval.
Open tasks →