Written by the people
who build the question banks.
Exam guides that go beyond tips, syllabus notes from our editors, method write-ups grounded in what our data actually shows, and the occasional engineering post about building for a country where the power goes out.
Start with your paper
Every guide is filed under the exam it is written for. Each of these is a page, not a filter.
The archive
Longer than a tip list, shorter than a textbook. Each one comes out of a question we get asked repeatedly.
Exam guides that go
past “revise regularly”.
Anyone can tell you to practise. Our guides start from the format: forty questions and fifty minutes on EPS-TOPIK, two hundred questions and a percentile cut-off on MECEE-BL, a twenty per cent deduction on a Lok Sewa objective paper. What you should do follows from those numbers, and most advice never mentions them.
Claims we can
actually support.
When we write that spacing beats cramming, we say what the research shows and what our own data shows, separately, and we say plainly where our data cannot support a causal claim. Where an article states an exam pattern, it states the pattern as published, and tells you to check the notice for your own sitting.
Notes from building
for these constraints.
Offline-first sync, audio delivery on metered data, multi-script typography, scoring integrity against motivated users. Written for other engineers building in similar conditions, because very little of the available writing assumes them.
Reading about it is the easy part.
Every guide here describes something you can start doing today in the app. Take the diagnostic and pick the one that applies to you.