Test yourself the way the loop will.
Pick a topic or take the whole spread, choose how hard and how long, and answer real multiple-choice scenarios drawn from what FDE interviews actually probe. Every answer comes back with the why, and with a link into the worked material that goes deeper. The questions rotate between takes, so a retake is a real re-measure, not a memory test.
What a test looks like
Two samples from the bank, answer and explanation included. Inside a test, the explanation appears after you commit to an answer, which is where the learning happens.
RAG & Agent System Design · easy · sampleA RAG answer is wrong. Before touching anything, which single question splits the failure into its two fundamentally different bug classes?Show the options and the answer →
If the right passage never came back, you have a retrieval bug: fix chunking, indexing, or the query, and no prompt work will help. If it came back and the model ignored or contradicted it, you have a generation bug with a completely different toolbox. One log lookup separates them, which is why seasoned people ask this before theorizing. Teams that skip it reflexively rewrite prompts to fix retrieval failures, the single most common wasted week in RAG debugging.
Behavioral & Customer Scenarios · easy · sampleYour demo breaks in front of the customer, mid-demo. What is the strongest move in the room?Show the options and the answer →
The panel is not grading the demo; it is grading you during the failure, because production will hand you worse moments in front of the same audience. Composure plus a prepared fallback signals operational maturity: you expected failure as a possibility and built for it, which is the exact quality customers want on-site. Live debugging holds the room hostage to your terminal; ending early wastes the executives you may not reassemble for a month; blaming the network is transparent and spends credibility. The tell interviewers listen for: 'my backup plan exists BEFORE the demo', not improvisation talent.
Eleven topics, three difficulties
Easy questions teach the vocabulary. Medium is applied judgment. Hard is where staff-level tradeoffs and 3am triage live. Every topic maps to a question journey and a concept track, so a weak score has an obvious next step.
Where practice tests fit
Before: find your gaps
The free readiness assessment diagnoses which of the 11 areas you have actually covered and builds a study plan from the misses.
Take the assessment →During: drill and measure
Practice tests are the reps. Learn mode explains every answer as you go; exam mode holds the reveal for the end. The score is a recall check, honestly framed: it measures what you can recognize under time, not whether you can run a discovery call.
After: go deep where you missed
Every explanation links the concept or worked question behind it: 606 full questions with worked answers, 157 concepts, three courses.
Browse the full questions →Common questions
- Are the practice tests free?
- Yes, with a free account: easy-difficulty tests up to 20 questions, on any topic, with full explanations after every question. Medium, hard and adaptive tests, and longer runs up to 100 questions, are part of premium.
- Do the questions repeat if I retake a test?
- The bank rotates: a retake deals questions you have not seen before, until you have genuinely exhausted the pool for that topic and difficulty. The bank currently holds 408 questions and grows.
- How is this different from the readiness assessment?
- The assessment diagnoses which of the 11 areas you have covered and builds a study plan. Practice tests are the drilling half: score yourself on a topic, learn from every explanation, and watch the score move as you study.
- What do the tests cover?
- The same 11 areas real FDE loops test: RAG and agents, LLM fundamentals, system design, SQL and data engineering, MLOps, ML infrastructure and GPUs, classical ML, ML product design, coding, AI security, and the customer-facing rounds.