Our Testing Methodology

Three ways to measure your cognitive performance

Short Test

25 Questions

Quick assessment with standard Wonderlic scoring

Duration: ~12 minutes

Best for: Quick benchmarking

Scoring: 0-50 scale

Full Test

50 Questions

Complete assessment with comprehensive scoring

Duration: ~25 minutes

Best for: Detailed evaluation

Scoring: 0-50 scale

Adaptive (ACE)

10-20 Questions

Dynamic difficulty with efficiency-based scoring

Duration: Variable

Best for: Elite performance

Scoring: Elite Quotient

The ACE Algorithm

Adaptive Cognitive Efficiency - Version 1

Core Philosophy

This algorithm distinguishes between "Processing Power" (Difficulty) and "Processing Efficiency" (Time/Stability). Unlike standard tests, accuracy is a binary gate, not the score itself. You only accrue points if you are accurate; the amount of points is determined by how efficiently you arrived at the truth.

The Scoring Function (Per Question)

Time-Decayed Exponential Model

Si = Ai × Di1.5 × e-λ(Ti - Ttarget)/Ttarget × max(0.5, 1 - α × Ci)

This formula prevents the "infinity score" glitch while aggressively rewarding speed and stability.

Variable Definitions

VariableNameTypeDefinition
AiAccuracy VectorBinary0 if incorrect/skipped, 1 if correct
DiDifficultyIntegerThe complexity rating of the specific question (1-5)
TiActual TimeFloat (ms)Time elapsed from question render to final submission
TtargetTarget TimeFloat (ms)The "Elite Benchmark" - time a top 1% performer takes at this difficulty
CiChange CountIntegerNumber of times the answer selection was toggled before submission

Tunable Constants

The "Knobs" that control the algorithm

ConstantValueDescription
λ (Lambda)0.7The Decay Factor. A higher value makes the score drop off faster as time passes. λ = 0.7 ensures that meeting Ttarget exactly retains ~50% of max potential points.
α (Alpha)0.05The Uncertainty Penalty. The percentage of score lost per answer toggle (5%).

Difficulty Scaler

Di1.5

Difficulty is raised to the power of 1.5 rather than kept linear. Solving a Difficulty 10 problem is exponentially more valuable than a Difficulty 1 problem. This prevents gaming the system by answering easy questions quickly.

Time Decay

e-λ(Ti-Ttarget)/Ttarget

As Ti increases, the multiplier approaches 0, but never becomes negative. If you answer faster than the target time, the exponent becomes smaller, pushing the multiplier closer to 1 (Maximum Efficiency).

Stability Penalty

max(0.5, 1 - α × Ci)

Penalizes "guessing" or "fidgeting." Each answer change removes 5% of the raw score. The max() function ensures that even 20+ toggles still allows 50% of points if you eventually get it right.

The Adaptive Logic

How the algorithm determines which question is served next

The adaptive engine looks at the Performance Ratio (P) = Ti / Ttarget, not the Score itself.

ConditionLogicNext QuestionInterpretation
Ai = 0IncorrectDifficulty -1User hit failure point. Reduce load.
P < 0.5"Super Speed"Difficulty +2User is bored/overqualified. Aggressive jump.
0.5 ≤ P ≤ 1.0"In Flow"Difficulty +1User is performing optimally. Standard progression.
P > 1.0"Struggling"Difficulty +0User got it right, but too slowly. Do not increase difficulty.

The Skip Protocol

In an efficiency test, skipping is a strategic resource.

Score Impact: Si = 0(No points awarded)
Adaptive Impact: Difficulty +0(No change)
Reasoning: Unlike a wrong answer (which implies inability), a skip impliestime management strategy. We do not lower the difficulty, but we do not award points. This prevents users from tanking their difficulty on purpose to get easier points later.

Final Aggregation: Elite Quotient (EQ)

The Total "Elite Quotient" is not just the sum. It is the sum normalized by the highest difficulty reached.

EQ = Σ(Si) / max(Dachieved)

This normalization ensures that reaching higher difficulties is rewarded, even if you don't answer as many questions. A user who answers 10 questions at Difficulty 8-10 will score higher than someone who answers 50 questions at Difficulty 1-3.

Implementation Requirements

What the system needs to make ACE work

1. Metadata Tables

Every question must contain a validated Ttarget (Target Time) based on empirical data from top performers at each difficulty level.

2. Frontend Listeners

Capture onclick events for Change Count (Ci) and precise timestamps for Actual Time (Ti).

3. Real-time Calculation

The scoring function must be computed server-side immediately after each question submission to determine the next difficulty level.

The ACE Algorithm is designed to measure cognitive efficiency, not just knowledge. It rewards quick, confident, accurate problem-solving at increasing levels of complexity.