Market microstructure for product builders
Order books, matching, and latency concepts explained for people who ship interfaces—not for designing personal strategies.
Tuition (informational): KRW 640,000
Description
Hands-on labs use sanitized UI mocks and replay files so you can see how matching engines behave under load. Discussions stay anchored to reliability, observability, and user-facing copy—not individual participation choices.
What is included
- Replay kit with three pre-recorded session types
- Latency budget worksheet tied to UX copy decisions
- Pair exercises on error states and empty-book messaging
- Reading list on enterprise markets structure papers
- Office hours with a former exchange reliability lead
- Checklist for incident records when feeds stall
- Capstone: narrate a fictional outage timeline
Outcomes
- Describe matching steps suitable for a design critique.
- List telemetry you would expect before declaring an outage.
- Draft user-visible copy that avoids implying guaranteed depth.
FAQ
Will we place live orders?
No. All exercises use fictional data and archived replays supplied by AtlasMint.
Prerequisites?
Comfort with basic HTTP and JSON; no prior trading desk experience expected.
Hardware expectations?
A laptop from the last five years is sufficient; GPU not required.
Notes from learners
-
Finally a microstructure class that spoke to designers—especially the module on empty states when books go quiet.
-
Short, punchy labs; I still open the latency worksheet before sprint planning.