Design before you code. Defend every decision.

One real engineering problem. Not a puzzle, not a quiz. The kind of work that decides whether a system holds up in production. Design it, build it, then defend your reasoning.

Loading the live cycle

One path. Three stages.

Design it. Build it. Defend it.

You cannot build what you have not designed, and a diagram alone is not a system. Every entry carries all three stages, and every stage is scored.

Architecture and system design

Map the components, data flow and failure modes first. Share a Figma, C4 or sequence diagram, or a design doc.

Production implementation

Build what you designed. A public GitHub repository with working code, tests and honest error handling.

Engineering defence

Explain your trade-offs, assumptions and decisions. Reviewers check that the code honours the design.

How a cycle runs

A problem drops

We publish one real engineering problem, drawn from the kind of work that actually happens in production teams.

You design, then build

Every entry starts with a system design and ends with working code. A diagram alone or code alone is not a complete entry.

Senior engineers review

Reviewers from real engineering teams read your submission and leave written feedback on your decisions and trade-offs.

Winners get published

Standout submissions are published with your name on them, so your thinking becomes part of your public record.

Anyone can enter. Not everyone will finish.

The Blueprint Challenge is free and open to every LytQuester. Academy alumni carry a verified badge, but the leaderboard is earned, never assigned.

Create your LytQuester account