Learn

Architecture & pattern guides

Read the idea, build it on a Grid, prove it in a challenge. Short, practical guides — illustrated with RodGrid's own nodes — on system design, design patterns, flow modeling, and how to get the most out of the app.

All articles

Guided challenges: four stages, one check each

Walk a system-design Challenge the way an interview does, requirements before boxes, with an optional check at every stage.

Start guided or Start classic? Some Architecture Challenges carry a Guided badge, and their cards ask you to choose before the clock starts. Both give you the same Grid, the same timer and the same submit. Classic hands you the brief and an empty canvas. Guided prompts you to say what you are building before you draw it, which is what a system-design interview asks of you.

Six criteria, dealt into four stages

An Architecture Challenge is graded on six criteria, and guided splits them across the four stages of that interview. On URL Shortener, each stage opens with its own prompt and a pointer or two to think with, and its check grades only what that stage is about:

  1. Requirements is a typed answer: the functional requirements and a scale estimate, including the read/write ratio. Its check grades requirements coverage.
  2. API & Entities is a typed answer: the core entities and the key endpoints. Its check grades data flow.
  3. High-Level Design is on the Grid: the client, the API layer, the store and the redirect path. Its check grades component selection and architecture quality.
  4. Deep Dive is on the Grid: caching the hot read path and calling out bottlenecks. Its check grades scalability and trade-offs.

The order is the point. Forgetting the click analytics in the URL Shortener brief costs a sentence at the first stage. Discover it after submitting and it is already part of your grade. The timer keeps running through the typing, so URL Shortener's 20 minutes have to hold your answers as well as your Grid.

What a check tells you, and what it does not

Check this step (4 cr) spends 4 credits each time. It reads your typed answer on the first two stages and what you have drawn so far on the last two, and it does not look at the reference solution. It comes back Ready or Needs work, with a short summary and a To improve list of at most three items. On a Grid stage those items can name your nodes, and clicking a name takes you to the node.

The button reads Rechecking… while any check runs and Recheck (4 cr) once this stage has a result, and the recheck worth paying for is the one after you changed something. Pro and above include a monthly allowance; for the balances, see AI credits: what they buy and how they are spent.

None of it is the grade. Ready means the stage covers its criteria well enough to move on; it is not a verdict on the whole design and does not predict your score. The full evaluation still happens when you submit, by either of the two routes in How Challenge Mode works, and it reads your stage answers and your checks along with the Grid. A later check also gets the verdict and summary of earlier ones, so it can build on what they found.

One way through

Next stage moves you on whenever you like, and a check is never required. It is also the only direction: the panel shows just the current stage and has no way back. Once you leave Requirements you cannot rewrite that answer or check it in this attempt. So any check you want comes before you press Next stage.

What guided does not do is hold you to the order. The Grid is open during the typed stages, and the submit buttons are there at every stage, ready as soon as the Grid has a node. Draw first and answer afterwards, and you give up what the order is for: your answers then follow the Grid instead of shaping it.

NoteA guided attempt has no Hint button and no Defend your design section: the stages already do both jobs. After you submit, the Stage timeline lists every stage with its last check, or Not checked in for the ones you skipped; the score beside it is explained in After you submit: the score, the defense and the reference.

The requirement you would have skipped

Start URL Shortener guided. Write the requirements and your scale estimate, check that stage once, and read what comes back before you place a single node. Then notice which requirement you would have skipped if the Grid had come first.

Practice this