When I set out to build IQCognify, I thought the hard part would be the questions. It wasn't. Writing pattern-recognition and logic puzzles is fun. The hard part was everything around them: making the test fair, making the score mean something, and making the whole thing run fast in a browser with no signup wall.
The score has to mean something
An IQ score only works because it is normalized. By definition, 100 is the average, and the scale uses a standard deviation of 15. That means a score of 115 is one standard deviation above average, 130 is two. If your scoring is sloppy — if the questions are too easy, or the mix is unbalanced — the numbers stop meaning anything.
So before I wrote a single question, I decided on the structure: a fixed number of items, balanced across pattern recognition, logical reasoning, and spatial puzzles. Every question type gets equal weight. No question is a trick. A test that measures how well you know trivia is not an IQ test.
Timing is part of the test
Working memory and processing speed are part of what these tests measure, so the test is timed — 15 minutes for the full run. That created a real engineering constraint: the timer has to be reliable, survive tab switches gracefully, and never punish someone for a slow connection. I keep all question assets tiny and preloaded so the test itself never stalls.
No signup, no friction
I made a deliberate decision: no account, no email gate, no paywall. You open the site, you take the test, you get your score breakdown. That choice costs me the usual retention tricks, but it is the whole point of the project — quality cognitive assessment that anyone can use.
The result is live at IQCognify — a free IQ test with an instant score breakdown. If you build anything similar, start with the scoring model, not the questions. The questions are the easy part.
Top comments (0)