One hundred questions. Eighty-two come straight out of the thirty days, two or three per day, tied to the exact thing you built that morning. Eighteen are bonus questions that go past the curriculum into cost, ops, incident response and career judgment, the kind that show up once you are past the take-home and inside the loop.
No answers are provided. Not on this page, not in the cohort, not on request.
That is the whole exercise. You build the thing in the morning, then you write down in your own words why it works. A question you can only answer by reading someone else's answer is a question you cannot answer.
Filter by Day and take that day's two or three questions after you commit your build. Write your answer in your own repo, in the day's README. Ten minutes, not thirty.
By Day 30 you will have a written answer bank in your own voice, sitting in a public repo, that you can reread the night before an interview. That artifact is worth more than the questions.
Topic groups questions across weeks. If an interview is coming up and you know it will be heavy on retrieval, filter to RAG, Hybrid Search and Chunking and run those twenty.
Format splits Technical, Behavioral and System Design. Behavioral questions are the ones people skip and then fumble. Do not skip them. Write the answer down.
Week is Bonus for the eighteen that sit outside the curriculum. Save those for Week 4, once you have enough built to answer them from experience rather than theory.
The thirty coding problems are separate and live on their own page.