ONLINE GAMES
You model nonlinear systems.
You run statistics.
Maybe you write Python before breakfast.
Then a consulting assessment asks you to calculate market share.
You relax.
That is exactly when the mistake happens.
The online test is rarely trying to discover whether you can do mathematics more advanced than another applicant.
It is asking whether you can use basic quantitative reasoning quickly, selectively, and accurately while several other things compete for your attention.
That is a different skill.
The math is easy... until the question is not really about math
Consider this:
A company's revenue rises from $80 million to $100 million.
Easy.
25% growth.
Now add a chart with five business units, a time limit, two irrelevant columns, and an answer choice expressed in basis points or percentage points.
The arithmetic did not become harder.
The decision around the arithmetic did.
Quantitative strength can hide reading mistakes.
PhDs sometimes move so quickly toward the calculation that they solve a nearby question rather than the one on the screen.
Before touching the numbers:
What am I being asked?
What units should the answer have?
Can I estimate the range first?
Which data actually matter?
For a broader preparation plan across consulting assessments, see How Undergraduates Should Prepare for McKinsey Solve, BCG Casey, and Bain Assessments. The underlying assessment habits apply well beyond undergraduates.
Your calculator is not the bottleneck... this is
Suppose two candidates both calculate correctly.
Candidate A takes 90 seconds because they copy every number, write the full equation, calculate to several decimal places, and verify it twice.
Candidate B estimates first, identifies the relevant inputs, calculates once, checks whether the result is directionally sensible, and moves on.
Both know the math.
Only one has protected time for the next question.
Speed is partly a prioritization skill.
That should sound familiar.
In consulting, the team can analyze almost anything.
The question is what deserves analysis first.
Four PhD habits look impressive... until the timer starts
| PhD habit | Why it works in research | Why it can hurt here |
|---|---|---|
| Maximum precision | Results must withstand scrutiny | Extra decimals may add no value |
| Full derivation | Reproducibility matters | The intermediate steps may consume time |
| Double-check everything | Errors can be costly | Low-risk questions steal time from harder ones |
| Explore interesting patterns | Discovery is valuable | The question may require one narrow answer |
The answer is not to become sloppy.
It is to distinguish accuracy from overprocessing.
That is a consulting skill hiding inside a quantitative test.
And the non-quant questions may be the real surprise
A technical candidate can devote almost all preparation to math because that is the part that looks testable.
Then verbal reasoning, logical reasoning, exhibit interpretation, or situational questions feel less automatic.
The imbalance is avoidable.
You do not need to transform yourself into a verbal reasoning specialist.
You need to find the parts of the assessment where your baseline ability is not already strong.
That is where an hour of preparation may create more improvement than another hour of arithmetic drills.
What actually separates strong test performance?
Not “being quantitative.”
Plenty of applicants are quantitative.
The useful combination is:
- read the exact question
- prioritize the relevant information
- estimate before calculating
- calculate cleanly
- sanity-check once
- move when the answer is sufficient
For more on what can differentiate performance in these screening stages, read Stand Out Consulting Pre-Screening Tests.
Your PhD is still an advantage.
Just not because the test is going to ask you for an eigenvalue.
It is an advantage because you have spent years reasoning with data.
The twist is that consulting wants you to know when less analysis produces the better answer.
That part may require more practice than the math.